Ben Collins-Sussman wrote:
>
> Michael Price <mprice@atl.lmco.com> writes:
>
> > Blair Zajac writes:
> > > I do need to sweat the log stuff doing the incremental backups.
> > >
> > > I plan on replacing the db backup solution with the svnadmin dump based
> > > backup solution due to the large disk space that the db based backups
> > > are using, I indicated my the first message in this thread.
> >
> > I guess I'm already lost then. With several of my repos at home, the
> > gzip'd dump is several times LARGER than the gzip'd repository itself.
> >
> > Where exactly is the space savings? (or do I not understand what your
> > doing?)
>
> Yeah, I was going to ask this same question! A dumpfile doesn't have
> *any* compression in it at all, the way our repository does. If a
> file changes in some revision, the repository stores it as a diff, but
> in the dumpfile the fulltext is always written out.
>
> What's going on, Blair? I don't understand the itch you're
> scratching.
I ran a du -ks on my hot-backups directory and after 100 revisions,
I had 1 Gbyte of disk space used for a 12 Mbyte repository.
Granted, I'll need to remove the revisions that reflect an older
repository format, but that's still a lot of disk space to use.
I'll say, that's pretty big itch :)
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 Thu Aug 22 19:49:54 2002