[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: repository on client is newer than on server as a result of server hd failure

From: Josh Kuo <josh.kuo_at_prioritynetworks.net>
Date: 2006-02-09 00:16:45 CET

> 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?

-- 
Josh Kuo <josh.kuo@prioritynetworks.net>

Received on Thu Feb 9 00:18:38 2006

This is an archived mail posted to the Subversion Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.