Skip to main content

ATI thinks existing tib local backup should be tibx after upgrade to 22510

Thread needs solution

I had two backup jobs running in ATI 2020 update 1, one to cloud and one to my NAS (Samba share). After upgrading to update 2 (22510), my local job has a red X on it with a message "The latest backup has been stopped due to the product update", with a link to "Edit connection settings". If I try editing the connection settings, even though the testing says "Connection established", if I press "Connect" it says "Failed to open backup \\mynas\backup\My pc.tibx. Check your network connections." The existing local job was an incremental one, backed up to "mynas\backup\My pc.tib". How do I get ATI back on track?

0 Users found this helpful

FWIW there are only .tib files in the directory on the NAS, and I looked for that metadata file just in case, nothing.

aheid, probably the easiest way to get things back as they were would be to delete the current problem task from the ATI GUI but take the option to only remove the settings, not delete the files on your NAS.

Next, use the option to 'Add existing backup' which is found when you click on the caret to the right of the normal 'Add backup' option. 

Navigate to your NAS and select the most recent .tib file for your backup to be added, which will add a new task to the GUI using the file name.

Rename the task to remove all the extra characters starting from the first _ (underscore), then reconfigure the task settings for the Source and all other Options, then either Validate the task, or perform a new Backup using it.

Steve Smith wrote:

Rename the task to remove all the extra characters starting from the first _ (underscore), then reconfigure the task settings for the Source and all other Options, then either Validate the task, or perform a new Backup using it.

I can't even see what the current options are due to this issue, guess I'll have to look at the XML file.

Not very pleased at all about this latest update :(

Looking at the XML file it's referring to a .tibx file, but existing backup is in .tib only. So I figured no wonder, and restored a version from before the upgrade. It's identical, also referring to the .tibx file?!

So, maybe they fixed a bug where they did not respect some setting in the XML file, and now they do, and since that setting was wrong all along things blew up when I upgraded.

Sorry, but you should not be touching the script XML files for your tasks.

@aheid,

I have experienced a similar issue as you with respect to the NAS connection.  My fix was to shutdown my computer and then cold start it once again.  That released all network connections and restarted them all again and that solved the problem.

Steve Smith wrote:

Sorry, but you should not be touching the script XML files for your tasks.

Not modifying, just reading.

I've made a new backup job, let's see how it goes.

Enchantech wrote:

I have experienced a similar issue as you with respect to the NAS connection.  My fix was to shutdown my computer and then cold start it once again.  That released all network connections and restarted them all again and that solved the problem.

Ah, guess I could have tried that. I'll do that if it happens again, thanks for the pointer!