On Feb 8, 2006, at 3:16 PM, Josh Kuo wrote:
>> I'm thinking a quicker process would be to have the post-commit hook
>> only trigger an incremental backup, to a file whose name is based on
>> the revision number, stored in a directory "incremental". Then do a
>> nightly full dump, when the server is less busy, by getting the HEAD
>> revision (svnlook youngest); dumping everything up to that revision
>> into a file whose name is based on that revision, stored in a
>> directory "full"; deleting the now-superfluous incrementals up to
>> that revision; and deleting the older full dumps, possibly leaving
>> the last couple as additional safeguards.
> This sounds good, mine was a quick hack... and like I said, the
> repository I am using it in doesn't have that much commit traffic,
> so no
> one notices the performance issue.
> Does subversion already come with such backup script? Maybe we should
> submit these scripts back, I think some others may find it helpful...
> where would I submit it to?
Subversion comes with three. svnadmin hotcopy, hot-backup.py and svn-
hot-backup.py is a Python wrapper around 'svnadmin hotcopy' that
removes older backups, keeping at most N backups around.
My preferred one is svn-fast-backup. This one only works if you use
FSFS on Unix based system that supports hard-links. It's faster and
less disk intensive than 'svnadmin hotcopy' and hot-backup.py.
The backups are exact duplicates of the entire repository structure
(the backup is not a dump file). So if you need to recover, you
make a copy of the backup and move it into place.
Any files in the latest backup that do not differ from the last
backup are hard-links, so it's cheap on disk space and fast, since
there's no copying being done.
Blair Zajac, Ph.D.
CTO, OrcaWare Technologies
Subversion training, consulting and support
To unsubscribe, e-mail: email@example.com
For additional commands, e-mail: firstname.lastname@example.org
Received on Sun Feb 12 03:43:35 2006