Scheduled Backups not running.
I built a new computer running a fresh copy of Window7 64bit and Acronis True Image 2013. I have created two scheduled backup tasks. The first is a full backup of my C: drive that should run at 12:00am every day. The backup files for this task are stored on a separate NTFS disk (E:). The second is an incremental backup of my D: drive that should run at 2:00am every day. The backup files for this task are stored in an Acronis Secure Zone on another disk (F:).
The computer has been running continuously for the past week and has not run the scheduled backups at the designated time. This computer is always on, and sleep and hibernation have been disabled. The computer only has one user and is an administrator.
When I start the True Image console to check the status of the backup, I always see a Windows UAC message that I must accept, and more often then not, one of the backup tasks will start immediately. I've included a image of the event log screen for review. The log claims the backup was initiated by schedule, but that obviously seems incorrect.
I've made sure that the Acronis services are running, see image. I also added the user account and password information to the backup tasks in case there is an authentication issue. I've included screen shots of all the setttings for each of the backup tasks.
I've included all the log files generated as well as a screen shot of the window showing several True Image console errors and All syncs errors. Attempting to use the knowledge base error code lookup was no help as the error codes were not found.
Any thoughts on what I should try next?
Thanks in advance,
Andrew
System:
Windows7 64bit
Gigabyte Z77-D3H
Intel i3-3220
8GB DDR3
Crucial M4-64GB SSD (C:)
Western Digital 1TB Black (D:)
| Anhang | Größe |
|---|---|
| event_logs.zip | 477.14 KB |
| acronis_services.png | 78.39 KB |
| all_log_errors.png | 152.11 KB |
| c_backup_log.png | 144.55 KB |
| c_backup_main.png | 81.27 KB |
| c_backup_schedule.png | 60.42 KB |
| c_backup_scheme.png | 58.69 KB |
| d_backup_log.png | 142.14 KB |
| d_backup_main.png | 77.83 KB |
| d_backup_schedule.png | 54.13 KB |
| d_backup_scheme.png | 66.07 KB |
- Anmelden, um Kommentare verfassen zu können
Observations:
Error logs indicate tasks are edited. Better results can be obtained if tasks not edited. Start new tasks if edit needs. These are my personal recommendations.
------------------
Both backup tasks configured to only when computer is idle which could mean they would never run except after a reboot. The run when idle option will cause the backup never to run on any schedle. Suggest you uncheck this option on both tasks.
---------
SD backup scheme: Ok. As configured it will keep a revolving 14 newest backups.
--------
Dif backup scheme:
Trigger set to start deletion after 28 days. YOu would get better results if you changed the option based on the keeping of x number of recent version Chains. In your situtation, a recent version chain is 1 full plus 28 differential backups so each x would multiples of 29. If you set x to 1, then when the 30 backup would run, it would create a new full and delete the oldest 1 full +29 diffs and restart a new series.
Also, each new dif will be increasing larger as it capures all changes since the last full backup bases was created.
---------
No incremental backups configured--only full and full plus differential
-----------------
Having a secure zone on a separate disk is discouraged by Acronis. Is this really needed? Backup files may not be accessible when needed if hardware issues. Could the backup files be stored on a routine storage disk. The individual backkup should be password protected anyway.
-----------------------------
check this link regrading path to backup disk
http://forum.acronis.com/forum/36623
if Non-stop backup is not being used, the service can be stopped and disabled.
Same is true for Sync-agent. If not use, service can be stopped and disabled.
- Anmelden, um Kommentare verfassen zu können
Thanks for the advice. I think the "Only run when idle" setting was the real culprit. My backups are running as expected now.
- Anmelden, um Kommentare verfassen zu können