Hello,
Unfortunately last month we had backup issues with our last Friday of the month Full Monthly Backup, (dated 27/06) the tapes were not changed and thus the Monthly backup consisting of 3 jobs did not run. The Monthly job tried to run on the Daily 4 tape which already had data written to it and as there was no admin input, it cancelled after a while. The other sheduled job on 28/06 was also automatically cancelled.
The following week, Daily Sets 1-4 (Mon to Thurs. respectively) ran with partial success, with only 2 of the 3 jobs succeeding. The week after the failed monthly job (05/07) the 3rd job was automatically cancelled even though the correct Weekly tape was inserted into the drive.
The following week (beginning 07/07 diagram above) the daily jobs ran normally between the 7th to the 10th. On the 11th a LiveUpdate was ran and the server was not restarted post installation, which caused the job cancellations on Monday 14th. This also caused the 6 missed jobs. The issue was reported to Symantec, who unfortunately misdiagnosed the problem and then asked us to try changing the Media Insert alert category properties to 'Respond with Yes/No' instead of Cancel, which had the consequence of generating 3000+ alerts between the Saturday 18th and Monday 20th when we had to manually cancel the backup job as to be able to run the day's Daily Backup job. This was reverted. The daily backup jobs then ran normally Monday night and Tuesday night. Below is the monthly schedule for the up and coming Monthly backup on Friday.
The daily and weekly updates in this instance are superseded by the scheduled monthly updates.
The question is, what exactly has happened to our schedule because of a) the correct tape not being inserted last month and b) another instance of backup service being disturbed due to services not being available, and how do we revert the status quo and then ensure the job runs through correctly?
Thank you