Setting retention rules and automatic cleanup to use full disk
I use several disks (4TB each internal, external, and removeable) to store custom full backups. Each disk is dedicated to a unique daily recurring custom full backup. I want to set the cleanup rules and use automatic cleanup such that without, regard to backup and/or disk size, backups will continue to accumulate until there is not enough space for the current backup at which time the oldest backup(s) will be deleted until the required space on that disk is available.
The current cleanup rules only allow:
1 - delete versions older than x days. I don't want to empirically calculate what may fit based on average backup and disk size. Can I set the number vary high (99) and when the disk is full, will the oldest backup(s) be deleted to make room for the current backup without regard to the "x days" entry?
2 - store no more than x recent versions. Same as (1). I don't want to calculate what will fit based on some average backup size. Can I set the number vary high (99) and when the disk is full, will the oldest backup(s) be deleted to make room for the current backup without regard to the "x recent versions" entry?
If either (1) or (2) work with high numbers, is there a preference for using either?
This is not addressed in the TI 2016 manual and probably should be added for clarifcation
BTW, the "keep size of the backup no more than x" is misleading. It should read "keep size of this TOTAL backup ARCHIVE to no more than x".
I realize this is a special case where many kinds backups are not being placed on the same destination, but nonetheless, I don't want to have to worry about backup size (always variable and increasing) or disk size other than monitoring how many backups are currently fitting on each disk.
Pat L,
Appreciate the response. The most useful part of your respose is "ATI doesn't delete stuff before completing a run, it does it after. In particular, ATI always completes a new full backup before deleting any older chain (full + associated incremental or differential)." I searched the manual for automatic cleanup and nowhere is this little gem stated. A user selecting the "old version cleanup rules" would assume, as did I, that if space is needed, ATI will create the space before attempting to create a backup of known size and give the user an error only if space required and the rules are incompatible. IF ATI wants to operate this way, the user ought to be given tools to aid in the selection of days or recent versions. This selection of "days" failed occasionally for me because I never thought ATI would attempt to create a backup knowing that the subsequent deletion of a backup according to the "rules" would leave enough disk space for the next backup. While this is a great way to manage small backups with limited disk space, it really wastes space on a "large" disk where my typical backup size is 0.6TB.
As a rule of thumb, I typically try to have 7 days of full daily backup for recovery from crashes and restoration of specific old/corrupted data. The 7th day generates a weekly backup on a set disks that rotate sequentially from "off site" that will allow recovery from of image or data from several months ago.
Again, thanks. If you have influence at ATI, plaese have them add an "automatic cleanup" section that elaborates more on the "old version cleanup rules", especially "ATI doesn't delete stuff before completing a run, it does it after" and actually describes the "errors" that may occur from "incorrect" application of these rules. If the information is readily available in Help and I missed it, please ignore this.
cc
The "Secure Zone" option is close to what you describe as preferable with its automatic cleanup. Check out this link but it can only be used on one disk at a time.
This might be worth testing. I don't use this feature but others do--depending upon your needs.
http://www.acronis.com/en-us/support/documentation/ATI2016/index.html#1…
Here are some other links which may be of interest.
http://forum.acronis.com/forum/100416
Note in my example of custom schemes, there is an option to keep the first full so automatic cleanup bypasses the oldest when doing its deletions.
Option is:
Do not delete the first version of the backup - Select this check box to keep the initial data state. The program will create two initial full backup versions. The first version will be excluded from the automatic cleanup, and will be stored until you delete it manually.
http://forum.acronis.com/forum/64634
Plus other of my links at this link.
https://forum.acronis.com/forums/acronis-true-image-home-discussions/be…
Here is a feedback link where users can express their desires for future changes.
http://www.acronis.com/en-us/support/feedback.html