I have a backup system set up for our VisualSVN server running on Windows Server 2016. It consists of a batch file scheduled to run nightly on the SVN server.
The batch uses a series of commands, one for each of the backed up repositories and has been in place from 2018. Now when checking the state of the backup I have found that one single repository is not up to date on the backup server, so I accesssed the Windows server to see what was going on. Turns out that when I run the backup command manually on the server for this repository I get the following output: E:\>"C:\Program Files\VisualSVN Server\bin\svnsync.exe" synchronize --sync-username syncuser https://backupservername/svn/pcb https://agiengineering/svn/pcb Failed to get lock on destination repos, currently held by 'AGIENGINEERING:2e8676b6-0783-584c-8276-757df1507352' ...... 8 repeats of the same ..... Failed to get lock on destination repos, currently held by 'AGIENGINEERING:2e8676b6-0783-584c-8276-757df1507352' svnsync: E000022: Couldn't get lock on destination repos after 10 attempts Notice: All other repos sync as intended. Only pcb acts up. What can I do to remedy this? It seems to have stopped working about 3 weeks ago for this single repository. Note that the backup server, which is an Ubuntu 20.04.5 LTS Server box on another location, is connected using the Internet when doing the backups. This Ubuntu server has been rebooted a few times since the last working backup was synced. What can cause a failure to obtain a lock on that remote server for this specific repo? It is only used as a backup for the main SVN server. The main Windows server is running svn version 1.9.7 (r1800392) and the Linux backup server is running svn version 1.13.0 (r1867053) Is therte some log on the backup server I can access to see what if anything is happening there? -- Bo Berglund Developer in Sweden
