Aller au contenu principal

Cleanup using retention rules does not work

Thread needs solution

I bought ABR 10 back at the beginning of the year after using the trial version of the program through the end of last year. I set up a single backup plan with the following configuration:

What to backup: C: and D: drive
Where to backup:
Path: Personal vault, F:\DesktopBackup (F: is my external USB drive)
Name: Archive(1)
Backup scheme: Custom
Full Backup:
Schedule: Every 2 weeks on Sunday at 12:00:00 AM
Conditions: Not specified
Incremental:
Schedule: Every 1 week on Monday, Tuesday, Wednesday, Thursday, Friday at 11:00:00 PM
Conditions: Not specified
Differential:
Schedule: Not specified
Clean up archive: Using retention rules
Retention rules:
Delete backups older than: 5 weeks
Deleting a backup with dependencies: Retain the backup until all dependent backups become subject to deletion.
Apply retention rules: After backup
Archive validation: Never
Backup options:
Settings: Custom (although there aren't any settings that differ from defaults)
E-mail notifications: Enabled
Convert to VM: Never

The problem is that the cleanup does not do anything. I see no errors, but there are a number of files that have not been deleted that should have. Here's a directory listing of the F:\DesktopBackup directory where everything is being archived:

-------------------
++++ F:\DesktopBackup> dir

Volume in drive F is My Book Serial number is 6824:1da4
Directory of F:\DesktopBackup\*

2/21/2010 0:55 .
2/21/2010 0:55 ..
1/05/2010 15:10 .meta
12/29/2009 13:14 71,345,148,928 Archive(1)_2009_12_29_11_54_13_484D.TIB
12/29/2009 19:21 69,091,121,664 Archive(1)_2009_12_29_18_09_07_796D.TIB
12/30/2009 0:32 20,460,110,848 Archive(1)_2009_12_29_18_09_07_796D2.TIB
12/31/2009 0:35 34,484,962,304 Archive(1)_2009_12_29_18_09_07_796D3.TIB
1/01/2010 0:13 7,303,683,584 Archive(1)_2009_12_29_18_09_07_796D4.TIB
1/02/2010 0:53 55,717,736,448 Archive(1)_2010_01_02_00_00_07_906D.TIB
1/04/2010 0:20 432,421,888 Archive(1)_2010_01_02_00_00_07_906D2.TIB
1/05/2010 0:11 5,207,115,264 Archive(1)_2010_01_02_00_00_07_906D3.TIB
1/10/2010 0:59 56,558,686,208 Archive(1)_2010_01_10_00_00_08_515D.TIB
1/11/2010 23:23 6,256,070,144 Archive(1)_2010_01_10_00_00_08_515D2.TIB
1/12/2010 23:14 7,486,914,048 Archive(1)_2010_01_10_00_00_08_515D3.TIB
1/13/2010 23:11 4,438,593,536 Archive(1)_2010_01_10_00_00_08_515D4.TIB
1/14/2010 23:15 8,638,275,584 Archive(1)_2010_01_10_00_00_08_515D5.TIB
1/15/2010 23:16 10,409,768,448 Archive(1)_2010_01_10_00_00_08_515D6.TIB
1/18/2010 23:24 6,997,423,104 Archive(1)_2010_01_10_00_00_08_515D7.TIB
1/19/2010 23:11 3,525,529,600 Archive(1)_2010_01_10_00_00_08_515D8.TIB
1/20/2010 23:09 1,853,854,208 Archive(1)_2010_01_10_00_00_08_515D9.TIB
1/21/2010 23:12 5,764,915,712 Archive(1)_2010_01_10_00_00_08_515D10.TIB
1/22/2010 23:12 5,869,259,264 Archive(1)_2010_01_10_00_00_08_515D11.TIB
1/24/2010 0:53 57,003,448,832 Archive(1)_2010_01_24_00_00_08_640D.TIB
1/25/2010 23:25 7,039,090,688 Archive(1)_2010_01_24_00_00_08_640D2.TIB
1/26/2010 23:12 5,385,434,112 Archive(1)_2010_01_24_00_00_08_640D3.TIB
1/27/2010 23:08 1,383,056,384 Archive(1)_2010_01_24_00_00_08_640D4.TIB
1/28/2010 23:09 1,289,260,032 Archive(1)_2010_01_24_00_00_08_640D5.TIB
1/29/2010 23:11 3,397,059,072 Archive(1)_2010_01_24_00_00_08_640D6.TIB
2/01/2010 23:25 8,001,685,504 Archive(1)_2010_01_24_00_00_08_640D7.TIB
2/02/2010 23:11 4,085,627,392 Archive(1)_2010_01_24_00_00_08_640D8.TIB
2/03/2010 23:12 4,592,381,440 Archive(1)_2010_01_24_00_00_08_640D9.TIB
2/04/2010 23:10 1,917,584,384 Archive(1)_2010_01_24_00_00_08_640D10.TIB
2/05/2010 23:09 1,031,366,656 Archive(1)_2010_01_24_00_00_08_640D11.TIB
2/07/2010 0:57 57,514,556,416 Archive(1)_2010_02_07_00_00_08_359D.TIB
2/08/2010 23:28 12,400,287,744 Archive(1)_2010_02_07_00_00_08_359D2.TIB
2/09/2010 23:13 4,235,514,880 Archive(1)_2010_02_07_00_00_08_359D3.TIB
2/10/2010 23:12 2,219,487,232 Archive(1)_2010_02_07_00_00_08_359D4.TIB
2/11/2010 23:12 3,128,634,368 Archive(1)_2010_02_07_00_00_08_359D5.TIB
2/12/2010 23:13 4,124,425,216 Archive(1)_2010_02_07_00_00_08_359D6.TIB
2/15/2010 23:28 9,460,635,648 Archive(1)_2010_02_07_00_00_08_359D7.TIB
2/16/2010 23:14 5,713,845,248 Archive(1)_2010_02_07_00_00_08_359D8.TIB
2/17/2010 23:17 9,312,605,184 Archive(1)_2010_02_07_00_00_08_359D9.TIB
2/18/2010 23:19 8,236,854,784 Archive(1)_2010_02_07_00_00_08_359D10.TIB
2/19/2010 23:15 7,819,360,256 Archive(1)_2010_02_07_00_00_08_359D11.TIB
2/21/2010 0:55 60,546,086,400 Archive(1)_2010_02_21_00_00_08_140D.TIB
661,679,878,656 bytes in 42 files and 3 dirs 661,679,947,776 bytes allocated
825,568,063,488 bytes free
-----------------
According to my figuring, the 2009_12_29 and 2010_01_02 files should all have been deleted by now. The latest file that depends upon any of those files was dated 1/5/2010, which was over 6 weeks ago.

Here are all the log entries from the last time the backup ran (which was yesterday at midnight):
-----------------

------------------

Can you please tell me what I'm missing here? Is there some option I can specify to get more information about what the cleanup is doing so that I can get some idea of why it has not yet deleted anything?

Jim Babka.

0 Users found this helpful

in the cleanup options try to activate "CONSOLIDATE" instead of "Deleting a backup with dependencies"

OK. It appears that the problem has to do with when I switched from the trial version to the real one. It asked me to completely uninstall the trial version before installing the real. Even though I named the backup exactly the same as before, it evidently did not remember the backup files from the trial version. It just deleted the batch of backups from the first backup that I ever did with the real product. This was the right time to delete those, since the latest backup that depended upon that one was dated 1/22, and that is now 5 weeks old.

Suggestion for Acronis: document that when you install the real version and it tells you to uninstall the trial, it will not remember anything about the trial backups.

Well, if the version is 10.11345, there is ability to change license from trial to real from the program itself, without reinstall. After reinstalll the instance id probably was changed, causing the problem.