Hello,
Question in title. My set up is:
On my LAN - Several devices backing up to 1 Kopia repo on a dedicated Kopia backups drive on my NAS. Am considering off-site backup options including setting up a server at a friend’s (accessed via Tailscale). My follow up query is, if the answer is is yes sync-to is the way to do this, then is there a risk of propagating repo corruption to the off-site copy?
Thanks.
Each type of repo sync bears this particular risk. The only way around that would be to have the clients use the remote repo as well, but that is way too much overhead. I have been using repo sync-to S3 for years now and never had an issue with it.
My suggestion would be to keep your focus on your local repo, which is the most important one and you should be good. Kopia’s repo sync-to is very efficient.
Thanks very much. And is to sync-to good for the initial large copy (on LAN initially before taking off-site) or take the server offline and rsync the repo locally in a separate device? (Which was my plan for an initial quicker copy)
As I said, repo sync-to is very efficient. I doubt that you can gain much more using rsync. Also, repo sync-to also performs the necessary conversions, should the target repo not be of the same type as the source one, e.g. source one being filesystem and target one being S3 (as it it in my case).
That seems not to be an issue in your setup, but its just one thing to be aware of.
Good to know. Thank you!