Not supposed to validate at logon but it always does

Give the purpose of validation I can understand why it continues even when you have stopped running the backup task.

As far as I can work out validation and backup function operate independently. So changing the validation settings for a backup task does not do anything to the backup itself. There is only two ways to delete the backup itself, through the ATI App or through Windows Explorer (not recommended - you will need to temporarily suspend Active Protection to do so).

Edit: I may have misunderstood what is going on. Are you saying that you have tried to change the validation setting and it is not being recognised? Please explain what you have done in attempting to stop the validation on bootup.

Ian

I created a short movie of what happens. This will be my first attempt to upload it to demonstrate the anomaly. It is a zip file containing an MP4.

Let's see if this helps explain it...

YrbkMgr, once you uncheck the option to validate at logon, in order to commit it, you may need to immediately press the "run backup" button, otherwise the change may not be committed.  It is definitely needed when configuring a new backup and it seems like even though modifications are usually committed automatically after backups have already started, sometimes this can help.  Unfortunately, there is no dedicated save button when making configuration changes and it can be difficult to know if the changes have been saved or not without one.  It sounds like your change is just being ignored, because it is not being committed. 

Try that and see if it helps.  If not, I would suggest opening a ticket directly with Acronis technical support and working with them.  If this is a bug, that should help identify it and allow Acronis to fix it in a future update.

That's a good suggestion so thank you for thinking about my issue and suggesting it. You're right, it's not "committing" Consider this...

I click on that particular backup on the left panel - let's call it My PC. I click on "Options". I click on Advanced, then Validation. I have "Validate when backup is created" checked. I UNcheck "Validate backup regularly at:". It always defaults to User Logon. Then, I click on OK. If I go right back to "Advanced" and review the validation settings, they are as I just left them.

Then in the left panel, I choose a different backup, NEW My Pc. When I immediately go back to the My PC by clicking on the left panel again, and if I inspect the Validation settings under the advanced tab, the settings have reverted to both boxes being checked.

My second backup scheme (NEW My PC) retains the settings I have chosen for validation. Only a single backup scheme exhibits this anomaly (My PC).

Btw, "commiting" by making my validation selections then backing up doesn't help. Right after the backup, validation settings revert to both boxes being checked.

I wanted to make sure that I wasn't missing something obvious - rather than try to solve this at this point, I'm going to remove the backup scheme My PC, since NEW My PC is the one I'll be using (since it retains the validation settings).

Thanks for the update.  That would have been my next recommendation.  Sometimes, if a backup scheme seems "borked", creating a new one can be simpler and faster if it behaves better.  Over time, existing backups can carry oddities from past upgrades where bugs used to exist.  I wouldn't say this is is normal, or especially common, but it does seem to happen from time to time.  

If you create a new backup, you can always keep the old one for as long as you need to (or want to) for historical recovery purposes.  And if you don't want it in the console, you can delete just the backup scheme, but still retain the backup files.  And of course, once you no longer need them, then you can delete them to free up the space again.

Glad to hear the new backup is working as expected!

Change the validation settings then click on the 'Save as default' button to ensure that the change is carried forward to any new tasks being created.  This applies to password protection and some other settings too.

**UPDATE**

I deleted the offending backup scheme. Then in the left panel at the bottom, I selected "add existing backup" and functionally restored the one I had deleted. Lo and behold, as they say, the selections for validation "stuck" and are now what they should be.

Weird.

That said, I'm still going to use the new on I created, and keep the old scheme so that I have access to the recovery data easily.

Separate question though...

If I have a discrete backup scheme that is NOT scheduled, what happens with the "old version cleanup rules"? Will it ignore deleting the backups from that scheme that are 183 days old (or whatever)? Or will it delete them, even if I don't run that backup scheme anymore? Or do I have to "turn off automatic cleanup"?

Nice work!  If the backup is no longer scheduled, it shouldn't run and shouldn't clean up either since the cleanup is based on the backups when they run. 

HOWEVER, to be on the safe side, I would disable the automatic cleanup, just in case.  Can't hurt and should be an extra layer of protection if you want to keep them around without having to worry about some unplanned cleanup happening out of the blue.  

Roger that. Good suggestion on turning it off.

Thanks for the sage help on this.