Aller au contenu principal

Options not properly executed

Thread needs solution

I am having troubles with my settings.

1) I have checked the option "Validate backup when it is created" in "Disk Backup Options"/"Advanced" and unchecked the option "Validate backup regularly". Nevertheless, all the versions of the images are validated after creating a new image, while I only want the new one to be validated. How can I avoid validating all the versions of an image?

2) I have checked "Store no more than 3 recent versions" in "Disk Backup Options"/"Backup scheme". Nevertheless, older than three versions are not (or irregularly) deleted. What can be wrong?

Note: sometimes I delete an image manually. How do these options cope with manually deleted images? And if this creates problems, how can I delete an image manually properly?

0 Users found this helpful

1. It is all or none and nothing inbetweeen. Via the advanced settings , you either enable or disable the validate when created. Another method would be to disable the setting so no validtion is none during backups. Then, use the manual option on the main screen to validate a specific chain or task at a time when it is convenient to you. This way your backups will be validated occasionally manually with no validations during the backups.

2. Post a picture of your backup scheme would help although if you deleted outside the program, that could be involved in the wrong retention of backups. Click on link #2 below and look at illustrations 11-full, or 11-Inc, or 11-Dif. Set up a new task but adjust the 6 and 4 3 examples to fit your needs. Do read the text associated with each of the 3 pictures.

3. Note the listing of backups across the bottom row of the link below.
http://forum.acronis.com/system/files/delete-tib-file.jpg

If using the very latest build of 2014, if you want to delete the latest backup, you can right click on that specific file and choose delete from the right click options offered. Or, if you are wanting to delete all of a single chain, you can right click on the full backup and all of the newer inc or diff will also be deleted.

If NOT using the latest builld, you will need to start with the last or newest backup in a specific chain and delete siingle files backwards and the prior programs will not delete whloe chains--only singles.
Following any deletions, I would return to the main screen and specific task, click the gearwheel (upper right) and click the validate backup option. If errors, keeping click the ignore option and work your way thru any missing entries until the validtion does actually begin.

4. You mght try this manual validtion procedure on your backup which are not deleting but it may not help.
5. One of the biggest causes of a scheme not working is that the user makes changes or edits the original configuration and the program gets confused from that time forward. If corrections needed, start a new task and point to a new and empty folder or sub-folder--no mixing of backup files from different tasks.

6. Did you ever resolve your pre/post power problem?
http://forum.acronis.com/forum/45056

"1. It is all or none and nothing in between": strange there is no option to validate the new image only.

"2. Post a picture of your backup scheme": see attachment.

Point 3 - 5: From now on I will delete images by the 'formal' way and see if this works. I use the latest build of TI.

"6. Did you ever resolve your pre/post power problem?": see the post.

Fichier attaché Taille
144991-110335.png 18.38 Ko

1. Within the options of each task is a validate option and since your is full backups, it should just validate the single full backup as it is the only backup in that specific chain.

2. Thank you for the image. This shows full only so vaidation should not be appearing as multiple validations unless you have your validate options set to do more validation than just at time of backup creation.

3. Editing a task or wrong deletion could affect file retention. Let's wait and watch the new tasks .My experiene has been that automatic works so the next deletion of a single full will immediately occur after the nextfull backup following reaching the "keep x number of rcent version chains.