On Tue, 7 Nov 2006, Gavin Lambert wrote:
> Quoth Abha Shrimal <mailto:abha_shrimal@rediffmail.com>:
> > How can we decide on the frequency of backing up Subversion
> > repository. Whether it should be on hourly basis or daily or weekly
> > or monthly ? Please help me on deciding the the frequency of taking
> > backup of Subversion repository so that even if the subversion server
> > goes down we can restore the same from the backup without much loss
> > of data and everything is safe and sound as before.
>
> That depends entirely on the frequency of committing that you do, and
> how much data you're willing to lose/reconstruct.
>
> If you only commit weekly, then backing up more frequently than that
> isn't going to do you any good. If you commit hourly, but only back up
> weekly, then you have to be prepared to recreate everything you've done
> that week if you have to restore the backup. It's a balancing act,
> which only you can decide on.
I also ran into this recently. Especially after reading about members of
this list having problems reconstructing a repository from a backup that
was slightly old (and dealing with synchronizing working copies). I
decided to take a first pass at backup infrastructure like so:
(1) post-commit hook that svnadmin hotcopy's to a local directory
- hotcopy only works when there's something to work on
(2) hourly 'rsync -av --checksum /backups/svnhotcopy/
remote:/backups/svnhotcopy'
- rsync only copies across the things that changed.
Worst case, your remote backup's only an hour old.
If you have reliable nfs or some such, you might consider doing the
post-commit-hotcopy directly to the remote disk?
Cheers
- Mark
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Wed Nov 8 05:26:20 2006