Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    text
    copied!<p>The theoretical way of doing a backup safely is to use the <code>svnadmin hotcopy</code> command (<a href="http://svnbook.red-bean.com/nightly/en/svn.ref.svnadmin.c.hotcopy.html" rel="nofollow noreferrer">more details here</a>). It basically does a copy of one repository (not a <em>dump</em>, a <em>copy</em>), taking care to block all the operations during that time.</p> <p>This operation is quite fast, so I shouldn't think any client would have an error, they may experience some delay though (depending on the server load and so on).</p> <p>You can find an example of script on the <a href="http://svn.apache.org/repos/asf/subversion/trunk/tools/backup/hot-backup.py.in" rel="nofollow noreferrer">Apache subversion project website</a>.</p> <p>If you do a dump, besides the huge time it takes, you won't be sure it will done in an atomic way. Dumps are useful to </p> <ul> <li>make sure you can migrate from one version to the next - think long-term backups. For example if your server is upgraded from version 1.4 to 1.5, or to 1.6, it's interesting to make a dump then a load of your repositories to take full advantage of the improvements. In some more drastic upgrades it's a necessity because the repository format changes too much.</li> <li>filter files out, or merge repositories, those are more complex operations, out of topic here.</li> </ul> <p>Before opting for a dump, should you prefer that anyway, I encourage you to do the operation manually before, to make sure it is not too long. Make sure also to compress those files, which are much bigger than a repository (hotcopy) - the latter is very well compressed.</p>
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload