Direkt zum Inhalt

Incorrectly reporting the number of backup versions on the main backup task screen...

Thread needs solution

I appreciate any help as I cannot figure out what is wrong. I have attached and included four screen capture images which will hopefully help me explain my issue.

The first image shows my configuration for this backup task. This is a full disk with partition backup. It is setup to create a full version after 30 incremental versions. The old version cleanup rule is set to delete version chains older than 30 days.

The second image shows the main screen under the backups tab. Here it shows a total of 40 versions.

The third image shows the actual files present on the backup hard drive.

The fourth image shows the number of backup files/versions that was in the third image and on the backup hard drive. 35 files are present. How can there be 35 actual files created and Acronis displaying 40 versions? I checked my other backup tasks and they are 1 for 1. In other words, if Acronis is displaying 36 versions then the number of files in that backup series is 36. However, this is not the case for this backup of the hard drive/partitions.

Thanks for any help you can provide.

0 Users found this helpful

Tim,
In both your postings, the same issue exists. My fix would be to use different options.
The options based on elapsed days or disk space limitations involve consolidation which takes time and can confuse the program. Also any editing or changing of options also can confuse the program.

I would stop using the existing backup task and start a new task using the option to keep x number of recent version chains. This option is listed just below your selection based on # of days. My example is link #2 below and illustated by example 11-Inc.

While keeping 31 incrementals are permissible by the program, I would prefer that you do more frequent full backups with fewer incrmentals. This is for the sake of data safety. If inc #15 gets corrupt or non-readable, then 16 to 31 are useless as the chain was broken with #15. I don't know what a reasonable number is to keep but do understand the risk of keeping too many incrmentals. Whereas, the differential type only needs the full plus any single diff to have a successful restore. Diff can be larger as they are the accumulation of all changes since the last full but I felt I should remind you of the difference. This is illustrated in 11-Dif inside my link.

In summary, I would begin a new task pointing to a new empty storage folder and do not change any parameters along the way within that task. Or, if you do a restore, I would also suggest that you start a new task pointing to an empty folder for that function as well.

Thes are the practices that I have found works for me but not necessarily found in the user manual.