All,

Call me silly (and some of you will) but my problem was a combination of
administrator oversights (mainly mine) and a full transaction log.

Trap for new players - when running Windows 2K Clustering, and you want to
launch the second instance of TSM (Server2) on the second node of the
cluster, make sure you specify the second instance. When starting the
server through "DSMSERV", it looks like it will try and launch the first
instance it comes across in the registry, which in this case is instance #1
(Server1). The disk resources for Server1 will not be seen by the second
node in the cluster, so funnily enough won't be able to see the
dsmserv.dsk.

Solution - run "DSMSERV -k Server2" to specify the second instance of TSM
in the registry. Once I did this the server tried to start up but gave
errors regarding the transaction log being full. I extended the log,
restarted the server and all was well (after a full db backup).

Just thought I would share the experience.

Regards,

------------------------------------------------------------------------------

Graham Trigge
IT Technical Specialist
Server Support
Telstra Australia

Office:  (02) 8272 8657
Mobile: 0409 654 434





             Richard Sims
             <rbs AT BU DOT EDU>
             Sent by: "ADSM:                                            To
             Dist Stor                 ADSM-L AT VM.MARIST DOT EDU
             Manager"                                                   cc
             <[email protected]
             .EDU>                                                 Subject
                                       Re: Help!! dsmserv.dsk not readable

             14/02/2004 12:49
             AM


             Please respond to
             "ADSM: Dist Stor
                 Manager"
             <[email protected]
                   .EDU>






>I am running Windows 2K cluster, TSM 4.2. Early yesterday morning the
>server crashed and would not start (on either node of the cluster). When I
>try and start it manually I get:
>      "ANR0212E. Unable to read disk definition file: dsmserv.dsk"
...

The reason for the crash may be spilling over into the reason you cannot
restart.  In many cases, a failing server will write a dsmserv.err (or
similarly named error log) in its server directory, giving some indication
of cause.  I would check your system for general environmental health
problems, such as full disk partitions or disk usability problems (which
would include the server home directory, the db and recovery log volumes,
and the stgpool disk volumes).  We hope you were using TSM mirroring, to
improve your chances of restarting without db recovery.

   Richard Sims  http://people.bu.edu/rbs