Backup best practices?

[Grant Rettke <gr...@acm.org>]

Hi,

We are running svn 1.3.1 on Windows XP Pro. We keep the server running 
all the time. For backup, we do a hotcopy and then dump that hotcopy to 
a file, and the compress the dump file. Based on what we have read in 
the documentation, this seems to be the safest approach.

Is this the best way to do it?

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org

Re[2]: Backup best practices?

["Fernando P. Nájera Cano" <su...@fernandonajera.com>]

Sorry, I press Reply and sent this to Ryan Schmidt only instead the
list.

------------------

Hi,

I'm quite interested in this thread. I've had some troubles recently
<http://svn.haxx.se/users/archive-2006-04/1014.shtml> and nobody has
answered yet, so now I feel my only hope is in the backups (and hope
to replace Windows with *nix as Subversion OS...)

RS> I'd recommend using svnadmin dump in a post-commit hook, to dump each
RS> revision as it happens, possibly in addition to the hotcopy you're  
RS> already doing. See this recent mail:

RS> http://svn.haxx.se/users/archive-2006-05/0509.shtml

RS> "The net result is that now I have a post-commit hook which dumps and
RS> backups a revision as soon as it is committed. I believe that any  
RS> other backup strategy for a SVN server (say, hotcopy once a day) is  
RS> basically useless."

I understand the email referenced above, and I'm now worried about my
hourly hotcopy, nigthly (put the hotcopied repo offline and zip it up)
and weekly (put the main repo offline and zip it up). Just a question
here, where do you dump each revision to? Email? Another dir in the
server?

Best regards,

Fernando Nájera

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org

Re: Backup best practices?

[Ryan Schmidt <su...@ryandesign.com>]

On May 17, 2006, at 16:46, Grant Rettke wrote:

> We are running svn 1.3.1 on Windows XP Pro. We keep the server  
> running all the time. For backup, we do a hotcopy and then dump  
> that hotcopy to a file, and the compress the dump file. Based on  
> what we have read in the documentation, this seems to be the safest  
> approach.
>
> Is this the best way to do it?

I'd recommend using svnadmin dump in a post-commit hook, to dump each  
revision as it happens, possibly in addition to the hotcopy you're  
already doing. See this recent mail:

http://svn.haxx.se/users/archive-2006-05/0509.shtml

"The net result is that now I have a post-commit hook which dumps and  
backups a revision as soon as it is committed. I believe that any  
other backup strategy for a SVN server (say, hotcopy once a day) is  
basically useless."



---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org