Not sure if this helps you, I have a post-commit hook script that backs
up the repository, so I know I always have the most up-to-date backup.
Here's a overly simplified version writtien in shell:
<post-commit>
#!/bin/sh
svnadmin dump "$1" > /home/backups/backup.svndump &
</post-commit>
I discovered that my commit was taking a while because of the dump, so I
put the process in the background (with the & symbol), so there's no
delay when users commit new revisions.
On Wed, 2006-02-08 at 13:41 -0500, Phillip Susi wrote:
> Jon Scott Stevens wrote:
> > hi there,
> >
> > i had a hard drive failure on my server and my backups were about a
> > month old. long story, but normally i'm much better (ie: daily) about
> > backups. i do have my svn project checked out on my laptop and that is
> > the latest version of the project so that is good as i haven't lost any
> > data. i also have all the old commitmessage emails so i can see what
> > changed over the month of lost data.
> >
> > now, i would like to now bring the server back up to date with what is
> > on my laptop. since my laptop thinks the server revision doesn't exist,
> > i don't know of any other idea than doing a fresh checkout of the older
> > revision on the server, copying the files on my laptop over the fresh
> > checkout and then committing back.
> >
>
> That's basically what you have to do. In the future you might want to
> set up a nightly cron job to backup the repo to another disk/machine.
>
> > advice on the best practices in this situation is appreciated.
> >
> > thanks,
> >
> > jon
> >
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
> For additional commands, e-mail: users-help@subversion.tigris.org
>
--
Josh Kuo <josh.kuo@prioritynetworks.net>
Received on Wed Feb 8 20:15:39 2006