On Thu, 2015-10-01 at 09:29 -0400, Nico Kadel-Garcia wrote: > If you're doing an rsync or scp to a remote system and doing the > svndump there, you're running the risk of transferring content in the > middle of an atomic operation and thus confusing the system. > > > svnrdump dump -r 51686:77787 > > https://myhost/subversion/repository/PROJECT/trunk/amodule | gzip > > > amodule.dump.gz
> Does anyone actually use "svnrdump"? I've not explored it myself, but > don't see where it's a big advantage over a remote "ssh hostname > svnadmin dump" command, which avoids the kind of confusion I just > described. I'd start there, to avoid certain levels of uncertainty and > incompatibility with an out of date and no longer supported Subversion > release with a more modern tool that may not have been thoroughly > tested with it. What is interesting with svnrdump is that it is efficient to generate a "partial" dump, in term of revision range and selected path ! What "svnadmin dump" is not able to do without scanning a large part of the full repository (10 GiB)... Indeed you were right. As there is no merge tool for format 3 dumps, I decided to rsync over ssh the repository and run svnadmin dump on my workstation to avoid disturbing users. Thank you for that tip -- Yves Martin
