Féliciano Matias <feliciano.matias@free.fr> writes:
> Le ven 12/07/2002 à 14:48, Ben Collins-Sussman a écrit :
> > Féliciano Matias <feliciano.matias@free.fr> writes:
> > ----
> >
>
> >
> > > Le ven 12/07/2002 à 07:41, Féliciano Matias a écrit :
> > > > First, excuse my poor english.
> > > >
> > > > ** Can i do a hot dump (with svnadmin dump).
> > > >
> > >
> > > I see a python script (tool/backup/hot-backup.py) that do the jobs by
> > > doing some copy file. I prefer a real dump (svnadmin) that is more
> > > portable/secure.
> >
> > As I said, 'svnadmin dump' is not for backups. It has nothing to do
> > with the BSD 'dump' command that you would spool to a tape device.
> > It's for data migration, and is very slow.
> >
> > 'cp' is for backups. What is un-portable.
>
> un-portable :
>
> This is un-portable between version of subversion. I see un thread here
> about "Problem compiling r2092 in order to convert database". I don't
> want to deal with such problem.
Yes, I understand your point. A subversion 'dumpfile' will always be
universally readable by past and future versions of subversion.
I guess it's just a matter of how you define a "backup".
To me, a backup is something you quickly copy to tape every night --
or in our case, after every single commit. It needs to be fast. It
exists for the short-term only; there's no worry that I suddenly
won't have the right tools around to read the backup.
For the *longer* term, yes, a full 'svnadmin dump' makes sense. It's
a long-term safety guarantee, but it's slow and very large, so I would
only do it every once in a while.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Sat Jul 13 00:58:36 2002