BRI-Consulting
asked on
Extending Backup Exec Time Window
Hello,
I am running Symantec Backup Exec 11d with SP4. I am trying to take full backups of 30 servers once a week. My problem is that the process for backing up all 30 servers lasts longer than the largest time window I am able to set, 11:00 PM to 10:59:59 the following day and a couple of jobs get missed that I have to manually rerun so that all 30 jobs will complete. My question is, is there a way to extend this window so that all of my backups fit within it?
I have tried adding an error handling rule. I made a new rule with Error Code E000E020 (The job was scheduled to run, but the availability window closed before the job could start. There may not have been any destination devices available during the window, or the job may have been submitted to run when the window was closed) checked and telling the rule to retry the job if this error is thrown. I also told the rule to retry 99 times with a retry interval of 60 minutes. But for some reason, this rule does not work. I think it doesn't even catch because the rule only allows you the option "Final job status: failed" (you cannot change this option) but the jobs actual final job status is Missed.
Please advise,
Morgan
I am running Symantec Backup Exec 11d with SP4. I am trying to take full backups of 30 servers once a week. My problem is that the process for backing up all 30 servers lasts longer than the largest time window I am able to set, 11:00 PM to 10:59:59 the following day and a couple of jobs get missed that I have to manually rerun so that all 30 jobs will complete. My question is, is there a way to extend this window so that all of my backups fit within it?
I have tried adding an error handling rule. I made a new rule with Error Code E000E020 (The job was scheduled to run, but the availability window closed before the job could start. There may not have been any destination devices available during the window, or the job may have been submitted to run when the window was closed) checked and telling the rule to retry the job if this error is thrown. I also told the rule to retry 99 times with a retry interval of 60 minutes. But for some reason, this rule does not work. I think it doesn't even catch because the rule only allows you the option "Final job status: failed" (you cannot change this option) but the jobs actual final job status is Missed.
Please advise,
Morgan
ASKER
I'm sorry, I failed to mention that the 30 different jobs that are kicked off by a policy template. 24 or so of those jobs fall within the template's time window, but the final 6 or so do not and are missed.
I hope this is more clear.
I hope this is more clear.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
This seems a little sloppy. But if it is the only solution, I will try it and let you know how it works. Is there no other way, some hidden registry key for example?
-Morgan
-Morgan
Not that I know of, but i've never gone digging around in the SQL databases. If your comfortable with the SQL query language, then that's where I'd look. I'm guessing you will find that there's no Date field for the Start Windows ending time, since it would serve no purpose, but i've seen stranger things. Also, it would probably get overwritten anytime you make a policy change in the GUI.
ASKER
This solution will most likely work, but is not ideal.
The time window you're referring to is the Start Time window. In other words, the job has to Start (but not necessarily finish) within that window. Maybe I'm missing something, but the obvious answer would be to set the 'Start Time' of the 2nd job (or whichever job is being missed) to be 24 hours after the start of the 1st job.
...or am I missing something??