Cluster node just takes TCP/IP address, which has no relationship whith used management classess/copy groups. TCP/IP address is important just for communication during backup/restore operations, but not for storing data on TSM server.
________________________________________ From: ADSM: Dist Stor Manager [ads...@vm.marist.edu] On Behalf Of Rick Adamson [rickadam...@winn-dixie.com] Sent: Friday, April 16, 2010 10:38 PM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] Tcp/ip address not correctly associated to cluster node Am I missing something, If it uses the node that actively owns the cluster instance for the shared resource backups don't you risk duplicating backup data? Since the shared data could actually be stored by each node when they own the instance. At least that has been my experience, I use a separate TSM node and services for the clustername. ~Rick Adamson Sr. Systems Engineer Jacksonville, FL. -----Original Message----- From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of Lee, Gary D. Sent: Friday, April 16, 2010 3:11 PM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] Tcp/ip address not correctly associated to cluster node Thanks dwight. Don't know why I didn't see that. Must be time to go home. Think the brain needs a recharge. Gary Lee Senior System Programmer Ball State University phone: 765-285-1310 -----Original Message----- From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of Dwight Cook Sent: Friday, April 16, 2010 2:54 PM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] Tcp/ip address not correctly associated to cluster node If you want to force it to use the cluster ip for the cluster node, set the tcpclientaddress in the dsm.opt file used by the cluster node client acceptor & scheduler... but if those follow the cluster OK, it really shouldn't matter if they use the cluster address or the address of the server currently serving the cluster since they technically are one and the same... -----Original Message----- From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of Lee, Gary D. Sent: Friday, April 16, 2010 1:43 PM To: ADSM-L@VM.MARIST.EDU Subject: [ADSM-L] Tcp/ip address not correctly associated to cluster node Microsoft windows 2008, tsm client 6.2 tsmserver 5.5.4. under suse sles9 under zvm 5.3. We have a two node cluster with clustername sqltestcluster. There is one group (win 2008 no longer refers to them as groups) called sqltsmcluster. Cluster nodes are called sqltestcl01 and sqltestcl02. Sqltestcl01 and 02 back up local file resourses fine. Tried to create a cluster tsm node called sqltestcluster to match the cluster name. Defined all the schedulers, and acceptors. Services fail over correctly. However, the ip address for the cluster is never associated with tsm node sqltsmcluster. It gets its ip address as whichever node is active. Yes, there is a network name and ip address resource defined within the group sqltsmcluster. I am at a loss. Where is the link established between the tsm node_name and the tcp/ip addresss resource which moves between cluster nodes? Thanks for any help. Gary Lee Senior System Programmer Ball State University phone: 765-285-1310 = Please consider the environment before printing this Email. CONFIDENTIALITY AND WAIVER: The information contained in this electronic mail message and any attachments hereto may be legally privileged and confidential. The information is intended only for the recipient(s) named in this message. If you are not the intended recipient you are notified that any use, disclosure, copying or distribution is prohibited. If you have received this in error please contact the sender and delete this message and any attachments from your computer system. We do not guarantee that this message or any attachment to it is secure or free from errors, computer viruses or other conditions that may damage or interfere with data, hardware or software.