Skip to main content

Why is validation of a new task asking for access to an old task's tib files?

Thread needs solution

Why is validation of a new task asking for access to an old (now unscheduled) task's tib files?

The only connection I can see is that both tasks backup the same drive.

My plan is to delete the old task (now unscheduled) and its associated tib files. But will this cause future validations of the new task to fail?

Thanks for your time.

B R

 

0 Users found this helpful

B R, the only reason that I am aware of is when backup tasks have reused the same name and this is still referenced in the internal Acronis Database files.

If this has been the case for you, then you may need to consider removing the task that you want to keep from the GUI, then removing / deleting the old task files, before using the option to Add existing backup for the most recent file from the first removed task, followed by reconfiguring the task.  This should clean up the database but would be more guaranteed if you renamed the files you will be adding back, to make their name unique for the task that will be created.

Hi Steve

Thanks for replying.

The new and old tasks have completely different names. So that isnt the cause on this occasion.

The only thing they share is the new task includes the same drive as the old task source. The new task also has another drive included backup.

I'll try as you suggested and report back to let you know how it goes.

The lesson here is to remove the old task before creating a new one that includes the same source.

Thanks again for your time.

B R