Re: Clustered Mount points don't show up as clustered in TSM
Hi, File space rename? Not if you configure the ITSM ba client for the cluster node(s) correctly! Clustercontroler A will have all its drives stored under \\A\drive$ Clustercontroler B will have all its drives stored under \\A\drive$ The virtual server(s) will store all there data under \\clustername\drive$\mp . One of my clusters. Cluster controlers cln021 en cln022, clustername cluster02 and (one of its) virtual server names fs021 Virtual server FS021 \\cluster02\f$ 1 WinNTNTFS Yes 8,628.6 50.9 FS021 \\cluster02\f$\users12 WinNTNTFS Yes258,938. 99.4 FS021 \\cluster02\f$\users23 WinNTNTFS Yes258,938. 75.3 F:\adsm\DSM.OPT nodenamenuwnlfs021 HTTPPORT1582 CLUSTERNODE YES CLUSTERDISKSONLYNO Clustercontroler A CLN021 \\cln021\c$1 WinNTNTFS Yes34,718.6 33.6 CLN021 SYSTEM 2 WinNTSYSTEM Yes 0.0 0.0 SERVICES CLN021 SYSTEM 3 WinNTSYSTEM Yes 0.0 0.0 STATE CLN021 ASR4 WinNTNTFS Yes 0.0 0.0 C:\win32app\ibm\adsm\baclient\dsm.opt DOMain C: domain systemservices domain systemstate clusternode no CLUSTERDISKSONLYYes Clustercontroler B CLN022 \\cln022\c$1 WinNTNTFS Yes34,718.6 39.6 CLN022 SYSTEM 2 WinNTSYSTEM Yes 0.0 0.0 SERVICES CLN022 SYSTEM 3 WinNTSYSTEM Yes 0.0 0.0 STATE CLN022 ASR4 WinNTNTFS Yes 0.0 0.0 C:\win32app\ibm\adsm\baclient\dsm.opt DOMain C: domain systemservices domain systemstate clusternode no CLUSTERDISKSONLYYes Regards, Karel -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of TSM_User Sent: vrijdag 12 mei 2006 1:36 To: ADSM-L@VM.MARIST.EDU Subject: Re: Clustered Mount points don't show up as clustered in TSM Karel, How do you deal with the fact that the mount point name changes when the cluster groups moves from one node to another? We were thinking about having two seperate dsm.opt files. Each would have the domain statments that list the mount point names based on the server name. Then we were going to have a *.bat file run as a preschedule command that would rename the mount point's file space name on the TSM server so that the data always got backed up to the same file space no matter what server the mount point was on. Did you do anything like this? Or, do you just let the mount points backup to two different filespaces. Remember the file space name has the complete path in it which includes the server name which will make it look like a different mount point based on what server it is mounted from. Kyle "Bos, Karel" <[EMAIL PROTECTED]> wrote: Hi, Read about it after the my first Windows 2003 cluster server, with mounted disks, as ITSM back-up client. Normal clusters I had done that before, so I did the standard config: - Install BA client on the cluster controlers; - Setup the back-up of the clustercontrolers (clusternode=no and domain only local stuff); - Setup cluster node (clusternode=yes and only cluster stuff). And the last would not work as before. Mountpoint are on windows local so the back-up would create \\controlereA\mp and after the switch \\controleB\mp. After a while I though lets look in the change history of the newest ITSM client at that time and found the (for me) new option CLUSTERDISKSONLY and some example combinations of CLUSTERNODE YES/No CLUSTERDISKSONLY NO/Yes Now I use the CLUSTERNODE YES CLUSTERDISKSONLY NO And define every mp on the clusternode. Regards, Karel -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of TSM_User Sent: donderdag 11 mei 2006 0:42 To: ADSM-L@VM.MARIST.EDU Subject: Re: Clustered Mount points don't show up as clustered in TSM It looks like this option is used to allow the local disks to show up as well when you have "CLUSTERNODE YES" in the dsm.opt file. This may get us to a point where we can move from backing up the mount points on one node in the cluster to backing them up under the node for the cluster group. However, our real problem still sits with how the mountpoints themselves show up to the OS. The mount point
Re: Clustered Mount points don't show up as clustered in TSM
I appreciate you going back and forth with me on this but I think you are missing my point. This isn't a TSM configuration issue. The mount points themselves have been created by this customer and they have the name of the physical server in them and that changes when the cluster groups move from one node to another node in the cluster. This is completey outside of TSM. The drives are fine. They have the virtual server name in their path, they show up as clustered drives and I am backing them as they should be with the TSM BAClient. My main question is do you have mount points on your cluster that uses VVM? If you do can you open the BAClient that lists the mount points. Then go to View | File Detatils. See if in the path TSM sees for the mountpoints you see the physical server name or the virtual server name. If you see the virtual server name then I know that this customer of mine has something configured incorrectly in VVM and if I saw a screen shot of what you see then I can tell them they have a config issue in VVM. If you see your physical server name and not your virtual server name then you will see my delima because that name in that path will change when you move the group to a different node in the cluster. When the path changes, the filespace name that TSM sees changes and then when the data is backed up on that node it will run another first time backup of all the data. It is for the mount points alone that we are looking at the rename script. Kyle "Bos, Karel" <[EMAIL PROTECTED]> wrote: Hi, File space rename? Not if you configure the ITSM ba client for the cluster node(s) correctly! Clustercontroler A will have all its drives stored under \\A\drive$ Clustercontroler B will have all its drives stored under \\A\drive$ The virtual server(s) will store all there data under \\clustername\drive$\mp . One of my clusters. Cluster controlers cln021 en cln022, clustername cluster02 and (one of its) virtual server names fs021 Virtual server FS021 \\cluster02\f$ 1 WinNT NTFS Yes 8,628.6 50.9 FS021 \\cluster02\f$\users1 2 WinNT NTFS Yes 258,938. 99.4 FS021 \\cluster02\f$\users2 3 WinNT NTFS Yes 258,938. 75.3 F:\adsm\DSM.OPT nodename nuwnlfs021 HTTPPORT 1582 CLUSTERNODE YES CLUSTERDISKSONLY NO Clustercontroler A CLN021 \\cln021\c$ 1 WinNT NTFS Yes 34,718.6 33.6 CLN021 SYSTEM 2 WinNT SYSTEM Yes 0.0 0.0 SERVICES CLN021 SYSTEM 3 WinNT SYSTEM Yes 0.0 0.0 STATE CLN021 ASR 4 WinNT NTFS Yes 0.0 0.0 C:\win32app\ibm\adsm\baclient\dsm.opt DOMain C: domain systemservices domain systemstate clusternode no CLUSTERDISKSONLY Yes Clustercontroler B CLN022 \\cln022\c$ 1 WinNT NTFS Yes 34,718.6 39.6 CLN022 SYSTEM 2 WinNT SYSTEM Yes 0.0 0.0 SERVICES CLN022 SYSTEM 3 WinNT SYSTEM Yes 0.0 0.0 STATE CLN022 ASR 4 WinNT NTFS Yes 0.0 0.0 C:\win32app\ibm\adsm\baclient\dsm.opt DOMain C: domain systemservices domain systemstate clusternode no CLUSTERDISKSONLY Yes Regards, Karel -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of TSM_User Sent: vrijdag 12 mei 2006 1:36 To: ADSM-L@VM.MARIST.EDU Subject: Re: Clustered Mount points don't show up as clustered in TSM Karel, How do you deal with the fact that the mount point name changes when the cluster groups moves from one node to another? We were thinking about having two seperate dsm.opt files. Each would have the domain statments that list the mount point names based on the server name. Then we were going to have a *.bat file run as a preschedule command that would rename the mount point's file space name on the TSM server so that the data always got backed up to the same file space no matter what server the mount point was on. Did you do anything like this? Or, do you just let the mount points backup to two different filespaces. Remember the file space name has the complete path in it which includes the server name which will make it look like a different mount point based on what server it is mounted from. Kyle "Bos, Karel" wrote: Hi, Read about it after the my first Windows 2003 cluster server, with mounted disks, as ITSM back-up client. Normal clusters I had done that before, so I did the standard config: - Install BA client on the cluster controlers; - Setup the back-up of the clustercontrolers (clusternode=no and domain only local stuff); - Setup cluster node (clusternode=yes and only cluster stuff). And the last would not work as before. Mountpoint are on windows local so the back-up would create \\controlereA\mp and after the switch \\controleB\mp. After a while I though lets look in the change history of the newest ITSM client at that time and found the (for me) new option CLUSTERDISKSONLY and some example combinations of CLUSTERNODE YES/No CLUSTERDISKSONLY NO/Yes Now I use the CLUSTERNODE YES CLUSTERDISKSONLY NO And define every mp on the clusternode. Regards, Karel -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PR
TDP oddity with an extra registered client?
I've got: TSM 5.1.9.6 server on AIX 5.2-ML7 TDP 5.2 for MSSQL (Windows 2003 Server running MS SQL Server 2000) The strange thing is: tsm: SERVER>q lic [...] Number of TDP for MS SQL Server in use: 3 [...] But I only have two TDP 5.2 clients. How can I determine a list of all 3 registered TDP clients? And how can I delete the offending client? Or does the TSM server count as a TDP client for licensing purposes? Any suggestions or insight welcome. Thanks! -Dan
Re: TDP oddity with an extra registered client?
On Saturday 13 May 2006 21:37, Dan Foster wrote: > I've got: > > TSM 5.1.9.6 server on AIX 5.2-ML7 > TDP 5.2 for MSSQL (Windows 2003 Server running MS SQL Server 2000) > > The strange thing is: > > tsm: SERVER>q lic > [...] > Number of TDP for MS SQL Server in use: 3 > [...] > > But I only have two TDP 5.2 clients. > > How can I determine a list of all 3 registered TDP clients? select LICENSE_NAME, NODE_NAME from LICENSE_DETAILS Stef
Re: TDP oddity with an extra registered client?
Hot Diggety! Stef Coene was rumored to have written: > > tsm: SERVER>q lic > > [...] > > Number of TDP for MS SQL Server in use: 3 > > [...] > > > > But I only have two TDP 5.2 clients. > > > > How can I determine a list of all 3 registered TDP clients? > select LICENSE_NAME, NODE_NAME from LICENSE_DETAILS Ah! Thanks. As I suspected, the problem was due to me making a silly configuration file error without thinking when I first installed it on a TDP client. (It registered under the wrong name.) I changed config file to use the proper name immediately after I realized my error... but too late, wrong name was already registered in TSM. Does anybody know how I can delete the TDP registration for the incorrectly registered client? tsm> select LICENSE_NAME, NODE_NAME from LICENSE_DETAILS MSSQLVN01-DB MSSQLVN02-DB MSSQLW3USPHX1 [...] VN01 and VN02 is correct. W3USPHX1 was the mistake. tsm: GBLX-PHX>select * from license_details where node_name='W3USPHX1' LICENSE_NAME NODE_NAME LAST_USED TRYBUY -- -- -- MSSQLW3USPHX1 2006-04-06 FALSE 01:31:02.00 MGSYSLAN W3USPHX1 2006-05-13 FALSE 19:41:46.00 So I need to delete MSSQL license registration for W3USPHX1 only, but leave the MGSYSLAN license registration alone. Is there a way to do that without having to delete W3USPHX1 entirely then recreate and re-backup its TSM data? -Dan
Re: TDP oddity with an extra registered client?
On Saturday 13 May 2006 23:02, Dan Foster wrote: > Does anybody know how I can delete the TDP registration for the > incorrectly registered client? Don't worry. The license information in TSM has nothing to do with how many licenses you have to buy. You can recount the number of licenses with audit licens. Stef