[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

RE: Backup strategies

From: Karan, Cem \(Civ, ARL/CISD\) <CKaran_at_arl.army.mil>
Date: 2005-01-10 17:26:15 CET

> -----Original Message-----
> From: Ritesh Nadhani [mailto:riteshp@webyog.com]
> Sent: Friday, January 07, 2005 12:05 AM
> To: users@subversion.tigris.org
> Subject: Backup strategies
>
>
> Hello,
>
> We have a small development team of around 4 people. We are
> using Subversion
> on Windows with subversion file system (Berkeley DB was too
> flaky) for the
> last couple of months.
>
> We now plan to have backup system in place. Our repository is
> located in
> f:\svbrepos.
>
> Reading the docs the various methods to backup a repository are:
>
> 1.) svnadmin dump --incremental
> 2.) Do a complete backup of the folder? (it is supposed to be
> unsafe as
> somebody might be checking at that time)
> 3.) use hot-backup.py.
>
> We are little biased towards the second option as we know
> that nobody is
> checking when we are doing a backup. Its only 4 of us and we
> do the backup
> on rewritable cd, 2 times a week.
>
> Since we hadnt had failures - yet, we have not been able to
> actually restore
> the repository from a backup so I was just wondering - just
> do a simple a
> svnrepos copy to a cd will do or we need to do something else?
>
> Lets say - godforbid...if something happens then - we just
> need to copy
> svnrepos at the repository place and everything should be OK?
>
> Just require your insights.

Look in the SVN-book.pdf at chapter 5/Repository Maintenance/Repository
Backup for more info.

I personally do svnadmin dump (no --incremental switch) because you have
to do this to load a repository if you update anyways, and because it
seems to compress a little better (YMMV). The downside is that
reloading a large repository can take time, as can the dump itself (my
repositories all tend to be very small (one/project) so my dumps usually
take less than a minute)

I think I heard/read somewhere that #2 isn't safe to do, but I may be
remembering incorrectly. Does anyone more knowledgeable know if this is
safe? #3 seems to do the same thing as #2, but without having to worry
about corrupting the repository as you're copying. maybe it also
handles the fact that the copy is somewhere other than the original
location as well???

Thanks,
Cem Karan

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Mon Jan 10 17:29:00 2005

This is an archived mail posted to the Subversion Users mailing list.