Seems your goal is to recreate one of the storages ( M-1 preferably - since it isn’t copy-compatible with the others) but to ‘seed’ that storage from the old one, locally, in order to reduce bandwidth… 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). 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. 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. Now the problem is that M-0 is dead/down and no longer accessible. Then only occasionally run the following from M-0ĭuplicacy copy -id=some-id -r= -from=storage-0 -to=storage-2.From the primary machine where the data is, often run:.Now at M-0 i had also added an online storage/back-end, say storage-2, as a copy of storage-0: duplicacy init -e storage-name=storage-0 some-id /path/to/storage-0ĭuplicacy add -e copy=storage-0 storage-2 some-id storage-0 and 1 basically resided on different (local) machines - M-0 and M-1, if it matters. I used to backup my machine to two back ends - say storage-0 and storage-1.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |