[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: Mark Phippard <markphip_at_gmail.com>
Date: Wed, 24 Jul 2013 15:03:53 -0400

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)
> * Tuesday through Sunday overnights, incremental backups (svnadmin
> dump --incremental, compress the result)

Why not do this from a post-commit hook? That would reduce your
exposure. Also note that there is a new --incremental option on
svnadmin hotcopy. So the hook could even just do that.

> * After completing the Monday night full backup, purge the previous
> week's incrementals.
> * After completing the Monday night full backup, run svnadmin pack

Running pack would probably make the idea of continuing to use hotcopy
not work right.

> Will svnadmin pack have a significant impact on the incremental backup
> I take the following day(s)? I'm guessing not because those are dumps
> and not hotcopies, but want to be sure.

I cannot see why it would impact a dump.

Mark Phippard
Received on 2013-07-24 21:04:25 CEST

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

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.