Re: How to run a command for a Mac client
Aha, ok the the simplets solution is the best :-) Works a treat. Thanks Farren -Original Message- From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of Remco Post Sent: 07 October 2010 18:08 To: ADSM-L@vm.marist.edu Subject: Re: [ADSM-L] How to run a command for a Mac client Have you considered creating a normal Incremental schedule and using -opt='-incrbydate' flag? This seems to be far less error prone? On 7 okt 2010, at 13:56, Minns, Farren - Chichester wrote: > Hi all, I wonder if you can help. > > I need to schedule a Mac client to do a daily incrbydate backup. > > On the client I have created a file called daily-incrbydate.sh with the > single line "dsmc incremental -incrbydate" in. > > If I run this directly it works fine, but when I try to create a schedule on > the server to reference this script it does not and I don't know why. > > The schedule looks as follows:- > > Policy Domain Name: STANDARD > Schedule Name: MACSERVERS > Description: Mac Servers >Action: Command > Options: > Objects: /Server HD/Applications/Tivoli Storage > Manager/scripts/daily-incrbydate.sh > > > The error I see in the log are ANS5190E and ANS1512E > > Any ideas? > > Regards > > Farren > > > > > 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, United Kingdom. PO19 8SQ. > -- Met vriendelijke groeten/Kind Regards, Remco Post r.p...@plcs.nl +31 6 248 21 622 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, United Kingdom. PO19 8SQ.
Re: How to run a command for a Mac client
El oct 8, 2010 4:58 a.m., "Minns, Farren - Chichester" escribió: Aha, ok the the simplets solution is the best :-) Works a treat. Thanks Farren -Original Message- From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf ... Have you considered creating a normal Incremental schedule and using -opt='-incrbydate' flag? Thi...
IC65890: running windows xp and tsm client 6.2.1
Just popped up today. Ibm says this apar is closed, march 2010. where can I find the supposed fix? Gary Lee Senior System Programmer Ball State University phone: 765-285-1310
Re: IC65890: running windows xp and tsm client 6.2.1
Hi Gary, The version 6.2 fix for this APAR is targeted for fix pack 6.2.2 in December. The usual caveat applies: until the fixing level is actually available, this information is subject to change. The workaround is to exclude the event logs from the system object backup by adding this to your client options file: exclude.systemobject eventlog While this will not affect the ability to restore the systemobject, the viability of this workaround depends on the criticality of Windows XP event logs to your organization. The fix is currently available in the 5.5.3 client, but reverting to 5.5 would also be tedious: it would require uninstalling 6.2.1, installing 5.5.3, renaming the node name to something else, recreating the original node name again, and starting backups again from scratch. Best regards, Andy Raibeck IBM Software Group Tivoli Storage Manager Client Product Development Level 3 Team Lead Internal Notes e-mail: Andrew Raibeck/Hartford/i...@ibmus Internet e-mail: stor...@us.ibm.com IBM Tivoli Storage Manager support web page: http://www.ibm.com/support/entry/portal/Overview/Software/Tivoli/Tivoli_Storage_Manager "ADSM: Dist Stor Manager" wrote on 2010-10-08 08:33:00: > From: "Lee, Gary D." > To: ADSM-L@vm.marist.edu > Date: 2010-10-08 08:33 > Subject: IC65890: running windows xp and tsm client 6.2.1 > Sent by: "ADSM: Dist Stor Manager" > > Just popped up today. > Ibm says this apar is closed, march 2010. where can I find the supposed fix? > > Gary Lee > Senior System Programmer > Ball State University > phone: 765-285-1310 > >
- ANR999D - Attempt to open volume with conflicting device class IDs
Hi, I just got these messages, but I cannot find any information on it. Can anyone help me? Thank you! Yann MEUNIER De : TSMManager [mailto:TSMManager] Envoyé : vendredi 8 octobre 2010 14:58 À : LD-DPI-STOCKAGE Objet : TSM alert for TSMEP3 at 10/8/2010 (Warning messages) TSM alert for TSMEP3 at 10/8/2010 2:57:38 PM Message(s) : 10/8/2010 2:57:08 PM ANRD_1141620605 pvrOpen(pvr.c:1349) Thread<279076>: Attempt to open volume with conflicting device class IDs: 8, 7 10/8/2010 2:57:08 PM ANRD Thread<279076> issued message from: 10/8/2010 2:57:08 PM ANRD Thread<279076> 0x0001c7e8 StdPutText 10/8/2010 2:57:08 PM ANRD Thread<279076> 0x0001fb90 OutDiagToCons 10/8/2010 2:57:08 PM ANRD Thread<279076> 0x0001a2d0 outDiagfExt 10/8/2010 2:57:08 PM ANRD Thread<279076> 0x000100262d9c pvrOpen 10/8/2010 2:57:08 PM ANRD Thread<279076> 0x0001004096c0 OpenActiveVol 10/8/2010 2:57:08 PM ANRD Thread<279076> 0x00010040b700 AsOpenVol 10/8/2010 2:57:08 PM ANRD Thread<279076> 0x0001002eba34 AsAcquireInputVol 10/8/2010 2:57:08 PM ANRD Thread<279076> 0x00010040229c AsOpenSeg 10/8/2010 2:57:08 PM ANRD Thread<279076> 0x0001003f2194 DoOpenSeg 10/8/2010 2:57:08 PM ANRD Thread<279076> 0x0001003f37f0 AuxAsSource 10/8/2010 2:57:08 PM ANRD Thread<279076> 0x0001003f4554 SsAuxSrcThread 10/8/2010 2:57:08 PM ANRD Thread<279076> 0x0001000151b0 StartThread 10/8/2010 2:57:27 PM ANR1092E Space reclamation is ended for volume 203584. An internal server error was detected. 10/8/2010 2:57:27 PM ANRD Thread<278876> issued message 1092 from: 10/8/2010 2:57:27 PM ANRD Thread<278876> 0x0001e138 StdPutMsg 10/8/2010 2:57:27 PM ANRD Thread<278876> 0x000100013cd4 outRptf 10/8/2010 2:57:27 PM ANRD Thread<278876> 0x0001005547a4 EndMoveVolume 10/8/2010 2:57:27 PM ANRD Thread<278876> 0x0001000c RclmQueuedSourceVols 10/8/2010 2:57:27 PM ANRD Thread<278876> 0x000100555d60 RclmOffsiteVols 10/8/2010 2:57:27 PM ANRD Thread<278876> 0x000100558fd4 AfRclmVolumeThread 10/8/2010 2:57:27 PM ANRD Thread<278876> 0x0001000151b0 StartThread 10/8/2010 2:57:27 PM ANR8216W Error sending data on socket 129. Reason 32. 10/8/2010 2:57:27 PM ANR1854E Unable to flush data to TEC at daintsys1 rc -1 10/8/2010 2:57:27 PM ANR8216W Error sending data on socket 129. Reason 32. Afin de préserver l'environnement, merci de n'imprimer ce courriel qu'en cas de nécessité. Please consider the environment before printing this mail. Ce message et toutes les pièces jointes (ci-après le « message ») sont confidentiels et établis à lintention exclusive de ses destinataires. Toute utilisation de ce message non conforme à sa destination, toute diffusion ou toute publication, totale ou partielle, est interdite, sauf autorisation expresse. Si vous recevez ce message par erreur, merci de le détruire sans en conserver de copie et den avertir immédiatement lexpéditeur. Internet ne permettant pas de garantir lintégrité de ce message, la Caisse des Dépôts et Consignations décline toute responsabilité au titre de ce message sil a été modifié, altéré, déformé ou falsifié. Par ailleurs et malgré toutes les précautions prises pour éviter la présence de virus dans nos envois, nous vous recommandons de prendre, de votre côté, les mesures permettant d'assurer la non-introduction de virus dans votre système informatique. This email message and any attachments (the email) are confidential and intended only for the recipient(s) indicated. If you are not an intented recipient, please be advised that any use, dissemination, forwarding or copying of this email whatsoever is prohibited without Caisse des Depots et Consignations's prior written consent. If you have received this email in error, please delete it without saving a copy and notify the sender immediately. Internet emails are not necessarily secured, and declines responsibility for any changes that may have been made to this email after it was sent. While we take all reasonable precautions to ensure that viruses are not transmitted via emails, we recommend that you take your own measures to prevent viruses from entering your computer system.
Logging which files that have been restored?
Hello Our security team is asking me for a way to log exactly which files are restored How can I see exactly which files and by who they have been restored? The activites table only shows number of objects, but not the specific objects. The restores table seems empty , I did a restore and after that Ran select * from restores, but didn't get any information at all How are you guys monitoring restores? Med vänlig hälsning Niklas Lundström Niklas Lundström Storage Administrator Swedbank AB (publ) 105 34 Stockholm Telefon: +46 (0)8 5859 5164 Mobil: +46 (0)70 24 76 345 Vi ber dig lägga märke till att detta e-postmeddelande kan innehålla konfidentiell information. Om du felaktigt blivit mottagare av detta meddelande ber vi dig informera avsändaren om felet genom att använda svara-funktionen. Vi ber dig också att radera e-postmeddelandet utan att skicka det vidare eller kopiera det. Trots att vi intygar att e-postmeddelandet och eventuella bilagor inte innehåller virus och andra fel som kan påverka datorn eller IT-systemet där det mottages och läses, öppnas det på mottagarens eget ansvar. Vi tar inte på oss något ansvar för förlust eller skada, som har uppstått i samband med att e-postmeddelandet mottagits och använts. _ Please note that this message may contain confidential information. If you have received this message by mistake, please inform the sender of the mistake by sending a reply, then delete the message from your system without making, distributing or retaining any copies of it. Although we believe that the message and any attachment are free from viruses and other errors that might affect the computer or IT system where it is received and read, the recipient opens the message at his or her own risk. We assume no responsibility for any loss or damage arising from the receipt or use of this message.
Re: - ANR999D - Attempt to open volume with conflicting device class IDs
Have you checked out APAR IC70657? Richard Sims
Re: Logging which files that have been restored?
Ideally, clients will log their TSM activities - which the security team might want to insist upon. Architecturally, TSM offers the REPORTRETRIEVE server option. Beware that it can be expensive in terms of TSM db space and added db activity. Richard Sims
TDP TCP/IP error
Hi Everyone, I have a new Microsoft Exchange Server 2010 running on a Windows Server 2008 R2. The TSM Client version is 6.2.1.0 and TDP version 6.1.2.1 I trying to get the TDP working but when I try to run a manual backup do I only get. ANS1033E (RC-53) An invalid TCP/IP address was specified. So I run instead following commands to verify that my connection to TSM work fine by running Tdpexcc query tsm And that did work OK. Then I run a communication test to my Exchange Server Tdpexcc query Exchange And TDP can find the Exchange Server but when it try to connect to the DSMAgent I got a TCP/IP Error. ACN5229E Error obtaining VSS information from Local DSMAgent Node: 'BA_NODE_NAME'. ANS1033E (RC-53) An invalid TCP/IP address was specified. Any idea why I got a TCPIP problem to the local DSM Agent? Thanks Christian
Re: TDP TCP/IP error
Christian, Is your DSMAGENT nodename actually named "BA_NODE_NAME". If not, then I am afraid that you did not follow the configuration steps in the User's Guide. Initial configuration for Exchange 2010 is slightly more complicated than legacy because it uses VSS. Take a look at the book, you will need to perform a a few additional steps like GRANT PROXY on your TSM Server and also set the LOCALDSMAGENTNODE to point to your real DSMAGENT nodename. For example: TDPEXCC SET LOCALDSMAGENTNODE=EXCSEREVR55 Thanks, Del "ADSM: Dist Stor Manager" wrote on 10/08/2010 09:41:55 AM: >> From: Christian Svensson >> To: ADSM-L@vm.marist.edu >> Date: 10/08/2010 09:43 AM >> Subject: TDP TCP/IP error >> Sent by: "ADSM: Dist Stor Manager" >> >> Hi Everyone, >> I have a new Microsoft Exchange Server 2010 running on a Windows >> Server 2008 R2. >> The TSM Client version is 6.2.1.0 and TDP version 6.1.2.1 >> >> I trying to get the TDP working but when I try to run a manual >> backup do I only get. >> ANS1033E (RC-53) An invalid TCP/IP address was specified. >> >> So I run instead following commands to verify that my connection to >> TSM work fine by running >> >> Tdpexcc query tsm >> >> And that did work OK. >> >> Then I run a communication test to my Exchange Server >> Tdpexcc query Exchange >> >> And TDP can find the Exchange Server but when it try to connect to >> the DSMAgent I got a TCP/IP Error. >> >> ACN5229E Error obtaining VSS information from Local DSMAgent Node: >> 'BA_NODE_NAME'. >> ANS1033E (RC-53) An invalid TCP/IP address was specified. >> Any idea why I got a TCPIP problem to the local DSM Agent? >> >> Thanks >> Christian
Re: TDP TCP/IP error
Hi Christian. You must follow the guide ! I'm installed recently this configuration ! You must make theses points : 1 Verify your VSS (you found an explication on IBM site) 2 Configure correctly your TDP 2.1 If you are in DAG/DAC Mode then you must create a node for the dag and a node for your system 2.2 You dag node must be a proxy node and your system node is a granted to save as the proxy 2.3 you muste modify your TDP exchange configuration file. 2.4 You must install the remote agent service (and before CAD + Scheduler) 2.5 You user must have Administrator Priviliges and Exchange Admin too. Best regards Yann MEUNIER -Message d'origine- De : ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] De la part de Christian Svensson Envoyé : vendredi 8 octobre 2010 15:42 À : ADSM-L@VM.MARIST.EDU Objet : [ADSM-L] TDP TCP/IP error Hi Everyone, I have a new Microsoft Exchange Server 2010 running on a Windows Server 2008 R2. The TSM Client version is 6.2.1.0 and TDP version 6.1.2.1 I trying to get the TDP working but when I try to run a manual backup do I only get. ANS1033E (RC-53) An invalid TCP/IP address was specified. So I run instead following commands to verify that my connection to TSM work fine by running Tdpexcc query tsm And that did work OK. Then I run a communication test to my Exchange Server Tdpexcc query Exchange And TDP can find the Exchange Server but when it try to connect to the DSMAgent I got a TCP/IP Error. ACN5229E Error obtaining VSS information from Local DSMAgent Node: 'BA_NODE_NAME'. ANS1033E (RC-53) An invalid TCP/IP address was specified. Any idea why I got a TCPIP problem to the local DSM Agent? Thanks Christian Afin de préserver l'environnement, merci de n'imprimer ce courriel qu'en cas de nécessité. Please consider the environment before printing this mail. Ce message et toutes les pièces jointes (ci-après le « message ») sont confidentiels et établis à lintention exclusive de ses destinataires. Toute utilisation de ce message non conforme à sa destination, toute diffusion ou toute publication, totale ou partielle, est interdite, sauf autorisation expresse. Si vous recevez ce message par erreur, merci de le détruire sans en conserver de copie et den avertir immédiatement lexpéditeur. Internet ne permettant pas de garantir lintégrité de ce message, la Caisse des Dépôts et Consignations décline toute responsabilité au titre de ce message sil a été modifié, altéré, déformé ou falsifié. Par ailleurs et malgré toutes les précautions prises pour éviter la présence de virus dans nos envois, nous vous recommandons de prendre, de votre côté, les mesures permettant d'assurer la non-introduction de virus dans votre système informatique. This email message and any attachments (the email) are confidential and intended only for the recipient(s) indicated. If you are not an intented recipient, please be advised that any use, dissemination, forwarding or copying of this email whatsoever is prohibited without Caisse des Depots et Consignations's prior written consent. If you have received this email in error, please delete it without saving a copy and notify the sender immediately. Internet emails are not necessarily secured, and declines responsibility for any changes that may have been made to this email after it was sent. While we take all reasonable precautions to ensure that viruses are not transmitted via emails, we recommend that you take your own measures to prevent viruses from entering your computer system.
Re: - ANR999D - Attempt to open volume with conflicting device class IDs
No, I didn't find it ! I had a look, its the same issue, but I'm not in the same version. My tsm server is in 5.5.3.0. If i understood, I have to wait for an update ! :) Thanks for your help. Best regards, Yann MEUNIER -Message d'origine- De : ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] De la part de Richard Sims Envoyé : vendredi 8 octobre 2010 15:30 À : ADSM-L@VM.MARIST.EDU Objet : Re: [ADSM-L] - ANR999D - Attempt to open volume with conflicting device class IDs Have you checked out APAR IC70657? Richard Sims Afin de préserver l'environnement, merci de n'imprimer ce courriel qu'en cas de nécessité. Please consider the environment before printing this mail. Ce message et toutes les pièces jointes (ci-après le « message ») sont confidentiels et établis à lintention exclusive de ses destinataires. Toute utilisation de ce message non conforme à sa destination, toute diffusion ou toute publication, totale ou partielle, est interdite, sauf autorisation expresse. Si vous recevez ce message par erreur, merci de le détruire sans en conserver de copie et den avertir immédiatement lexpéditeur. Internet ne permettant pas de garantir lintégrité de ce message, la Caisse des Dépôts et Consignations décline toute responsabilité au titre de ce message sil a été modifié, altéré, déformé ou falsifié. Par ailleurs et malgré toutes les précautions prises pour éviter la présence de virus dans nos envois, nous vous recommandons de prendre, de votre côté, les mesures permettant d'assurer la non-introduction de virus dans votre système informatique. This email message and any attachments (the email) are confidential and intended only for the recipient(s) indicated. If you are not an intented recipient, please be advised that any use, dissemination, forwarding or copying of this email whatsoever is prohibited without Caisse des Depots et Consignations's prior written consent. If you have received this email in error, please delete it without saving a copy and notify the sender immediately. Internet emails are not necessarily secured, and declines responsibility for any changes that may have been made to this email after it was sent. While we take all reasonable precautions to ensure that viruses are not transmitted via emails, we recommend that you take your own measures to prevent viruses from entering your computer system.
Re: TDP TCP/IP error
Hi Christian: I'm not an expert in this area, but ran in to a problem where I could not obtain VSS information from Local DSMAgent Node and an IBM subscriber on this listserv pointed out to me that I had USERID=NONE set for the node when I registered it and it cannot be set to USERID=NONE. Just thought I would throw that out. Not sure it will even pertain to your situation. Regards, Danny Schmanny ___ From: Christian Svensson [christian.svens...@cristie.se] To: ADSM SubscriberList [ads...@vm.marist.edu] CC: Subject:[ADSM-L] TDP TCP/IP error Time: 10/8/2010 at 9:41AM Hi Everyone, I have a new Microsoft Exchange Server 2010 running on a Windows Server 2008 R2. The TSM Client version is 6.2.1.0 and TDP version 6.1.2.1 I trying to get the TDP working but when I try to run a manual backup do I only get. ANS1033E (RC-53) An invalid TCP/IP address was specified. So I run instead following commands to verify that my connection to TSM work fine by running Tdpexcc query tsm And that did work OK. Then I run a communication test to my Exchange Server Tdpexcc query Exchange And TDP can find the Exchange Server but when it try to connect to the DSMAgent I got a TCP/IP Error. ACN5229E Error obtaining VSS information from Local DSMAgent Node: 'BA_NODE_NAME'. ANS1033E (RC-53) An invalid TCP/IP address was specified. Any idea why I got a TCPIP problem to the local DSM Agent? Thanks Christian
SV: TDP TCP/IP error
Hi Del, Here is the ouput from a couple of query commands from tdpexcc. Tdpexecc query tsm IBM Tivoli Storage Manager for Mail: Data Protection for Microsoft Exchange Server Version 6, Release 1, Level 2.01 (C) Copyright IBM Corporation 1998, 2010. All rights reserved. Tivoli Storage Manager Server Connection Information Nodename ... BA_NAME_EXCH NetWork Host Name of Server xxx.xxx.xxx.xxx TSM API Version Version 6, Release 2, Level 1.0 Server Name TSM_SERVERNAME Server Type Linux/x86_64 Server Version . Version 6, Release 2, Level 1.0 Compression Mode ... Client Determined Domain Name MAIL_DO Active Policy Set .. PS_DB Default Management Class ... MC_DB Tdpexecc query tdp IBM Tivoli Storage Manager for Mail: Data Protection for Microsoft Exchange Server Version 6, Release 1, Level 2.01 (C) Copyright IBM Corporation 1998, 2010. All rights reserved. Data Protection for Exchange Preferences BACKUPDESTination... TSM BACKUPMETHod VSS DATEformat . 3 LANGuage ... ENU LOCALDSMAgentnode... BA_NAME LOGFile tdpexc.log LOGPrune ... 60 MOUNTWait .. Yes NUMberformat ... 1 REMOTEDSMAgentnode.. TEMPDBRestorepath... TEMPLOGRestorepath.. TIMEformat . 1 Tdpexecc query exchange IBM Tivoli Storage Manager for Mail: Data Protection for Microsoft Exchange Server Version 6, Release 1, Level 2.01 (C) Copyright IBM Corporation 1998, 2010. All rights reserved. Querying Exchange Server to gather component information, please wait... Microsoft Exchange Server Information - Server Name: BA_NAME Domain Name: company.net Exchange Server Version: 14.1.218.15 (Exchange Server 2010) Databases and Status Db1 Circular Logging - Disabled DAG Status - Active Recovery - False Db1 Online Db3 Circular Logging - Disabled DAG Status - Passive (Healthy) Recovery - False Db3 Online Db4 Circular Logging - Disabled DAG Status - Active Recovery - False Db4 Online DB6 Circular Logging - Disabled DAG Status - Passive (Healthy) Recovery - False DB6 Online Volume Shadow Copy Service (VSS) Information ACN5229E Error obtaining VSS information from Local DSMAgent Node: 'BA_NODE'. ANS1033E (RC-53) An invalid TCP/IP address was specified. type ..\baclient\dsmwebcl.log 10/08/2010 15:15:20 (dsmcad) IBM Tivoli Storage Manager 10/08/2010 15:15:20 (dsmcad) Client Acceptor - Built Apr 27 2010 04:37:40 10/08/2010 15:15:20 (dsmcad) Version 6, Release 2, Level 1.0 10/08/2010 15:15:20 (dsmcad) ANS3000I TCP/IP communications available on port 20 570. 10/08/2010 15:15:20 (dsmcad) Dsmcad is working in Webclient mode. 10/08/2010 15:15:20 (dsmcad) ANS3000I HTTP communications available on port 1581 . 10/08/2010 15:28:16 (dsmcad) IBM Tivoli Storage Manager 10/08/2010 15:28:16 (dsmcad) Client Acceptor - Built Apr 27 2010 04:37:40 10/08/2010 15:28:16 (dsmcad) Version 6, Release 2, Level 1.0 10/08/2010 15:28:16 (dsmcad) ANS3000I TCP/IP communications available on port 15 251. 10/08/2010 15:28:16 (dsmcad) Dsmcad is working in Webclient mode. 10/08/2010 15:28:16 (dsmcad) ANS3000I HTTP communications available on port 1581 . tsm: TSM_SERVER>q proxyn Session established with server 888STHBCK001: Linux/x86_64 Server Version 6, Release 2, Level 1.0 Server date/time: 10/08/2010 16:17:05 Last access: 10/08/2010 13:39:25 Target Node Agent Node --- - BA_NAME_EXCHBA_NAME Thanks Christian -Ursprungligt meddelande- Från: Del Hoobler [mailto:hoob...@us.ibm.com] Skickat: den 8 oktober 2010 15:56 Till: ADSM-L@VM.MARIST.EDU Ämne: Re: TDP TCP/IP error Christian, Is your DSMAGENT nodename actually named "BA_NODE_NAME". If not, then I am afraid that you did not follow the configuration steps in the User's Guide. Initial configuration for Exchange 2010 is slightly more complicated than legacy because it uses VSS. Take a look at the book, you will need to perform a a few additional steps like GRANT PROXY on your TSM Server and also set the LOCALDSMAGENTNODE to point to your real DSMAGENT nodename. For example: TDPEXCC SET LOCALDSMAGENTN
Re: SV: TDP TCP/IP error
The problem is that your DSMAGENT node name appears to be: BA_NODE but your LOCALDSMAGENTNODE is set to: BA_NAME Please correct this. Thanks, Del
Re: Looking for SAN/tape experts assistance
Sergio,
Thanks for the experience/guidance/details. Looks like we may be heading
in this direction, although we aren't sure why.
To update our situation.
After doing some digging and pure-luck, I discovered one of the fibre
connections had gone "amber". Not sure why since when we cabled the
server to the switch, we always make sure it is green. Working with the
SAN person (tried cable swapping, etc), he discovered that switch port was
set to 1GB vs auto. He reconfigured to auto. I rebooted the server
5-times and after the 2nd reboot, the /dev/IBMtape values seemed to stay
the same after each reboot.
We thought everything was smooth sailing until last night (
http://www.wtvr.com/news/wtvr-downtown-smoke-power-grid-story,0,3680878.story
)
After we got things back up and running today, not only did the
/dev/IBMtape mappings change on this server, but it also changed on my
1-production 6.1 server, which in the past had been steady. The
4-production 5.5 servers did not change.
So, we are sortof back to square-1.
I am beginning to wonder if it has something to do with the OS. All of
the 5.5 servers are running RH4 or older RH5 kernels (-92 vs -128/-194)
Did you finish testing your configuration/accessing the drives?
I am curious - are other folks out there who run Linux TSM servers
creating these rules?
Zoltan Forray
TSM Software & Hardware Administrator
Virginia Commonwealth University
UCC/Office of Technology Services
zfor...@vcu.edu - 804-828-4807
Don't be a phishing victim - VCU and other reputable organizations will
never use email to request that you reply with your password, social
security number or confidential personal information. For more details
visit http://infosecurity.vcu.edu/phishing.html
From:
"Sergio O. Fuentes"
To:
ADSM-L@VM.MARIST.EDU
Date:
09/27/2010 01:43 PM
Subject:
Re: [ADSM-L] Looking for SAN/tape experts assistance
Sent by:
"ADSM: Dist Stor Manager"
I'm doing this work right now for a big project here. My first endeavor
into Linux.
The lin_tape drivers for 6.2 will require a .rules file in
/etc/udev/rules.d (or wherever your udev stuff lives) mainly because of
the instance owner/group requirements to run 6.2 dsmserv processes. Unless
you can alter your default udev rules for EVERYTHING, then you'll need the
.rule file to assign ownership and mode parameters for the tape devices.
Mine, so far, looks like this:
#cat /etc/udev/rules.d/98-lin_tape.rules
KERNEL=="IBMchanger*", SYSFS{primary_path}=="Primary",
SYSFS{serial_num}=="078150090402", OWNER="tsminst1", MODE="0600",
SYMLINK="lin_tape/IBMchanger137B"
KERNEL=="IBMchanger*", SYSFS{primary_path}=="Alternate",
SYSFS{serial_num}=="078150090402", OWNER="tsminst1", MODE="0600",
SYMLINK="lin_tape/IBMchanger138A"
KERNEL=="IBMtape*[0-9]",SYSFS{ww_port_name}=="0x5005076300549127",
OWNER="tsminst1", MODE="0600", SYMLINK="lin_tape/IBMtape137"
KERNEL=="IBMtape*[0-9]",SYSFS{ww_port_name}=="0x5005076300549128",
OWNER="tsminst1", MODE="0600", SYMLINK="lin_tape/IBMtape138"
KERNEL=="IBMtape*[0-9]",SYSFS{ww_port_name}=="0x5005076300549129",
OWNER="tsminst1", MODE="0600", SYMLINK="lin_tape/IBMtape139"
KERNEL=="IBMtape*n", OWNER="tsminst1", MODE="0600"
There are a lot of gotchas with this method that I'm running into. I'm
not sure if they are kernel bugs or driver issues but not much of this is
documented anywhere. Bullet-list (so far):
-If you have alternate pathing or data path failover, lin_taped needs
be installed and running. Problem is getting persistent binding to work
with this. There's a race condition where once modprobe lin_tape is run,
the udev files are created with the rules. But the SYSFS{primary_path}
key isn't defined correctly until lin_taped is run, BUT lin_taped can't
run until lin_tape is loaded. So by the time lin_taped is executed and
running, the lin_tape rules have already been processed for udev.
oMy workaround will be to create an init script that will run
lin_taped and then udevtrigger. Seems to work, but udevtrigger once
crashed the system.
-Sometimes when lin_tape is loaded, the mode is incorrect for devices.
The fix is again "udevtrigger".
-KERNEL=="IBMtape*" doesn't work for renaming, because sometimes a
symlink to IBMtape1n is used instead of IBMtape1. Which is why I have the
character class "IBMtape*[0-9]"
Here's the output for ls /dev/ commands for when I believe things are
configured correctly. Caveat: I haven't even tested reading/writing to
these devices yet, let alone defining the devices to TSM.
#ls -l /dev/IBMtape*
crw-r--r-- 1 root root 250, 3071 Sep 27 11:43 /dev/IBMtape
crw--- 1 tsminst1 root 250,0 Sep 27 11:43 /dev/IBMtape0
crw--- 1 tsminst1 root 250, 1024 Sep 27 11:43 /dev/IBMtape0n
crw--- 1 tsminst1 root 250,1 Sep 27 11:43 /dev/IBMtape1
crw--- 1 tsminst1 root 250, 1025 Sep 27 11:43 /dev/IBMtape1n
crw--- 1 ts
Frustrated by slowness in TSM 6.2
Hi all I am running TSM 6.2.1.1 on AIX V615 in a LPAR on a P770. The LPAR has 6 shared CPU's, 12 virtual CPU;s, and 64GB of memory. There are 2 VIO servers with 4 fiber channel connections to XIV storage for the DB and LOG, and 2 10Gbit Ethernet in each VIO in an Etherchannel configuration. The storage pool is on Data Domain DD880's, 2 per AIX, 1 per instance. I am seeing consistenly poor performance from this setup. I have tested network from VIO to cloud, and LPAR to VIO, which seems fine. I tested LPAR to Data Domain, and things seem fine. But, when backups are running (and I only have a few nodes there yet, this is a new setup), TSM doesn't seem to want to go over 20 to 30MB/s throughput. I tried backing up the TSM server over lo, and that was a little better at 50MB/s, but not screaming. I tried using chunk of SAN as a disk pool ahead of the Data Domain, no change. I am at my whit's end. If anyone has any ideas, please let me know. Thanks. -- Andy Carlson --- Gamecube:$150,PSO:$50,Broadband Adapter: $35, Hunters License: $8.95/month, The feeling of seeing the red box with the item you want in it:Priceless.
Re: Frustrated by slowness in TSM 6.2
I would be suspicious of having the db on XIV. Do you have any FC or SAS Disk you could try putting the DB on? I know XIV has lots of CPU & cache, but underneath it all is still SATA. I've heard Marketing types rave about how fast XIV is, even with SATA, because I/O can be spread across many spindles, but I'm not entirely convinced it's as good as 15k FC or SAS. ..Paul On Oct 8, 2010, at 12:27 PM, "Andrew Carlson" wrote: > Hi all > > I am running TSM 6.2.1.1 on AIX V615 in a LPAR on a P770. The LPAR > has 6 shared CPU's, 12 virtual CPU;s, and 64GB of memory. There are 2 > VIO servers with 4 fiber channel connections to XIV storage for the DB > and LOG, and 2 10Gbit Ethernet in each VIO in an Etherchannel > configuration. The storage pool is on Data Domain DD880's, 2 per AIX, > 1 per instance. > > I am seeing consistenly poor performance from this setup. I have > tested network from VIO to cloud, and LPAR to VIO, which seems fine. > I tested LPAR to Data Domain, and things seem fine. But, when backups > are running (and I only have a few nodes there yet, this is a new > setup), TSM doesn't seem to want to go over 20 to 30MB/s throughput. > I tried backing up the TSM server over lo, and that was a little > better at 50MB/s, but not screaming. I tried using chunk of SAN as a > disk pool ahead of the Data Domain, no change. I am at my whit's end. > > If anyone has any ideas, please let me know. Thanks. > > -- > Andy Carlson > --- > Gamecube:$150,PSO:$50,Broadband Adapter: $35, Hunters License: $8.95/month, > The feeling of seeing the red box with the item you want in it:Priceless.
Re: Frustrated by slowness in TSM 6.2
It is a lightly loaded XIV, and the disk system does not seem under pressure, unless I force it with dd or something in testing, but I will check it out. Any other ideas out there? On Fri, Oct 8, 2010 at 11:37 AM, Paul Zarnowski wrote: > I would be suspicious of having the db on XIV. Do you have any FC or SAS Disk > you could try putting the DB on? I know XIV has lots of CPU & cache, but > underneath it all is still SATA. I've heard Marketing types rave about how > fast XIV is, even with SATA, because I/O can be spread across many spindles, > but I'm not entirely convinced it's as good as 15k FC or SAS. > > ..Paul > > > On Oct 8, 2010, at 12:27 PM, "Andrew Carlson" wrote: > >> Hi all >> >> I am running TSM 6.2.1.1 on AIX V615 in a LPAR on a P770. The LPAR >> has 6 shared CPU's, 12 virtual CPU;s, and 64GB of memory. There are 2 >> VIO servers with 4 fiber channel connections to XIV storage for the DB >> and LOG, and 2 10Gbit Ethernet in each VIO in an Etherchannel >> configuration. The storage pool is on Data Domain DD880's, 2 per AIX, >> 1 per instance. >> >> I am seeing consistenly poor performance from this setup. I have >> tested network from VIO to cloud, and LPAR to VIO, which seems fine. >> I tested LPAR to Data Domain, and things seem fine. But, when backups >> are running (and I only have a few nodes there yet, this is a new >> setup), TSM doesn't seem to want to go over 20 to 30MB/s throughput. >> I tried backing up the TSM server over lo, and that was a little >> better at 50MB/s, but not screaming. I tried using chunk of SAN as a >> disk pool ahead of the Data Domain, no change. I am at my whit's end. >> >> If anyone has any ideas, please let me know. Thanks. >> >> -- >> Andy Carlson >> --- >> Gamecube:$150,PSO:$50,Broadband Adapter: $35, Hunters License: $8.95/month, >> The feeling of seeing the red box with the item you want in it:Priceless. > -- Andy Carlson --- Gamecube:$150,PSO:$50,Broadband Adapter: $35, Hunters License: $8.95/month, The feeling of seeing the red box with the item you want in it:Priceless.
Re: Looking for SAN/tape experts assistance
Well, I've gotten a little further along. The drives and paths have been added
to TSM and TSM is reporting all the information correctly (SN, Support RW
types, WWN's, etc.). Still haven't tried opening the drives and
reading/writing tapes (next step). The init script I use to load lin_tape is
as follows: (this is actually just a basic rc script that we have to use for
customized applications. lin_tape has its own /etc/init.d/lin_tape start up
script, but I have opted not to use it for now):
[ -x /etc/init.d/functions ] && . /etc/init.d/functions
echo -n "Starting lin_tape: "
modprobe lin_tape
RETVAL=$?
[ $RETVAL -eq 0 ] && [ -x /usr/bin/lin_taped ] && /usr/bin/lin_taped start
RETVAL=$RETVAL||$?
echo -n "Binding IBMtape and IBMchanger devices: "
[ $RETVAL -eq 0 ] && /sbin/udevtrigger
echo
Notice how udevtrigger is there. I don't believe that's in the lin_tape init
script by default. We've rebooted the server several times, have created new
kernel updates regularly and nothing has been able to break the lin_tape
functionality, so that's a plus (knock on wood). We're on a pretty recent
kernel though, so that must be helping some:
$ uname -r
2.6.18-194.11.4.el5
Lin_tape version
#modinfo lin_tape
filename: /lib/modules/2.6.18-194.11.4.el5/kernel/drivers/scsi/lin_tape.ko
version:1.41.1
license:GPL
description:IBM Linux SCSI Tape Device Driver for IBM Tape Devices
author: IBM Corporation
srcversion: CA19B1A253F80F44D925789
depends:scsi_mod
vermagic: 2.6.18-194.3.1.el5 SMP mod_unload gcc-4.1
SF
-Original Message-
From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of Zoltan
Forray/AC/VCU
Sent: Friday, October 08, 2010 12:19 PM
To: ADSM-L@VM.MARIST.EDU
Subject: Re: [ADSM-L] Looking for SAN/tape experts assistance
Sergio,
Thanks for the experience/guidance/details. Looks like we may be heading
in this direction, although we aren't sure why.
To update our situation.
After doing some digging and pure-luck, I discovered one of the fibre
connections had gone "amber". Not sure why since when we cabled the
server to the switch, we always make sure it is green. Working with the
SAN person (tried cable swapping, etc), he discovered that switch port was
set to 1GB vs auto. He reconfigured to auto. I rebooted the server
5-times and after the 2nd reboot, the /dev/IBMtape values seemed to stay
the same after each reboot.
We thought everything was smooth sailing until last night (
http://www.wtvr.com/news/wtvr-downtown-smoke-power-grid-story,0,3680878.story
)
After we got things back up and running today, not only did the
/dev/IBMtape mappings change on this server, but it also changed on my
1-production 6.1 server, which in the past had been steady. The
4-production 5.5 servers did not change.
So, we are sortof back to square-1.
I am beginning to wonder if it has something to do with the OS. All of
the 5.5 servers are running RH4 or older RH5 kernels (-92 vs -128/-194)
Did you finish testing your configuration/accessing the drives?
I am curious - are other folks out there who run Linux TSM servers
creating these rules?
Zoltan Forray
TSM Software & Hardware Administrator
Virginia Commonwealth University
UCC/Office of Technology Services
zfor...@vcu.edu - 804-828-4807
Don't be a phishing victim - VCU and other reputable organizations will
never use email to request that you reply with your password, social
security number or confidential personal information. For more details
visit http://infosecurity.vcu.edu/phishing.html
From:
"Sergio O. Fuentes"
To:
ADSM-L@VM.MARIST.EDU
Date:
09/27/2010 01:43 PM
Subject:
Re: [ADSM-L] Looking for SAN/tape experts assistance
Sent by:
"ADSM: Dist Stor Manager"
I'm doing this work right now for a big project here. My first endeavor
into Linux.
The lin_tape drivers for 6.2 will require a .rules file in
/etc/udev/rules.d (or wherever your udev stuff lives) mainly because of
the instance owner/group requirements to run 6.2 dsmserv processes. Unless
you can alter your default udev rules for EVERYTHING, then you'll need the
.rule file to assign ownership and mode parameters for the tape devices.
Mine, so far, looks like this:
#cat /etc/udev/rules.d/98-lin_tape.rules
KERNEL=="IBMchanger*", SYSFS{primary_path}=="Primary",
SYSFS{serial_num}=="078150090402", OWNER="tsminst1", MODE="0600",
SYMLINK="lin_tape/IBMchanger137B"
KERNEL=="IBMchanger*", SYSFS{primary_path}=="Alternate",
SYSFS{serial_num}=="078150090402", OWNER="tsminst1", MODE="0600",
SYMLINK="lin_tape/IBMchanger138A"
KERNEL=="IBMtape*[0-9]",SYSFS{ww_port_name}=="0x5005076300549127",
OWNER="tsminst1", MODE="0600", SYMLINK="lin_tape/IBMtape137"
KERNEL=="IBMtape*[0-9]",SYSFS{ww_port_name}=="0x5005076300549128",
OWNER="tsminst1", MODE="0600", SYMLINK="lin_tape/IBMtape138"
KERNEL=="IBMtape*[0-9]",SYSFS{ww_port_name}=="0x5005076300549129",
OWN
Re: Frustrated by slowness in TSM 6.2
> I would be suspicious of having the db on XIV. Do you have any FC > or SAS Disk you could try putting the DB on? I know XIV has lots > of CPU & cache, but underneath it all is still SATA. I've heard > Marketing types rave about how fast XIV is, even with SATA, > because I/O can be spread across many spindles, but I'm not > entirely convinced it's as good as 15k FC or SAS. This is _exactly_ what IBM has not, and seems unwilling, to explain. Soon after IBM finalized the purchase of XIV, they had a series of seminars around the country (usa) about the box. This wasn't some little out of the way seminar . . . Moshe (inventor of the box) was there and gave much of the presentation. I attended one - Lets just say it was strange!!! They hammered on "high performance", over and over. They threw up one graph where they claimed 25k iops at 3ms response time for a "cache miss" workload. Lets see, cache miss means having to go to the spindle to do the I/O. SATA drives come no where close to this response time. The workload was either not cache miss, or, they effectively short-stroked the drive such that the heads never moved. When I questioned this claim I got nowhere - just run-around. Rick - The information contained in this message is intended only for the personal and confidential use of the recipient(s) named above. If the reader of this message is not the intended recipient or an agent responsible for delivering it to the intended recipient, you are hereby notified that you have received this document in error and that any review, dissemination, distribution, or copying of this message is strictly prohibited. If you have received this communication in error, please notify us immediately, and delete the original message.
Re: Frustrated by slowness in TSM 6.2
Rick, I think their response would be something along these lines... The XIV can perform better than other traditional arrays because the [cache miss] I/Os are spread across so many more spindles. I get that. But it seems to be that that can break down when the overall I/O load gets sufficiently high, across all of the spindles. In an I/O intensive environment such as TSM, I think this could be more likely to happen - particularly if you are using XIV for storage pools as well as for database volumes. I'm still skeptical about how far it can go. I can buy that it has good performance --- for a SATA-based product. But not compared to a pure 15K spindle-based product. Oh, and the SATA drives are larger than the SAS or FC drives, which doesn't help. ..Paul At 01:57 PM 10/8/2010, Richard Rhodes wrote: >> I would be suspicious of having the db on XIV. Do you have any FC >> or SAS Disk you could try putting the DB on? I know XIV has lots >> of CPU & cache, but underneath it all is still SATA. I've heard >> Marketing types rave about how fast XIV is, even with SATA, >> because I/O can be spread across many spindles, but I'm not >> entirely convinced it's as good as 15k FC or SAS. > >This is _exactly_ what IBM has not, and seems unwilling, to explain. > >Soon after IBM finalized the purchase of XIV, they had a series >of seminars around the country (usa) about the box. This wasn't some >little out of the way seminar . . . Moshe (inventor of the box) >was there and gave much of the presentation. I attended one - Lets >just say it was strange!!! They hammered on "high performance", over >and over. They threw up one graph where they claimed 25k iops at >3ms response time for a "cache miss" workload. Lets see, cache miss >means having to go to the spindle to do the I/O. SATA drives come >no where close to this response time. The workload was either >not cache miss, or, they effectively short-stroked the drive such >that the heads never moved. When I questioned this claim I >got nowhere - just run-around. > >Rick > > > >- >The information contained in this message is intended only for the personal >and confidential use of the recipient(s) named above. If the reader of this >message is not the intended recipient or an agent responsible for delivering >it to the intended recipient, you are hereby notified that you have received >this document in error and that any review, dissemination, distribution, or >copying of this message is strictly prohibited. If you have received this >communication in error, please notify us immediately, and delete the original >message. -- Paul ZarnowskiPh: 607-255-4757 Manager, Storage Services Fx: 607-255-8521 719 Rhodes Hall, Ithaca, NY 14853-3801Em: p...@cornell.edu
