I used to backup my machine to two back ends - say
storage-1. All encrypted.
storage-0 and 1 basically resided on different (local) machines -
M-1, if it matters. Now at
M-0 i had also added an online storage/back-end, say
storage-2, as a copy of
duplicacy init -e storage-name=storage-0 some-id /path/to/storage-0 duplicacy add -e copy=storage-0 storage-2 some-id <online://bucket>
So my process used to be:
- From the primary machine where the data is, often run:
duplicacy backup -storage storage-0 duplicacy backup -storage storage-1
- Then only occasionally run the following from
duplicacy copy -id=some-id -r=<latest> -from=storage-0 -to=storage-2
Now the problem is that
M-0 is dead/down and no longer accessible.
storage-1 is ofc fine. So I turned to
M-1 and tried to set up similar copy to existing
storage-2 but it says that the
Two storages are not compatible for the copy operation.
I ofc don’t want to delete
storage-2 again and make a new one that is compatible with
storage-1 as i’ll have to now upload huge amount of data and then if
storage-1 is dead later, I’ll be in the same predicament.
What is the best way forward given this scenario ? Even if I cannot somehow make
storage-1 and 2 copy compatible, is there a normal backup from
storage-1 to 2 that i can run which will do the expected incremental backup (so only the new/affected chunks since the last revision in storage-2) ? Can you please specify the command just for sake of clarity ? (I don’t want to mess anything up).