Acronis True Image 2014 Scheduler Problem
I am running TI2014, build 6673, on a Windows 8.1, 64-bit system. My hardware is a Sony VAIO running an Intel i7-4500u CPU.
Here is the issue:
If I setup a scheduled backup (e/mail, files or partition) things run fine as long as I don't ever modify the backup settings. However, if I update the scheduled backup in any way, the next time it attempts to run, whether I initiate it manually or allow it to run on the schedule, it will go into a "queued" state and never run. To clear the problem I have to delete the scheduled backup, recreate it and boot the PC.
I opened an issue with Acronis support and they suggested that I uncheck the "Compatibility mode" option for the Acronis executable. This option was not checked, so this was not the cause of the problem.
When I discovered that all I had to do was delete and redefined the scheduled tasks I closed the issue with Acronis because I thought it was a "one time" problem. However, as I mentioned, all I have to do is touch the backup definition and it breaks it.
Any help, suggestions or ideas would be appreciated.
Hi GroverH. Thank you for the detailed information. I'm happy to see that changing from scheduled to non-scheduled or vice versa, or changing the schedule itself does not damage the task. It is frustrating that changing the settings of the task renders it useless. I guess I will just have to rebuild my tasks from scratch if I ever want to modify them. That is, until Acronis can find the problem and fix it.
It would be nice if there were a command line interface that would allow for creating tasks via a batch file. That way rebuilding a task would be quick and painless. I've searched in vain to see if Acronis has such a facility but apparently they do not have a command line interface.
One method of creating identical tasks or replacement task is the "clone task" feature.
If you cease to use a task, it can be cloned and changes made before it first usage.
This can help to save some task creation time.
That's a great idea. Thanks again!
Edward,
If you do use the clone task method, DON'T use the cloned task until you have changed the
name of the backup file
path to a new storage folder
changed the name of the backup task.
Making those 3 changes will help you to avoid confusion of what is working or not working.
When setting up a normal full backup or a full backup to be used to create a replacement disk (should there be a need),
my recommendation of a backup type is the disk option or disk mode backup as illustrated in the very first picture of signature link 2 below.
Or, if you want to use full backups combined with incremental or differential follow ups, here is an one example of how to use automatic cleanup so no consolidation is involved and the deletion of old backups is automatic by the program once it reaches the user selected number "store no more than X recent version chains." Chance the number of inc's to keep or the number of "store no more than X recent version chains" to fit your own storage requirements.
