Daniel Berlin wrote:
>In FSFS, older revisions are immutable.
>This means that the data in them won't ever be written to. The only
>thing you *really* need to ensure is that the db/current file gets
>copied first, so that it doesn't reference a revision file that appeared
>since you started your copy.
>Other than that, something like rsync should make this *very* fast.
>
>
>
>
When I started looking at Subversion for our company, the mandatory
requirements were reliability and availability. We have development
offices in several countries and require 24-hour access. I waited until
FSFS was available and stable and have since begun pilot testing.
FSFS with rsync is indeed the way to go. We use rsync to backup our
repositories being careful to backup db/current first. The backup cron
job is amazingly fast - maybe a few seconds every hour, so we get highly
reliable backups with essentially no impact on the server. We copy to a
standby server (to be located in a disaster recovery center), so should
the main server fail, or we lose network connectivity, we can be up and
running again in under an hour.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Sat Jul 2 17:20:10 2005