Hello,
I've set up a backup script that dumps my repositories on a regular
basis. It does a full dump on demand, and two levels of differential
dumps. When I do the differential dumps, I look up the youngest revision
with svnlook, and get the previous version from a number stored in a
file from the next higher-level dump.
This has been working fine for a few weeks, but now in my log, I'm
seeing this notice in one repository, at always the same revision:
[root@foraker svnbackup]# svnadmin dump -r 237:246 --incremental
/var/svn/repos > repos.try
* Dumped revision 237.
WARNING: cmp_rev 197 is older than oldest dumped rev 237
... loading this dump into an empty repository will fail.
* Dumped revision 238.
<snip>
This has happened with every backup containing revision 237, even if I
make the revision range lower or higher. What does it mean? If I have
the previous dumps all the way back to rev 0, is this something to be
concerned about?
Part II: I discovered, going through this, that my script was starting
with the last revision number, not the next one in the sequence. For
example, a weekly backup dumped up to (and including) revision 237. The
daily one is starting with 237. If I load these two dumps, revision 237
will get passed in twice. Does svnadmin load discard the extra deltas
when it sees they've been applied, or will I get unpredictable results
here?
... and one more question while I'm at it. I'm very confused by all of
the log files, and the svnadmin archive/lsdblog/whatever it's called
now. What should I be doing on a regular basis to clean out unnecessary
log files? There's several hundred in my biggest repository now.
Thanks,
John Locke
http://freelock.com
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Thu Sep 4 18:31:20 2003