[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: Les Mikesell <lesmikesell_at_gmail.com>
Date: Wed, 24 Jul 2013 15:21:34 -0500

On Wed, Jul 24, 2013 at 2:22 PM, Thomas Harold <thomas-lists_at_nybeta.com> wrote:
> >
> What we might do once 1.8 server is stable is switch to doing the new
> "incremental" style hotcopy on Mon-Sat evenings and do a full hotcopy on
> Sun. Right now, we address the time it takes to do full hotcopy of all 300+
> repositories by only doing a nightly hotcopy of any repositories that have
> changes within the last N days (usually 7 days, and usually a only a few
> dozen repositories see activity each week). Doing the hotcopy to a
> different set of platters also helps.
> This is based on the assumption that "svnadmin hotcopy" is a preferred
> backup method over "svnadmin dump" for daily backups, because it grabs
> everything out of the repository directory while "svnadmin dump" misses
> things like scripts.

Is that better than using svnsync from a remote server plus some
normal file backup approach for the conf/hooks directories?

  Les Mikesell
Received on 2013-07-24 22:22:07 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.