Aller au contenu principal

Scheduled job failing for a strange reason and also preventing all other future jobs to not start

Thread needs solution

Hi: I am performing a File Backup with Backup method set to Full. I also have "Delete versions older than" selected with 31 days (attached Backup Options Window). This is a weekly backup that started on 12/22/2013. Backups were happening fine every week (12/22, 12/29, 01/5, 1/12, 1/19, 1/26). On 2/2, the 12/22 backup was deleted, the backup on 2/2 failed with this error (Attached Error Window). This message was on a pop up window with Retry, Knowledge Base and Cancel Buttons. I didn't log on to the server for 5 days. All the daily backup jobs did not even run.

Information: Failed to open backup \\Consult1\consult1_shared\Weekly_full_Data_2013-12-22_0030_full_b1_s1_v1.tib. Make sure the backup location is accessible and contains all versions of the backup. This backup may also be corrupted.

Click Retry to try to read from the same location. Otherwise, click Cancel to cancel the operation.

1. Why is the backup failing. I can access the \\Consult1\consult1_shared folder fine. I also see the backup file Weekly_full_Data_2013-02-02_0130_full_b7_s1_v1.tib in the folder.
2. How can prevent other jobs not to start just b'cos one of the jobs failed?

Thanks
Ravi

Fichier attaché Taille
errormessage.png 22.9 Ko
backup_option_window.png 33.73 Ko
0 Users found this helpful

At this point, as the backup has stalled looking for the Dec 22 b1 backup. My suggestion would be to stop using the task and start over with a new task and I am suggesting new options. I have had very good success in setting up a Custom/Full/ Automatic Cleanup based on "Store no more than X recent versions." with X set to 4 (28 days of backups) or 5 (35 days of backup). My experience has been that the automatic cleanup works using this type settings. I discourage the use of elapsed days or used disk space as controls and I will not use any consolidation settings--all of the preceding are my personal preferences that has worked for me. The new task should point to a new empty sub-folder on your storage disk so there is not intermixing of backup files within the same folder and no edit or changes of configuration once the task has been commited.

As it relates to some task not running, did you look at the log file to see if there were any error messages relating to the tasks which did not run? The failure of one should not have stopped (maybe delayed the other) the other tasks from running. I am assuming that the other tasks ran ok during the time that the weekly task was running. As a precaution, you might look at the schedule options on one of the task which did not run to confirm thier settings match this example.
http://forum.acronis.com/system/files/resize/schedule-advance-settings-…