TSM Cluster Scheduler Question
Hi All TSM 5.4.1.2 on Solaris 2.9 Backing up Exchange (MS Windows Server 2003, RC2 SP) - 5.5.0.0 in a clustered environment. We had this set up by an outside company and are now seeing some problems with the TSM Cluster Scheduler automatically failing over the cluster due to a password issue (this is as far as I can see anyway). So, the dumb question, what does the Cluster Scheduler actually do? I can see there is a separate schedule for the Exchange TDP backups. Thanks Farren This email (and any attachment) is confidential, may be legally privileged and is intended solely for the use of the individual or entity to whom it is addressed. If you are not the intended recipient please do not disclose, copy or take any action in reliance on it. If you have received this message in error please tell us by reply and delete all copies on your system. Although this email has been scanned for viruses you should rely on your own virus check as the sender accepts no liability for any damage arising out of any bug or virus infection. Please note that email traffic data may be monitored and that emails may be viewed for security reasons. John Wiley Sons Limited is a private limited company registered in England with registered number 641132. Registered office address: The Atrium, Southern Gate, Chichester, West Sussex, PO19 8SQ.
Re: TSM Disk pools on EMC issue
Thanks for the info guys. SANDISCOVERY is turned ON at the moment. I have turned it OFF now - just waiting for the go-ahead to reboot the server. Regards, Jacques van den Berg TSM / Storage / SAP Basis Administrator Pick 'n Pay IT Email : [EMAIL PROTECTED] Tel : +2721 - 658 1711 Fax : +2721 - 658 1676 Mobile : +2782 - 653 8164 Dis altyd lente in die hart van die mens wat God en sy medemens liefhet (John Vianney). -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Shawn Drew Sent: 30 June 2008 10:11 PM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] TSM Disk pools on EMC issue Same here, We only recently isolated our Clariion problems to this. We would have random days where the HBA's just logged out of the Clariion and would not connect at all, no matter what we did. We had to reboot these P570s multiple times (not pleasant!) until I took a wild guess to turn off SANDISCOVERY. Regards, Shawn Shawn Drew Internet [EMAIL PROTECTED] Sent by: ADSM-L@VM.MARIST.EDU 06/30/2008 11:24 AM Please respond to ADSM-L@VM.MARIST.EDU To ADSM-L cc Subject Re: [ADSM-L] TSM Disk pools on EMC issue I had a client that was trying to connect a CX700 to their AIX TSM system. What they say is that the SANDISCOVER was causing problems and IBM suggested they disable it in the DSMSERV.OPT. Been working ever since. I wasn't involved in the issue, this is just what they told me they found out. But you might want to give it a try. Bill Boyer 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. Read our disclaimer at: http://www.picknpay.co.za/pnp/view/pnp/en/page5093? If you don't have web access, the disclaimer can be mailed to you on request. Disclaimer requests to be sent to [EMAIL PROTECTED]
Re: TSM Cluster Scheduler Question
Hi, First, de-select affect group in the cluster resource properties for the TSM Cluster Scheduler in cluster administrator, cluadmin.exe. This prevents the whole cluster to failover when the TSM service stops due to whatever.. ex. bad password. Verify that the correct registry parameter is replicated as a part of the cluster resource: HKEY_LOCAL_MACHINE\SOFTWARE\IBM\ADSM\CurrentVersion\Nodes\ nodename\TSM server instance name Consider to set passexp=0 on the TSM server for the Exchange node. Update PW on both cluster nodes. what does the Cluster Scheduler actually do? Backing up Exchange? :-) You will find the answer if you search on the nodename and schedule in TSM. //Henrik -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Minns, Farren - Chichester Sent: den 1 juli 2008 11:31 To: ADSM-L@VM.MARIST.EDU Subject: [ADSM-L] TSM Cluster Scheduler Question Hi All TSM 5.4.1.2 on Solaris 2.9 Backing up Exchange (MS Windows Server 2003, RC2 SP) - 5.5.0.0 in a clustered environment. We had this set up by an outside company and are now seeing some problems with the TSM Cluster Scheduler automatically failing over the cluster due to a password issue (this is as far as I can see anyway). So, the dumb question, what does the Cluster Scheduler actually do? I can see there is a separate schedule for the Exchange TDP backups. Thanks Farren This email (and any attachment) is confidential, may be legally privileged and is intended solely for the use of the individual or entity to whom it is addressed. If you are not the intended recipient please do not disclose, copy or take any action in reliance on it. If you have received this message in error please tell us by reply and delete all copies on your system. Although this email has been scanned for viruses you should rely on your own virus check as the sender accepts no liability for any damage arising out of any bug or virus infection. Please note that email traffic data may be monitored and that emails may be viewed for security reasons. John Wiley Sons Limited is a private limited company registered in England with registered number 641132. Registered office address: The Atrium, Southern Gate, Chichester, West Sussex, PO19 8SQ. --- The information contained in this message may be CONFIDENTIAL and is intended for the addressee only. Any unauthorised use, dissemination of the information or copying of this message is prohibited. If you are not the addressee, please notify the sender immediately by return e-mail and delete this message. Thank you.
Re: TSM Cluster Scheduler Question
Hi Henrik, many thanks for that, very helpful. The reason I'm confused about the 'cluster scheduler' is that we also have a 'TSM Exchange TDP Scheduler' running, and I assumed it was this that was responsible for the backups? Why the need for the two separate schedulers? Thanks again. Farren -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Henrik Vahlstedt Sent: 01 July 2008 10:58 To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] TSM Cluster Scheduler Question Hi, First, de-select affect group in the cluster resource properties for the TSM Cluster Scheduler in cluster administrator, cluadmin.exe. This prevents the whole cluster to failover when the TSM service stops due to whatever.. ex. bad password. Verify that the correct registry parameter is replicated as a part of the cluster resource: HKEY_LOCAL_MACHINE\SOFTWARE\IBM\ADSM\CurrentVersion\Nodes\ nodename\TSM server instance name Consider to set passexp=0 on the TSM server for the Exchange node. Update PW on both cluster nodes. what does the Cluster Scheduler actually do? Backing up Exchange? :-) You will find the answer if you search on the nodename and schedule in TSM. //Henrik -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Minns, Farren - Chichester Sent: den 1 juli 2008 11:31 To: ADSM-L@VM.MARIST.EDU Subject: [ADSM-L] TSM Cluster Scheduler Question Hi All TSM 5.4.1.2 on Solaris 2.9 Backing up Exchange (MS Windows Server 2003, RC2 SP) - 5.5.0.0 in a clustered environment. We had this set up by an outside company and are now seeing some problems with the TSM Cluster Scheduler automatically failing over the cluster due to a password issue (this is as far as I can see anyway). So, the dumb question, what does the Cluster Scheduler actually do? I can see there is a separate schedule for the Exchange TDP backups. Thanks Farren This email (and any attachment) is confidential, may be legally privileged and is intended solely for the use of the individual or entity to whom it is addressed. If you are not the intended recipient please do not disclose, copy or take any action in reliance on it. If you have received this message in error please tell us by reply and delete all copies on your system. Although this email has been scanned for viruses you should rely on your own virus check as the sender accepts no liability for any damage arising out of any bug or virus infection. Please note that email traffic data may be monitored and that emails may be viewed for security reasons. John Wiley Sons Limited is a private limited company registered in England with registered number 641132. Registered office address: The Atrium, Southern Gate, Chichester, West Sussex, PO19 8SQ. --- The information contained in this message may be CONFIDENTIAL and is intended for the addressee only. Any unauthorised use, dissemination of the information or copying of this message is prohibited. If you are not the addressee, please notify the sender immediately by return e-mail and delete this message. Thank you. This email (and any attachment) is confidential, may be legally privileged and is intended solely for the use of the individual or entity to whom it is addressed. If you are not the intended recipient please do not disclose, copy or take any action in reliance on it. If you have received this message in error please tell us by reply and delete all copies on your system. Although this email has been scanned for viruses you should rely on your own virus check as the sender accepts no liability for any damage arising out of any bug or virus infection. Please note that email traffic data may be monitored and that emails may be viewed for security reasons. John Wiley Sons Limited is a private limited company registered in England with registered number 641132. Registered office address: The Atrium, Southern Gate, Chichester, West Sussex, PO19 8SQ.
Re: TSM Cluster Scheduler Question
Farren, You may be affected by a faulty configuration, where the password in MS cluster's checkpoint file is not synchronized with the local registry password anymore, thus making the service fail ... It happened several times in our shop already ! IBM noticed the problem, and published a solution here : http://www-1.ibm.com/support/docview.wss?uid=swg21243061 May be of interest for you ! Cheers. Arnaud ** Panalpina Management Ltd., Basle, Switzerland, CIT Department Viadukstrasse 42, P.O. Box 4002 Basel/CH Phone: +41 (61) 226 11 11, FAX: +41 (61) 226 17 01 Direct: +41 (61) 226 19 78 e-mail: [EMAIL PROTECTED] ** -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Henrik Vahlstedt Sent: mardi 1 juillet 2008 11:58 To: ADSM-L@VM.MARIST.EDU Subject: Re: TSM Cluster Scheduler Question Hi, First, de-select affect group in the cluster resource properties for the TSM Cluster Scheduler in cluster administrator, cluadmin.exe. This prevents the whole cluster to failover when the TSM service stops due to whatever.. ex. bad password. Verify that the correct registry parameter is replicated as a part of the cluster resource: HKEY_LOCAL_MACHINE\SOFTWARE\IBM\ADSM\CurrentVersion\Nodes\ nodename\TSM server instance name Consider to set passexp=0 on the TSM server for the Exchange node. Update PW on both cluster nodes. what does the Cluster Scheduler actually do? Backing up Exchange? :-) You will find the answer if you search on the nodename and schedule in TSM. //Henrik -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Minns, Farren - Chichester Sent: den 1 juli 2008 11:31 To: ADSM-L@VM.MARIST.EDU Subject: [ADSM-L] TSM Cluster Scheduler Question Hi All TSM 5.4.1.2 on Solaris 2.9 Backing up Exchange (MS Windows Server 2003, RC2 SP) - 5.5.0.0 in a clustered environment. We had this set up by an outside company and are now seeing some problems with the TSM Cluster Scheduler automatically failing over the cluster due to a password issue (this is as far as I can see anyway). So, the dumb question, what does the Cluster Scheduler actually do? I can see there is a separate schedule for the Exchange TDP backups. Thanks Farren This email (and any attachment) is confidential, may be legally privileged and is intended solely for the use of the individual or entity to whom it is addressed. If you are not the intended recipient please do not disclose, copy or take any action in reliance on it. If you have received this message in error please tell us by reply and delete all copies on your system. Although this email has been scanned for viruses you should rely on your own virus check as the sender accepts no liability for any damage arising out of any bug or virus infection. Please note that email traffic data may be monitored and that emails may be viewed for security reasons. John Wiley Sons Limited is a private limited company registered in England with registered number 641132. Registered office address: The Atrium, Southern Gate, Chichester, West Sussex, PO19 8SQ. --- The information contained in this message may be CONFIDENTIAL and is intended for the addressee only. Any unauthorised use, dissemination of the information or copying of this message is prohibited. If you are not the addressee, please notify the sender immediately by return e-mail and delete this message. Thank you.
Re: TSM Cluster Scheduler Question
Thanks Arnaud If resetting the passwords fails I will move on to that. Regards Farren -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of PAC Brion Arnaud Sent: 01 July 2008 11:15 To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] TSM Cluster Scheduler Question Farren, You may be affected by a faulty configuration, where the password in MS cluster's checkpoint file is not synchronized with the local registry password anymore, thus making the service fail ... It happened several times in our shop already ! IBM noticed the problem, and published a solution here : http://www-1.ibm.com/support/docview.wss?uid=swg21243061 May be of interest for you ! Cheers. Arnaud ** Panalpina Management Ltd., Basle, Switzerland, CIT Department Viadukstrasse 42, P.O. Box 4002 Basel/CH Phone: +41 (61) 226 11 11, FAX: +41 (61) 226 17 01 Direct: +41 (61) 226 19 78 e-mail: [EMAIL PROTECTED] ** -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Henrik Vahlstedt Sent: mardi 1 juillet 2008 11:58 To: ADSM-L@VM.MARIST.EDU Subject: Re: TSM Cluster Scheduler Question Hi, First, de-select affect group in the cluster resource properties for the TSM Cluster Scheduler in cluster administrator, cluadmin.exe. This prevents the whole cluster to failover when the TSM service stops due to whatever.. ex. bad password. Verify that the correct registry parameter is replicated as a part of the cluster resource: HKEY_LOCAL_MACHINE\SOFTWARE\IBM\ADSM\CurrentVersion\Nodes\ nodename\TSM server instance name Consider to set passexp=0 on the TSM server for the Exchange node. Update PW on both cluster nodes. what does the Cluster Scheduler actually do? Backing up Exchange? :-) You will find the answer if you search on the nodename and schedule in TSM. //Henrik -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Minns, Farren - Chichester Sent: den 1 juli 2008 11:31 To: ADSM-L@VM.MARIST.EDU Subject: [ADSM-L] TSM Cluster Scheduler Question Hi All TSM 5.4.1.2 on Solaris 2.9 Backing up Exchange (MS Windows Server 2003, RC2 SP) - 5.5.0.0 in a clustered environment. We had this set up by an outside company and are now seeing some problems with the TSM Cluster Scheduler automatically failing over the cluster due to a password issue (this is as far as I can see anyway). So, the dumb question, what does the Cluster Scheduler actually do? I can see there is a separate schedule for the Exchange TDP backups. Thanks Farren This email (and any attachment) is confidential, may be legally privileged and is intended solely for the use of the individual or entity to whom it is addressed. If you are not the intended recipient please do not disclose, copy or take any action in reliance on it. If you have received this message in error please tell us by reply and delete all copies on your system. Although this email has been scanned for viruses you should rely on your own virus check as the sender accepts no liability for any damage arising out of any bug or virus infection. Please note that email traffic data may be monitored and that emails may be viewed for security reasons. John Wiley Sons Limited is a private limited company registered in England with registered number 641132. Registered office address: The Atrium, Southern Gate, Chichester, West Sussex, PO19 8SQ. --- The information contained in this message may be CONFIDENTIAL and is intended for the addressee only. Any unauthorised use, dissemination of the information or copying of this message is prohibited. If you are not the addressee, please notify the sender immediately by return e-mail and delete this message. Thank you. This email (and any attachment) is confidential, may be legally privileged and is intended solely for the use of the individual or entity to whom it is addressed. If you are not the intended recipient please do not disclose, copy or take any action in reliance on it. If you have received this message in error please tell us by reply and delete all copies on your system. Although this email has been scanned for viruses you should rely on your own virus check as the sender accepts no liability for any damage arising out of any bug or virus infection. Please note that email traffic data may be monitored and that emails may be viewed for security reasons. John Wiley Sons
Re: TSM Cluster Scheduler Question
Hi again Farren ! Aha ok, two nodenames? My best guess is that TSM Cluster Scheduler is only backing up the OS. And TSM Exchange TDP Scheduler is responsible for Exchange backups. What I do is to use two TSM nodes and two scheduler services on Exchange servers like you seem to have. But I only have TSM Exchange TDP Scheduler defined as a cluster resource. OS backup is not a part of the cluster and should be defined per host, which requires two nodenames. Thanks Henrik -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Minns, Farren - Chichester Sent: den 1 juli 2008 12:10 To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] TSM Cluster Scheduler Question Hi Henrik, many thanks for that, very helpful. The reason I'm confused about the 'cluster scheduler' is that we also have a 'TSM Exchange TDP Scheduler' running, and I assumed it was this that was responsible for the backups? Why the need for the two separate schedulers? Thanks again. Farren -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Henrik Vahlstedt Sent: 01 July 2008 10:58 To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] TSM Cluster Scheduler Question Hi, First, de-select affect group in the cluster resource properties for the TSM Cluster Scheduler in cluster administrator, cluadmin.exe. This prevents the whole cluster to failover when the TSM service stops due to whatever.. ex. bad password. Verify that the correct registry parameter is replicated as a part of the cluster resource: HKEY_LOCAL_MACHINE\SOFTWARE\IBM\ADSM\CurrentVersion\Nodes\ nodename\TSM server instance name Consider to set passexp=0 on the TSM server for the Exchange node. Update PW on both cluster nodes. what does the Cluster Scheduler actually do? Backing up Exchange? :-) You will find the answer if you search on the nodename and schedule in TSM. //Henrik -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Minns, Farren - Chichester Sent: den 1 juli 2008 11:31 To: ADSM-L@VM.MARIST.EDU Subject: [ADSM-L] TSM Cluster Scheduler Question Hi All TSM 5.4.1.2 on Solaris 2.9 Backing up Exchange (MS Windows Server 2003, RC2 SP) - 5.5.0.0 in a clustered environment. We had this set up by an outside company and are now seeing some problems with the TSM Cluster Scheduler automatically failing over the cluster due to a password issue (this is as far as I can see anyway). So, the dumb question, what does the Cluster Scheduler actually do? I can see there is a separate schedule for the Exchange TDP backups. Thanks Farren This email (and any attachment) is confidential, may be legally privileged and is intended solely for the use of the individual or entity to whom it is addressed. If you are not the intended recipient please do not disclose, copy or take any action in reliance on it. If you have received this message in error please tell us by reply and delete all copies on your system. Although this email has been scanned for viruses you should rely on your own virus check as the sender accepts no liability for any damage arising out of any bug or virus infection. Please note that email traffic data may be monitored and that emails may be viewed for security reasons. John Wiley Sons Limited is a private limited company registered in England with registered number 641132. Registered office address: The Atrium, Southern Gate, Chichester, West Sussex, PO19 8SQ. --- The information contained in this message may be CONFIDENTIAL and is intended for the addressee only. Any unauthorised use, dissemination of the information or copying of this message is prohibited. If you are not the addressee, please notify the sender immediately by return e-mail and delete this message. Thank you. This email (and any attachment) is confidential, may be legally privileged and is intended solely for the use of the individual or entity to whom it is addressed. If you are not the intended recipient please do not disclose, copy or take any action in reliance on it. If you have received this message in error please tell us by reply and delete all copies on your system. Although this email has been scanned for viruses you should rely on your own virus check as the sender accepts no liability for any damage arising out of any bug or virus infection. Please note that email traffic data may be monitored and that emails may be viewed for security reasons. John Wiley Sons Limited is a private limited company registered in England with registered number 641132.
Re: TSM Cluster Scheduler Question
Hello Ah OK, that makes sense. I just checked and the TSM CHI-MB Cluster RG Scheduler points to a standard looking dsm.opt file although we don't do normal backups on these servers anyway (yes). The TSM Exchange TDM Cluster RG Scheduler points to \Tivoli\TSM\TDPExchange\dsm.opt that contains the nodename CHI-MB-EXCH. I know that this is the nodename referenced with the actual exchange backups. Thanks for your help with this, took a bit of getting my head around. Regards Farren -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Henrik Vahlstedt Sent: 01 July 2008 11:32 To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] TSM Cluster Scheduler Question Hi again Farren ! Aha ok, two nodenames? My best guess is that TSM Cluster Scheduler is only backing up the OS. And TSM Exchange TDP Scheduler is responsible for Exchange backups. What I do is to use two TSM nodes and two scheduler services on Exchange servers like you seem to have. But I only have TSM Exchange TDP Scheduler defined as a cluster resource. OS backup is not a part of the cluster and should be defined per host, which requires two nodenames. Thanks Henrik -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Minns, Farren - Chichester Sent: den 1 juli 2008 12:10 To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] TSM Cluster Scheduler Question Hi Henrik, many thanks for that, very helpful. The reason I'm confused about the 'cluster scheduler' is that we also have a 'TSM Exchange TDP Scheduler' running, and I assumed it was this that was responsible for the backups? Why the need for the two separate schedulers? Thanks again. Farren -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Henrik Vahlstedt Sent: 01 July 2008 10:58 To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] TSM Cluster Scheduler Question Hi, First, de-select affect group in the cluster resource properties for the TSM Cluster Scheduler in cluster administrator, cluadmin.exe. This prevents the whole cluster to failover when the TSM service stops due to whatever.. ex. bad password. Verify that the correct registry parameter is replicated as a part of the cluster resource: HKEY_LOCAL_MACHINE\SOFTWARE\IBM\ADSM\CurrentVersion\Nodes\ nodename\TSM server instance name Consider to set passexp=0 on the TSM server for the Exchange node. Update PW on both cluster nodes. what does the Cluster Scheduler actually do? Backing up Exchange? :-) You will find the answer if you search on the nodename and schedule in TSM. //Henrik -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Minns, Farren - Chichester Sent: den 1 juli 2008 11:31 To: ADSM-L@VM.MARIST.EDU Subject: [ADSM-L] TSM Cluster Scheduler Question Hi All TSM 5.4.1.2 on Solaris 2.9 Backing up Exchange (MS Windows Server 2003, RC2 SP) - 5.5.0.0 in a clustered environment. We had this set up by an outside company and are now seeing some problems with the TSM Cluster Scheduler automatically failing over the cluster due to a password issue (this is as far as I can see anyway). So, the dumb question, what does the Cluster Scheduler actually do? I can see there is a separate schedule for the Exchange TDP backups. Thanks Farren This email (and any attachment) is confidential, may be legally privileged and is intended solely for the use of the individual or entity to whom it is addressed. If you are not the intended recipient please do not disclose, copy or take any action in reliance on it. If you have received this message in error please tell us by reply and delete all copies on your system. Although this email has been scanned for viruses you should rely on your own virus check as the sender accepts no liability for any damage arising out of any bug or virus infection. Please note that email traffic data may be monitored and that emails may be viewed for security reasons. John Wiley Sons Limited is a private limited company registered in England with registered number 641132. Registered office address: The Atrium, Southern Gate, Chichester, West Sussex, PO19 8SQ. --- The information contained in this message may be CONFIDENTIAL and is intended for the addressee only. Any unauthorised use, dissemination of the information or copying of this message is prohibited. If you are not the addressee, please notify the sender immediately by return e-mail and delete this message. Thank you.
Re: AW: [ADSM-L] Export / import nodes with shared library
Otto, After you export using the server to server method, verify that all data has been successfully imported to the target TSM server. Then delete the node and all of it's data on the source TSM server. The volumes holding the deleted data will have free space. The volumes can then be reclaimed through normal reclamation or move data commands. Nothing needs to be performed on the TSM Library manager. For a short period of time you will need two times the number of tapes because the data is fully duplicated on both the source and target TSM servers. Cheers, Neil Strand Storage Engineer - Legg Mason Baltimore, MD. (410) 580-7491 Whatever you can do or believe you can, begin it. Boldness has genius, power and magic. -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Otto Chvosta Sent: Saturday, June 28, 2008 4:57 AM To: ADSM-L@VM.MARIST.EDU Subject: [ADSM-L] AW: [ADSM-L] Export / import nodes with shared library Hi again, Thank you Neil ! - Sorry, but 'UPD LIBV ... OWN=' do not solve the problem ... --- ANR8969E The owner of volume XX can not be updated to owner TSM1. - we also use 'EXPORT NODE ... TOSERVER=...' and it works great. But it is not very useful to transfer nodedata (hundrets of TB) over ethernet because there is no idea how to get the export volumes to scratch state after importing on another server in a shared library environment ... - After importing the ownership changes to the importing server - volumes should get back to SCRATCH after 'DEL VOLHIST T=EXP' on the exporting server (the volumes are deleted from volhist but remain PRIVATE because owner is another server) - after that the only way to put them to SCRATCH is 'AUDIT LIBRARY' (otherwise the volumes stay PRIVATE forever) Any other idea(s) ? Thank you ! Otto -Ursprüngliche Nachricht- Von: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] Im Auftrag von Strand, Neil B. Gesendet: Freitag, 27. Juni 2008 16:39 An: ADSM-L@VM.MARIST.EDU Betreff: Re: [ADSM-L] Export / import nodes with shared library Otto, - You should be able to just update the libvol owner on the library manager to the new server. - You may also consider using server-server export which transfers data through the ethernet from the source to target server. This process allows for concurrent export/import and reduces the chance of mixing up the sequence of export tape volumes. To do this you need to set up server-server communications betweeen the source and target servers. See the help page for export node EXPORT NODE -- Directly to Another Server for the export syntax. Cheers, Neil Strand Storage Engineer - Legg Mason Baltimore, MD. (410) 580-7491 Whatever you can do or believe you can, begin it. Boldness has genius, power and magic. -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Otto Chvosta Sent: Friday, June 27, 2008 10:06 AM To: ADSM-L@VM.MARIST.EDU Subject: [ADSM-L] Export / import nodes with shared library Hi TSM'ers, We splitted our TSM Server up to five instances (four library clients, one library manager, 3494) To move the nodes to new instances we export/import them on tape (TSM0 is library manager, TSM1-TSM4 are library clients) (1) on instance TSM1: Export node to volume(s) volhist entries are made owner ist TSM1 (2) on instance TSM2: import node from those volumes now owner is TSM2 there were no entries made into volhist (3) after succesful import on instance TSM1: del volhist type=export ... entries in volhist of TSM1 are removed But we got an error on TSM0 (Library manager): ANRD smlshare.c(4724): ThreadId 21 Invalid owner(TSM1) attempting to delete volume J20010. Is this the normal behavior ? Is the only way to get the volumes back to scratch an AUDIT LIBRARY on the library clients ? Is this the recommended way to do that ? Where is the recommended way documented ? TIA ! Otto _ TSM Administration Medical University Vienna Austria IMPORTANT: E-mail sent through the Internet is not secure. Legg Mason therefore recommends that you do not send any confidential or sensitive information to us via electronic mail, including social security numbers, account numbers, or personal identification numbers. Delivery, and or timely delivery of Internet mail is not guaranteed. Legg Mason therefore recommends that you do not send time sensitive or action-oriented messages to us via electronic mail. This message is intended for the addressee only and may contain privileged or confidential information. Unless you are the intended recipient, you may not use, copy or disclose to anyone any information contained in this message. If you have received this message in error, please notify the
Please tell me about your LTO3 / LTO4 performance
Hi all- For quite some time now, I have been trying to track down an elusive bottleneck in my TSM environment relating to disk-to-tape performance. This is a long read, but I would be very greatful for any suggestions. Hopefully some of you folks much smarter than me out there will be able to point me in the right direction. If any other LTO3 or LTO4 users out there could give me some examples of their real-world performance along with a little detail on their config, that would be most helpful as well! My current environment consists of: * TSM server = p570 LPAR w/4 1.9GHz processors and 8GB RAM, (6) 2Gb HBAS (2 for disk and 4 for tape traffic), and a 10Gb Ethernet adapter. * TSM 5.4.1.2 on AIX 5.3 TL6 * 3584 w/14 LTO3 drives at primary site * 3584 w/12 LTO1 drives at DR/hotsite (copypool volumes are written directly to this library via SAN routing) * DB (80GB -- 4GB DBVOL size) residing on IBM DS8300 behind IBM SVC * Log (11GB - single LOGVOL) residing on IBM DS8300 behind IBM SVC * Primary Storage pool in question (2.5TB -- 20GB volume size), DISK device class, residing on IBMDS8300 behind IBM SVC I currently back up about 4.5TB / night, of which ~2TB is written directly to my primary LTO3 tape pool with a simultaneous write to my copypool across town. So, each morning I'm left with about 2.5TB of data to copy and migrate from my disk pool(s) to copypool and onsite tape respectively. My backup stg performance to LTO1 tape (copypool) is about what I would expect. I run 5 threads for this process (5 mount points used), and I consistently average 20-25MB/sec/drive. Fair enough. I don't know of anyone getting a whole lot more than that out of an LTO1 drive. After that is complete, I then migrate that data to my LTO3 tape here onsite. That performance is pretty lousy compared to what I would expect to get out of LTO3. I run 6 migration threads (6 mount points used), and I average around 25MB/sec/drive going to LT03 as well. All SAN links between the TSM server and the LT03 drives are a minimum of 2Gb, so that is my lowest common denominator. I've tried using less threads to see if perhaps I was saturating an HBA rather than the drive. Same speed. I've tried separating my DB and STG pools on different storage subsystems. Same speed. I've opened PMR's with IBM support, and they have poured over all of my TSM server settings / config and found nothing to go on. We've had IBM ATS teams evaluate the situation, and they've never been able to pinpoint a problem. I've tried various tools--tapewrite, nmon, filemon, etc. and I've not found a smoking gun. At this point, my gut is that SVC is the bottleneck, but for those of you familiar with SVC, you know that trying to obtain meaningful performance statistics on the SVC cluster itself is frustrating. I know there are folks out there getting much better performance out of LTO3 drives, so please tell me how you're doing it! Suggestions? Questions? Thank you! -Kevin - This E-mail contains PRIVILEGED AND CONFIDENTIAL INFORMATION intended only for the use of the Individual(s) named above. If you are not the intended recipient of this E-mail, or the employee or agent responsible for delivering it to the intended recipient, you are hereby notified that any dissemination or copying of this E-mail is strictly prohibited. If you have received this E-mail in error, please immediately notify us at (865)374-4900 or notify us by E-mail at [EMAIL PROTECTED]
Re: Please tell me about your LTO3 / LTO4 performance
If you think it's the SVC, why not try taking TSM out of the picture: If you use OS tools to COPY a big chunk of data (say a 20 GB file) from one spot behind the SVC to the other, and time it, what is your MB/sec rate? On 7/1/08, Thach, Kevin G [EMAIL PROTECTED] wrote: Hi all- For quite some time now, I have been trying to track down an elusive bottleneck in my TSM environment relating to disk-to-tape performance. This is a long read, but I would be very greatful for any suggestions. Hopefully some of you folks much smarter than me out there will be able to point me in the right direction. If any other LTO3 or LTO4 users out there could give me some examples of their real-world performance along with a little detail on their config, that would be most helpful as well! My current environment consists of: * TSM server = p570 LPAR w/4 1.9GHz processors and 8GB RAM, (6) 2Gb HBAS (2 for disk and 4 for tape traffic), and a 10Gb Ethernet adapter. * TSM 5.4.1.2 on AIX 5.3 TL6 * 3584 w/14 LTO3 drives at primary site * 3584 w/12 LTO1 drives at DR/hotsite (copypool volumes are written directly to this library via SAN routing) * DB (80GB -- 4GB DBVOL size) residing on IBM DS8300 behind IBM SVC * Log (11GB - single LOGVOL) residing on IBM DS8300 behind IBM SVC * Primary Storage pool in question (2.5TB -- 20GB volume size), DISK device class, residing on IBMDS8300 behind IBM SVC I currently back up about 4.5TB / night, of which ~2TB is written directly to my primary LTO3 tape pool with a simultaneous write to my copypool across town. So, each morning I'm left with about 2.5TB of data to copy and migrate from my disk pool(s) to copypool and onsite tape respectively. My backup stg performance to LTO1 tape (copypool) is about what I would expect. I run 5 threads for this process (5 mount points used), and I consistently average 20-25MB/sec/drive. Fair enough. I don't know of anyone getting a whole lot more than that out of an LTO1 drive. After that is complete, I then migrate that data to my LTO3 tape here onsite. That performance is pretty lousy compared to what I would expect to get out of LTO3. I run 6 migration threads (6 mount points used), and I average around 25MB/sec/drive going to LT03 as well. All SAN links between the TSM server and the LT03 drives are a minimum of 2Gb, so that is my lowest common denominator. I've tried using less threads to see if perhaps I was saturating an HBA rather than the drive. Same speed. I've tried separating my DB and STG pools on different storage subsystems. Same speed. I've opened PMR's with IBM support, and they have poured over all of my TSM server settings / config and found nothing to go on. We've had IBM ATS teams evaluate the situation, and they've never been able to pinpoint a problem. I've tried various tools--tapewrite, nmon, filemon, etc. and I've not found a smoking gun. At this point, my gut is that SVC is the bottleneck, but for those of you familiar with SVC, you know that trying to obtain meaningful performance statistics on the SVC cluster itself is frustrating. I know there are folks out there getting much better performance out of LTO3 drives, so please tell me how you're doing it! Suggestions? Questions? Thank you! -Kevin - This E-mail contains PRIVILEGED AND CONFIDENTIAL INFORMATION intended only for the use of the Individual(s) named above. If you are not the intended recipient of this E-mail, or the employee or agent responsible for delivering it to the intended recipient, you are hereby notified that any dissemination or copying of this E-mail is strictly prohibited. If you have received this E-mail in error, please immediately notify us at (865)374-4900 or notify us by E-mail at [EMAIL PROTECTED]
STORServer ABC
A bit of a survey for those of you that happen to use the OpenVMS ABC client. I've recently found the /summary option, but the format in the act log is quite different than the normal job reports and our reporting software doesn't catch it. We'll have to modify it, but I was just wondering... How does everyone report on their ABC client backups? Just a normal shell script report? 3rd party reporting tool? Regards, Shawn Shawn Drew 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.
Re: Please tell me about your LTO3 / LTO4 performance
How are your tape drives attached to your TSM HBAs? Presumably by SAN switch, so how do you have the drives zoned? Ideally, every drive should be visible on every fiber and alternate path support should be enabled (chdev -l rmtx -a alt_pathing=yes) (do NOT do for the SMC if you do not have path failover; may not work for LTO3 if you do not have path failover). I have 10 LTO4 and 6 LTO2 drives, and 10 fibers to tape from my TSM LPAR; two SAN switches, with the even-numbered drives in one and the odd-numbered drives in the other. The result is 80 rmt (tape) devices for the LPAR. I know I'm network limited - so I only get a maximum of 110 MB/sec per drive/network interface in my nightly SAP backups. (dedicated Gb networks, one per concurrent backup session - Gigabit Ethernet NICs are cheap!) My off-site copy processes run at LTO2 drive speed (the 'twos are only used for offsite tapes). This is for 4 concurrent sessions over two network interfaces: BKI1215I: Average transmission rate was 762.364 GB/h (216.850 MB/sec). BKI1227I: Average compression factor was 1.000. BKI0020I: End of program at: Mon Jun 30 20:55:08 EDT 2008 . BKI0021I: Elapsed time: 01 h 52 min 00 sec . BKI0024I: Return code is: 0. So I averaged 108 MB/sec over the NIC, and 54 MB/sec to the drive. Tom Kauffman NIBCO, Inc -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Thach, Kevin G Sent: Tuesday, July 01, 2008 10:41 AM To: ADSM-L@VM.MARIST.EDU Subject: Please tell me about your LTO3 / LTO4 performance Hi all- For quite some time now, I have been trying to track down an elusive bottleneck in my TSM environment relating to disk-to-tape performance. This is a long read, but I would be very greatful for any suggestions. Hopefully some of you folks much smarter than me out there will be able to point me in the right direction. If any other LTO3 or LTO4 users out there could give me some examples of their real-world performance along with a little detail on their config, that would be most helpful as well! My current environment consists of: * TSM server = p570 LPAR w/4 1.9GHz processors and 8GB RAM, (6) 2Gb HBAS (2 for disk and 4 for tape traffic), and a 10Gb Ethernet adapter. * TSM 5.4.1.2 on AIX 5.3 TL6 * 3584 w/14 LTO3 drives at primary site * 3584 w/12 LTO1 drives at DR/hotsite (copypool volumes are written directly to this library via SAN routing) * DB (80GB -- 4GB DBVOL size) residing on IBM DS8300 behind IBM SVC * Log (11GB - single LOGVOL) residing on IBM DS8300 behind IBM SVC * Primary Storage pool in question (2.5TB -- 20GB volume size), DISK device class, residing on IBMDS8300 behind IBM SVC I currently back up about 4.5TB / night, of which ~2TB is written directly to my primary LTO3 tape pool with a simultaneous write to my copypool across town. So, each morning I'm left with about 2.5TB of data to copy and migrate from my disk pool(s) to copypool and onsite tape respectively. My backup stg performance to LTO1 tape (copypool) is about what I would expect. I run 5 threads for this process (5 mount points used), and I consistently average 20-25MB/sec/drive. Fair enough. I don't know of anyone getting a whole lot more than that out of an LTO1 drive. After that is complete, I then migrate that data to my LTO3 tape here onsite. That performance is pretty lousy compared to what I would expect to get out of LTO3. I run 6 migration threads (6 mount points used), and I average around 25MB/sec/drive going to LT03 as well. All SAN links between the TSM server and the LT03 drives are a minimum of 2Gb, so that is my lowest common denominator. I've tried using less threads to see if perhaps I was saturating an HBA rather than the drive. Same speed. I've tried separating my DB and STG pools on different storage subsystems. Same speed. I've opened PMR's with IBM support, and they have poured over all of my TSM server settings / config and found nothing to go on. We've had IBM ATS teams evaluate the situation, and they've never been able to pinpoint a problem. I've tried various tools--tapewrite, nmon, filemon, etc. and I've not found a smoking gun. At this point, my gut is that SVC is the bottleneck, but for those of you familiar with SVC, you know that trying to obtain meaningful performance statistics on the SVC cluster itself is frustrating. I know there are folks out there getting much better performance out of LTO3 drives, so please tell me how you're doing it! Suggestions? Questions? Thank you! -Kevin - This E-mail contains PRIVILEGED AND CONFIDENTIAL INFORMATION intended only for the use of the Individual(s) named above. If you are not the intended recipient of this E-mail, or the employee or agent responsible for delivering it to the intended recipient, you are hereby notified that any dissemination or copying of this
Re: Please tell me about your LTO3 / LTO4 performance
I am set up very similar to you. My TSM LPAR HBAS connect to a director class switch which has an ISL to each of the edge switches that the tape drives themselves connect to (odd drives on one and even on the other like yourself.) Therefore, I have 64 rmt devices at the AIX level for my LTO3 drives, as each tape HBA sees each of the 14 drives. I am not using the alternate pathing. -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Kauffman, Tom Sent: Tuesday, July 01, 2008 11:42 AM To: ADSM-L@VM.MARIST.EDU Subject: Re: Please tell me about your LTO3 / LTO4 performance How are your tape drives attached to your TSM HBAs? Presumably by SAN switch, so how do you have the drives zoned? Ideally, every drive should be visible on every fiber and alternate path support should be enabled (chdev -l rmtx -a alt_pathing=yes) (do NOT do for the SMC if you do not have path failover; may not work for LTO3 if you do not have path failover). I have 10 LTO4 and 6 LTO2 drives, and 10 fibers to tape from my TSM LPAR; two SAN switches, with the even-numbered drives in one and the odd-numbered drives in the other. The result is 80 rmt (tape) devices for the LPAR. I know I'm network limited - so I only get a maximum of 110 MB/sec per drive/network interface in my nightly SAP backups. (dedicated Gb networks, one per concurrent backup session - Gigabit Ethernet NICs are cheap!) My off-site copy processes run at LTO2 drive speed (the 'twos are only used for offsite tapes). This is for 4 concurrent sessions over two network interfaces: BKI1215I: Average transmission rate was 762.364 GB/h (216.850 MB/sec). BKI1227I: Average compression factor was 1.000. BKI0020I: End of program at: Mon Jun 30 20:55:08 EDT 2008 . BKI0021I: Elapsed time: 01 h 52 min 00 sec . BKI0024I: Return code is: 0. So I averaged 108 MB/sec over the NIC, and 54 MB/sec to the drive. Tom Kauffman NIBCO, Inc -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Thach, Kevin G Sent: Tuesday, July 01, 2008 10:41 AM To: ADSM-L@VM.MARIST.EDU Subject: Please tell me about your LTO3 / LTO4 performance Hi all- For quite some time now, I have been trying to track down an elusive bottleneck in my TSM environment relating to disk-to-tape performance. This is a long read, but I would be very greatful for any suggestions. Hopefully some of you folks much smarter than me out there will be able to point me in the right direction. If any other LTO3 or LTO4 users out there could give me some examples of their real-world performance along with a little detail on their config, that would be most helpful as well! My current environment consists of: * TSM server = p570 LPAR w/4 1.9GHz processors and 8GB RAM, (6) 2Gb HBAS (2 for disk and 4 for tape traffic), and a 10Gb Ethernet adapter. * TSM 5.4.1.2 on AIX 5.3 TL6 * 3584 w/14 LTO3 drives at primary site * 3584 w/12 LTO1 drives at DR/hotsite (copypool volumes are written directly to this library via SAN routing) * DB (80GB -- 4GB DBVOL size) residing on IBM DS8300 behind IBM SVC * Log (11GB - single LOGVOL) residing on IBM DS8300 behind IBM SVC * Primary Storage pool in question (2.5TB -- 20GB volume size), DISK device class, residing on IBMDS8300 behind IBM SVC I currently back up about 4.5TB / night, of which ~2TB is written directly to my primary LTO3 tape pool with a simultaneous write to my copypool across town. So, each morning I'm left with about 2.5TB of data to copy and migrate from my disk pool(s) to copypool and onsite tape respectively. My backup stg performance to LTO1 tape (copypool) is about what I would expect. I run 5 threads for this process (5 mount points used), and I consistently average 20-25MB/sec/drive. Fair enough. I don't know of anyone getting a whole lot more than that out of an LTO1 drive. After that is complete, I then migrate that data to my LTO3 tape here onsite. That performance is pretty lousy compared to what I would expect to get out of LTO3. I run 6 migration threads (6 mount points used), and I average around 25MB/sec/drive going to LT03 as well. All SAN links between the TSM server and the LT03 drives are a minimum of 2Gb, so that is my lowest common denominator. I've tried using less threads to see if perhaps I was saturating an HBA rather than the drive. Same speed. I've tried separating my DB and STG pools on different storage subsystems. Same speed. I've opened PMR's with IBM support, and they have poured over all of my TSM server settings / config and found nothing to go on. We've had IBM ATS teams evaluate the situation, and they've never been able to pinpoint a problem. I've tried various tools--tapewrite, nmon, filemon, etc. and I've not found a smoking gun. At this point, my gut is that SVC is the bottleneck, but for those of you familiar with SVC, you know that trying to obtain meaningful
Re: Please tell me about your LTO3 / LTO4 performance
Two items, then. Alternate pathing may help. Also, what is the available bandwidth of the ISL to the edge switches? For your system, it should be at least 6 Gb; 8 would be marginally better (three paired ports at 2 Gb/port, or two paired ports at 4 Gb/port). -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Thach, Kevin G Sent: Tuesday, July 01, 2008 11:52 AM To: ADSM-L@VM.MARIST.EDU Subject: Re: Please tell me about your LTO3 / LTO4 performance I am set up very similar to you. My TSM LPAR HBAS connect to a director class switch which has an ISL to each of the edge switches that the tape drives themselves connect to (odd drives on one and even on the other like yourself.) Therefore, I have 64 rmt devices at the AIX level for my LTO3 drives, as each tape HBA sees each of the 14 drives. I am not using the alternate pathing. -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Kauffman, Tom Sent: Tuesday, July 01, 2008 11:42 AM To: ADSM-L@VM.MARIST.EDU Subject: Re: Please tell me about your LTO3 / LTO4 performance How are your tape drives attached to your TSM HBAs? Presumably by SAN switch, so how do you have the drives zoned? Ideally, every drive should be visible on every fiber and alternate path support should be enabled (chdev -l rmtx -a alt_pathing=yes) (do NOT do for the SMC if you do not have path failover; may not work for LTO3 if you do not have path failover). I have 10 LTO4 and 6 LTO2 drives, and 10 fibers to tape from my TSM LPAR; two SAN switches, with the even-numbered drives in one and the odd-numbered drives in the other. The result is 80 rmt (tape) devices for the LPAR. I know I'm network limited - so I only get a maximum of 110 MB/sec per drive/network interface in my nightly SAP backups. (dedicated Gb networks, one per concurrent backup session - Gigabit Ethernet NICs are cheap!) My off-site copy processes run at LTO2 drive speed (the 'twos are only used for offsite tapes). This is for 4 concurrent sessions over two network interfaces: BKI1215I: Average transmission rate was 762.364 GB/h (216.850 MB/sec). BKI1227I: Average compression factor was 1.000. BKI0020I: End of program at: Mon Jun 30 20:55:08 EDT 2008 . BKI0021I: Elapsed time: 01 h 52 min 00 sec . BKI0024I: Return code is: 0. So I averaged 108 MB/sec over the NIC, and 54 MB/sec to the drive. Tom Kauffman NIBCO, Inc -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Thach, Kevin G Sent: Tuesday, July 01, 2008 10:41 AM To: ADSM-L@VM.MARIST.EDU Subject: Please tell me about your LTO3 / LTO4 performance Hi all- For quite some time now, I have been trying to track down an elusive bottleneck in my TSM environment relating to disk-to-tape performance. This is a long read, but I would be very greatful for any suggestions. Hopefully some of you folks much smarter than me out there will be able to point me in the right direction. If any other LTO3 or LTO4 users out there could give me some examples of their real-world performance along with a little detail on their config, that would be most helpful as well! My current environment consists of: * TSM server = p570 LPAR w/4 1.9GHz processors and 8GB RAM, (6) 2Gb HBAS (2 for disk and 4 for tape traffic), and a 10Gb Ethernet adapter. * TSM 5.4.1.2 on AIX 5.3 TL6 * 3584 w/14 LTO3 drives at primary site * 3584 w/12 LTO1 drives at DR/hotsite (copypool volumes are written directly to this library via SAN routing) * DB (80GB -- 4GB DBVOL size) residing on IBM DS8300 behind IBM SVC * Log (11GB - single LOGVOL) residing on IBM DS8300 behind IBM SVC * Primary Storage pool in question (2.5TB -- 20GB volume size), DISK device class, residing on IBMDS8300 behind IBM SVC I currently back up about 4.5TB / night, of which ~2TB is written directly to my primary LTO3 tape pool with a simultaneous write to my copypool across town. So, each morning I'm left with about 2.5TB of data to copy and migrate from my disk pool(s) to copypool and onsite tape respectively. My backup stg performance to LTO1 tape (copypool) is about what I would expect. I run 5 threads for this process (5 mount points used), and I consistently average 20-25MB/sec/drive. Fair enough. I don't know of anyone getting a whole lot more than that out of an LTO1 drive. After that is complete, I then migrate that data to my LTO3 tape here onsite. That performance is pretty lousy compared to what I would expect to get out of LTO3. I run 6 migration threads (6 mount points used), and I average around 25MB/sec/drive going to LT03 as well. All SAN links between the TSM server and the LT03 drives are a minimum of 2Gb, so that is my lowest common denominator. I've tried using less threads to see if perhaps I was saturating an HBA rather than the drive. Same speed. I've tried separating my DB and STG pools on
Back tracking retention
I have a number of retired systems that still have data archived on one of my TSM servers. I'm exporting the data to another TSM server. Is there an easy way to find what mgmt class the data was originally retained as ?
Re: Please tell me about your LTO3 / LTO4 performance
Single migrate process of compress data from DS-4200 to LTO4 ~ 300 GB per hour. 4 Gb fabric, No ISL. -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Kauffman, Tom Sent: Tuesday, July 01, 2008 9:07 AM To: ADSM-L@VM.MARIST.EDU Subject: Re: Please tell me about your LTO3 / LTO4 performance Two items, then. Alternate pathing may help. Also, what is the available bandwidth of the ISL to the edge switches? For your system, it should be at least 6 Gb; 8 would be marginally better (three paired ports at 2 Gb/port, or two paired ports at 4 Gb/port). -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Thach, Kevin G Sent: Tuesday, July 01, 2008 11:52 AM To: ADSM-L@VM.MARIST.EDU Subject: Re: Please tell me about your LTO3 / LTO4 performance I am set up very similar to you. My TSM LPAR HBAS connect to a director class switch which has an ISL to each of the edge switches that the tape drives themselves connect to (odd drives on one and even on the other like yourself.) Therefore, I have 64 rmt devices at the AIX level for my LTO3 drives, as each tape HBA sees each of the 14 drives. I am not using the alternate pathing. -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Kauffman, Tom Sent: Tuesday, July 01, 2008 11:42 AM To: ADSM-L@VM.MARIST.EDU Subject: Re: Please tell me about your LTO3 / LTO4 performance How are your tape drives attached to your TSM HBAs? Presumably by SAN switch, so how do you have the drives zoned? Ideally, every drive should be visible on every fiber and alternate path support should be enabled (chdev -l rmtx -a alt_pathing=yes) (do NOT do for the SMC if you do not have path failover; may not work for LTO3 if you do not have path failover). I have 10 LTO4 and 6 LTO2 drives, and 10 fibers to tape from my TSM LPAR; two SAN switches, with the even-numbered drives in one and the odd-numbered drives in the other. The result is 80 rmt (tape) devices for the LPAR. I know I'm network limited - so I only get a maximum of 110 MB/sec per drive/network interface in my nightly SAP backups. (dedicated Gb networks, one per concurrent backup session - Gigabit Ethernet NICs are cheap!) My off-site copy processes run at LTO2 drive speed (the 'twos are only used for offsite tapes). This is for 4 concurrent sessions over two network interfaces: BKI1215I: Average transmission rate was 762.364 GB/h (216.850 MB/sec). BKI1227I: Average compression factor was 1.000. BKI0020I: End of program at: Mon Jun 30 20:55:08 EDT 2008 . BKI0021I: Elapsed time: 01 h 52 min 00 sec . BKI0024I: Return code is: 0. So I averaged 108 MB/sec over the NIC, and 54 MB/sec to the drive. Tom Kauffman NIBCO, Inc -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Thach, Kevin G Sent: Tuesday, July 01, 2008 10:41 AM To: ADSM-L@VM.MARIST.EDU Subject: Please tell me about your LTO3 / LTO4 performance Hi all- For quite some time now, I have been trying to track down an elusive bottleneck in my TSM environment relating to disk-to-tape performance. This is a long read, but I would be very greatful for any suggestions. Hopefully some of you folks much smarter than me out there will be able to point me in the right direction. If any other LTO3 or LTO4 users out there could give me some examples of their real-world performance along with a little detail on their config, that would be most helpful as well! My current environment consists of: * TSM server = p570 LPAR w/4 1.9GHz processors and 8GB RAM, (6) 2Gb HBAS (2 for disk and 4 for tape traffic), and a 10Gb Ethernet adapter. * TSM 5.4.1.2 on AIX 5.3 TL6 * 3584 w/14 LTO3 drives at primary site * 3584 w/12 LTO1 drives at DR/hotsite (copypool volumes are written directly to this library via SAN routing) * DB (80GB -- 4GB DBVOL size) residing on IBM DS8300 behind IBM SVC * Log (11GB - single LOGVOL) residing on IBM DS8300 behind IBM SVC * Primary Storage pool in question (2.5TB -- 20GB volume size), DISK device class, residing on IBMDS8300 behind IBM SVC I currently back up about 4.5TB / night, of which ~2TB is written directly to my primary LTO3 tape pool with a simultaneous write to my copypool across town. So, each morning I'm left with about 2.5TB of data to copy and migrate from my disk pool(s) to copypool and onsite tape respectively. My backup stg performance to LTO1 tape (copypool) is about what I would expect. I run 5 threads for this process (5 mount points used), and I consistently average 20-25MB/sec/drive. Fair enough. I don't know of anyone getting a whole lot more than that out of an LTO1 drive. After that is complete, I then migrate that data to my LTO3 tape here onsite. That performance is pretty lousy compared to what I would expect to get out of LTO3. I run 6 migration threads (6 mount points used), and
Re: Please tell me about your LTO3 / LTO4 performance
There are two 2Gb ISL's going to each switch for a total bandwidth of 4Gb to each edge. Our SAN monitoring tool (EFCM) doesn't show that we're maxing out the ISL's, but I can easily add one to see what happens. I'll also try the alternate pathing ASAP. Thanks for the suggestions! -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Kauffman, Tom Sent: Tuesday, July 01, 2008 12:07 PM To: ADSM-L@VM.MARIST.EDU Subject: Re: Please tell me about your LTO3 / LTO4 performance Two items, then. Alternate pathing may help. Also, what is the available bandwidth of the ISL to the edge switches? For your system, it should be at least 6 Gb; 8 would be marginally better (three paired ports at 2 Gb/port, or two paired ports at 4 Gb/port). -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Thach, Kevin G Sent: Tuesday, July 01, 2008 11:52 AM To: ADSM-L@VM.MARIST.EDU Subject: Re: Please tell me about your LTO3 / LTO4 performance I am set up very similar to you. My TSM LPAR HBAS connect to a director class switch which has an ISL to each of the edge switches that the tape drives themselves connect to (odd drives on one and even on the other like yourself.) Therefore, I have 64 rmt devices at the AIX level for my LTO3 drives, as each tape HBA sees each of the 14 drives. I am not using the alternate pathing. -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Kauffman, Tom Sent: Tuesday, July 01, 2008 11:42 AM To: ADSM-L@VM.MARIST.EDU Subject: Re: Please tell me about your LTO3 / LTO4 performance How are your tape drives attached to your TSM HBAs? Presumably by SAN switch, so how do you have the drives zoned? Ideally, every drive should be visible on every fiber and alternate path support should be enabled (chdev -l rmtx -a alt_pathing=yes) (do NOT do for the SMC if you do not have path failover; may not work for LTO3 if you do not have path failover). I have 10 LTO4 and 6 LTO2 drives, and 10 fibers to tape from my TSM LPAR; two SAN switches, with the even-numbered drives in one and the odd-numbered drives in the other. The result is 80 rmt (tape) devices for the LPAR. I know I'm network limited - so I only get a maximum of 110 MB/sec per drive/network interface in my nightly SAP backups. (dedicated Gb networks, one per concurrent backup session - Gigabit Ethernet NICs are cheap!) My off-site copy processes run at LTO2 drive speed (the 'twos are only used for offsite tapes). This is for 4 concurrent sessions over two network interfaces: BKI1215I: Average transmission rate was 762.364 GB/h (216.850 MB/sec). BKI1227I: Average compression factor was 1.000. BKI0020I: End of program at: Mon Jun 30 20:55:08 EDT 2008 . BKI0021I: Elapsed time: 01 h 52 min 00 sec . BKI0024I: Return code is: 0. So I averaged 108 MB/sec over the NIC, and 54 MB/sec to the drive. Tom Kauffman NIBCO, Inc -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Thach, Kevin G Sent: Tuesday, July 01, 2008 10:41 AM To: ADSM-L@VM.MARIST.EDU Subject: Please tell me about your LTO3 / LTO4 performance Hi all- For quite some time now, I have been trying to track down an elusive bottleneck in my TSM environment relating to disk-to-tape performance. This is a long read, but I would be very greatful for any suggestions. Hopefully some of you folks much smarter than me out there will be able to point me in the right direction. If any other LTO3 or LTO4 users out there could give me some examples of their real-world performance along with a little detail on their config, that would be most helpful as well! My current environment consists of: * TSM server = p570 LPAR w/4 1.9GHz processors and 8GB RAM, (6) 2Gb HBAS (2 for disk and 4 for tape traffic), and a 10Gb Ethernet adapter. * TSM 5.4.1.2 on AIX 5.3 TL6 * 3584 w/14 LTO3 drives at primary site * 3584 w/12 LTO1 drives at DR/hotsite (copypool volumes are written directly to this library via SAN routing) * DB (80GB -- 4GB DBVOL size) residing on IBM DS8300 behind IBM SVC * Log (11GB - single LOGVOL) residing on IBM DS8300 behind IBM SVC * Primary Storage pool in question (2.5TB -- 20GB volume size), DISK device class, residing on IBMDS8300 behind IBM SVC I currently back up about 4.5TB / night, of which ~2TB is written directly to my primary LTO3 tape pool with a simultaneous write to my copypool across town. So, each morning I'm left with about 2.5TB of data to copy and migrate from my disk pool(s) to copypool and onsite tape respectively. My backup stg performance to LTO1 tape (copypool) is about what I would expect. I run 5 threads for this process (5 mount points used), and I consistently average 20-25MB/sec/drive. Fair enough. I don't know of anyone getting a whole lot more than that out of an LTO1 drive. After that is complete, I then
Re: STORServer ABC
Folks, When I saw this post, I asked our engineers if it would be possible to more nearly approximate the other messages from our client. Unfortunately, we're a V 3.1 API client and as such have very limited support for messages. We can't get them there with what we have. I am equally interested in the results of the post and we'll take the idea under advisement if we become a client based on a later API version. Thanks, Kelly Lipp CTO STORServer, Inc. 485-B Elkton Drive Colorado Springs, CO 80907 719-266-8777 www.storserver.com -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Shawn Drew Sent: Tuesday, July 01, 2008 9:17 AM To: ADSM-L@VM.MARIST.EDU Subject: [ADSM-L] STORServer ABC A bit of a survey for those of you that happen to use the OpenVMS ABC client. I've recently found the /summary option, but the format in the act log is quite different than the normal job reports and our reporting software doesn't catch it. We'll have to modify it, but I was just wondering... How does everyone report on their ABC client backups? Just a normal shell script report? 3rd party reporting tool? Regards, Shawn Shawn Drew 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.
Re: Back tracking retention
On Jul 1, 2008, at 12:53 PM, Ochs, Duane wrote: I have a number of retired systems that still have data archived on one of my TSM servers. I'm exporting the data to another TSM server. Is there an easy way to find what mgmt class the data was originally retained as ? Perform a Select on the Archives table. Richard Sims
