Another thing we do is deactivate (upd sch xxxxxx t=a active=n) any admin
schedules that may try to run after coming back up, and we unplug the network
cable to prevent clients from checking in before we can get in to disable
schedules. Once the server seems to OK without sessions, we plug the network
cable in, enable sessions, and if that goes OK, reactivate admin schedules. 

-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of
Stapleton, Mark
Sent: Wednesday, March 05, 2008 11:40 AM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Re: [ADSM-L] Upgrade 5.2.3 to 5.5 directly

From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of
Schneider, John
> It has become a habit of mine, on any major upgrade of the TSM server,
> to start the TSM server in the foreground first and watch for unusual
> messages.  Then if everything comes up fine, halt it and start it
again
> in the background.

Excellent advice. Never assume that everything is both hunky and dorey
until you've seen the server start-up messages.
 
--
Mark Stapleton
CDW Berbee
System engineer
7145 Boone Avenue North, Suite 140
Brooklyn Park MN 55428-1511
763-592-5963
www.berbee.com

-----------------------------------------
Confidentiality Notice:
The information contained in this email message is privileged and
confidential information and intended only for the use of the
individual or entity named in the address. If you are not the
intended recipient, you are hereby notified that any dissemination,
distribution, or copying of this information is strictly
prohibited. If you received this information in error, please
notify the sender and delete this information from your computer
and retain no copies of any of this information.