duplicity-talk
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Duplicity-talk] Desynchronized multi-backend


From: Nathan MALO
Subject: [Duplicity-talk] Desynchronized multi-backend
Date: Tue, 23 Jan 2024 18:30:03 +0100

Hi,

I have a theoretical question about duplicity's multi-backend feature.
I am currently using the multi-backend that consists of three targets :
- 1 local folder on the server located on a separated physical drive
- 2 remote SFTP targets.

Yesterday, my remote SFTP targets went offline, so I tweeked the json to remove the SFTP targets and leave only the local folder.

So now my local folder has a newer backup chain that my remote SFTP targets do not have.

My remote SFTP targets are back online so usually I resync manually the newer backup chain to each SFTP destination to get them back synchronized.

But what would duplicity tell me/do I if did not re-synchronize the 3 targets of my multi backend ?

If I ran a collection-status against the multi backend what would it tell me ?

If I ran a collection-status against each target of the multi-backend separately, what would duplicity tell me ?

If I performed a backup, what would duplicity tell me/do ?

The questions are purely theoretical but I've wondered for quite some time.

At last, thank you for this great software. I've been using it to backup 700+GB of data each month, and it never failed me !

Best regards, 

Nate

reply via email to

[Prev in Thread] Current Thread [Next in Thread]