OES Linux, I think is what he was referring to, however, the
instructions are still correct.
First you setup TSM for each base node, and have a stanza in the
/opt/tivoli/tsm/client/ba/bin/dsm.sys file that has "clusternode no"
set, and a DOMAIN statement that includes the file system(s) that are
NOT shared.
Second you setup another node that covers the clustered volumes and in
the dsm.sys file add a stanza (that looks the same on both nodes) that
includes "clusternode yes", a domain statement with the share
filesystem(s), and http tcpip address, and port number lines that are
unique to the cluster. We normally use 1583 for clustered dsmcad
instances, 1503 for the client tcp port. Etc.
Then in your cluster configs you include scripts that stop/start/restart
all relevant tsm services. For example when the failover to nodeb
happens you may need to restart the base node dsmc services just to be
sure they pickup any slight differences in IP configs.
I have some example AIX cluster dsm.sys files, that will work just about
the same on Linux if you'd like to email me directly. It's been a long
time since I've worked with OES linux.
See Ya'
Howard
> -----Original Message-----
> From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf
> Of Grigori Solonovitch
> Sent: Monday, October 26, 2009 2:43 AM
> To: ADSM-L AT VM.MARIST DOT EDU
> Subject: Re: [ADSM-L] OES Linus cluster question
>
> Hello Robert,
>
> You need to create dedicated TSM Scheduler for Node_Cluster using
> /media/nss/APPS/tivoli/cluster.opt with "clusternode yes" and put TSM
> Scheduler service into the same resource group.
>
> MS Cluster will start/stop TSM Scheduler during failover operation
> (stop on inactive node and start on active node). So you can run
> backups/restores in any case and it does not matter where resource
> group is.
>
> Regards,
>
>
>
> Grigori G. Solonovitch
>
>
>
> Senior Technical Architect
>
>
>
> Information Technology Bank of Kuwait and Middle East
> http://www.bkme.com
>
>
>
> Phone: (+965) 2231-2274 Mobile: (+965) 99798073 E-Mail:
> G.Solonovitch AT bkme DOT com
>
>
>
> Please consider the environment before printing this Email
>
>
>
>
>
> -----Original Message-----
> From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf
> Of Robert Ouzen Ouzen
> Sent: Monday, October 26, 2009 10:31 AM
> To: ADSM-L AT VM.MARIST DOT EDU
> Subject: [ADSM-L] OES Linus cluster question
>
>
>
> Hello.
>
>
>
> I'm looking for getting TSM configured in an OES2 Cluster environment.
> We currently have a two node (NodeA NodeB) sharing a NSS volume ,
when
> one node is active (NodeA).
>
>
>
> Nodea and NodeB backup local volume , I created an another node
> (Node_cluster) to backup the NSS volume.
>
>
>
>
>
>
>
> I added in each dsm.sys the instance for Node_cluster and load for
> NodeA
>
>
>
> 1. Dsmcad (to backup local FS , local dsm.opt)
>
>
>
> 2. Dsmcad -optfile=/media/nss/APPS/tivoli/cluster.opt
>
>
>
>
>
>
>
> For NodeB I load only Dsmcad (to backup local FS , local dsm.opt), I
> have on this node exactly the same configuration to backup the NSS
> volume as NodeA (in dsm.sys the instance of Node_cluster too).
>
>
>
>
>
>
>
> My question is how I can manage in case of failure of NodeA when NodeB
> became active the process of TSM (Dsmcad -
> optfile=/media/nss/APPS/tivoli/cluster.opt ) to be load automatic to
> continue to backup the NSS volume ??????
>
>
>
>
>
>
>
> T.I.A Regards
>
>
>
>
>
>
>
> Robert Ouzen
>
>
>
>
>
>
>
>
>
>
>
> Please consider the environment before printing this Email.
>
> ________________________________
> "This email message and any attachments transmitted with it may
contain
> confidential and proprietary information, intended only for the named
> recipient(s). If you have received this message in error, or if you
are
> not the named recipient(s), please delete this email after notifying
> the sender immediately. BKME cannot guarantee the integrity of this
> communication and accepts no liability for any damage caused by this
> email or its attachments due to viruses, any other defects,
> interception or unauthorized modification. The information, views,
> opinions and comments of this message are those of the individual and
> not necessarily endorsed by BKME."
|
