05-23-2008 12:08 PM
05-28-2008 01:23 PM
06-04-2008 07:55 AM
06-11-2008 07:30 AM
07-23-2008 10:45 AM
Thank you for your response. We have been involved in a huge dialog with Symantec over this issue which has taken literally months to clarify. And it's such a simple item. Your response, combined with the agonizingly obtuse responses from Symantec, pretty much confirms that BUE cannot perform this utterly simple requirement.
To re-iterate. Four different jobs created. Two file data backups, one SQL backup and one Exchange BU. Backing up to large disk storage NAS. BUE recommends thatr SQL, MSX and data backups be created as seperate jobs (and they obviously need sepeerate settings and selection lists) and then be run sequentially.
But BUE cannot be set to run jobs sequentially. As in, when job one finishes, start job two. We have to use a guestimate of elapsed time to complete previous jobs, and that can vary dramatically depending upon the type of job and the data, etc.
How hard can it be to check a box that says, when job 1 completes, start job 2?
wowser!
07-28-2008 03:42 AM
@Joseph Engel wrote:...
But BUE cannot be set to run jobs sequentially. As in, when job one finishes, start job two. We have to use a guestimate of elapsed time to complete previous jobs, and that can vary dramatically depending upon the type of job and the data, etc.
How hard can it be to check a box that says, when job 1 completes, start job 2?
wowser!
BE can start job 2 when job one finishes, using a policy. However, a policy applies to a group of selection lists, whereas what you want is different jobs for different selection lists. So there is a limitation that applies to you for the start one job when another completes rule.