Skip to main content

Active Protection alerts when delete backups w/File Explorer

Thread needs solution

I've just for the first time with Active Protection enabled, manually deleted some .tib files with File Explorer.  I got multiple AP alerts, which I handled each time with the button to allow explorer.exe for an hour.

What would best practice be for this?  (I don't figure I want to exlcude .tib files from protection.)

0 Users found this helpful

Coyote, you have two choices for how to proceed here.

1.  To do as you have said above and allow each action for an hour as and when you need to delete .TIB files.

2.  To temporarily Turn off AAP via the option shown when right-clicking on the AAP icon in the system tray while doing any such deletions then turn it back on again later.

In reply to by truwrikodrorow…

Thank you very much, Steve. 

I think I'll turn off AAP while I do the deletes then turn it back on, since that would mean less clicking.  (Hopefully I'll remember to turn it back on after the deletes.)

New question, please: I wonder if I'll even need to do this weekly now that I'm using ATIH2018: I was hopeful (that Automatic Cleanup will start working for me) when I read in another thread that with ATIH2018 there are "no more issues with updating a scheduled task and causing the backup version chain to restart the count".  Is my practice (of switching task Method to force Fulls when desired) relevant to that improvement?

Coyote, I can only suggest testing that this change is working for you in your practice of changing the Backup Scheme method periodically, it should be easy to check whether version chain counts have been reset or not?

It will be easy.  I created a new Full last night (right after I upgraded to ATIH2018).  So next time I run a Full I'll discover (and report my results) whether ATIH2018 has resolved my issue.

The result is that No, ATIH2018 has not solved my issue.  Despite the promise I noted in another thread (that there are "no more issues with updating a scheduled task and causing the backup version chain to restart the count"), my practice (of switching task Method [from Incremental] to force Fulls when desired) has resulted in 2 chains being left after backup (there was only 1 chain before backup) despite the Setting "Store no more than '1' Recent Versions" left 2 chains.

Coyote, I can only advise that you submit a Support Case to Acronis for this issue and explain exactly what you are doing and the behaviour you are expecting to see versus what actually happens for you.

In reply to by truwrikodrorow…

Thank you very much for your reply, Steve.  In fact I already did so.