Gary,

Have you included clusternode yes in the cluster.opt file for each logical
node on the cluster.  One option is to create a schedule for each logical
drive shared by the cluster.  Once you create the schedule for each drive on
each node you can then add the generic service to the cluster administrator.
Ex.. I have a cluster server called MECLUSTER, It has two nodes that compose
the cluster.  ME1 & ME2  I must create a clustere.opt clusterf.opt
clusterg.opt.....so on and so on for each logical cluster drive. This
schedule must be repeated for each node that can take ownership of the
cluster.

 Once you create the schedule for each cluster logical drive you are backing
up,  then you have to go back and create the generic service for each
schedule using cluster administrator.  This will allow failover to occur if
one of the nodes has a problem.   I used 3.1.0.8, on gotcha is that you must
reboot the server after installation of 3.1.0.8,  I had a problem of
schedule not recognizing the clusternode yes option.  There is a good
MS_Cluster.PDF that will provide detailed descriptions on installation.

Remember to use the new options for cluster server.

D:\adsm\baclient>dsmcutil install /name:"ADSM_F /clientdir:d:\adsm\baclient
/optfile:d:\adsm\baclient\clusterf.opt /group:pfilecluster /clusternode:yes
/node:pfilecluster_f /password:pfilecluster_f

I did not use the /autostart:yes option because I have the NT Cluster
Administrator handling that option.

Good Luck

Arturo Lopez




        -----Original Message-----
        From:   Gary Ison [SMTP:Gary.Ison AT MAIL.STATE.KY DOT US]
        Sent:   Wednesday, March 22, 2000 4:17 PM
        To:     ADSM-L AT VM.MARIST DOT EDU
        Subject:        Help on Backing Up Clustered Disks or Why are disks
not visible t o BS client

        Hi folks,

                I'm looking for help on why certain local drives are not
visible to
        the BA client.  The platform is NT 4.0, unknown SP level, with 8
local disks
        defined (C, E-K) with full control access by the system account.
When the
        BA GUI is started, only the C and E drives show as local drives.
The drives
        can be backed up by the command line client using the syntax "sel
x:\*
        -su=yes".  I am told that the drives F-K are defined to the
Microsoft disk
        clustering software.

                I'm running Tivoli client level 3.7.1.0 on the client.  The
options
        file contains entries for a specific directory backup and exclude
all other
        directories, i. e.

                        Exclude F:\...\*
                        Include F:\sub-dir\...\*

        in this sequence.

                My questions are 1) does anybody have any experience with
this type
        of environment; 2) is anyone aware of any agent software that can
interface
        with the clustering software; 3) does anyone have any answers to why
a disk
        is invisible to the BA client outside the clustering scenario?

                Any help would be greatly appreciated and as an added
incentive (?),
        I have about 50 *SM scripts I'll give to the winning solution(s).

                Thanks in advance for the many replies I'm sure I'll
receive.

                Gary L. Ison
                Governor's Office for Technology
                101 Cold Harbor Drive
                Frankfort, Ky.   40601
                Phone:  (502) 564-8724
                    Fax:  (502) 564-6856
        E-mail: Gary.Ison AT mail.state.ky DOT us
<mailto:Gary.Ison AT mail.state.ky DOT us>