Saulius Grazulis wrote:
> On Monday 11 April 2005 16:34, Bax, Arjen wrote:
>
>> If you use an fsfs repository, you can make rsync operate directly on
>> the repository directory and make incremental backups. No need for
>> svnadmin dump.
>
> What about locking? What if someone does checkin at the very moment when
> rsync backup is running? Wouldn't that lead to an somewhat incorrect
> repository backup -- stale locks, inconsistent state or whatever?
>
> (Admittedly, I also run rsync to backup my FSFS repositories, and I am
> pretty sure nobody check in late at night when rsync is but I am just
> curious if there can be any problems in principle).
>
> Regards,
>
As long as the 'current' file is synced before revs directory, there's no
problem; a half-completed commit might get copied, but wouldn't be
mentioned.
In practice, half-completed commits are under txns anyway, and are put into
revs with a single mv, so you either get them or not regardless.
if one wants to get really fancy, if you
* read 'current'
* sync revs
* write the value of 'current' you originally read
and than the target mirror is also consistent the entire time, since having
revisions showing up under revs that aren't referenced yet is harmless.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Thu Apr 14 04:57:32 2005