Mech_An Space Mgmt Feature

Mech_An,


Would you know if there are any Paragon plans to add a "space management" feature enhancement to the next release of B&R Home ?
... Space Management is the only feature that I find missing in B&R Home. Other, Imaging Pgms like Acronis, Macrium, etc. all have the feature of Space Management and this is an important feature for paragon to implement soon, in order to stay competitive.

In either case, can you forward my below ideas of "Space Management Policies" and "Revised Cyclic Backup - Processing" to the Development Team, for consideration ?


....By "space management", I mean a policy feature on Deleting Backup Archives where the user could specify their choice of the following (3) space managment policies to take effect:

I. Retention Policies (space management):

# 1. Specify the the Maxium Number of Archive "Generations to Retain". When the number of generations to retain is exceeded, Delete the Oldest achive generation.

# 2. Specify the Number of Days to Retain the archive for. Delete the archive, when its retention date is past.

# 3. For the third policy, it should allow a combination of Policy 1 and Policy 2, where you:
.... specify the [B]Minimum[/B] Number of Archive Generations to Retain and the Number of Days for Retention .... and this would work as follows:
If an Archive's Retention Date is Past, **only** Delete the Archive if the Archive is beyond (past/olderthan) the Min. Number of Generations to Retain.


II. The above should hopefully be applied as follows:

A) The above "Space Policies" should be applied to both "Full Image Backups" and also to "Cyclic Backup Sets".

B) In terms of Cyclic Backups, the above "Space Polices" (i.e. No. of Generations to Retain and Retain Days would be related to the status of "Base" Archive.

C) Also, Cyclic Backups should be enhanced so that the Deletion would delete both the Base Image Archive and All Differential Backup Archives associated with the Base Image Archive.

D) The Cyclic Backup GUI - Screen should have a New Option of allowing "Scheduling" (via paragon's normal interface of creating a task scheduler job) of the "Cyclic Base Archive creation". The screen should also allow "Scheduling" of the "Differential Archive Creation".
(.... Cyclic GUI Screen should allow for Weekly and Monthly Scheduling of Cyclic "Base Archive Creation" and "Differential Archive Creation" - Cyclic "Sets".)

...... 1. When the next Scheduled "Cyclic" Base Generation Archive is created, the New Scheduled "Differentials" created should now be created from this New "Cyclic" Base, automatically.

E) Deleted Archives, must also be "Deleted" from the Archive Database, so that their entries no longer appear on the GUI - Archive Tab of B&R 10 Home.


Notes:
1. Of all the Polices, the most important Policy to implement, is Policy 1 (Specify the the "Number of Archive Generations to Retain").

2. The disadvantage with Policy 2 is that if your scheduled or "manual" backups have *not* been executing and you run the next backup you could end up having all your backup archives deleted because their "retention date" has past.

3. Policy 3 is extra insurance over Policy 1, in the situation where you may accidentily re-run the backup an extra time(s). In Policy 1 the generation will spill out of the number to retain (ahead of you normal scheduled execution interval) and be deleted. But, with policy 3, it will *not* be deleted until it passes its Retention Days. (you just have an extra generation(s) hanging around which is fine, at least you did not lose an archive that still may be needed).

 

Mech_An,

Revised to correct/clarify the wording description of space mgmt policy #3.


Would you know if there are any Paragon plans to add a "space management" feature enhancement to the next release of B&R Home ?
... Space Management is the only feature that I find missing in B&R Home. Other, Imaging Pgms like Acronis, Macrium, etc. all have the feature of Space Management and this is an important feature for paragon to implement soon, in order to stay competitive.

In either case, can you forward my below ideas of "Space Management Policies" and "Revised Cyclic Backup - Processing" to the Development Team, for consideration ?

....By "space management", I mean a policy feature on Deleting Backup Archives where the user could specify their choice of the following (3) space managment policies to take effect:

I. Retention Policies (space management):

# 1. Specify the the Maxium Number of Archive "Generations to Retain". When the number of generations to retain is exceeded, Delete the Oldest achive generation.

# 2. Specify the Number of Days to Retain the archive for. Delete the archive, when its retention date is past.

# 3. For the third policy, it should allow a combination of Policy 1 and Policy 2, where you:
.... specify the Minimum Number of Archive Generations to Retain and the Number of Days for Retention

.... and this would work as follows:

----> When the "Number of Generations to Retain" is exceeded, Delete the old exceeded Generations *only* if their Retention Dates have Past.


II. The above should hopefully be applied as follows:

A) The above "Space Policies" should be applied to both "Full Image Backups" and also to "Cyclic Backup Sets".

B) In terms of Cyclic Backups, the above "Space Polices" (i.e. No. of Generations to Retain and Retain Days would be related to the status of "Base" Archive.

C) Also, Cyclic Backups should be enhanced so that the Deletion would delete both the Base Image Archive and All Differential Backup Archives associated with the Base Image Archive.

D) The Cyclic Backup GUI - Screen should have a New Option of allowing "Scheduling" (via paragon's normal interface of creating a task scheduler job) of the "Cyclic Base Archive creation". The screen should also allow "Scheduling" of the "Differential Archive Creation".
(.... Cyclic GUI Screen should allow for Weekly and Monthly Scheduling of Cyclic "Base Archive Creation" and "Differential Archive Creation" - Cyclic "Sets".)

...... 1. When the next Scheduled "Cyclic" Base Generation Archive is created, the New Scheduled "Differentials" created should now be created from this New "Cyclic" Base, automatically.

E) Deleted Archives, must also be "Deleted" from the Archive Database, so that their entries no longer appear on the GUI - Archive Tab of B&R 10 Home.


Notes:
1. Of all the Polices, the most important Policy to implement, is Policy 1 (Specify the the "Number of Archive Generations to Retain").

2. The disadvantage with Policy 2 is that if your scheduled or "manual" backups have *not* been executing and you run the next backup you could end up having all your backup archives deleted because their "retention date" has past.

3. The next most important Policy to implement, is Policy 3 is extra insurance over Policy 1, in the situation where you may accidentily re-run the backup an extra time(s). In Policy 1 the generation will spill out of the number to retain (ahead of you normal scheduled execution interval) and be deleted. But, with policy 3, it will *not* be deleted until it passes its Retention Days. (you just have an extra generation(s) hanging around which is fine, at least you did not lose an archive that still may be needed).

 

Mech_An,

P.S.

Cyclic Backup - Should be enhanced to be able to also Backup "Multiple Partitions" and the "Entire Hard Disk".