KSRC Posted July 1, 2009 Report Share Posted July 1, 2009 so we have 2 backup sets, one we keep on site for a week and another of site. Every week we swap them out so we have 2 backup destinations and have the timeout set to 4 mins. However the scripts don't stop until they've processed through all the source data to see what needs to be backed up. For most of the scripts this isn't a big deal, they end up stoping 4-5mins total, but there's a few that take 1-5+ hours. Is there a way to make it not do this and just time out when it that backup set isn't in? here's an example: + Normal backup using KSRC01D at 6/27/2009 1:35 AM (Execution unit 4) To Backup Set 1-KSRC01D... - 6/27/2009 1:35:04 AM: Copying Local Disk (D:) on KSRC01 Media request for "1-1-KSRC01D" timed out after waiting 0:04:00 6/27/2009 2:42:54 AM: Execution incomplete Remaining: 1535 files, 753.7 MB Completed: 0 files, zero KB Performance: 0.0 MB/minute Duration: 01:07:51 (01:07:03 idle/loading/preparing) here this backup set isn't in so instead of taking 4 mins it's taking over an hour. I'm not the one that made the scripts this way so if there's a better way to do it with 2 backup sets let me know too. Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.