Aller au contenu principal

Diff Backup Scheme Ignored

Thread needs solution

I have a custom Diff backup scheme to create a full backup with 3 diff versions and a cleanup setting of keep 3 version chains.  this worked fine in TI2015 but is being ignored in TI2016. the result is an endless chain of diff versions.  attached is a screenshot of my backup screen and the resulting back up folder on external drive.  can some one help with solving this Problem?  Thanks in advance.

 

Fichier attaché Taille
backupscheme.jpg 112.89 Ko
backup_folder.jpg 121.46 Ko
0 Users found this helpful

If this task was a carryover from 2015, this often times does not work correctly. Or, if you made edits and changed the configuration anytime, this could also be a cause.

At this point, I would suggest that you start over with a new task. You an use the same Full plus 3 diff; and store 3 chains as before.

Do be sure that the name of your backup scheme is "custom". The backup scheme name is hidden in your attachemt but your comments indicate its name is custom--just make sure it is named custom.

Two changes in your task confuration. Point to a new storage folder name (maybe AcronisBU-2016), and change your task name from WeeklyDiff to something like WeeklyDiff33 (any change will do--just different from your prior).

Let me know the results, I am expecting them to be successful without issue. This link may be of interest.

http://forum.acronis.com/forum/100416

Note: if you wish to delete some of the excess diff files, you can keep the two most recent (S11 & S12) and delete the other diff files via Windows Explorer.

After any deletion, manually validate the S12 and respond "ignore" to EACH of the error message on missing files.

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

Note, if you have the storage space, consider using the option "do not delete first version of the backup" as often time, it is the oldest backup which is the most help for recovery of missing files.  This would add one more full to your overall storage, but it would be ignored by the automatic deletion.

Using this option, you would still have a revolving 3 chains, plus the first do not delete chain.

 

GroverH, Thanks so much for your help. I have set up a new task just as you have suggested.  I did get my 1st full backup from this new task in a new backup folder.  Your solution makes sense to me and I am sure it will correct my issue. I will keep you updated as the diff chains proceed and cleanup occurs.

Again thanks for your time and advice!

Always glad to help with the learning curve.  Do keep us posted on the results.

Hello GroverH, I promised to follow up with the results of the problem for this thread. i am sad to say i am still having the same problem.  I set up my configuration just as you reccommended and i am still getting multiple diffs beyond the 3 that are specified in the options for the backup scheme.  I have attached Screen shots of my current backup folder and the custom scheme.

Since we last talked i now have 7 diffs and only the original Full backup even though the setting is for 3 diffs then new full.

I am curent on the software at build 6027.

Here's the catch. i have a license for 3 PC's and have the exact same custome scheme running on a dell desktop and it is running correctly.  a full, 3 diffs, another full, 3 diffs, etc.,  with 3 sets and the 4th oldest is deleted. I am having the problem on a Dell Laptop. Both PC's running same version of Win7 with equal updates and both are running same build of TI2016. 

Again i did not have this problem with TI 2015.  Any ideas about what is unique about my laptop with the problem?

Thanks in advance for ideas you might have!!

AL

Fichier attaché Taille
317629-124477.jpg 96.52 Ko
317629-124480.jpg 93.81 Ko

Hi Al,

I don't know the real cause of your issue other than to believe that the upgrade to 2016 was less than 100% effective.

On the problem laptop, I would run the 2015 TI Cleanup utility (refer link #4 my signature) and then re-install 2016. You will need to again input your serials.  The existing tib backup files will not be deleted but you will need to recreate all new tasks.

YOu can use the same backup scheme settings but again, do use a differeent task name and a different folder name so there is no  intermixing of old backups. Let uos know the results.