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

Re: Backup strategy sanity check

From: Stefan Sperling <stsp_at_elego.de>
Date: Thu, 25 Jul 2013 13:27:30 +0200

On Wed, Jul 24, 2013 at 11:08:28PM -0400, Nico Kadel-Garcia wrote:
> On Wed, Jul 24, 2013 at 2:59 PM, Andy Levy <andy.levy_at_gmail.com> wrote:
> > I'm planning my upgrade to SVN 1.8 & to go along with it, setting up a
> > new backup process. Here's what I'm thinking:
> >
> > * Monday overnight, take a full backup (svnadmin hotcopy, then
> > compress the result for storage)
>
> Insufficient. You also need the Apache or svnserve or SSH configs, and
> the varoius commit scripts from the base repository, along with their
> ownership and permissions. Tarballs are good, "rsync -avH" is even
> better for imaging such loactions in a decodable format.

Well, actually, a hotcopy includes hook scripts and config stored
inside the repository directory. A dump file does not. I suppose
you're confusing the two?

Andy, if you're upgrading to 1.8, perhaps the new incremental
hotcopy feature can help you:
http://subversion.apache.org/docs/release-notes/1.8.html#incremental-hotcopy

You might also want to consider making use of 'svnadmin freeze':
http://subversion.apache.org/docs/release-notes/1.8.html#svnadmin-freeze
Received on 2013-07-25 13:28:08 CEST

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