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

"Malformed dumpfile header" after recovering a repository with incremetal backup

From: <thurm_at_azs-hamburg.de>
Date: 2005-11-24 18:13:20 CET


in the past we backupped our repositories with hotcopy, which worked quite well, but now one of our repositories is so big that we decided to perform a full backup with hotcopy only once a month and doing incremental backups the other days, because changes are made to this repository only every now and then.
But when I performed tests with recovering the repository with reloading the last full backup and additinal loading the incremental dump(s) I get a "Malformed dumpfile header".
This is what I did (Subversion 1.1.4 on Debian Sarge):

To create an incremetal dump:

YOUNGEST=`svnlook youngest $REPO`
for REPO in *; do
# read out the last backupped revision number (for we only perform a backup if revision number has changed)
 [ -f $BACKUP_DIR/$REPO.txt ] && LAST=`head -1 $BACKUP_DIR/$REPO.txt`
svnadmin dump -r $NEXT:$YOUNGEST --incremental $REPO_DIR/$REPO/ > $BACKUP_DIR/$REPO-$NEXT-$YOUNGEST.dmp

The incremetal backup completes wiothout errors or warnings.

To recover the repository to the head revision:
(re-creating the repository with the last full backup with "hotcopy" - works without problems. (Let's say the revision number of the last full backup was 100 and the head revision is 103):

svnadmin load ../svnrepos/Test Test-101-103.dmp

This command doesn't terminate. When hitting <ENTER> I get the above error message.

What's wrong?
Are there any known bugs in recovering a repository with incremental backups?

Any help would be highly appreciated.


Undine Thurm.

To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Thu Nov 24 18:12:52 2005

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

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