I've probably a much smaller site than you, Paul, and a bit of a
different NBU client update philosophy.
My test philosophy is not to test, but to update simple, non-critical
machines first, progress through others, and wait almost as long as
possible on production/critical machines. ;-)
As to rebooting, I'm flexible with my machine owners. We have two
plans. I tell them they can avoid a reboot if they update when there is
no backup/restore activity *and* they have shutdown the NetBackup Client
Service. With the 2nd plan, I'll be happy to help them through any
problems they might have *if* they comply with the first suggestion
*and* they reboot before applying the update and reboot again after the
update (at least once!). Of course, I'll help them anyway, but at
least before Win2003, I believe a reboot is your friend, even if
difficult to do on some machines. It's not necessarily required by
NetBackup, it simply tells them, at good and appropriate times, that
their machine can (is able to) boot ... and that boot-time message or
problem was due to that other software/hardware change, not NetBackup.
Thanks for your activity on the NetBackup mailing list ...
cheers, wayne
Paul Keating wrote, in part, on 4/27/2005 2:17 PM:
> I'm prepping to push out 5.0 MP4 to the windows clients in my env.
>
> Reading the readme, it appears that the clients only need to be
> rebooted IF one of the files being replaced as part of the patch are
> inuse at the time of the patch.
>
> So....assuming no backups are running when the patch is pushed, then
> in theory, none of the machines "really" need to be rebooted.....
>
> In any case that requires a reboot, the words "in use" will appear in
> the log, referring to the "in use" file.
>
> Comments?
>
> Also, what process do most of you use to patch, with respect to
> testing before the rollout.
>
> Here we are testing backup and restore of every platform (Solaris,
> 2000, 2003, etc) in the configuration with our NBU test server at the
> new release and test clients at the old release, then again with
> client and server at new release, then repeating these tests on any
> applications that differ from the standard OS + data (Oracle,
> Exchange, MSCS, SCS, etc, etc)
>
> Paul
|
