mainstoreBackup - Support: sr #108955, Confusion about archive flag


sr #108955: Confusion about archive flag

Submitter:  None
Submitted:  Sat 16 Jan 2016 11:59:53 AM UTC
Category:  None Priority:  5 - Normal
Severity:  3 - Normal Status:  None
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

Sun 17 Jan 2016 04:08:55 PM UTC, comment #2: 


yeah, that definitely helped.

So the archive flag in the config file only takes place if there is more backups then specified in keepMaxNumber, which for me will never happen, since I set no value there.

That mentioned, the solution for my problem would be, renaming the backup. Done that now.

And again this backup tool shows it's potential by being super simple but yet effective.

Thanks a lot for the explanations.


Sat 16 Jan 2016 07:20:44 PM UTC, comment #1: 

Hi Lookbehind,

the algorithm behind "archives" are very simple.

1. If you rename a backup from <timestamp> to <timestamp>-something, then it's simply ignored from (or So this is the "brute force" method to separate a backup logically from all the others.

2. Using the archive flag:
Let's assume you use some keep* flags (except keepRelative, this doesn't work with the archive flag). The result of those flags may be you keep 42 old backups. But you've set keepMaxNumber to 40. Then the two oldest backup not_to_delete by the other keep* rules will be deleted. But for some reason you don't want your oldest backup to keep (resulting from eg. keepLastOfYear) to be deleted. Then you have to set the 'archive-flag' for keepLastOfYear.
The algorithm is as follows: Generate the number of backups to be deleted, in this example 0...41, where backup number 41 is the oldest. Check if keepMaxNumber is smaller than the number of backup to keep. If the number is smaller (eg. 40), delete the supernumerary (here: 2) ones starting with the oldest and ignore those backups which are "marked" with the archive flag. So in the example, where only backup number 41 has the archive flag, backup number 40 and 39 will be deleted (because in this example, they have to be kept because of keepLastOfMonth (without archive flag)).

To make things somewhat more complicated, keepMaxNumber ignores duplicate backups of a day. ;-)

Hope the stuff above is intelligible :-)

Regards, Heinz-Josef

Heinz-Josef Claes <hjclaes>
Group administrator
Sat 16 Jan 2016 11:59:53 AM UTC, original submission:  

Hi there,

I have read the Manual from top to bottom and up again and now I'm a bit confused about the functionality of the archive flag.
It seams there are two different kinds of this.
One where you just rename the backup to something like <date>-archive.
And then there is something to be set in the "keep" options of the config file. This one seams to be somewhat related to keepMaxNumber?
I'm a bit confused how these two tie in together. Maybe someone can shed some light?

I recently discovered that someone did some major changes to his system just before Christmas (23. Dec.). No big Problem, thats why we do daily backups and keep them for a month. But it might turn out, that these changes are a real improvement. So I don't just want to restore everything but want to keep on testing. However I also want to keep the ability to use the backup, in case it turns out to be a problem.
So I want to keep one single backup beyond the usual (automatic) delete schedule.
What do I have to do to achieve this?

Greatings and TIA




(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.


    No changes have been made to this item

    Back to the top

    Powered by Savane 3.13-ee12.
    Corresponding source code