I am wondering if there is any danger with propagating corruption when “syncing” multiple storages via copy vs running separate backups to each storage.
Ie. if configs or chunks are corrupted in the source can the corruption propagate to the copy destination and destroy the destination backup integrity?
Corrupted chunks won’t be copied to the destination, because after a chunk is downloaded from the source, its hash will be checked before uploading to the destination. If the chunks is corrupted then an error will be thrown first.
This topic was automatically closed 10 days after the last reply. New replies are no longer allowed.