Sheduled task just deleted unrelated tib files.

No explanation as to why your backup files have been deleted.  Maybe if you provided more information about it someone could.

Backup tasks fun by scripts stored in the application.  Removing the scripts should remove the tasks.

If it were me and I wanted to start afresh as you do by removing all task traces I would remove all the scripts.  The scripts are held in a folder at C:\ProgramData\Acronis\TrueImageHome\Scripts.

I would suggest that you use the app GUI to remove that task scripts.  You can remove only the task scripts and retain any backups that remain doing so.  If you click on a task to select it then right click on that task you will get a menu that offers a Delete option.  Selecting Delete you will have the option to remove Completely which means delete task and backup file(s) or Remove from list which will remove only the task script.

If you navigate using to Explorer to the Scripts folder the scripts should appear in the order in which created with the newest or last task created appearing at the top of the list.  You can therefore find the script that controls your offending task as if it is the third task in the app GUI then it should be the third one in the Script folder list.  You can open the listed scripts in the Scripts folder as they are text files.  Each one will have the task they control name in them so that you can further identify the correct script. 

Make note of the offending script in the Scripts folder then use the app GUI to remove the task and verify that the script task has been removed from the Scripts folder by refreshing the Explorer view.  If you desire to remove all tasks use the GUI Delete option to do so.

You should also force a rebuild of the internal database if you want a clean start.

To do this, stop all Acronis Services first, then end all Acronis Processes.

Navigate to C:\ProgramData\Acronis\TrueImageHome and delete or rename the Database folder.

Launch the main ATI GUI and this will create a new Database folder & required files, plus will relaunch required services and processes again.

Board Room, I've never seen or heard of this in my own experience, and very rarely in the forum.  Usually, if something like this happens, it's because the backup tasks are all the same (not unique) and/or because all of the backup are also being written to the same folder where they are muddled together.

Best practice/use (in any backup program in my opinion), is to make sure to always use a unique backup name for every backup task - especially if you have older backups with the same name and plan to make a new task using the same name again... just make it unique by appending something simple to the end such as a sequential number or letter to keep it as close as needed, but still unique.

And, keeping each backup task in it's own separate folder will also help avoid issues based on cleanup of a specific tasks location.  

As Steve and Enchantech mentioned, since you have experienced this though, regardless, I would also recreate the backup database, but then, I'd go back and pick the source and destination of each task after that to ensure it is set correctly... following the recommendation to make sure each backup has a unique name and a unique destination folder.

Thank you all for taking the time to reply.

Really helpful info to make a fresh start.

When my brain is fresh and time allows I will implement these steps.

Thanks again.

B R

Bobbo_3C0X1 wrote:

...Best practice/use (in any backup program in my opinion), is to make sure to always use a unique backup name for every backup task...

Yes indeed. All my backup tasks have unique names and each has separate destination folders.

Thats what made it all the more scary. Tib files from completely unrelated tasks and sources being deleted.

This only occured during the consolidation stage of the errant task when it came to deleting older chains. It decided to include the most recent backup files from two separate unrelated tasks.

Cheers

B R

Yeah, that’s scary if that’s what happened.  Can honestly say you’re the first Ive heard of this happening this way though - lucky you ;)

But seriously, not good, if it’s even possible.  Could you also submit in app feedback and submit a system report to Acronis and submit a case to them?  If this is happening, they should look into it and will need some information about how or what caused it to occur.