If you want to do a hot backup, then use svnadmin hotcopy, otherwise,
just backup like normal while nobody is accessing the repository. I
have my nightly backup script shut down apache before taring up the
filesystem.
thomas mauch wrote:
> Hello
>
> I read the notes about backing up a FSFS repository in
>
> http://svn.collab.net/repos/svn/trunk/notes/fsfs
>
> I'm not quite sure however how I have to interpret the last paragraph:
> So, if you are using standard backup tools to make backups of a FSFS
> repository, configure the software to copy the "current" file before
> the numbered revision files, if possible, and configure it not to copy
> the "transactions" directory. If you can't do those things, use
> "svnadmin hotcopy", or be prepared to cope with the very occasional
> need for manual repair of the repository upon restoring it from
> backup.
>
> What is meant with manual repairing a repository? As written in the
> paragraph
> above, this seams to be errors which svnadmin recover does not (yet)
> fix.
> But will svnadmin verify give such a detailled error message that the
> administrator knows what to do? Or is there a description what to do if
> such a backup is damaged? Or is there already development under the way
> to
> improve svnadmin recover as proposed in the notes about FSFS?
>
> Many thanks,
> Thomas
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Fri Mar 3 19:50:55 2006