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

Re: Best practices: BACKUP?

From: Andy Levy <andy.levy_at_gmail.com>
Date: 2006-06-19 14:59:22 CEST

On 6/19/06, Norbert Unterberg <nunterberg@gmail.com> wrote:
> 2006/6/9, Mayur Jobanputra (V) <MJobanputra@intrawest.com>:
> > Must have: nightly backups of the complete db to a shared folder on the
> > network.
> >
> > Nice to have: the backups are zipped before they are sent over the network,
> > and instructions for disaster recovery situations
> Don't forget about the RESTORE problem, as far as I know there is no
> documented procedure to restore the user's working copies.
> The problem here is when you backup repository revision 100, then
> users commit revisions 101 and 102, and then the server crashes. The
> backup is at revision 100, the user's working copies believe the
> server is at revision 102. How do you sync the user's working copies
> without losing there local modifications?

Some people do an incremental backup in their post-commit hook, so
that they have a backup of each revision individually.

If you have a lot of commits between full backups, this could make
restoring pretty tedious.

To unsubscribe, e-mail: users-unsubscribe@tortoisesvn.tigris.org
For additional commands, e-mail: users-help@tortoisesvn.tigris.org
Received on Mon Jun 19 15:01:33 2006

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

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