On Thu, 22 Aug 2019 09:38:02 -0400, Mark Phippard <markp...@gmail.com> wrote:
>My first choice option would be to setup a repository on a second server >and use svnsync from a post-commit hook script to sync the change. After >that, I would use svnadmin hotcopy with the new --incremental option (as of >1.8?). Dump is not a great choice for backups. > >The main advantage of svnsync is you can push the change via HTTP or SVN to >a different system where as hotcopy needs FS access so the only way to get >the repos on to a second server is if you can mount the FS via NFS or >something. That is also what I did! Our main server runs on a Windows Server on the corporate LAN. The backup server is a Linux box in a different location altogether. Both locations have fiber access to the Internet. The backup server is set up with https access (thanks to LetsEncrypt and Certbot) through the router. I have synced the servers after first loading the backup server from dump files so as not to have to use Internet bandwidth for the original data transfer. On the Windows man server I have set up a nightly task that uses svnsync to synchronize the two servers. It has been running just fine for 18 months without fail. Recommended solution. Bo Berglund
