On Fri, 13 Jul 2018 20:01:13 +0000, Colin Foster <colin.fos...@in-advantage.com> wrote:
>I'm not sure if this is a "bug", a "configuration issue", or simply a network >issue. FWIW: Back in March I set up a svnsync replication of our main SVN repository (which is on Windows Server 16 with SVN 1.9.7) across the Internet. I also got hit by a failure to initialize the synced repository properly, it stopped in the middle at a revision that contained a *lot* of stuff. It seemed to be caused by the slow network speed and a timeout in the svnsync transfer. So I switched approach and created a dump of the source repository, then transferred the dump file (rather big at several GB even in compressed form) over the Internet to the target server, which is running Ubuntu Server 16.04-3 LTS) and SVN 1.9.3. After loading the dump file into the target I could start svnsync with command switches that recognized the target server as already populated from the dump so no data for existing revisions needed to be transfered. I don't remember the exact commands I used but searching the svn users list for my discussion of this dated 2018-03-24 to 29 with subject: "Subversion 1.9.7 server on Windows, advice on setting up svnsync?" might help you too. I now have a working backup system using svnsync. -- Bo Berglund Developer in Sweden
