Aller au contenu principal

[RESOLVED] Warning: Renaming of imported backup reverts to file name after short time

Thread needs solution

When you do a clean install of ATI 2019 it searches for backup files, however, it is not particularly intelligent, and for previous backup tasks is treats each backup-set (full + increments) as separate tasks. In attempt to regain order for backups I then delete (remove for data base) all those tasks and then add the last backup for each of those tasks. Unfortunately ATI 2019 does not retain the renaming. There is nothing in the user guide (4.7.1 Backup operations menu) suggesting that you cannot rename such backups.

I am sure that in earlier versions of ATI it properly included all files created by a backup task as one task.

Update: Looks like reconfiguring the task sorts out the renaming issue. Will keep an eye on this!

Update 2: Yes that is the solution!

Ian

0 Users found this helpful

That's a clean install, but what of an upgrade? Or is it better to go clean?

Michael,

In general, an upgrade from the previous 2018 version to the new 2019 version should work just fine. 

I cannot speak for Ian however, he was on the BETA test team.  He was the only one whom posted this issue with the BETA to the BETA Forum during testing.  Therefore I must assume that his issue was a one off incident.

As for is it better to upgrade or clean install, Since Ian was running the BETA version I suspect that he chose to uninstall that version and then install the release version clean.  That is what I would do myself as a BETA version can have non- optimized code that may remain and cause issue.  I have not installed the release version yet myself but when I do it will be a clean install.

Yes, the problem was caused by my having to uninstall an existing ATI 2019 beta. The renaming issue only arose when I did the last uninstall and installed the release version of ATI 2019. I did not attempt renaming when using beta. On the system I did a simle upgrade from ATI 2018 to 2019 everything went well.

There is a separate, and as yet unresolved problem that I have with both beta and release version of each backup set (full + incrementals/differentials) being recognised as separate task and are not deleted when I do a recovery of settings. This problem only became apparent (to me) in the last week or so of beta testing thus has not been resolved in the release version. As I said in another post, not sure if ATI 2018 behaved in same way - cannot remember.

Ian

 

Thank you gents for your replies.  I'll bear it all in mind in my evaluations should I go ahead.