Re: hotcopy --incremental auto-upgrade Re: Backup strategy sanity check

2013-08-12 Thread Stefan Sperling
On Mon, Aug 12, 2013 at 08:36:42AM -0500, Les Mikesell wrote: > On Sat, Aug 10, 2013 at 5:25 PM, Daniel Shahaf wrote: > > > >> It would have been nice if --incremental would automatically upgrade the > >> target repository (and fallback to a full backup) if the versions > >> mismatch. > > > > Hmm.

AW: hotcopy --incremental auto-upgrade Re: Backup strategy sanity check

2013-08-12 Thread Markus Schaber
Hi, Von: Les Mikesell [mailto:lesmikes...@gmail.com] > > On Sat, Aug 10, 2013 at 5:25 PM, Daniel Shahaf wrote: > > > >> It would have been nice if --incremental would automatically upgrade > >> the target repository (and fallback to a full backup) if the versions > >> mismatch. > > > > Hmm. Int

Re: hotcopy --incremental auto-upgrade Re: Backup strategy sanity check

2013-08-12 Thread Les Mikesell
On Sat, Aug 10, 2013 at 5:25 PM, Daniel Shahaf wrote: > >> It would have been nice if --incremental would automatically upgrade the >> target repository (and fallback to a full backup) if the versions >> mismatch. > > Hmm. Interesting idea, but replacing failure modes with automagical > behaviour

Re: hotcopy --incremental auto-upgrade Re: Backup strategy sanity check

2013-08-11 Thread Thomas Harold
On 8/10/2013 6:28 PM, Daniel Shahaf wrote: Daniel Shahaf wrote on Sun, Aug 11, 2013 at 01:25:24 +0300: Thomas Harold wrote on Sat, Aug 10, 2013 at 10:53:43 -0400: With the 'svnadmin hotcopy --incremental' backups, we have to do extra checking in the script (comparing reponame/db/format versions

Re: hotcopy --incremental auto-upgrade Re: Backup strategy sanity check

2013-08-10 Thread Daniel Shahaf
Daniel Shahaf wrote on Sun, Aug 11, 2013 at 01:25:24 +0300: > Thomas Harold wrote on Sat, Aug 10, 2013 at 10:53:43 -0400: > > With the 'svnadmin hotcopy --incremental' backups, we have to do extra > > checking in the script (comparing reponame/db/format versions) in order > > to make sure that

hotcopy --incremental auto-upgrade Re: Backup strategy sanity check

2013-08-10 Thread Daniel Shahaf
Thomas Harold wrote on Sat, Aug 10, 2013 at 10:53:43 -0400: > With the 'svnadmin hotcopy --incremental' backups, we have to do extra > checking in the script (comparing reponame/db/format versions) in order > to make sure that the hotcopy runs correctly. > If you have to do that, please do it

Re: Backup strategy sanity check

2013-08-10 Thread Thomas Harold
On 7/25/2013 7:30 AM, Stefan Sperling wrote: On Wed, Jul 24, 2013 at 03:22:11PM -0400, Thomas Harold 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. In Subversion 1.8, a full hotcopy is i

Re: Backup strategy sanity check

2013-07-25 Thread Andy Levy
On Thu, Jul 25, 2013 at 7:27 AM, Stefan Sperling wrote: > 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 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 th

Re: Backup strategy sanity check

2013-07-25 Thread Stefan Sperling
On Wed, Jul 24, 2013 at 03:22:11PM -0400, Thomas Harold 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. In Subversion 1.8, a full hotcopy is implemented as an incremental hotcopy into a

Re: Backup strategy sanity check

2013-07-25 Thread Stefan Sperling
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 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 (svnadm

Re: Backup strategy sanity check

2013-07-25 Thread Thomas Harold
On 7/24/2013 4:21 PM, Les Mikesell wrote: Is that better than using svnsync from a remote server plus some normal file backup approach for the conf/hooks directories? Not sure, I have not tried out svnsync. We also don't use post-commit hooks (yet). I am under the impression that hotcopy do

Re: Backup strategy sanity check

2013-07-24 Thread Nico Kadel-Garcia
On Wed, Jul 24, 2013 at 2:59 PM, Andy Levy 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 n

Re: Backup strategy sanity check

2013-07-24 Thread Les Mikesell
On Wed, Jul 24, 2013 at 2:22 PM, Thomas Harold 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

Re: Backup strategy sanity check

2013-07-24 Thread Thomas Harold
On 7/24/2013 2:59 PM, Andy Levy 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, increme

Re: Backup strategy sanity check

2013-07-24 Thread Mark Phippard
On Wed, Jul 24, 2013 at 2:59 PM, Andy Levy 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 Sunda