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

Backup strategy sanity check

From: Andy Levy <andy.levy_at_gmail.com>
Date: Wed, 24 Jul 2013 14:59:24 -0400

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)
* After completing the Monday night full backup, purge the previous
week's incrementals.
* After completing the Monday night full backup, run svnadmin pack
* Keep the last 6 full backups on local disk (these will be kept
written to the corporate backup system, so we can go back further if

I'm saving the packing for after the Monday full backup so that in
case something goes wrong with it, I have the full backup right there
that I can restore from.

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 recognize that this isn't 100% air-tight, in that we're exposed
during the workday, but based on the size of our repositories & the
frequency of commits, standing up another server to act as an svnsync
mirror or adding the complexity of making a backup of each commit when
it happens is more than I can get away with right now.

Aside from that, is this a sound strategy? Have I overlooked anything?
Received on 2013-07-24 21:00:45 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.