Strange behavior process onsite - offsite
Hello everyone! I have this tapes in state mountable: 27,30,29,25 I move all this tape in state vault, so i remove them from library But, today when I give q drmedia it shows only 27,30,29 in state vault. Where is tape 25 ? tape 25 disapear completly? q libvol does not show nothing about tape 25 And another thing. select volume_name,access,status from volumes show me data about tape 27 with access OFFLINE , which is in vault. 27 is the only tape with access offsite. Is that corect? The other 2 tapes(29,30) i see them only with q drmedia in state vault. q libvol not showing all those tapes. Can anyone explain what happened in this scenario? TIA
Re: How to see what files are being backed up.
Something like this SELECT HL_NAME,LL_NAME FROM BACKUPS - WHERE NODE_NAME='YOURNODE' - AND BACKUP_DATE BETWEEN '2004-08-25 18:00' AND '2004-08-26 08:00' Jason Couto [EMAIL PROTECTED] Sent by: ADSM: Dist Stor Manager [EMAIL PROTECTED] 25/08/2004 19:32 Please respond to ADSM: Dist Stor Manager [EMAIL PROTECTED] To [EMAIL PROTECTED] cc Subject How to see what files are being backed up. We are using Quiet mode in the dsm.sys file in unix clients, is there any way to query the database to find out what files are being backed up on any given day? We are trying to find out what files are being backed up by our incremental job to compile our versioning scheme. Jason This e-mail may be privileged and/or confidential, and the sender does not waive any related rights and obligations. Any distribution, use or copying of this e-mail or the information it contains by other than an intended recipient is unauthorized. If you received this e-mail in error, please advise me (by return e-mail or otherwise) immediately. Ce courriel est confidentiel et protege. L'expediteur ne renonce pas aux droits et obligations qui s'y rapportent. Toute diffusion, utilisation ou copie de ce message ou des renseignements qu'il contient par une personne autre que le (les) destinataire(s) designe(s) est interdite. Si vous recevez ce courriel par erreur, veuillez m'en aviser immediatement, par retour de courriel ou par un autre moyen. ** The information in this E-Mail is confidential and may be legally privileged. It may not represent the views of Scottish and Southern Energy Group. It is intended solely for the addressees. Access to this E-Mail by anyone else is unauthorised. If you are not the intended recipient, any disclosure, copying, distribution or any action taken or omitted to be taken in reliance on it, is prohibited and may be unlawful. Any unauthorised recipient should advise the sender immediately of the error in transmission. Scottish Hydro-Electric, Southern Electric, SWALEC and S+S are trading names of the Scottish and Southern Energy Group. **
Re: Running periodic Full backups
Maybe, worth another think about this Are tape mount delays really the problem ? If you have tape robot this is rarely a major factor in slow restores, Usually it is the network or the client that is the bottleneck Have you looked at the restore session stats. If you really think that tape mounts are an issue then have a look at 1) move node data 2) backupsets 3) reclamation thresholds George Hagopian [EMAIL PROTECTED] Sent by: ADSM: Dist Stor Manager [EMAIL PROTECTED] 25/08/2004 23:43 Please respond to ADSM: Dist Stor Manager [EMAIL PROTECTED] To [EMAIL PROTECTED] cc Subject Re: Running periodic Full backups Use the selective backup option...you have to tell TSM what filesystems/drive letters to backup but it does work. -Original Message- From: Cargill, Bill [mailto:[EMAIL PROTECTED] Sent: Wednesday, August 25, 2004 6:20 PM To: [EMAIL PROTECTED] Subject:Running periodic Full backups Does anyone know how to easily force a full backup? I know about changing the management class attribute copymode to absolute. What I'm trying to do is run a monthly full backup to improve our restore performance. What we're running into are many tape mounts doing a point in time restore even in a co-located storage pool. Bill Cargill Sr. Technical Support Specialist 425-783-4466 [EMAIL PROTECTED] ** The information in this E-Mail is confidential and may be legally privileged. It may not represent the views of Scottish and Southern Energy Group. It is intended solely for the addressees. Access to this E-Mail by anyone else is unauthorised. If you are not the intended recipient, any disclosure, copying, distribution or any action taken or omitted to be taken in reliance on it, is prohibited and may be unlawful. Any unauthorised recipient should advise the sender immediately of the error in transmission. Scottish Hydro-Electric, Southern Electric, SWALEC and S+S are trading names of the Scottish and Southern Energy Group. **
Select on tsm server version?
Hi, Is there a table where TSM holds it´s server version that I can use in a select statement? I know I get the info from q stat but I rather not do that on 1+ servers. //Henrik --- 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: Running periodic Full backups
What about running image backups? There's a section of the client manual discussing image backups and incrementals for restore/recovery. Bill Boyer A Life? Cool!! Where can I download one of those? - ??? -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] Behalf Of John Naylor Sent: Thursday, August 26, 2004 4:08 AM To: [EMAIL PROTECTED] Subject: Re: Running periodic Full backups Maybe, worth another think about this Are tape mount delays really the problem ? If you have tape robot this is rarely a major factor in slow restores, Usually it is the network or the client that is the bottleneck Have you looked at the restore session stats. If you really think that tape mounts are an issue then have a look at 1) move node data 2) backupsets 3) reclamation thresholds George Hagopian [EMAIL PROTECTED] Sent by: ADSM: Dist Stor Manager [EMAIL PROTECTED] 25/08/2004 23:43 Please respond to ADSM: Dist Stor Manager [EMAIL PROTECTED] To [EMAIL PROTECTED] cc Subject Re: Running periodic Full backups Use the selective backup option...you have to tell TSM what filesystems/drive letters to backup but it does work. -Original Message- From: Cargill, Bill [mailto:[EMAIL PROTECTED] Sent: Wednesday, August 25, 2004 6:20 PM To: [EMAIL PROTECTED] Subject:Running periodic Full backups Does anyone know how to easily force a full backup? I know about changing the management class attribute copymode to absolute. What I'm trying to do is run a monthly full backup to improve our restore performance. What we're running into are many tape mounts doing a point in time restore even in a co-located storage pool. Bill Cargill Sr. Technical Support Specialist 425-783-4466 [EMAIL PROTECTED] ** The information in this E-Mail is confidential and may be legally privileged. It may not represent the views of Scottish and Southern Energy Group. It is intended solely for the addressees. Access to this E-Mail by anyone else is unauthorised. If you are not the intended recipient, any disclosure, copying, distribution or any action taken or omitted to be taken in reliance on it, is prohibited and may be unlawful. Any unauthorised recipient should advise the sender immediately of the error in transmission. Scottish Hydro-Electric, Southern Electric, SWALEC and S+S are trading names of the Scottish and Southern Energy Group. **
Re: Licensing
Yes, the node that used to be lan free is still an active node and still has (lots) of data on tsm. It just does not use lan free anymore. The Server definition for the storage agent that the lan free client used to use was removed from tsm over a year ago. David [EMAIL PROTECTED] 8/25/2004 3:30:25 AM Hi Does the storage agent node (_SA) have data within TSM? If not, you need to remove the storage agent node from the TSM server(which shouldnt be a problem, as the node in question is no longer using LAN-free functionality). That should also remove the license requirement. Best Regards Daniel Sparrman --- Daniel Sparrman Exist i Stockholm AB Propellervägen 6B 183 62 TÄBY Växel: 08 - 754 98 00 Mobil: 070 - 399 27 51 David E Ehresman [EMAIL PROTECTED] Sent by: ADSM: Dist Stor Manager [EMAIL PROTECTED] 2004-08-24 18:40 Please respond to ADSM: Dist Stor Manager [EMAIL PROTECTED] To [EMAIL PROTECTED] cc Subject Re: Licensing That would tell TSM that I'm not doing any SAN but a Q LIC shows that TSM still thinks I'M doing SAN. So the question again is how to convince TSM that the old node is no longer doing Lan Free. [EMAIL PROTECTED] 8/24/2004 11:55:52 AM I have a node that used to be Lan Free but no longer uses Lan Free. How do I convince TSM licensing to stop counting it as a MGSYSSAN node? I believe by doing a REGister LICense with Number=0 which unregisters the license. Richard Sims
Connection of TSM DB to Other Softwares
Dear All, Does any one know how to connect the TSM Database, to make a personnel catalog using the existing database. Regards Sujay Dinakar R. Regards Siujay Dinakar R. - Do you Yahoo!? New and Improved Yahoo! Mail - Send 10MB messages!
Re: Running periodic Full backups
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Cargill, Bill Does anyone know how to easily force a full backup? I know about changing the management class attribute copymode to absolute. What I'm trying to do is run a monthly full backup to improve our restore performance. What we're running into are many tape mounts doing a point in time restore even in a co-located storage pool. Rather than force full backups (with all the traffic and tape issues that entails, try using the MOVE NODEDATA command to periodically move all of a node's data to one (or more tapes). -- Mark Stapleton ([EMAIL PROTECTED]) Berbee Information Networks Office 262.521.5627
Re: Connection of TSM DB to Other Softwares
Tivoli Storage Manager for Windows installs an ODBC plug-in. I use it to run against the TSM database using MSAccess. Kenny Barnes Systems Analyst GmacInsurance 336-770-8280 [EMAIL PROTECTED] -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Sujay Dinakar R. Sent: Thursday, August 26, 2004 9:00 AM To: [EMAIL PROTECTED] Subject: Connection of TSM DB to Other Softwares Dear All, Does any one know how to connect the TSM Database, to make a personnel catalog using the existing database. Regards Sujay Dinakar R. Regards Siujay Dinakar R. - Do you Yahoo!? New and Improved Yahoo! Mail - Send 10MB messages! -- Note: The information contained in this message may be privileged and confidential and protected from disclosure. If the reader of this message is not the intended recipient, or an employee or agent responsible for delivering this message to the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please notify us immediately by replying to the message and deleting it from your computer. Thank you. --
Re: Connection of TSM DB to Other Softwares
Do you have a more specific explanation of what you are trying to do? You can use the supplied ODBC client and connect to the TSM DB via ACCESS for query purposes, but not update. You could put some sort of application interface in front of that. [EMAIL PROTECTED] 08/26/2004 9:00:19 AM Dear All, Does any one know how to connect the TSM Database, to make a personnel catalog using the existing database. Regards Sujay Dinakar R. Regards Siujay Dinakar R. - Do you Yahoo!? New and Improved Yahoo! Mail - Send 10MB messages!
TSM migration from 5.1 to 5.2
Hi: We are getting set for the migration from TSM 5.1 to 5.2. For people who have already done this, did you precede the install of the 5.2 software with an 'audit db fix=yes'?
Re: Connection of TSM DB to Other Softwares
A simple way to extract information from the TSM DB is to do selects from each table using -commadelimited output -- it will import directly into most Databases as CSV is a pretty universal format. My question would be why are you trying to re-invent the wheel? Lawrence Clark [EMAIL PROTECTED] Sent by: ADSM: Dist Stor Manager [EMAIL PROTECTED] 08/26/2004 09:08 AM Please respond to ADSM: Dist Stor Manager To: [EMAIL PROTECTED] cc: Subject:Re: Connection of TSM DB to Other Softwares Do you have a more specific explanation of what you are trying to do? You can use the supplied ODBC client and connect to the TSM DB via ACCESS for query purposes, but not update. You could put some sort of application interface in front of that. [EMAIL PROTECTED] 08/26/2004 9:00:19 AM Dear All, Does any one know how to connect the TSM Database, to make a personnel catalog using the existing database. Regards Sujay Dinakar R. Regards Siujay Dinakar R. - Do you Yahoo!? New and Improved Yahoo! Mail - Send 10MB messages!
Re: Running periodic Full backups
I have used MOVE NODEDATA and included all nodes associated with a particular non-collocated tape pool, the advantages are obvious. Is there any advantage in using MOVE NODEDATA with co-located nodes ? Is there any advantage in using MOVE NODEDATA over reclamation for co-located nodes ? Bill Stapleton, Mark [EMAIL PROTECTED] Sent by: ADSM: Dist Stor Manager [EMAIL PROTECTED] 26/08/2004 14:01 Please respond to ADSM: Dist Stor Manager To: [EMAIL PROTECTED] cc: Subject:Re: Running periodic Full backups From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Cargill, Bill Does anyone know how to easily force a full backup? I know about changing the management class attribute copymode to absolute. What I'm trying to do is run a monthly full backup to improve our restore performance. What we're running into are many tape mounts doing a point in time restore even in a co-located storage pool. Rather than force full backups (with all the traffic and tape issues that entails, try using the MOVE NODEDATA command to periodically move all of a node's data to one (or more tapes). -- Mark Stapleton ([EMAIL PROTECTED]) Berbee Information Networks Office 262.521.5627
Re: TSM migration from 5.1 to 5.2
No! I would not do an audit db if I dont have been told to do one by IBM support, or if I have strong evidence that I need to do an audit. The upgrade itself does not require an audit db! //Henrik |+- || Lawrence Clark | || [EMAIL PROTECTED]| || ATE.NY.US | || Sent by: ADSM: Dist | || Stor Manager | || [EMAIL PROTECTED] | || | || | || 2004-08-26 15:09 | || Please respond to | || ADSM: Dist Stor | || Manager | || | |+- ---| | | | To: [EMAIL PROTECTED] | | cc: (bcc: Henrik Wahlstedt) | | Subject: TSM migration from 5.1 to 5.2 | ---| Hi: We are getting set for the migration from TSM 5.1 to 5.2. For people who have already done this, did you precede the install of the 5.2 software with an 'audit db fix=yes'? --- 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 migration from 5.1 to 5.2
Just curious Why would you not do an audit DB and what all does an audit DB do? -Original Message- From: Henrik Wahlstedt [mailto:[EMAIL PROTECTED] Sent: Thursday, August 26, 2004 8:34 AM To: [EMAIL PROTECTED] Subject: Re: TSM migration from 5.1 to 5.2 No! I would not do an audit db if I dont have been told to do one by IBM support, or if I have strong evidence that I need to do an audit. The upgrade itself does not require an audit db! //Henrik |+- || Lawrence Clark | || [EMAIL PROTECTED]| || ATE.NY.US | || Sent by: ADSM: Dist | || Stor Manager | || [EMAIL PROTECTED] | || | || | || 2004-08-26 15:09 | || Please respond to | || ADSM: Dist Stor | || Manager | || | |+- --- | | | | To: [EMAIL PROTECTED] | | cc: (bcc: Henrik Wahlstedt) | | Subject: TSM migration from 5.1 to 5.2 | --- | Hi: We are getting set for the migration from TSM 5.1 to 5.2. For people who have already done this, did you precede the install of the 5.2 software with an 'audit db fix=yes'? --- 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 files transmitted with it are confidential and intended solely for the use of the addressee. If you are not the intended addressee, then you have received this email in error and any use, dissemination, forwarding, printing, or copying of this email is strictly prohibited. Please notify us immediately of your unintended receipt by reply and then delete this email and your reply. Tyson Foods, Inc. and its subsidiaries and affiliates will not be held liable to any person resulting from the unintended or unauthorized use of any information contained in this email or as a result of any additions or deletions of information originally contained in this email.
Re: Running periodic Full backups
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Bill Dourado I have used MOVE NODEDATA and included all nodes associated with a particular non-collocated tape pool, the advantages are obvious. Is there any advantage in using MOVE NODEDATA with co-located nodes ? No. Is there any advantage in using MOVE NODEDATA over reclamation for co-located nodes ? No. -- Mark Stapleton ([EMAIL PROTECTED]) Berbee Information Networks Office 262.521.5627
Windows 2003 Storage Server
Hi, Is Windows 2003 Storage Server supported by TSM? Is there anyone who backs up data stored on a NAS with Windows 2003 Storage Server? I'm looking for some experience but I didn't really find anything on the net. Regards, Imre
Problem with delete volhist type=dbb
I'm using a dedicated pool of tapes for off-site database backups, which seems to be working OK - almost. The problem is that the delete volhist returns the tape to scratch status, making it available to the next process that wants a scratch tape. 15 days later (my rotation) the database backup fails because all the tapes in my list are in use, most of them for something other than database backups. Am I missing something on the delete? Why I'm doing this: We have LTO-2 drives now, and a mix of LTO1 and LTO2 media. Our D/R hotsite contract specs LTO1 drives, so I'm using the LTO1 media for off-siting, with designated tapes in each storage pool. Unfortunately, my LTO1 media has lower volsers than the LTO2, so any LTO1 scratch is next in line to be glommed for an in-the-box storage pool. TSM 5.1.6.3 on AIX 5.1-04; 3584 with 10 drives. Suggestions? Tom Kauffman NIBCO, Inc CONFIDENTIALITY NOTICE: This email and any attachments are for the exclusive and confidential use of the intended recipient. If you are not the intended recipient, please do not read, distribute or take action in reliance upon this message. If you have received this in error, please notify us immediately by return email and promptly delete this message and its attachments from your computer system. We do not waive attorney-client or work product privilege by the transmission of this message.
Re: Problem with delete volhist type=dbb
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Kauffman, Tom I'm using a dedicated pool of tapes for off-site database backups, which seems to be working OK - almost. The problem is that the delete volhist returns the tape to scratch status, making it available to the next process that wants a scratch tape. 15 days later (my rotation) the database backup fails because all the tapes in my list are in use, most of them for something other than database backups. Am I missing something on the delete? If you offsite your database backups, you shouldn't be using DEL VOLHIST; you should be using the SET DRMDBBACKUPEXPIREDAYS parameter instead. Doing so will set old db backups to VAULTRETRIEVE status (rather than directly to scratch), which you then remedy by using the proper MOVE DRMEDIA commands. Please review the DRM procedures on pages 560 and following of the TSM for AIX Administrator's Guide, version 5.1.5. -- Mark Stapleton ([EMAIL PROTECTED]) Berbee Information Networks Office 262.521.5627
Re: TSM migration from 5.1 to 5.2
Checks the internal consistency of the data and fixes/ resolves inconsistencies. I recall this was recommended when we upgraded from ADSM 3.0 to TSM 4.0. At the time we were told that if the upgrade process found problems with the database when the database upgrade was in process, the upgrade would halt / fail. When we ran the auditdb it found a number of inconsistencies. I was wondering if it was still a recommended step. Hate to get everthing set and have to go through a restore of the existing databse after the code was upgraded. [EMAIL PROTECTED] 08/26/2004 9:41:08 AM Just curious Why would you not do an audit DB and what all does an audit DB do? -Original Message- From: Henrik Wahlstedt [mailto:[EMAIL PROTECTED] Sent: Thursday, August 26, 2004 8:34 AM To: [EMAIL PROTECTED] Subject: Re: TSM migration from 5.1 to 5.2 No! I would not do an audit db if I dont have been told to do one by IBM support, or if I have strong evidence that I need to do an audit. The upgrade itself does not require an audit db! //Henrik |+- || Lawrence Clark | || [EMAIL PROTECTED]| || ATE.NY.US | || Sent by: ADSM: Dist | || Stor Manager | || [EMAIL PROTECTED] | || | || | || 2004-08-26 15:09 | || Please respond to | || ADSM: Dist Stor | || Manager | || | |+- --- | | | | To: [EMAIL PROTECTED] | | cc: (bcc: Henrik Wahlstedt) | | Subject: TSM migration from 5.1 to 5.2 | --- | Hi: We are getting set for the migration from TSM 5.1 to 5.2. For people who have already done this, did you precede the install of the 5.2 software with an 'audit db fix=yes'? --- 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 files transmitted with it are confidential and intended solely for the use of the addressee. If you are not the intended addressee, then you have received this email in error and any use, dissemination, forwarding, printing, or copying of this email is strictly prohibited. Please notify us immediately of your unintended receipt by reply and then delete this email and your reply. Tyson Foods, Inc. and its subsidiaries and affiliates will not be held liable to any person resulting from the unintended or unauthorized use of any information contained in this email or as a result of any additions or deletions of information originally contained in this email.
Re: TSM migration from 5.1 to 5.2
Oh, you would NOT do an auditdb because it runs a very long time [EMAIL PROTECTED] 08/26/2004 9:41:08 AM Just curious Why would you not do an audit DB and what all does an audit DB do? -Original Message- From: Henrik Wahlstedt [mailto:[EMAIL PROTECTED] Sent: Thursday, August 26, 2004 8:34 AM To: [EMAIL PROTECTED] Subject: Re: TSM migration from 5.1 to 5.2 No! I would not do an audit db if I dont have been told to do one by IBM support, or if I have strong evidence that I need to do an audit. The upgrade itself does not require an audit db! //Henrik |+- || Lawrence Clark | || [EMAIL PROTECTED]| || ATE.NY.US | || Sent by: ADSM: Dist | || Stor Manager | || [EMAIL PROTECTED] | || | || | || 2004-08-26 15:09 | || Please respond to | || ADSM: Dist Stor | || Manager | || | |+- --- | | | | To: [EMAIL PROTECTED] | | cc: (bcc: Henrik Wahlstedt) | | Subject: TSM migration from 5.1 to 5.2 | --- | Hi: We are getting set for the migration from TSM 5.1 to 5.2. For people who have already done this, did you precede the install of the 5.2 software with an 'audit db fix=yes'? --- 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 files transmitted with it are confidential and intended solely for the use of the addressee. If you are not the intended addressee, then you have received this email in error and any use, dissemination, forwarding, printing, or copying of this email is strictly prohibited. Please notify us immediately of your unintended receipt by reply and then delete this email and your reply. Tyson Foods, Inc. and its subsidiaries and affiliates will not be held liable to any person resulting from the unintended or unauthorized use of any information contained in this email or as a result of any additions or deletions of information originally contained in this email.
Re: Windows 2003 Storage Server
Yes, I'm running ITSM 5.2.10 Client on an HP NAS. It is working just like any other Client. Doug Thorneycroft County Sanitation Districts of Los Angeles County (562) 699-7411 Ext. 1058 FAX (562) 699-6756 [EMAIL PROTECTED] -Original Message- From: Imre Kloknicer [mailto:[EMAIL PROTECTED] Sent: Thursday, August 26, 2004 6:50 AM To: [EMAIL PROTECTED] Subject: Windows 2003 Storage Server Hi, Is Windows 2003 Storage Server supported by TSM? Is there anyone who backs up data stored on a NAS with Windows 2003 Storage Server? I'm looking for some experience but I didn't really find anything on the net. Regards, Imre
Re: Select on tsm server version?
Hi, It's amazing but no! We have looked for it. You can get versions of nodes from NODES table but not for server. Best regards Christian Bagard email : [EMAIL PROTECTED] SOS-Restore - 32 cours Mirabeau - 13100 Aix-en-Provence - France www.sos-restore.com (only in french, sorry) - Original Message - From: Henrik Wahlstedt [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Thursday, August 26, 2004 2:07 PM Subject: Select on tsm server version? Hi, Is there a table where TSM holds it4s server version that I can use in a select statement? I know I get the info from q stat but I rather not do that on 1+ servers. //Henrik --- 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: Select on tsm server version?
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Christian Bagard It's amazing but no! We have looked for it. You can get versions of nodes from NODES table but not for server. It's not in the STATUS or SERVER tables, either. Weird. -- Mark Stapleton ([EMAIL PROTECTED]) Berbee Information Networks Office 262.521.5627
Re: Problem with delete volhist type=dbb
We don't do the DRM stuff (we're che/// frugal and didn't want to pop the money way back when) and with this exception, our processes have worked flawlessly. And it just dawned on me how to fix this one. I think my brain has fossilized or something. My previous challenge was to keep the database backups from *staying* private (all my returning tapes are checked in status=private and then marked access readwrite) so I went with the 15-day deletion cycle. All I need to do to fix this is shorten the cycle, so the volhist entries delete BEFORE the tapes are checked in again. Doh! After all, what counts is the volhist off-site; in our case, on a floppy strapped to the relevant database backup (also has the device config file and our dns zone files). Thanks for the suggestion, and my apologies for bothering the list with this one. Tom Kauffman NIBCO, Inc -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Stapleton, Mark Sent: Thursday, August 26, 2004 9:02 AM To: [EMAIL PROTECTED] Subject: Re: Problem with delete volhist type=dbb From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Kauffman, Tom I'm using a dedicated pool of tapes for off-site database backups, which seems to be working OK - almost. The problem is that the delete volhist returns the tape to scratch status, making it available to the next process that wants a scratch tape. 15 days later (my rotation) the database backup fails because all the tapes in my list are in use, most of them for something other than database backups. Am I missing something on the delete? If you offsite your database backups, you shouldn't be using DEL VOLHIST; you should be using the SET DRMDBBACKUPEXPIREDAYS parameter instead. Doing so will set old db backups to VAULTRETRIEVE status (rather than directly to scratch), which you then remedy by using the proper MOVE DRMEDIA commands. Please review the DRM procedures on pages 560 and following of the TSM for AIX Administrator's Guide, version 5.1.5. -- Mark Stapleton ([EMAIL PROTECTED]) Berbee Information Networks Office 262.521.5627 CONFIDENTIALITY NOTICE: This email and any attachments are for the exclusive and confidential use of the intended recipient. If you are not the intended recipient, please do not read, distribute or take action in reliance upon this message. If you have received this in error, please notify us immediately by return email and promptly delete this message and its attachments from your computer system. We do not waive attorney-client or work product privilege by the transmission of this message.
how do you checkin or checkout tape
I have a new tivoli server 5.2.3 running on windows 2003 connected to a storagetek L5500 library running ACSLS. when ever I try to checkout a tape I get the following failure. ANR8855E ACSAPI(acs_eject_volume) response with unsuccessful status, status=STATUS_CAP_IN_USE. checkin also fail, it never asks to load a tape in the load port. what am I doing wrong. thanx steve ** This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please notify the system manager at postmaster at dor.state.ma.us. **
[no subject]
I found this in the readme for the AIX 5.2.3.1 client: == IBM Tivoli Storage Manager (TSM) README 32bit Backup-Archive Client for AIX 5.1 and AIX 5.2 PPC Version 5, Release 2, Level 3.1 Interim Fix 1 ** * This TSM Interim Fix addresses the following problems/issues: * IC40710 IRIX CLIENT SCHEDULER CORE DUMPS AFTER BACKUP. Well, I am confused since there is no 5.2.3 IRIX client, that I can find on service.boulder.ibm.com ? AFAIK, the SGI IRIX client has been frozen at 5.1.6 ? Can someone from IBM explain this or enlighten me to the location of the 5.2.3 SGI IRIX client ?
Re: TSM migration from 5.1 to 5.2
Mostly because it typically takes a *very* long time to run (meaning many hours or even days) on a database of any size, and isn't usually necessary, unless something is badly broken. -Lloyd On Thu, 26 Aug 2004 08:41:08 -0500 Park, Rod [EMAIL PROTECTED] wrote thusly: Just curious Why would you not do an audit DB and what all does an audit DB do? -Original Message- From: Henrik Wahlstedt [mailto:[EMAIL PROTECTED] Sent: Thursday, August 26, 2004 8:34 AM To: [EMAIL PROTECTED] Subject: Re: TSM migration from 5.1 to 5.2 No! I would not do an audit db if I dont have been told to do one by IBM support, or if I have strong evidence that I need to do an audit. The upgrade itself does not require an audit db! //Henrik |+- || Lawrence Clark | || [EMAIL PROTECTED]| || ATE.NY.US | || Sent by: ADSM: Dist | || Stor Manager | || [EMAIL PROTECTED] | || | || | || 2004-08-26 15:09 | || Please respond to | || ADSM: Dist Stor | || Manager | || | |+- -- - | | | | To: [EMAIL PROTECTED] | | cc: (bcc: Henrik Wahlstedt) | | Subject: TSM migration from 5.1 to 5.2 | -- - | Hi: We are getting set for the migration from TSM 5.1 to 5.2. For people who have already done this, did you precede the install of the 5.2 software with an 'audit db fix=yes'? --- 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 files transmitted with it are confidential and intended solely for the use of the addressee. If you are not the intended addressee, then you have received this email in error and any use, dissemination, forwarding, printing, or copying of this email is strictly prohibited. Please notify us immediately of your unintended receipt by reply and then delete this email and your reply. Tyson Foods, Inc. and its subsidiaries and affiliates will not be held liable to any person resulting from the unintended or unauthorized use of any information contained in this email or as a result of any additions or deletions of information originally contained in this email. -- - Lloyd Dieter- Senior Technology Consultant Registered Linux User 285528 Synergy, Inc. http://www.synergyinc.cc [EMAIL PROTECTED] Main:585-389-1260fax:585-389-1267 -
Re: Firewall Issues:
I've got Windows clients running through a firewall at 5.2.0.2 and 5.2.2.5, no issues. Polling mode works fine, and the only port you need open for the scheduler to work is 1500. However, I'm not using managed services (dsmcad), just the regular old scheduler. I'm not sure what the effect is of using dsmcad. It's interesting though, that in your dsmerror.log, the client RECOGNIZED that you were trying to get a connection from the server; that means something got THROUGH the firewall to your client, yes? Being able to back up via the GUI also means you're getting through the firewall. What I would try next is to simplify the interaction by dropping managed services, and just using the standard scheduler, and see if you get different results. Wanda Prather I/O, I/O, It's all about I/O -(me) -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Marc Levitan Sent: Tuesday, August 24, 2004 11:17 PM To: [EMAIL PROTECTED] Subject: Firewall Issues: I am having an issue trying to backup a client through a firewall. I can run a manual backup from the client but cannot get the scheduled backup to work. I changed to Polling mode and opened firewall ports 1500 and 1581 between server and client. Server: TSM 5.2.2.4 on AIX 5.1 Client: TSM 5.2.2.0 on Solaris 5.8 dsm.sys on client: SErvername XX ERRORLOGNAME /var/tivoli/dsmerror.log NODENAME YYY SCHEDLOGNAME /var/tivoli/dsmsched.log COMMmethodTCPip TCPPort1500 TCPServeraddress XXX PASSWORDACCESS GENERATE schedlogretention 5 d errorlogretention 5 d schedmode polling queryschedperiod 1 managedservicesschedule webclient dsmerror.log Error -50 accepting inbound connection TCP/IP received rc 4 trying to accept connection from server Has anyone been in this situation??? Thanks, Marc Levitan Storage Management PFPC Global Funds Services - The contents of this email are the property of PNC. If it was not addressed to you, you have no legal right to read it. If you think you received it in error, please notify the sender. Do not forward or copy without permission of the sender.
Re: how do you checkin or checkout tape
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Weinstein, Stephen I have a new tivoli server 5.2.3 running on windows 2003 connected to a storagetek L5500 library running ACSLS. when ever I try to checkout a tape I get the following failure. ANR8855E ACSAPI(acs_eject_volume) response with unsuccessful status, status=STATUS_CAP_IN_USE. checkin also fail, it never asks to load a tape in the load port. what am I doing wrong. There is something going on between the library and ACSLS; TSM is just reporting the library's CAP status. You might want to run this past StorageTek. -- Mark Stapleton ([EMAIL PROTECTED]) Berbee Information Networks Office 262.521.5627
Re: how do you checkin or checkout tape
already checked with storage tek. They have me eject the tape from the ACSLS console and it worked fine. THey told me to call TIVOLI. -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] Behalf Of Stapleton, Mark Sent: Thursday, August 26, 2004 11:31 AM To: [EMAIL PROTECTED] Subject: Re: how do you checkin or checkout tape From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Weinstein, Stephen I have a new tivoli server 5.2.3 running on windows 2003 connected to a storagetek L5500 library running ACSLS. when ever I try to checkout a tape I get the following failure. ANR8855E ACSAPI(acs_eject_volume) response with unsuccessful status, status=STATUS_CAP_IN_USE. checkin also fail, it never asks to load a tape in the load port. what am I doing wrong. There is something going on between the library and ACSLS; TSM is just reporting the library's CAP status. You might want to run this past StorageTek. -- Mark Stapleton ([EMAIL PROTECTED]) Berbee Information Networks Office 262.521.5627 ** This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please notify the system manager at postmaster at dor.state.ma.us. **
Re: how do you checkin or checkout tape
Did you check acs_ssi process is running or not? What status do u see when you query from TSM Server? root 16776 1 0 Jun 06 - 72:55 /usr/tivoli/tsm/devices/bin/ssi 1 3690 50004 23 Thanks Balanand Pinni -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Weinstein, Stephen Sent: Thursday, August 26, 2004 10:42 AM To: [EMAIL PROTECTED] Subject: Re: how do you checkin or checkout tape already checked with storage tek. They have me eject the tape from the ACSLS console and it worked fine. THey told me to call TIVOLI. -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] Behalf Of Stapleton, Mark Sent: Thursday, August 26, 2004 11:31 AM To: [EMAIL PROTECTED] Subject: Re: how do you checkin or checkout tape From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Weinstein, Stephen I have a new tivoli server 5.2.3 running on windows 2003 connected to a storagetek L5500 library running ACSLS. when ever I try to checkout a tape I get the following failure. ANR8855E ACSAPI(acs_eject_volume) response with unsuccessful status, status=STATUS_CAP_IN_USE. checkin also fail, it never asks to load a tape in the load port. what am I doing wrong. There is something going on between the library and ACSLS; TSM is just reporting the library's CAP status. You might want to run this past StorageTek. -- Mark Stapleton ([EMAIL PROTECTED]) Berbee Information Networks Office 262.521.5627 ** This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please notify the system manager at postmaster at dor.state.ma.us. **
Re: Problem with delete volhist type=dbb
Tom, I just thought I might point out that you are licensed for DRM automatically! You have a library with 10 drives that immediately requires you to purchase ITSM EE which comes with DRM included. So be thankful, you can now manage your offsite tapes like the rest of us The DRM commands will make life much easier! Good Luck and if you have any more questions about this please feel free to contact me. Kauffman, Tom wrote: We don't do the DRM stuff (we're che/// frugal and didn't want to pop the money way back when) and with this exception, our processes have worked flawlessly. And it just dawned on me how to fix this one. I think my brain has fossilized or something. My previous challenge was to keep the database backups from *staying* private (all my returning tapes are checked in status=private and then marked access readwrite) so I went with the 15-day deletion cycle. All I need to do to fix this is shorten the cycle, so the volhist entries delete BEFORE the tapes are checked in again. Doh! After all, what counts is the volhist off-site; in our case, on a floppy strapped to the relevant database backup (also has the device config file and our dns zone files). Thanks for the suggestion, and my apologies for bothering the list with this one. Tom Kauffman NIBCO, Inc -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Stapleton, Mark Sent: Thursday, August 26, 2004 9:02 AM To: [EMAIL PROTECTED] Subject: Re: Problem with delete volhist type=dbb From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Kauffman, Tom I'm using a dedicated pool of tapes for off-site database backups, which seems to be working OK - almost. The problem is that the delete volhist returns the tape to scratch status, making it available to the next process that wants a scratch tape. 15 days later (my rotation) the database backup fails because all the tapes in my list are in use, most of them for something other than database backups. Am I missing something on the delete? If you offsite your database backups, you shouldn't be using DEL VOLHIST; you should be using the SET DRMDBBACKUPEXPIREDAYS parameter instead. Doing so will set old db backups to VAULTRETRIEVE status (rather than directly to scratch), which you then remedy by using the proper MOVE DRMEDIA commands. Please review the DRM procedures on pages 560 and following of the TSM for AIX Administrator's Guide, version 5.1.5. -- Mark Stapleton ([EMAIL PROTECTED]) Berbee Information Networks Office 262.521.5627 CONFIDENTIALITY NOTICE: This email and any attachments are for the exclusive and confidential use of the intended recipient. If you are not the intended recipient, please do not read, distribute or take action in reliance upon this message. If you have received this in error, please notify us immediately by return email and promptly delete this message and its attachments from your computer system. We do not waive attorney-client or work product privilege by the transmission of this message. -- Regards, Mark D. Rodriguez President MDR Consulting, Inc. === MDR Consulting The very best in Technical Training and Consulting. IBM Advanced Business Partner SAIR Linux and GNU Authorized Center for Education IBM Certified Advanced Technical Expert, CATE AIX Support and Performance Tuning, RS6000 SP, TSM/ADSM and Linux Red Hat Certified Engineer, RHCE ===
Re: Selectively duplicating client data across servers
I agree. Multiple storage pools really aren't difficult to manage, and it will make your process very simple, and incremental. With backupsets, you have to copy ALL the data onto a new backupset, which will be time-consuming. Another disadvantage of using backupsets, think about what happens if A B go bang - you are left sitting at C, trying to figure out how to use your backupsets. You will have to process entire backupsets to get anything back, and you have no inventory DB that shows you what is on them at the file level. If you send the data to C: as part of the BACKUP STGPOOL process, you can always open the client GUI to see what should be there, and do restores selectively. -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Steven Pemberton Sent: Wednesday, August 25, 2004 10:40 PM To: [EMAIL PROTECTED] Subject: Re: Selectively duplicating client data across servers On Thursday 26 August 2004 09:19, Stuart Lamble wrote: Hey ho. Here's the skinny. We will, eventually, have a number of clients backing up to a TSM server on a regular basis (we're still setting up the SAN and other ancillary things that are needed to support the TSM server). Some of them will be filesystem backups; others will be database backups (which, if I understand correctly, are most likely to be seen as archives rather than backups as such). The setup involves two sites, A and B, which have multiple gigabit fibre connections between them (so they're effectively on the same LAN; the only real difference is a very small amount of additional latency.) Systems at site A will backup to a server at site B, and vice versa. So, you have the following? 1/ Clients at A backup to TSM server at B. 2/ Clients at B backup to TSM server at A. Where are you producing the copypool versions? Eg: 1/ Client A - TSM B (primary) - TSM A (copy) ? 2/ Client A - TSM B (primary) - TSM B (copy) ? 3/ What copy pools? :( The project I'm working on involves a third site; call it site C. The connectivity from sites A and B to site C is significantly poorer than that between A and B, largely because site C is significantly remote to A and B (whilst A and B are within a few km of each other), precluding running of fibre to it. (Not sure what the current connections are; that's not my area.) The idea is that if things go boom in a major way, and we lose everything at _both_ site A and site B, we want to have copies of the university's critical data (student records, SAP, that sort of thing) available for restore. Maybe the data will be a little old, but better than nothing. Something like this? 1/ Client A - TSM B (primary) - TSM A (copy) (all) - TSM C (copy/export) (critical only) A healthy paranoia. :) So the idea is this. The servers holding the critical data backup to their backup server as normal. Once every so often (once a week, once a fortnight, once a month...), we want to take the data off the _backup server_, and copy it to another TSM server at site C. We want to do this only for those critical servers, not for all servers. The data may be in the form of either archives or filesystem backups, or some combination of the two. We _don't_ want to be running extra backups for the servers in question to provide this redundancy. The two solutions I've come up with involve data export, and copy pools (via virtual volumes). The problem is, both of those operate at the storage pool level; there's no way to specify copy/export only the data for _this_ client, and no others that I can see. Actually, you can export node for individual hosts, but I'm not sure if it's the best way to do what you're planning. However, export node can specify a client, time range, backup and/or archive data, active files only, and export/import directly via a server to server connection. It's preferable that we not have to create separate storage pools (all the way down to the tape level) for these systems just so we can do this -- we'd prefer to have one disk pool and one tape pool for the whole shebang if possible. I'd normally recommed that you DO create multiple storage pools, so that you can better control the physical location of the backup data. This can improve recovery performance by separating critical clients to their own storage pools and tapes. With only one huge disk/tape storage pool hierarchy each client's data will tend to fragment across a large number of tapes (unless you use collocation, which may greatly reduce tape efficiency instead). If you do create seperate storage pools, then it's simply a matter of running an additional backup stgpool command to produce the extra off-site copy for site C. This has another advantage in that it's a completely incremental process, and you can probably afford to run it every day (for the critical nodes/storage pools only). Backup sets may be doable, but I'm a little uncertain
Re: how do you checkin or checkout tape
Do you have tape volumes already in the IO bay of the library? Does TSM show any requests are outstanding? 'query requests' Matt. -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Weinstein, Stephen Sent: Thursday, August 26, 2004 3:54 PM To: [EMAIL PROTECTED] Subject: how do you checkin or checkout tape I have a new tivoli server 5.2.3 running on windows 2003 connected to a storagetek L5500 library running ACSLS. when ever I try to checkout a tape I get the following failure. ANR8855E ACSAPI(acs_eject_volume) response with unsuccessful status, status=STATUS_CAP_IN_USE. checkin also fail, it never asks to load a tape in the load port. what am I doing wrong. thanx steve ** This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please notify the system manager at postmaster at dor.state.ma.us. ** ___ Disclaimer Notice __ This message and any attachments are confidential and should only be read by those to whom they are addressed. If you are not the intended recipient, please contact us, delete the message from your computer and destroy any copies. Any distribution or copying without our prior permission is prohibited. Internet communications are not always secure and therefore Powergen Retail Limited does not accept legal responsibility for this message. The recipient is responsible for verifying its authenticity before acting on the contents. Any views or opinions presented are solely those of the author and do not necessarily represent those of Powergen Retail Limited. Registered addresses: Powergen Retail Limited, Westwood Way, Westwood Business Park, Coventry, CV4 8LG. Registered in England and Wales No: 3407430 Telephone +44 (0) 2476 42 4000 Fax +44 (0) 2476 42 5432
Re: how do you checkin or checkout tape
That sounds familiar. Used to be that you were required to set the CAP priority and mode to use ACSLS with TSM. I don't have an ACSLS/TSM library anymore, things may have changed a lot. But according to my notes, we had to enter the ACSLS console commands to: Set CAP mode to automatic Set CAP priority to 1 You'll have to look up the exact syntax. The changes are saved in the ACSLS data base, so you only have to do this once. Give it a try, won't hurt, even if it doesn't help. Good luck... Wanda Prather I/O, I/O, It's all about I/O -(me) -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Weinstein, Stephen Sent: Thursday, August 26, 2004 11:42 AM To: [EMAIL PROTECTED] Subject: Re: how do you checkin or checkout tape already checked with storage tek. They have me eject the tape from the ACSLS console and it worked fine. THey told me to call TIVOLI. -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] Behalf Of Stapleton, Mark Sent: Thursday, August 26, 2004 11:31 AM To: [EMAIL PROTECTED] Subject: Re: how do you checkin or checkout tape From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Weinstein, Stephen I have a new tivoli server 5.2.3 running on windows 2003 connected to a storagetek L5500 library running ACSLS. when ever I try to checkout a tape I get the following failure. ANR8855E ACSAPI(acs_eject_volume) response with unsuccessful status, status=STATUS_CAP_IN_USE. checkin also fail, it never asks to load a tape in the load port. what am I doing wrong. There is something going on between the library and ACSLS; TSM is just reporting the library's CAP status. You might want to run this past StorageTek. -- Mark Stapleton ([EMAIL PROTECTED]) Berbee Information Networks Office 262.521.5627 ** This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please notify the system manager at postmaster at dor.state.ma.us. **
database and recovery log protection..
Hi all Is there an easy way, like a command, to know what is my setup ... normal mode or roll-forward mode my TSM server is a Windows 2000 thanks
SQL database restore question
Hi people, Have been trying to restore a database to a different location on a different server but am having problems. Was wondering if anyone can shed any light as to where I am going wrong. First I queried the TSM server for the fileinfo of the database I want to restore from the new intended location as follows: C:\Program Files\Tivoli\TSM\TDPSqltdpsqlc query TSM DWHPROD full /fileinfo /fro msqlserver=GBSTPF54 /tsmnode=GBSTPF54_SQL /tsmpassword=ntbackup /mountwait=yes IBM Tivoli Storage Manager for Databases: Data Protection for Microsoft SQL Server Version 5, Release 2, Level 1.0 (C) Copyright IBM Corporation 1997, 2003. All rights reserved. Restoring metadata ... Waiting for TSM server.. ..Backup Object Information - SQL Server Name GBSTPF54 SQL Database Name DWHPROD Backup Object Type ... Full Backup Object State .. Active Backup Creation Date / Time .. 25-08-2004 22:17:55 Backup Size .. 104,785,560,064 Database Object Name . 20040825221755\0998 Number of stripes in backup object ... 1 SQL Group Logical Name ... PRIMARY SQL Group Space Allocated 114,512,822,272 SQL Group Space Used . 104,743,239,680 SQL File Logical Name ... DWH_Data SQL File Physical Name .. E:\Microsoft SQL Server\MSSQL\Data\DW HPROD.mdf SQL File Space Allocated 701,956,096 SQL File Space Used . 648,478,720 SQL File Logical Name ... DWH_1_Data SQL File Physical Name .. E:\Microsoft SQL Server\MSSQL\Data\DW HPROD_1.mdf SQL File Space Allocated 668,860,416 SQL File Space Used . 618,528,768 SQL File Logical Name ... DWH_2_Data SQL File Physical Name .. E:\Microsoft SQL Server\MSSQL\Data\DW HPROD_2.mdf SQL File Space Allocated 113,142,005,760 SQL File Space Used . 103,476,232,192 SQL Group Logical Name ... TRANSACTION LOG SQL Group Space Allocated 17,093,885,952 SQL Group Space Used . 16,693,812,224 SQL File Logical Name ... DWH_Log SQL File Physical Name .. E:\Microsoft SQL Server\MSSQL\Data\DW HPROD_LOG.LDF SQL File Space Allocated 105,906,176 SQL File Logical Name ... DHWPROD_Log SQL File Physical Name .. F:\Microsoft SQL Server\MSSQL\DATA\DH WPROD_Log.LDF SQL File Space Allocated 8,493,465,600 SQL File Logical Name ... DWHPROD_Log1 SQL File Physical Name .. E:\Microsoft SQL Server\MSSQL\Data\DW HPROD_Log1_Log.LDF SQL File Space Allocated 8,494,514,176 Using the information fro here I attempted to restore using the following command and this is what happens C:\Program Files\Tivoli\TSM\TDPSqltdpsqlc restore DWHPROD full /relocate=DWH_Da ta,DWH_Log /to=E:\Restore\DWHPROD.mdf,E:\Restore\DHWPROD_Log.LDF /fromsqlserver= GBSTPF54 /sqlserver=GBSTPT55 /tsmnode=GBSTPF54_SQL /tsmpassword=ntbackup /mountw ait=yes IBM Tivoli Storage Manager for Databases: Data Protection for Microsoft SQL Server Version 5, Release 2, Level 1.0 (C) Copyright IBM Corporation 1997, 2003. All rights reserved. Starting Sql database restore... Querying Tivoli Storage Manager server for a list of database backups, please wa it... Restoring metadata ... Waiting for TSM server.. . Beginning full restore of backup object DWHPROD, 1 of 1, to database DWHPROD Full: 0 Read: 0 Written: 0 Rate: 0.00 Kb/Sec Waiting for TSM server... Full: 1 Read: 3145728 Written: 6656 Rate: 0.22 Kb/Sec Restore of DWHPROD failed. [Microsoft][ODBC SQL Server Driver][SQL Server]File 'F:\Microsoft SQL Server\MSS QL\DATA\DHWPROD_Log.LDF' is on a network device not supported for database files . [Microsoft][ODBC SQL Server Driver][SQL Server]File 'DHWPROD_Log' cannot be rest ored to 'F:\Microsoft SQL Server\MSSQL\DATA\DHWPROD_Log.LDF'. Use WITH MOVE to i dentify a valid location for the file. [Microsoft][ODBC SQL Server Driver][SQL Server]RESTORE DATABASE is terminating a bnormally. Total database backups inspected: 1 Total database backups requested for restore: 1 Total database backups restored:0 Total database skipped: 0 Throughput rate:0.22 Kb/Sec Total bytes transferred:6,656 Elapsed processing time:30.00 Secs
Re: TSM server recovery with database copy2 volumes
Hi Mubashir!- Yes, you should be OK if you lose filesystem A. If filesystem A dies, you should ge a message in the activity log showing the error, and TSM will just keep on running with the DB copy on filesystem B. If you have to restart the TSM server and it can't find filesystem A, it will still come up and run with only the copy on filesystem B. You don't have to do anything special. How does it work? Browse (DO NOT EDIT!) the dsmserv.dsk file in the TSM server directory. That is the file TSM reads when it comes up, to find it's DB and log files. Wanda -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Mubashir Farooqi Sent: Wednesday, August 25, 2004 5:28 PM To: [EMAIL PROTECTED] Subject: TSM server recovery with database copy2 volumes Hi, I have a TSM/AIX server. TSM server database copy1 volumes are on filesystem A. TSM server database copy2 volumes are on filesystem B. If I loose filesystemA, can I restart TSM server with copy2 volumes? How can I restart/recover TSM server using database copy2 volumes? Thanks, Mubashir Farooqi World Bank, HQ Washington DC
Need to keep data for a client forever
Hi, I use TSM 5.1.6.0 and have a situation where they need me to not expire any data for A particular node [including those already backed up]. There is a lot of clients using same policy /management class that should not have their expiration changed. I would like to know what would be the cleanest way to accomplish this. We backup about 500GB/week for this node [just to give an idea of data size if I have to do a move nodedata] Thanking you for help Bala [EMAIL PROTECTED]
Re: Firewall Issues:
The issue was that I was using: managedservices schedule webclient in the dsm.sys AND dsmsched in the startup script!!! Once I removed the dsmsched from the startup script and bounced the client, everything worked... Thanks, Marc Levitan Storage Management PFPC Global Funds Services |-+--- | | Prather, Wanda| | | [EMAIL PROTECTED]| | | huapl.edu | | | | | | 08/26/2004 11:21| | | AM | | | | |-+--- -| | | |To: 'ADSM: Dist Stor Manager' [EMAIL PROTECTED] | |cc: '[EMAIL PROTECTED]' [EMAIL PROTECTED] | |Subject: RE: Firewall Issues: | -| I've got Windows clients running through a firewall at 5.2.0.2 and 5.2.2.5, no issues. Polling mode works fine, and the only port you need open for the scheduler to work is 1500. However, I'm not using managed services (dsmcad), just the regular old scheduler. I'm not sure what the effect is of using dsmcad. It's interesting though, that in your dsmerror.log, the client RECOGNIZED that you were trying to get a connection from the server; that means something got THROUGH the firewall to your client, yes? Being able to back up via the GUI also means you're getting through the firewall. What I would try next is to simplify the interaction by dropping managed services, and just using the standard scheduler, and see if you get different results. Wanda Prather I/O, I/O, It's all about I/O -(me) -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Marc Levitan Sent: Tuesday, August 24, 2004 11:17 PM To: [EMAIL PROTECTED] Subject: Firewall Issues: I am having an issue trying to backup a client through a firewall. I can run a manual backup from the client but cannot get the scheduled backup to work. I changed to Polling mode and opened firewall ports 1500 and 1581 between server and client. Server: TSM 5.2.2.4 on AIX 5.1 Client: TSM 5.2.2.0 on Solaris 5.8 dsm.sys on client: SErvername XX ERRORLOGNAME /var/tivoli/dsmerror.log NODENAME YYY SCHEDLOGNAME /var/tivoli/dsmsched.log COMMmethodTCPip TCPPort1500 TCPServeraddress XXX PASSWORDACCESS GENERATE schedlogretention 5 d errorlogretention 5 d schedmode polling queryschedperiod 1 managedservicesschedule webclient dsmerror.log Error -50 accepting inbound connection TCP/IP received rc 4 trying to accept connection from server Has anyone been in this situation??? Thanks, Marc Levitan Storage Management PFPC Global Funds Services - The contents of this email are the property of PNC. If it was not addressed to you, you have no legal right to read it. If you think you received it in error, please notify the sender. Do not forward or copy without permission of the sender. - The contents of this email are the property of PNC. If it was not addressed to you, you have no legal right to read it. If you think you received it in error, please notify the sender. Do not forward or copy without permission of the sender.
Re: database and recovery log protection..
q status Check the output for the line: LOG MODE: ... about 2/3 down. -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Luc Beaudoin Sent: Thursday, August 26, 2004 12:25 PM To: [EMAIL PROTECTED] Subject: database and recovery log protection.. Hi all Is there an easy way, like a command, to know what is my setup ... normal mode or roll-forward mode my TSM server is a Windows 2000 thanks
Re: Selectively duplicating client data across servers
Hi Everyone, I have deleted the thread of this email since I am sure everyone has read a couple of times already. I figure I would throw my $0.02 into the mix as well. I have done a few configs like this over the years so I have some experience in this area. I think you have been getting some good feedback here and when it all said and done you should be able to boil this down to something very workable. So here is what I would propose. Client A non-crit - TSM B non-crit Pri-pool - TSM B non-crit Copypool - Ship tapes to TSM C (Optional) |- TSM B non-crit onsite Copypool Client A crit - TSM B crit Pri-pool - TSM B crit Copypool (Virtual Volumes on TSM C) (Optional) |- TSM B crit onsite Copypool Mirror the config for client B I am assuming that C will be your DR site and therefore that is where your Copy pool data should wind up. It is not a good idea to keep both the primary and the copy (if you are having only one copypool copy) on the same site. Keep in mind that if you loose site A, site B could still be missing some critical data, i.e. Archive data that was deleted from the owner's system and inactive versions would all be missing! So it is important that at least one copypool's data be separated from the primary pool. I am recommending that you use Virtual Volumes for the most critical machine's copypool. This can be done by setting up a separate storage pool hierarchy for these critical machines of course this is predicated on having the necessary bandwidth to transfer all the critical data to site C. Keep in mind to make this functional you should also be backing up TSM A's and TSM B's DB through Virtual Volumes to TSM C as well. Now one thing to remember, backup environments are like buying insurance, so the more protection you want the more expensive it will get. However, you must make sure that you spend enough to protect your self! Having said that there is a few other things you can consider. You might consider keeping an onsite and an offsite copypool. This would allow for much faster recovery of data in the event of a primary tape failure. You will have a time delay exposure if the tape that fails is non-crit primary you will have to retrieve the copypool tape from offsite. If it is a critical primary tape then you will have to move the data back through the pipe and this could have some impact based on what else is trying to go through the pipe at that time. You might consider having clones of TSM A and TSM B at site C. This would allow for much quicker DR recovery times if that is a concern. And to take this one step further you could even to DB restores to those machines on a regular basis if needed. By the way those clone instances could run on the same system as TSM C. That would save licensing costs as well as have some performance advantages during DR restores. Make sure that you plan on testing this environment. Backing up is fine but restores is what it is all about! That means you must build into the plan up front how you are going to do your testing without impacting production and still feel confident that you can restore to production if necessary. This is the most common failure point for projects like this. They get designed and implemented with no fore thought on how to test it and when it comes time to do the DR test they got themselves in a jam. There is a lot more to consider for the testing phase them what information we have been given. As I said before I have done a few setups that were similar to this so if you have any further questions please feel free to ask. Good Luck. -- Regards, Mark D. Rodriguez President MDR Consulting, Inc. === MDR Consulting The very best in Technical Training and Consulting. IBM Advanced Business Partner SAIR Linux and GNU Authorized Center for Education IBM Certified Advanced Technical Expert, CATE AIX Support and Performance Tuning, RS6000 SP, TSM/ADSM and Linux Red Hat Certified Engineer, RHCE ===
Re: Need to keep data for a client forever
I use TSM 5.1.6.0 and have a situation where they need me to not expire any data for A particular node [including those already backed up]. There is a lot of clients using same policy /management class that should not have their expiration changed. I would like to know what would be the cleanest way to accomplish this. We backup about 500GB/week for this node [just to give an idea of data size if I have to do a move nodedata] Offhand, I can think of only one reasonable approach: 1.Use 'copy domain' to create a copy of the policy domain the node is in. 2.Update the retention parameters in the copy groups in the new domain. 3.Activate the appropriate policy set. 4.Use 'update node' to move the node to the new policy domain. If the node has scheduled backups, you will need to copy the schedule from the old domain and associate it with the node. You might need to restart the client scheduler process or service. We have always found this necessary when moving clients that use the prompted scheduling mode. Reports from other sites suggest that the restart is not necessary for clients that use the polling mode.
IRIX and 5.2.3 client ????
I found this in the readme for the AIX 5.2.3.1 client: ** * This TSM Interim Fix addresses the following problems/issues: snippage * IC40710 IRIX CLIENT SCHEDULER CORE DUMPS AFTER BACKUP. Well, I am confused since there is no 5.2.3 IRIX client, that I can find on service.boulder.ibm.com ? AFAIK, the SGI IRIX client has been frozen at 5.1.6 ? Can someone from IBM explain this or enlighten me to the location of the 5.2.3 SGI IRIX client ?
Need help with select command
I am trying to find the tapes needed to recover only the active backups of a client. I used the following select command and it gives me a list of all tapes for all backups of that client. How can I narrow the search to just active backups? select volume_name,filespace_name from volumeusage where - node_name='CLIENT NAME' and stgpool_name='STGPOOL'
Re: Export quesion
You will have to start the EXPORT from the beginning. -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Robert Ouzen Sent: Wednesday, August 25, 2004 5:53 PM To: [EMAIL PROTECTED] Subject: Export quesion Hi to all Today I ran an export command of a few nodes and during the process after a few hours I had an error command in one cartridge (DLT8000) couldn't be read successfully and the process was abandonded: 08/25/2004 15:44:57 ANR8944E Hardware or media error on drive SRV4 (/dev/mt4) (OP=LOCATE, Error Number=5, CC=306, KEY=03, ASC=11, ASCQ=00, SENSE=F0.00.03.00.00.00.BA.16.00.00.F3.38.11.00- .00.00.00.00.81.0D.90.00.00.44.B6.00.5D.47.6D., Description=Drive or media failure). Refer to Appendix D in the 'Messages' manual for recommended action. (SESSION: 3305, PROCESS: 210) 08/25/2004 15:44:57 ANR8359E Media fault detected on DLT volume 90 in drive SRV4 (/dev/mt4) of library SCALAR. (SESSION: 3305, PROCESS: 210) 08/25/2004 15:45:15 ANR0986I Process 210 for EXPORT NODE running in the BACKGROUND processed 504589 items for a total of 24,126,583,819 bytes with a completion state of FAILURE at 15:45:15. (SESSION: 3305, PROCESS: 210) My question is did I need to run the process from the beginning or can I continue from where it was abandonded after fixing the problem on the damage volume (move data...). Thanks in advance . Regards Robert Ouzen E-mail: [EMAIL PROTECTED] - FIGHT BACK AGAINST SPAM! Download Spam Inspector, the Award Winning Anti-Spam Filter http://mail.giantcompany.com http://mail.giantcompany.com/
Re: Need help with select command
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Karla Ross I am trying to find the tapes needed to recover only the active backups of a client. I used the following select command and it gives me a list of all tapes for all backups of that client. How can I narrow the search to just active backups? select volume_name,filespace_name from volumeusage where - node_name='CLIENT NAME' and stgpool_name='STGPOOL' Check the archives in search.adsm.org. This subject has been discussed thoroughly in the last year. Why exactly do you need this information, anyway? (If you get a select statement that works, be prepared to have it take hours if not days to run, with a *lot* of database activity.) -- Mark Stapleton ([EMAIL PROTECTED]) Berbee Information Networks Office 262.521.5627
Re: Need help with select command
Karla Ross wrote: I am trying to find the tapes needed to recover only the active backups of a client. I used the following select command and it gives me a list of all tapes for all backups of that client. How can I narrow the search to just active backups? select volume_name,filespace_name from volumeusage where - node_name='CLIENT NAME' and stgpool_name='STGPOOL' Hi, I am sure I could write one for you but before I do that do you realize that this will be a massive DB search and suck up a lot of CPU, Memory and I/O cycles to do this. This will be a massive search especially if you have a large number of nodes with a large number of files. The info you need is spread across to different tables, contents and backups, so you will have to generate a list of the active files from the backups table and then search the contents table for matching volumes. This is doable but it will take a long time to run and use lots of resources. Are you still interested? -- Regards, Mark D. Rodriguez President MDR Consulting, Inc. === MDR Consulting The very best in Technical Training and Consulting. IBM Advanced Business Partner SAIR Linux and GNU Authorized Center for Education IBM Certified Advanced Technical Expert, CATE AIX Support and Performance Tuning, RS6000 SP, TSM/ADSM and Linux Red Hat Certified Engineer, RHCE ===
Re: Need to keep data for a client forever
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Thomas Denier I use TSM 5.1.6.0 and have a situation where they need me to not expire any data for A particular node [including those already backed up]. There is a lot of clients using same policy /management class that should not have their expiration changed. I would like to know what would be the cleanest way to accomplish this. We backup about 500GB/week for this node [just to give an idea of data size if I have to do a move nodedata] Offhand, I can think of only one reasonable approach: 1.Use 'copy domain' to create a copy of the policy domain the node is in. 2.Update the retention parameters in the copy groups in the new domain. 3.Activate the appropriate policy set. 4.Use 'update node' to move the node to the new policy domain. If the node has scheduled backups, you will need to copy the schedule from the old domain and associate it with the node. You might need to restart the client scheduler process or service. We have always found this necessary when moving clients that use the prompted scheduling mode. Reports from other sites suggest that the restart is not necessary for clients that use the polling mode. There's a somewhat easier way: 1. Create a new management class for the domain the node currently belongs to. Make sure this new class contains a backup copygroup that sets number of copies kept to UNLIMITED. 2. Edit the node's client option file to contain the line include *:\...\* new_mgmtclass 3. Stop and start the node's TSM scheduler service. You can even modify the include statement to only affect the directories containing data. -- Mark Stapleton ([EMAIL PROTECTED]) Berbee Information Networks Office 262.521.5627
Re: Need to keep data for a client forever
There's a somewhat easier way: 1. Create a new management class for the domain the node currently belongs to. Make sure this new class contains a backup copygroup that sets number of copies kept to UNLIMITED. 2. Edit the node's client option file to contain the line include *:\...\* new_mgmtclass 3. Stop and start the node's TSM scheduler service. You can even modify the include statement to only affect the directories containing data. As far as I know, backups of files that had been deleted from the client would not get rebound to the new management class as a result of the above procedure. Such backups would age off according to the retention parameters of the management class they were assigned to when the corresponding client file was deleted.
Oracle Backup
I stopped using the TSM Oracle Agent...very complicated...and am just doing full exports to a file server. TSM then backs up the export. Mgmt. says, Hey, you're not getting the full benefit of a backup with redo logs, etc. Please comment. Should I be using RMAN instead of export? TIA Regards, Orin Port of Houston
Re: IRIX and 5.2.3 client ????
There is no IRIX client at the TSM 5.2 release level. The APAR was originally opened against the 5.1.6 IRIX client, but is applicable to all operating systems. the APAR abstract that you cited should more properly read CLIENT SCHEDULER CORE DUMPS AFTER BACKUP. A fix at the 5.1.x level for IRIX is not yet available, but if you need one, I would recommend contacting IBM support for assistance. Regards, Andy Andy Raibeck IBM Software Group Tivoli Storage Manager Client Development Internal Notes e-mail: Andrew Raibeck/Tucson/[EMAIL PROTECTED] Internet e-mail: [EMAIL PROTECTED] The only dumb question is the one that goes unasked. The command line is your friend. Good enough is the enemy of excellence. ADSM: Dist Stor Manager [EMAIL PROTECTED] wrote on 08/26/2004 10:47:24: I found this in the readme for the AIX 5.2.3.1 client: ** * This TSM Interim Fix addresses the following problems/issues: snippage * IC40710 IRIX CLIENT SCHEDULER CORE DUMPS AFTER BACKUP. Well, I am confused since there is no 5.2.3 IRIX client, that I can find on service.boulder.ibm.com ? AFAIK, the SGI IRIX client has been frozen at 5.1.6 ? Can someone from IBM explain this or enlighten me to the location of the 5.2.3 SGI IRIX client ?
Re: Oracle Backup
Orin Rehorst wrote: I stopped using the TSM Oracle Agent...very complicated...and am just doing full exports to a file server. TSM then backs up the export. Mgmt. says, Hey, you're not getting the full benefit of a backup with redo logs, etc. Please comment. Should I be using RMAN instead of export? TIA Regards, Orin Port of Houston Orin, I would recommend that you go back to using the TSM Oracle agent(aka ITSM for Database or as some of the old timers still call it TDP's) as soon as you can. The Oracle TDP will provide you the most robust protection. Although it might seem complicated at first once it is setup and configured correctly it is quite simple to use. If you need any assistance in getting it setup please contact me and I will see what I can do to help. BTW, I believe we met last year at your site to discuss TSM. Good Luck and please don't hesitate to get a hold of me. -- Regards, Mark D. Rodriguez President MDR Consulting, Inc. === MDR Consulting The very best in Technical Training and Consulting. IBM Advanced Business Partner SAIR Linux and GNU Authorized Center for Education IBM Certified Advanced Technical Expert, CATE AIX Support and Performance Tuning, RS6000 SP, TSM/ADSM and Linux Red Hat Certified Engineer, RHCE ===
Re: Export quesion
Wanda / IBM, This is an opportunity for an enhancement. I've been bit by that situation also. The problem is that an export is a single transaction. Either it fails or it succeeds. As I write this I'm holding my breath hoping that the last 100 GB of the current _3.7 TB_ export complete without a problem. It has been running for eight days now and has survived two dropped tape events by our 3583 LTO and is currently writing DLT # 64 in our HP 4/40. What I would like to see is for the export process to be able to resume at the end of the last completely filled tape. I don't care if it has to throw away a partially filled tape. I do care if it has to throw away 64 - or more - full tapes. As servers and data stores get larger, it just isn't practical to cancel a process running days or weeks because of a single tape I/O failure. Just a suggestion. Tab Trepagnier TSM Administrator Laitram, L.L.C. Prather, Wanda [EMAIL PROTECTED] Sent by: ADSM: Dist Stor Manager [EMAIL PROTECTED] 08/26/2004 01:24 PM Please respond to ADSM: Dist Stor Manager To: [EMAIL PROTECTED] cc: Subject:Re: Export quesion You will have to start the EXPORT from the beginning. -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Robert Ouzen Sent: Wednesday, August 25, 2004 5:53 PM To: [EMAIL PROTECTED] Subject: Export quesion Hi to all Today I ran an export command of a few nodes and during the process after a few hours I had an error command in one cartridge (DLT8000) couldn't be read successfully and the process was abandonded: 08/25/2004 15:44:57 ANR8944E Hardware or media error on drive SRV4 (/dev/mt4) (OP=LOCATE, Error Number=5, CC=306, KEY=03, ASC=11, ASCQ=00, SENSE=F0.00.03.00.00.00.BA.16.00.00.F3.38.11.00- .00.00.00.00.81.0D.90.00.00.44.B6.00.5D.47.6D., Description=Drive or media failure). Refer to Appendix D in the 'Messages' manual for recommended action. (SESSION: 3305, PROCESS: 210) 08/25/2004 15:44:57 ANR8359E Media fault detected on DLT volume 90 in drive SRV4 (/dev/mt4) of library SCALAR. (SESSION: 3305, PROCESS: 210) 08/25/2004 15:45:15 ANR0986I Process 210 for EXPORT NODE running in the BACKGROUND processed 504589 items for a total of 24,126,583,819 bytes with a completion state of FAILURE at 15:45:15. (SESSION: 3305, PROCESS: 210) My question is did I need to run the process from the beginning or can I continue from where it was abandonded after fixing the problem on the damage volume (move data...). Thanks in advance . Regards Robert Ouzen E-mail: [EMAIL PROTECTED] - FIGHT BACK AGAINST SPAM! Download Spam Inspector, the Award Winning Anti-Spam Filter http://mail.giantcompany.com http://mail.giantcompany.com/
Re: Windows 2003 Storage Server
I have customers running it on Dell NAS. It works fine for them as well. We have noticed that the TSM client can scan more objects per hour on Windows 2003 NAS than on the exact same hardware running Windows 2003. It seems the same optimization made for file server also helps the TSM client. This Dual CPU Windows 2003 NAS scans around over 2 million objects per hour. Imre Kloknicer [EMAIL PROTECTED] wrote: Hi, Is Windows 2003 Storage Server supported by TSM? Is there anyone who backs up data stored on a NAS with Windows 2003 Storage Server? I'm looking for some experience but I didn't really find anything on the net. Regards, Imre - Do you Yahoo!? Take Yahoo! Mail with you! Get it on your mobile phone.
Re: Export quesion
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Tab Trepagnier This is an opportunity for an enhancement. I've been bit by that situation also. The problem is that an export is a single transaction. Either it fails or it succeeds. As I write this I'm holding my breath hoping that the last 100 GB of the current _3.7 TB_ export complete without a problem. It has been running for eight days now and has survived two dropped tape events by our 3583 LTO and is currently writing DLT # 64 in our HP 4/40. one's_opinion_mode Any machine that has 3.7TB worth of files is *begging* to be broken up into multiple node names, each node responsible for backing up a portion of a physical machine. Particularly if you're using slow tape technology like DLT. /one's_opinion_mode Exports have been notoriously slow to write (and read) from ADSM/TSM first iteration. (This is one reason why you can now export directly from one TSM server to another.) Did you perform a MOVE NODEDATA prior to the export? If you didn't, and the node is not collocated, you made your life far harder than it had to be. -- Mark Stapleton ([EMAIL PROTECTED]) Berbee Information Networks Office 262.521.5627
Re: Export quesion
I would agree with that. I just lost 4 days of export because of an I/O error on a scratch Tape it could not mount. It was on it's last 200GB of it 2.1TB when this happenedWhat is up with that? It's really frustrating. TSM should be able to pick another scratch tape. Rajesh Oak Blue Cross Blue Shield of Michigan - Original Message - From: Tab Trepagnier [EMAIL PROTECTED] Date: Thu, 26 Aug 2004 18:02:25 -0500 To: [EMAIL PROTECTED] Subject: Re: Export quesion Wanda / IBM, This is an opportunity for an enhancement. I've been bit by that situation also. The problem is that an export is a single transaction. Either it fails or it succeeds. As I write this I'm holding my breath hoping that the last 100 GB of the current _3.7 TB_ export complete without a problem. It has been running for eight days now and has survived two dropped tape events by our 3583 LTO and is currently writing DLT # 64 in our HP 4/40. What I would like to see is for the export process to be able to resume at the end of the last completely filled tape. I don't care if it has to throw away a partially filled tape. I do care if it has to throw away 64 - or more - full tapes. As servers and data stores get larger, it just isn't practical to cancel a process running days or weeks because of a single tape I/O failure. Just a suggestion. Tab Trepagnier TSM Administrator Laitram, L.L.C. Prather, Wanda [EMAIL PROTECTED] Sent by: ADSM: Dist Stor Manager [EMAIL PROTECTED] 08/26/2004 01:24 PM Please respond to ADSM: Dist Stor Manager To: [EMAIL PROTECTED] cc: Subject:Re: Export quesion You will have to start the EXPORT from the beginning. -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Robert Ouzen Sent: Wednesday, August 25, 2004 5:53 PM To: [EMAIL PROTECTED] Subject: Export quesion Hi to all Today I ran an export command of a few nodes and during the process after a few hours I had an error command in one cartridge (DLT8000) couldn't be read successfully and the process was abandonded: 08/25/2004 15:44:57 ANR8944E Hardware or media error on drive SRV4 (/dev/mt4) (OP=LOCATE, Error Number=5, CC=306, KEY=03, ASC=11, ASCQ=00, SENSE=F0.00.03.00.00.00.BA.16.00.00.F3.38.11.00- .00.00.00.00.81.0D.90.00.00.44.B6.00.5D.47.6D., Description=Drive or media failure). Refer to Appendix D in the 'Messages' manual for recommended action. (SESSION: 3305, PROCESS: 210) 08/25/2004 15:44:57 ANR8359E Media fault detected on DLT volume 90 in drive SRV4 (/dev/mt4) of library SCALAR. (SESSION: 3305, PROCESS: 210) 08/25/2004 15:45:15 ANR0986I Process 210 for EXPORT NODE running in the BACKGROUND processed 504589 items for a total of 24,126,583,819 bytes with a completion state of FAILURE at 15:45:15. (SESSION: 3305, PROCESS: 210) My question is did I need to run the process from the beginning or can I continue from where it was abandonded after fixing the problem on the damage volume (move data...). Thanks in advance . Regards Robert Ouzen E-mail: [EMAIL PROTECTED] - FIGHT BACK AGAINST SPAM! Download Spam Inspector, the Award Winning Anti-Spam Filter http://mail.giantcompany.com http://mail.giantcompany.com/ -- ___ Find what you are looking for with the Lycos Yellow Pages http://r.lycos.com/r/yp_emailfooter/http://yellowpages.lycos.com/default.asp?SRC=lycos10
Re: Export quesion
Mark, one's_opinion_mode Any machine that has 3.7TB worth of files is *begging* to be broken up into multiple node names, each node responsible for backing up a portion of a physical machine. Particularly if you're using slow tape technology like DLT. /one's_opinion_mode I agree with you, and in fact, we've done that with our main file servers. But this is a Domino TDP node - all the databases (about 1000) and the entire history of its transaction log. I suppose I could have exported the databases and logs separately, but that would have just turned a nine-day export into two five-day exports. It should be possible for TSM to do a checkpoint at the end of every filled volume. As for our DLTs, they are slower than LTOs, but when we bought the 4/40 three years ago, it was a Cadillac compared to our old one-drive DLT 4000 autoloader. Our offsite tape throughput went from 2.5 MB/s to 32 MB/s. And three years ago, LTO-1 was just being introduced. We didn't think they were a suitable DR medium because of that newness. We only use DLT for offsite. Onsite we use LTO-1 and 3570, and hope to begin using a VTL by next year. Thanks for your feedback. Tab Trepagnier TSM Administrator Laitram, L.L.C. Stapleton, Mark [EMAIL PROTECTED] Sent by: ADSM: Dist Stor Manager [EMAIL PROTECTED] 08/26/2004 06:55 PM Please respond to ADSM: Dist Stor Manager To: [EMAIL PROTECTED] cc: Subject:Re: Export quesion From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Tab Trepagnier This is an opportunity for an enhancement. I've been bit by that situation also. The problem is that an export is a single transaction. Either it fails or it succeeds. As I write this I'm holding my breath hoping that the last 100 GB of the current _3.7 TB_ export complete without a problem. It has been running for eight days now and has survived two dropped tape events by our 3583 LTO and is currently writing DLT # 64 in our HP 4/40. one's_opinion_mode Any machine that has 3.7TB worth of files is *begging* to be broken up into multiple node names, each node responsible for backing up a portion of a physical machine. Particularly if you're using slow tape technology like DLT. /one's_opinion_mode Exports have been notoriously slow to write (and read) from ADSM/TSM first iteration. (This is one reason why you can now export directly from one TSM server to another.) Did you perform a MOVE NODEDATA prior to the export? If you didn't, and the node is not collocated, you made your life far harder than it had to be. -- Mark Stapleton ([EMAIL PROTECTED]) Berbee Information Networks Office 262.521.5627
