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

hot-backup.py bug?

From: Sandy Pérez <sperezgonza_at_yahoo.es>
Date: Thu, 24 Sep 2009 12:20:16 +0200


Looking at hot-backup.py code, I realized that the script calculates
the next available backup path using the result returned by "svnlook
youngest". For example, if "svnlook youngest" returns 30, a possible
backup path could be /BACKUPS_DIR/My_Repo-30

After having calculated the next available backup path, then the
script calls the "svnadmin hotcopy ..." command. For example, "svnadmin
hotcopy REPO_DIR /BACKUPS_DIR/My_Repo-30". This works fine. The backup
will be created, however, to suppose the last backed up revision is
the revision number 30 could be and error.

Suppose we run the hot-backup.py script. The script will calculate the
next available backup path basing on result returned by "svnlook
youngest". For example, /BACKUPS_DIR/My_Repo-30. However, while
calculating the next available backup path someone runs the "svn
commit" command. Now, the youngest revision will be the 31th. But,
hot-backup.py will call the "svnadmin hotcopy" command as follows:

svnadmin hotcopy REPO_DIR /BACKUPS_DIR/My_Repo-30.

That is, in My_Repo-30, we will have a backup of the 31th revision.

Is this a bug?

Best Regards,


To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subversion.tigris.org].
Received on 2009-09-24 12:23:27 CEST

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.