I schedule groups such that no two start within 15 minutes. I also have a test 
of test groups, which are called … test1, test2, test3, test4, and test4 and 
any client that needs troubleshooting gets put into one of those test groups 
and taken out of its production group. All my test groups are set to have the 
auto-start disabled and I do check them very frequently to make sure a client 
who's backkup is working isn't in any of those test groups.

On 08 2, 2010, at 9:17 AM, N.J.Tustain wrote:

> Does anyone use any kind of intelligent scheduling arrangement to prioritise 
> and control backup jobs?
> 
> Our operational people lump clients together in 'groups' test servers with 
> live servers then let them fight it out for available networker resources. 
> This is particularly bad over a weekend when most full backups get scheduled. 
> 
> On occasions it all falls over there are questions asked of the backup 
> software or the architecture. 
> 
> The emphasis seems to be on saying the backup system isn't capable of 
> handling the load, as opposed to resolving the problem by better management 
> of backup jobs.
> 
> 
> What are people's opinions on this? 
> 
> 
> Is that Networkers ability to multiplex backup jobs, one of its benefits lead 
> to poor job scheduling ability? Does TSM or netbackup work in a similar way?
> 
> Anyone else have problems with this?
> 
> Thanks
> Nick 
> 
> 
> 
> 
> -- 
> The Open University is incorporated by Royal Charter (RC 000391), an exempt 
> charity in England & Wales and a charity registered in Scotland (SC 038302).
> 
> To sign off this list, send email to listserv AT listserv.temple DOT edu and 
> type "signoff networker" in the body of the email. Please write to 
> networker-request AT listserv.temple DOT edu if you have any problems with 
> this list. You can access the archives at 
> http://listserv.temple.edu/archives/networker.html or
> via RSS at http://listserv.temple.edu/cgi-bin/wa?RSS&L=NETWORKER

To sign off this list, send email to listserv AT listserv.temple DOT edu and 
type "signoff networker" in the body of the email. Please write to 
networker-request AT listserv.temple DOT edu if you have any problems with this 
list. You can access the archives at 
http://listserv.temple.edu/archives/networker.html or
via RSS at http://listserv.temple.edu/cgi-bin/wa?RSS&L=NETWORKER