I've seen people do a trick for this, where they set up the service on the
secondary node to use a local (non clustered) config file.
Once the password is cached, they use dsmcutil to update the service to use the
location for the config and password file that corresponds to the resource
group.
I don't know if I still have an example of the script that does this.
Thanks,
[RC]
On Nov 18, 2010, at 10:00 AM, Shawn Drew <shawn.drew AT AMERICAS.BNPPARIBAS DOT
COM> wrote:
They advise this to so that the cluster dsm.opt will be available on the
other node when there is a failover.
My main problem with this is that you need to execute a failover to get
this all configured for the first time,
(To install the scheduler service on the failover node)
which isn't acceptable in my environment.
We keep everything in the baclient directory and just make sure the opt
files are exactly the same on both nodes.
Regards,
Shawn
________________________________________________
Shawn Drew
Internet
tsm-forum AT BACKUPCENTRAL DOT COM
Sent by: ADSM-L AT VM.MARIST DOT EDU
11/18/2010 02:07 AM
Please respond to
ADSM-L AT VM.MARIST DOT EDU
To
ADSM-L
cc
Subject
[ADSM-L] DSM.OPT file location for backing up cluster resources.
Hello,
I was reading this document about configure BA client for cluster
environment.
http://publib.boulder.ibm.com/tividd/td/TSMC/GC32-0788-02/en_US/HTML/ans60021.htm
1) For backing up cluster resources, the document recommends to.locate the
option file on one of the disk drives that are owned by the cluster group.
Question : When installing TDP for Exchange and to backup the virtual
Exchange server, I assume it is also advisable to place the dsm.opt file
in one of the disk drives owned by the cluster group. Is this correct?
Thanks
+----------------------------------------------------------------------
|This was sent by cc1702004 AT gmail DOT com via Backup Central.
|Forward SPAM to abuse AT backupcentral DOT com.
+----------------------------------------------------------------------
This message and any attachments (the "message") is intended solely for
the addressees and is confidential. If you receive this message in error,
please delete it and immediately notify the sender. Any use not in accord
with its purpose, any dissemination or disclosure, either whole or partial,
is prohibited except formal approval. The internet can not guarantee the
integrity of this message. BNP PARIBAS (and its subsidiaries) shall (will)
not therefore be liable for the message if modified. Please note that certain
functions and services for BNP Paribas may be performed by BNP Paribas RCC, Inc.
|
