----- Original Message -----
From: "Ulrich Eckhardt" <eckhardt@satorlaser.com>
To: <users@subversion.tigris.org>
Sent: Wednesday, July 05, 2006 7:45 AM
Subject: Re: backing up fsfs repo
> On Wednesday 05 July 2006 12:16, spock@dwinner.net wrote:
>> Can anybody tell me what the implications of just doing a normal backup
>> (unix dump or tar of flat file structure) of an fsfs repo might be? Is it
>> safe, or should I still be using "svnadmin dump"?
>
> IMHO, yes, because it is The Documented Way(tm) to make backups.
It's a slight bit risky, because if files are being written while being
tarballed, you may wind up with an incomplete change recorded on the last
last commit operation. FSFS seems much better about this than BDB, though.
>> I did some testing, and it seemed to me that I could take a repo, rename
>> it,
>> move it, copy it, make a tarball out of it, delete it, then restore it
>> from
>> tarball, and it seemed safe and still functional in every case. But I
>> don't
>> want any nasty surprises, so if anybody knows of a reason this is not a
>> good
>> idea, please let me know.
>
> The FSFS backend depends on portable ways to access files, so
> sophisticated
> stuff is probably not needed (and thus can't fail).
I'd personally suggest using hot-packup-py to make a clean backup, and
backing up that. In case anyone uses the system while you're in the midst of
doing the backup, it's handy to have a good clean snapshot like that. You
might not have the last commit recorded, but it seems much safer.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Wed Jul 5 15:26:59 2006