True Image 2010 coped with changing network backup drives, 2016 seems not to
True Image 2016 doesn't seem to be able to do what 2010 can do.
I have been using True Image 2010 on several computers that do an incremental backup onto the same networked drive. Computers 1, 2, 3 etc back up into folders 1,2,3 etc on the network drive. Each week I change the network drive to a new one, with empty folders 1,2,3 etc. ATI 2010 automatically identifies the folder is empty, creates a full backup and on subsequent nightly runs, does an incremental backup. This all happens without manual intervention.
At the end of the week, I replace the hard drive with another with empty folders, and ATI 2010 repeats the process.
With ATI 2016, when I replace the hard drive with one with empty folders, I get the message:
"The Specified File Does Not Exist. Click Retry to try to read from the same location. To create a new version according to the current backup scheme, click Ignore."
I have to manually go to each computer, click 'Backup Now', then 'Ignore' to force it to do the first full backup. After that, ATI 2016 will do the scheduled incremental backups. This is time consuming and means I can’t get the first backup to automatically start during the night.
How do I get ATI 2016 to do the first Full Backup of an incremental set to the backup schedule, without having to intervene manually, as ATI 2010 could?
2016 is your cause. As you found out, it will not create a backup except to the specific disk that was attached at time of task creating.
The program wants you attach a new disk and then create a new task. Task cloning option might help.
2010 did not track backup history but beginning with 2013, tracking began.
Thanks for your comments. I can understand why Acronis does this check for a situation where the backup is always being done onto the same network location, but that is surely a dangerous thing to do. Backup drives have to be changed weekly and stored off site for theft & fire proofing; for proof against virus or hacking attacks; for protection against backup drive failure; for having long term recovery of old versions.
You suggest cloning to solve this, but it means I have to log onto each computer on the network to clone the backcup.
Surely, changing the network backup drive is not an unusual security measure, and surely Acronis can handle this scenario automatically in some way? Am I doing something wrong or missing something?
Derek,
I think you misunderstand when the word clone is suggested. Clone in this case is talking about cloning the backup task not the disk itself. What the intent is, is to clone or essentially copy the already defined task and use that to create a new task pointed to a new disk/destination.