Re: Consistent live fsfs backups without copy

Thanks for all the suggestions. I think what I'm going to end up
doing is this:

On May 1, 2006, at 4:14 PM, Scott Lamb wrote:
> I could easily do this on backup:
>
> 1. pre script - copy current file to a location where it won't
> change, erroring out if it already exists

and also error out if "fs-type" doesn't hold "fsfs" or "format"
doesn't hold "1" or "2".

> 2. copy everything
> 3. post script - remove my copied current file

...and error out if any of the previous revision or revprop files
have timestamps newer than my copied current file. I don't think
adding a new revision alters any of the old ones...but if I'm wrong,
this extra step will mean that I find out about my incorrect
assumption right away rather than when I need to restore from a
backup that's been silently corrupted.

Looks like old revprops files can be replaced if we do "svn propset --
revprop", but we just won't do that during a backup. (Or if we do,
we'll try again after getting the 'backup failed' email.)

> and on restore,
>
> - throw away revisions and revprops newer than in my copied current
> file
> - throw away all transactions
> - copy the current file back to its proper location
>
> is this good enough?

-- 
Scott Lamb <http://www.slamb.org/>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org