Proniewski Patrick wrote:
> On 13 juin 05, at 13:59, Ulrich Eckhardt wrote:
> > 1. Use the hotcopy script to make a duplicate of your repository.
> > 2. 'svnadmin dump' the copy and backup that data - it's the
> > repository's
> > content.
>
> I do "1" on a weekly basis, and "2" on a daily basis.
Wait a second: you make a local copy of your data every week and backup that
local copy every day???
No, the idea is to only access the real repository via the hotcopy script.
This hotcopy script is much faster than 'svnadmin dump' and also copies the
files in the right order so you don't have partial commits - something that
could happen with a simple filecopy. Then, you get a repository on which you
perform the real dump operation whos results you back up.
Optionally, you can leave the hotcopy around, so you can quickly restore a
state that is at least recent while not current, just in case the original
gets hosed by some catastrophic failure. It is faster than from the dumps
because the configuration is also copied and because you don't have to do the
whole 'svnadmin load'.
> I'm keeping a month of backups on a remote server. I'm paranoid :)
Paranoid? I'd just call this unresponsible, unless you make backups on
read-only media and store them somewhere off-site. Just imagine some virus
that destroys both the repository and the data on the backup server... I
wouldn't want to be the admin having to tell some %BOSS% that one month of
work of a whole team was hosed due to some malware.
Uli
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Mon Jun 13 15:39:33 2005