From 018b6df18ae16ea389173c438e4f07efd78cba92 Mon Sep 17 00:00:00 2001 From: dodger Date: Sat, 28 Oct 2023 09:23:54 +0200 Subject: [PATCH] updates+++++++++++++++ --- intervention.md | 9 ++++++++- 1 file changed, 8 insertions(+), 1 deletion(-) diff --git a/intervention.md b/intervention.md index 541997a..303068d 100644 --- a/intervention.md +++ b/intervention.md @@ -69,7 +69,7 @@ I had to restart the _primary_ server to apply that config, sorrry for that. ## To be done -### Options +### Option #1 for archiving (recommended) As I say, this is far to be a good solution. In my opinion, the best option will be the one I already mention, map one network drive from one server to the other into `Z:\` and use: @@ -77,6 +77,13 @@ In my opinion, the best option will be the one I already mention, map one networ archive_command = 'copy "%p" "Z:\\archivelog\\%f"' ``` +We should investigate permissions for this solution. + +### Option #2 for archiving + +In the case we can't achieve the #1 solution, I suggest to keep the current configuration and perform the synchronization via _scheduled_ tasks. +So, for example, we will launch `rsync R:\postgresql\local\archivelog 10.6.x.3\R:\postgresql\archivelog` (the syntax will be wrong, I had never used `rsync` on windows...). +To copy archivelogs from one server to the opposite.