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

Re: Hot backup changes

From: Blair Zajac <blair_at_orcaware.com>
Date: 2002-08-21 07:11:42 CEST

cmpilato@collab.net wrote:
>
> Andy McCarty <mccarw@lom.med.va.gov> writes:
>
> > * cmpilato@collab.net <cmpilato@collab.net> [2002-08-20 23:01:19 -0500]:
> >
> > >
> > > So, the rule is:
> > >
> > > if (backup file exists)
> > > svnadmin dump --incremental last-rev > backup_file
> > > else
> > > svnadmin dump --incremental 0 last-rev > backup_file
> > >
> > > ?
> > >
> >
> > Any log changes will have to be done on the day of the
> > commit or it will not be recorded in the dumps.
> >
> > Correct?
>
> Wow, very correct. And might I say, insightful!
>
> > This may or may not be a deterrent.
>
> Indeed.

Maybe revision 2 of the dump file format dumps all the log
messages for the entire repository??? svnadmin load would
only update log messages for those that have changed. This
would take care of this issue.

Not that clean, but it would work.

Best,
Blair

-- 
Blair Zajac <blair@orcaware.com>
Web and OS performance plots - http://www.orcaware.com/orca/
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Wed Aug 21 07:12:26 2002

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

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