mainstoreBackup - Support: sr #108331, include renamed backup as backup...


sr #108331: include renamed backup as backup directory for hard linking

Submitter:  None
Submitted:  Thu 27 Jun 2013 07:32:46 PM UTC
Category:  None Priority:  5 - Normal
Severity:  1 - Wish Status:  Done
Privacy:  Public Assigned to:  None
Originator Email:  -email is unavailable- Open/Closed:  Open
Operating System:  GNU/Linux
* Mandatory Fields

Add a New Comment Rich Markup

Sat 29 Jun 2013 10:27:31 AM UTC, comment #3: 

better documentation in the next release

Heinz-Josef Claes <hjclaes>
Group administrator
Fri 28 Jun 2013 09:44:33 AM UTC, comment #2: 

Hi Heinz-Josef,

I agree 100% and it was in no way "important". Just knowing how storeBackup behaves is enough I need. Not to rename the last backup is a valid workaround / "restriction".

I just wanted to get clear I did not miss an option on my side ;-)

This is no bug at all.

Have a great day

lopiuh at

Fri 28 Jun 2013 04:48:19 AM UTC, comment #1: 


renaming of old backups was never meant to be more than a quick hack to give the opportunity to protect specific backups.

The problem in changing the case you mention is option lateLinks - and therefore "normal" lateLinks itself and isolated backup and replication.

I think the safest way to avoid potential problems with renamed backups is not to allow / support renaming of actively used backups. So there's a good reason why they are ignored. I will write a note in the documentation (for next release) about that - this point is missing in documentation.

Also, I think it's not worth the effort to change this behavior, because you simply can wait for one backup and then rename it.

The big advantage of storeBackup is that there's no central application to control things like this renaming stuff or locking, deleting, and all the other stuff done by storeBackup*.pl applications. So you can use it just on a plain file system (and also can restore in that way). Handling is pretty simple if you compare handling with the functionality.
But then, this design of storeBackup also has some drawbacks.

Regards, Heinz-Josef

Heinz-Josef Claes <hjclaes>
Group administrator
Thu 27 Jun 2013 07:32:46 PM UTC, original submission:  


"problem": rename last backup (mv 2003.07.28 06.12.41 2003.07.28 06.12.41-archive)

The renamed backup isn't used for hardlinking in the next run of (or do I miss something)?

use case: nothing special, name any reason for protecting a backup by renaming the buckup directory. If it is the last one you create
unnecessary dupes during next backup-run.





(Note: upload size limit is set to 16384 kB, after insertion of the required escape characters.)

Attach Files:

No files currently attached


Depends on the following items: None found

Items that depend on this one: None found


Carbon-Copy List
  • -email is unavailable- added by hjclaes (Posted a comment)

    There are 0 votes so far. Votes easily highlight which items people would like to see resolved in priority, independently of the priority of the item set by tracker managers.

    Only logged-in users can vote.


    Follows 1 latest change.

    Date Changed by Updated Field Previous Value => Replaced by
    2013-06-29 hjclaes StatusNone Done

    Back to the top

    Powered by Savane 3.13-4b48.
    Corresponding source code