All,
        I have the following config.

NB 5.0 MP1 (Enterprise)
Win 2K3 = Master Server (SSO)
Win 2000 = Media Servers (SSO)
SSO = ATL P7000 7 SDLT Drives
Windows NT 4.0, Windows 2000 & Windows 2003 server clients = 48
Policy 1 = Scheduled 4:00pm (10hr. window) - 12 Clients (Small & Medium
Sized 18gb - 146gb)
Policy 2 = Scheduled 7:00pm (10hr. window) - 12 Clients (Small & Medium
Sized 18gb - 146gb)
Policy 3 = Scheduled 9:00pm (10hr. window) - 10 Clients (Small & Medium
Sized 18gb - 146gb)
Policy 4 = Scheduled 11:00pm (10hr. window) - 6 Clients (Large Sized
146gb - 380gb +)<-- Media servers backing up self
Policy 5 = Scheduled 12:00am (10hr. window) - 8 Clients (Large Sized
146gb - 380gb +)<-- Media servers backing up self

Had errors that prevented the completion of scheduled policy backups on
multiple occasions. Now all scheduled jobs do not start at scheduled
times, they all start @ 12:00am. I assume this is because they already
ran earlier in the day (AM)...

My question is: Is there a way to trick NB 5.0 into thinking the jobs
have not run, so I can get the jobs back on schedule??? During full
backups I get a lot of network errors and job failures, during
incrementals I have successful completions. This appears to be related
to saturated 100mb full duplex switched network connection (i.e. 48
Clients/Media Servers all trying to communicate with Master Server)



Steve McAllister
Network/Systems Administrator
Orlando Regional Healthcare
---smcallister@orhs_org---Change _ to .