Re: Client : MS Cluster active - active
I'm not looking for that to occur. In our case we could not complete a backup of both devices from a single node in our backup window. -Original Message- From: Redell, Greg S. [mailto:[EMAIL PROTECTED] Sent: Thursday, October 16, 2003 11:22 AM To: [EMAIL PROTECTED] Subject: Re: Client : MS Cluster active - active Try running a scheduler in each cluster group. That way the backups will happen even if the groups are not on their normal nodes. -Original Message- From: Ochs, Duane [mailto:[EMAIL PROTECTED] Sent: Thursday, October 16, 2003 9:55 AM To: [EMAIL PROTECTED] Subject: Re: Client : MS Cluster active - active We did a test and failed the drives from one cluster node to the other and the same results, the next scheduled backup only backed up the base directories with no errors. Previous day 1.4 million files scanned 21,000+ backed up, day the drives were failed only 10 files scanned 1 backed up and no error messages. Scheduler service is not defined in the cluster service, Because the backup schedules for these systems would not complete in 12 hours if both devices were backed up from one of the two cluster nodes. Duane -Original Message- From: John Monahan [mailto:[EMAIL PROTECTED] Sent: Monday, October 13, 2003 2:17 PM To: [EMAIL PROTECTED] Subject: Re: Client : MS Cluster active - active ADSM: Dist Stor Manager [EMAIL PROTECTED] wrote on 10/13/2003 09:44:48 AM: TSM Server 5.1.6.2 ( AIX) TSM Client 5.1.5.15 (W2K cluster) Cluster node a - Has drive f$ Cluster node b - Has drive g$ To apply patches to the systems, nodea f$ is failed to node b, patches applied to nodea and rebooted, f$ and g$ are failed to node a, Node b then gets patch and rebooted then g$ is failed back to node b. At this point, backups can not be performed on either f$ or g$, only the top level directories are backed up and no failures are indicated in the Client log or the TSM server activity log. Only top level directories are backed up on f: and g:? How do you know this? Each node has a scheduler, If I restart the schedulers the scheduled backups run fine at next schedule. What schedmode are you using? Is your scheduler service defined in cluster administrator? What if you do a failover without doing the patches part, does the same thing happen?
Re: Client : MS Cluster active - active
We did a test and failed the drives from one cluster node to the other and the same results, the next scheduled backup only backed up the base directories with no errors. Previous day 1.4 million files scanned 21,000+ backed up, day the drives were failed only 10 files scanned 1 backed up and no error messages. Scheduler service is not defined in the cluster service, Because the backup schedules for these systems would not complete in 12 hours if both devices were backed up from one of the two cluster nodes. Duane -Original Message- From: John Monahan [mailto:[EMAIL PROTECTED] Sent: Monday, October 13, 2003 2:17 PM To: [EMAIL PROTECTED] Subject: Re: Client : MS Cluster active - active ADSM: Dist Stor Manager [EMAIL PROTECTED] wrote on 10/13/2003 09:44:48 AM: TSM Server 5.1.6.2 ( AIX) TSM Client 5.1.5.15 (W2K cluster) Cluster node a - Has drive f$ Cluster node b - Has drive g$ To apply patches to the systems, nodea f$ is failed to node b, patches applied to nodea and rebooted, f$ and g$ are failed to node a, Node b then gets patch and rebooted then g$ is failed back to node b. At this point, backups can not be performed on either f$ or g$, only the top level directories are backed up and no failures are indicated in the Client log or the TSM server activity log. Only top level directories are backed up on f: and g:? How do you know this? Each node has a scheduler, If I restart the schedulers the scheduled backups run fine at next schedule. What schedmode are you using? Is your scheduler service defined in cluster administrator? What if you do a failover without doing the patches part, does the same thing happen?
Re: Client : MS Cluster active - active
Try running a scheduler in each cluster group. That way the backups will happen even if the groups are not on their normal nodes. -Original Message- From: Ochs, Duane [mailto:[EMAIL PROTECTED] Sent: Thursday, October 16, 2003 9:55 AM To: [EMAIL PROTECTED] Subject: Re: Client : MS Cluster active - active We did a test and failed the drives from one cluster node to the other and the same results, the next scheduled backup only backed up the base directories with no errors. Previous day 1.4 million files scanned 21,000+ backed up, day the drives were failed only 10 files scanned 1 backed up and no error messages. Scheduler service is not defined in the cluster service, Because the backup schedules for these systems would not complete in 12 hours if both devices were backed up from one of the two cluster nodes. Duane -Original Message- From: John Monahan [mailto:[EMAIL PROTECTED] Sent: Monday, October 13, 2003 2:17 PM To: [EMAIL PROTECTED] Subject: Re: Client : MS Cluster active - active ADSM: Dist Stor Manager [EMAIL PROTECTED] wrote on 10/13/2003 09:44:48 AM: TSM Server 5.1.6.2 ( AIX) TSM Client 5.1.5.15 (W2K cluster) Cluster node a - Has drive f$ Cluster node b - Has drive g$ To apply patches to the systems, nodea f$ is failed to node b, patches applied to nodea and rebooted, f$ and g$ are failed to node a, Node b then gets patch and rebooted then g$ is failed back to node b. At this point, backups can not be performed on either f$ or g$, only the top level directories are backed up and no failures are indicated in the Client log or the TSM server activity log. Only top level directories are backed up on f: and g:? How do you know this? Each node has a scheduler, If I restart the schedulers the scheduled backups run fine at next schedule. What schedmode are you using? Is your scheduler service defined in cluster administrator? What if you do a failover without doing the patches part, does the same thing happen?
Client : MS Cluster active - active
TSM Server 5.1.6.2 ( AIX) TSM Client 5.1.5.15 (W2K cluster) Cluster node a - Has drive f$ Cluster node b - Has drive g$ To apply patches to the systems, nodea f$ is failed to node b, patches applied to nodea and rebooted, f$ and g$ are failed to node a, Node b then gets patch and rebooted then g$ is failed back to node b. At this point, backups can not be performed on either f$ or g$, only the top level directories are backed up and no failures are indicated in the Client log or the TSM server activity log. Each node has a scheduler, If I restart the schedulers the scheduled backups run fine at next schedule. Has anyone else experienced this ? Or maybe have an idea why I am seeing this . Duane Ochs Enterprise Computing Quad/Graphics Sussex, Wisconsin 414-566-2375 phone 414-917-0736 beeper [EMAIL PROTECTED] www.QG.com
Re: Client : MS Cluster active - active
ADSM: Dist Stor Manager [EMAIL PROTECTED] wrote on 10/13/2003 09:44:48 AM: TSM Server 5.1.6.2 ( AIX) TSM Client 5.1.5.15 (W2K cluster) Cluster node a - Has drive f$ Cluster node b - Has drive g$ To apply patches to the systems, nodea f$ is failed to node b, patches applied to nodea and rebooted, f$ and g$ are failed to node a, Node b then gets patch and rebooted then g$ is failed back to node b. At this point, backups can not be performed on either f$ or g$, only the top level directories are backed up and no failures are indicated in the Client log or the TSM server activity log. Only top level directories are backed up on f: and g:? How do you know this? Each node has a scheduler, If I restart the schedulers the scheduled backups run fine at next schedule. What schedmode are you using? Is your scheduler service defined in cluster administrator? What if you do a failover without doing the patches part, does the same thing happen?
Re: Client : MS Cluster active - active
Each time it has happened both systems eventually were rebooted and had the same results. 1) Blaster virus 2) security patches and 3) SP update. It occured each time and I do not always get notified when our Intel servers group performs these functions. We do not have the two schedulers configured as cluster services, but TSM is aware that they are a clustered system. I reviewed the dsmsched.log to find that only 4 files were scanned and 4 were backed up. Out of 1.4 million. Duane -Original Message- From: John Monahan [mailto:[EMAIL PROTECTED] Sent: Monday, October 13, 2003 2:17 PM To: [EMAIL PROTECTED] Subject: Re: Client : MS Cluster active - active ADSM: Dist Stor Manager [EMAIL PROTECTED] wrote on 10/13/2003 09:44:48 AM: TSM Server 5.1.6.2 ( AIX) TSM Client 5.1.5.15 (W2K cluster) Cluster node a - Has drive f$ Cluster node b - Has drive g$ To apply patches to the systems, nodea f$ is failed to node b, patches applied to nodea and rebooted, f$ and g$ are failed to node a, Node b then gets patch and rebooted then g$ is failed back to node b. At this point, backups can not be performed on either f$ or g$, only the top level directories are backed up and no failures are indicated in the Client log or the TSM server activity log. Only top level directories are backed up on f: and g:? How do you know this? Each node has a scheduler, If I restart the schedulers the scheduled backups run fine at next schedule. What schedmode are you using? Is your scheduler service defined in cluster administrator? What if you do a failover without doing the patches part, does the same thing happen?
Re: Client : MS Cluster active - active
I would put the TSM scheduler into cluster administrator, because that essentially stops/starts the scheduler service for you when you do a failover. Follow the instructions in one of the appendixes of the client manual. Should take care of the problem. __ John Monahan Senior Consultant Enterprise Solutions Computech Resources, Inc. Office: 952-833-0930 ext 109 Cell: 952-221-6938 http://www.compures.com Ochs, Duane [EMAIL PROTECTED] M To Sent by: ADSM: [EMAIL PROTECTED] Dist Stor cc Manager [EMAIL PROTECTED] Subject .EDU Re: Client : MS Cluster active - active 10/13/2003 02:30 PM Please respond to ADSM: Dist Stor Manager [EMAIL PROTECTED] .EDU Each time it has happened both systems eventually were rebooted and had the same results. 1) Blaster virus 2) security patches and 3) SP update. It occured each time and I do not always get notified when our Intel servers group performs these functions. We do not have the two schedulers configured as cluster services, but TSM is aware that they are a clustered system. I reviewed the dsmsched.log to find that only 4 files were scanned and 4 were backed up. Out of 1.4 million. Duane -Original Message- From: John Monahan [mailto:[EMAIL PROTECTED] Sent: Monday, October 13, 2003 2:17 PM To: [EMAIL PROTECTED] Subject: Re: Client : MS Cluster active - active ADSM: Dist Stor Manager [EMAIL PROTECTED] wrote on 10/13/2003 09:44:48 AM: TSM Server 5.1.6.2 ( AIX) TSM Client 5.1.5.15 (W2K cluster) Cluster node a - Has drive f$ Cluster node b - Has drive g$ To apply patches to the systems, nodea f$ is failed to node b, patches applied to nodea and rebooted, f$ and g$ are failed to node a, Node b then gets patch and rebooted then g$ is failed back to node b. At this point, backups can not be performed on either f$ or g$, only the top level directories are backed up and no failures are indicated in the Client log or the TSM server activity log. Only top level directories are backed up on f: and g:? How do you know this? Each node has a scheduler, If I restart the schedulers the scheduled backups run fine at next schedule. What schedmode are you using? Is your scheduler service defined in cluster administrator? What if you do a failover without doing the patches part, does the same thing happen?
netware client 5.1.5 cluster support
Hi *sm people: I have an issue with the latest Netware client 5.1.5 I have been waiting for the cluster support in the 5.1.5 client Now it seems I can not backup all clustered drives and NDS I see others have used nds: sys: vol1: etc I can not specify the drives to backup in the option file because this varies depending on the failover status of the clustered drives Does anyone have any ideas? Regards Dave
Re: netware client 5.1.5 cluster support
Hi Dave, I don't know the Netware Cluster but AFAIK you should use separate TSM client nodes for the local drives and each clustergroup (or whatever this is called in the Netware cluster) and its drives. Each TSM node has its own dsm.opt and uses as DOMAIN only the drives that are local to him. This way you don't have to deal with failover issues and available/unavailable drives on a cluster member. Mit freundlichen Grüßen, Met vriendelijke groeten, With best regards, Bien amicalement, CU/2, Dirk Billerbeck Dirk Billerbeck GE CompuNet Kiel Enterprise Computing Solutions Am Jaegersberg 20, 24161 Altenholz (Kiel), Germany Phone: +49 (0) 431 / 3609 - 117, Fax: +49 (0) 431 / 3609 - 190, Internet: dirk.billerbeck @ gecits-eu.com This email is confidential. If you are not the intended recipient, you must not disclose or use the information contained in it. If you have received this mail in error, please tell us immediately by return email and delete the document. [EMAIL PROTECTED]@VM.MARIST.EDU on 25.10.2002 10:32:28 Please respond to [EMAIL PROTECTED] Sent by: [EMAIL PROTECTED] To: [EMAIL PROTECTED] cc: Subject: netware client 5.1.5 cluster support -- Hi *sm people: I have an issue with the latest Netware client 5.1.5 I have been waiting for the cluster support in the 5.1.5 client Now it seems I can not backup all clustered drives and NDS I see others have used nds: sys: vol1: etc I can not specify the drives to backup in the option file because this varies depending on the failover status of the clustered drives Does anyone have any ideas? Regards Dave
Re: netware client 5.1.5 cluster support
Dirk, You are correct the Clustered drive is not an issue as you use a Clustergroup dsm.opt file What is still an issue is that to backup the NDS you must enter NDS: SYS: VOL1: in the DOMAIN statement As I do not have control of the Netware servers I want to backup any drive what ever it is called without checking each server every night to see if an Admin has created a new volume If you specify nothing in the DOMAIN statement the NDS does not get backed up If we could go back to the old way of doing things I could just use Domain All-Local NDS: this will backup the NDS and whatever drives are mounted Kind Regards Dave Dirk Billerbeck dirk.billerbeck@GECTo: [EMAIL PROTECTED] ITS-EU.COM cc: Sent by: ADSM: DistSubject: Re: netware client 5.1.5 cluster support Stor Manager [EMAIL PROTECTED] U 25/10/2002 11:51 Please respond to ADSM: Dist Stor Manager Hi Dave, I don't know the Netware Cluster but AFAIK you should use separate TSM client nodes for the local drives and each clustergroup (or whatever this is called in the Netware cluster) and its drives. Each TSM node has its own dsm.opt and uses as DOMAIN only the drives that are local to him. This way you don't have to deal with failover issues and available/unavailable drives on a cluster member. Mit freundlichen Grüßen, Met vriendelijke groeten, With best regards, Bien amicalement, CU/2, Dirk Billerbeck Dirk Billerbeck GE CompuNet Kiel Enterprise Computing Solutions Am Jaegersberg 20, 24161 Altenholz (Kiel), Germany Phone: +49 (0) 431 / 3609 - 117, Fax: +49 (0) 431 / 3609 - 190, Internet: dirk.billerbeck @ gecits-eu.com This email is confidential. If you are not the intended recipient, you must not disclose or use the information contained in it. If you have received this mail in error, please tell us immediately by return email and delete the document. [EMAIL PROTECTED]@VM.MARIST.EDU on 25.10.2002 10:32:28 Please respond to [EMAIL PROTECTED] Sent by: [EMAIL PROTECTED] To: [EMAIL PROTECTED] cc: Subject: netware client 5.1.5 cluster support -- Hi *sm people: I have an issue with the latest Netware client 5.1.5 I have been waiting for the cluster support in the 5.1.5 client Now it seems I can not backup all clustered drives and NDS I see others have used nds: sys: vol1: etc I can not specify the drives to backup in the option file because this varies depending on the failover status of the clustered drives Does anyone have any ideas? Regards Dave
Re: netware client 5.1.5 cluster support
Guys, Is the issue what you want to back up from the local node vs. the clustered volumes?. The reason I ask is the domain all-local nds: statement does work as long as the colon is included. At least it works on a standalone box, I need to try an NDS backup on a clustered node. What I'm still wrestling with is how to point to a separate optfile on a cluster volume. I keep getting invalid option optfile vol:\folder\file msg. I'd like to hear how you have thing set up for your clustergroup. Frost, Dave wrote: Dirk, You are correct the Clustered drive is not an issue as you use a Clustergroup dsm.opt file What is still an issue is that to backup the NDS you must enter NDS: SYS: VOL1: in the DOMAIN statement As I do not have control of the Netware servers I want to backup any drive what ever it is called without checking each server every night to see if an Admin has created a new volume If you specify nothing in the DOMAIN statement the NDS does not get backed up If we could go back to the old way of doing things I could just use Domain All-Local NDS: this will backup the NDS and whatever drives are mounted Kind Regards Dave Dirk Billerbeck dirk.billerbeck@GECTo: [EMAIL PROTECTED] ITS-EU.COM cc: Sent by: ADSM: DistSubject: Re: netware client 5.1.5 cluster support Stor Manager [EMAIL PROTECTED] U 25/10/2002 11:51 Please respond to ADSM: Dist Stor Manager Hi Dave, I don't know the Netware Cluster but AFAIK you should use separate TSM client nodes for the local drives and each clustergroup (or whatever this is called in the Netware cluster) and its drives. Each TSM node has its own dsm.opt and uses as DOMAIN only the drives that are local to him. This way you don't have to deal with failover issues and available/unavailable drives on a cluster member. Mit freundlichen Grüßen, Met vriendelijke groeten, With best regards, Bien amicalement, CU/2, Dirk Billerbeck Dirk Billerbeck GE CompuNet Kiel Enterprise Computing Solutions Am Jaegersberg 20, 24161 Altenholz (Kiel), Germany Phone: +49 (0) 431 / 3609 - 117, Fax: +49 (0) 431 / 3609 - 190, Internet: dirk.billerbeck @ gecits-eu.com This email is confidential. If you are not the intended recipient, you must not disclose or use the information contained in it. If you have received this mail in error, please tell us immediately by return email and delete the document. [EMAIL PROTECTED]@VM.MARIST.EDU on 25.10.2002 10:32:28 Please respond to [EMAIL PROTECTED] Sent by: [EMAIL PROTECTED] To: [EMAIL PROTECTED] cc: Subject: netware client 5.1.5 cluster support -- Hi *sm people: I have an issue with the latest Netware client 5.1.5 I have been waiting for the cluster support in the 5.1.5 client Now it seems I can not backup all clustered drives and NDS I see others have used nds: sys: vol1: etc I can not specify the drives to backup in the option file because this varies depending on the failover status of the clustered drives Does anyone have any ideas? Regards Dave -- Jim Kirkman AIS - Systems UNC-Chapel Hill 966-5884
Re: Netware Client 5.1.5 cluster support
Dean, et al. Talk about mixed results! There are three nodes in the test cluster here, each hosting at least one NSS volume. I've run backups on two of these using the domain all-local and/or the domain all-local nds: statement. One node backs up nds:, sys: and nss volume just fine. The other does not even attempt to back up the nss volume, doesn't even bring it up after the scan. I haven't checked with the NW admins to see if these guys are set up differently but that sure seem odd. Haven't gotten to clusternode options yet. Have you guys gotten any other responses on this? Frost, Dave wrote: Dirk, You are correct the Clustered drive is not an issue as you use a Clustergroup dsm.opt file What is still an issue is that to backup the NDS you must enter NDS: SYS: VOL1: in the DOMAIN statement As I do not have control of the Netware servers I want to backup any drive what ever it is called without checking each server every night to see if an Admin has created a new volume If you specify nothing in the DOMAIN statement the NDS does not get backed up If we could go back to the old way of doing things I could just use Domain All-Local NDS: this will backup the NDS and whatever drives are mounted Kind Regards Dave Dirk Billerbeck dirk.billerbeck@GECTo: [EMAIL PROTECTED] ITS-EU.COM cc: Sent by: ADSM: DistSubject: Re: netware client 5.1.5 cluster support Stor Manager [EMAIL PROTECTED] U 25/10/2002 11:51 Please respond to ADSM: Dist Stor Manager Hi Dave, I don't know the Netware Cluster but AFAIK you should use separate TSM client nodes for the local drives and each clustergroup (or whatever this is called in the Netware cluster) and its drives. Each TSM node has its own dsm.opt and uses as DOMAIN only the drives that are local to him. This way you don't have to deal with failover issues and available/unavailable drives on a cluster member. Mit freundlichen Grüßen, Met vriendelijke groeten, With best regards, Bien amicalement, CU/2, Dirk Billerbeck Dirk Billerbeck GE CompuNet Kiel Enterprise Computing Solutions Am Jaegersberg 20, 24161 Altenholz (Kiel), Germany Phone: +49 (0) 431 / 3609 - 117, Fax: +49 (0) 431 / 3609 - 190, Internet: dirk.billerbeck @ gecits-eu.com This email is confidential. If you are not the intended recipient, you must not disclose or use the information contained in it. If you have received this mail in error, please tell us immediately by return email and delete the document. [EMAIL PROTECTED]@VM.MARIST.EDU on 25.10.2002 10:32:28 Please respond to [EMAIL PROTECTED] Sent by: [EMAIL PROTECTED] To: [EMAIL PROTECTED] cc: Subject: netware client 5.1.5 cluster support -- Hi *sm people: I have an issue with the latest Netware client 5.1.5 I have been waiting for the cluster support in the 5.1.5 client Now it seems I can not backup all clustered drives and NDS I see others have used nds: sys: vol1: etc I can not specify the drives to backup in the option file because this varies depending on the failover status of the clustered drives Does anyone have any ideas? Regards Dave -- Jim Kirkman AIS - Systems UNC-Chapel Hill 966-5884
Client in Cluster.
Hi, Could TSM Client that is installing with TSM Server be used in a Microsoft Cluster Server or Is there a specific TSM Client for a Microsoft Cluster Server? Thanks in advance, Nazir
Re: Client in Cluster.
Yes you can use the standard TSM Client. You need to do a few modifacations though, you can find the instructions in the TSM Client manual. Kvedja/Regards Petur Eythorsson Taeknimadur/Technician IBM Certified Specialist - AIX Tivoli Storage Manager Certified Professional Microsoft Certified System Engineer [EMAIL PROTECTED] Nyherji Hf Simi TEL: +354-569-7700 Borgartun 37105 Iceland URL:http://www.nyherji.is -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED]]On Behalf Of Nazir Sent: 7. febrúar 2002 14:30 To: [EMAIL PROTECTED] Subject: Client in Cluster. Hi, Could TSM Client that is installing with TSM Server be used in a Microsoft Cluster Server or Is there a specific TSM Client for a Microsoft Cluster Server? Thanks in advance, Nazir
Re: Client in Cluster.
Hi, you can use the ordinary TSM Client for M$ Cluster Server, but you have to configure a TSM Node for every used Disk Group inside the cluster. [EMAIL PROTECTED] Sent by: [EMAIL PROTECTED] 07.02.2002 15:44 Please respond to ADSM-L To: [EMAIL PROTECTED] bcc: Subject:Client in Cluster. Hi, Could TSM Client that is installing with TSM Server be used in a Microsoft Cluster Server or Is there a specific TSM Client for a Microsoft Cluster Server? Thanks in advance, Nazir
Re: Client for Cluster
The regular TSM Backup-Archive client and the Tivoli Data Protection for MS SQL Server are all cluster aware applications. -- Joshua S. Bassi Independent IT Consultant IBM Certified - AIX/HACMP, SAN, Shark Tivoli Certified Consultant- ADSM/TSM Cell (408)(831) 332-4006 [EMAIL PROTECTED] -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED]] On Behalf Of Nazir Sent: Thursday, October 25, 2001 9:55 AM To: [EMAIL PROTECTED] Subject: Client for Cluster Hi, I have two machines that are working Win 2000 Server and SQL. Those machines are in cluster, and there is a virtual machine too. Is there TSM client for Microsoft cluster? What Can I do in this case? Thank you Nazir
Client for Cluster
Hi, I have two machines that are working Win 2000 Server and SQL. Those machines are in cluster, and there is a virtual machine too. Is there TSM client for Microsoft cluster? What Can I do in this case? Thank you Nazir
