Re: backup -- only backing in certain scenarios.

The log is too verbose. Use -debug stasher (this will log only the backup
function) and we'll increase verbosity afterwards if needed.

I see in the log this line: "[server: stasher] Backing up
/export/transfer/vincentl / testfile-in-corp2.txt to testfile-in-corp2.txt
in /export/archive"

Is the file actually not backed up or is the backup location incorrect?


On Wed, 11 Oct 2023 at 13:51, V Lo <[email protected]> wrote:

> Thanks for suggesting to log verbosely. My goal is to have 2 copies of my
> secret directory on two servers, where I might add/delete files
> independently. And in case I accidentally delete a file, it will get backed
> up by unison when I finds a discrepancy.
> In the verbose log, I can see that the file are being 'backed-up' but not
> really.
> Is there anyone knowledgeable to take a look at my verbose log?
> testfile-in-corp2.txt NOT BACKED UP - file was removed from client
> testfile-in-corp3.txt BACKED UP - file was removed from server
> Any help would be greatly appreciated. Thanks!
>
>
>
> On Wednesday, October 11, 2023 at 2:35:23 AM UTC-4 Tõivo Leedjärv wrote:
>
>> On Tue, 10 Oct 2023 at 20:54, V Lo <[email protected]> wrote:
>> >
>> > I run:
>> > unison /my/secret/drive ssh://client//my/secret/drive
>>
>> You can add -debug stasher to this command line to get some debugging
>> output.
>>
>> > Place a file in client, unison sync file to server. Remove the file
>> from server. On next unison run, file is backed up
>> > Place a file in client, unison sync file to server. Remove the file
>> from client. On next unison run, file is NOT backed up
>>
>> Are you checking if the backup exists on the server? A file removed on
>> the client should be backed up on the server.
>>
>

-- 
To unsubscribe from this group and stop receiving emails from it, send an email to [email protected].