[ If possible, please use bottom-posting or inline replying on this list, and preferably use plain-text. More below. ]
Op 20 sep. 2017 16:18 schreef "Saleh, Mai" <mai_sa...@mentor.com>: Also mirror, does not get hooks, we have to reconfigure it right. Dump+load or svnsync into the new FSFS format is not necessary, but like others have said, it might give you new features and the most optimal format available (this might give you space savings and very likely improved performance). This FAQ may be useful: http://subversion.apache.org/faq.html#dumpload As noted there: - svnsync is better at normalizing some issues with properties (among others the EOL problem in comments that Nico hinted at). - Apart from hooks and conf you also have to copy over locks (these are not svnsynced nor included in dump+load). If you don't want to load into a new format back-end (because it takes too long and you're not interested in the improvements): - I think you can safely use rsync if your repository is offline / read-only, or wrapped in the "svnadmin freeze" command (see http://svnbook.red-bean.com/vi/1.8/svn.ref.svnadmin.c.freeze.html). - You might also want to look into "svnadmin hotcopy". Also interesting to know: the next version of Subversion (1.10, currently in alpha, not yet ready for production use!) will most likely again include a new version of the FSFS format (with LZ4 compression (a bit larger, but usually a lot faster) so might be again a good candidate to plan a dump+load or svnsync, if you want it). And it will add a couple of improvements to "svnadmin load": - New option --no-flush-to-disk to make it a lot faster (by not flushing after every revision). - New option --normalize-props to perform the same EOL normalization on properties as svnsync does. (Disclaimer: since 1.10 is not final yet, things may still change ... nothing is set in stone yet) Final release of 1.10 is still some months away though. -- Johan
