Re: Tcp/ip address not correctly associated to cluster node

2010-04-17 Thread Grigori Solonovitch
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 St

Re: Tcp/ip address not correctly associated to cluster node

2010-04-16 Thread Rick Adamson
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

Re: Tcp/ip address not correctly associated to cluster node

2010-04-16 Thread Lee, Gary D.
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

Re: Tcp/ip address not correctly associated to cluster node

2010-04-16 Thread Dwight Cook
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 curren