AW: Bare Metal Restore Intel
Hello Christian and Phil, I also would be very interested in your procedures. Kind Regards, Stefan Holzwarth -- Stefan Holzwarth ADAC e.V. (Informationsverarbeitung - Systemtechnik - Basisdienste) Am Westpark 8, 81373 München, Tel.: (089) 7676-5212, Fax: (089) 76768924 [EMAIL PROTECTED]
TDP SQL sessions wants to write to same tape...
Hello I've been running a backup of a SQL server db but I took too long so I increased the stripe-parameter to 2 so it would utilize 2 sessions and 2 tape drives for the backup. However when the backup starts both sessions wants to write to the same volume, leaving one of the session in a media-wait state for the whole backup and the backup fails after 12h. 12,064 BPX-T- RecvW0 S 20.5 K 62.6 G Node TDP MSS- ROBUR22_SQL cp/Ip QL 12,066 BPX-T- MediaW 13.0 H 5.2 K 2.5 M Node TDP MSS- ROBUR22_SQL cp/Ip QL What can I do to fix this??? Regards Niklas Lundström Swedbank
Re: Migration of TSM server from OS390 or Z-OS to a UNIX or Windows platform
[EMAIL PROTECTED] wrote The idea of moving off of OS/390 is because we are taking too much CPU and weekly IPLs. Why weekly ipls? One of the big advantages of mainframe technology is that ipls are (should be) infrequent If your TSM is in a sharing lpar the TSM dispatching priority can be set so that it does not impact on higher profile work. I say higher profile because backups are generally not regarded as important, until they are needed. If your processor/s cannot truly cope with the workload, what about an upgrade, and maybe a separate lpar for TSM, so that nobody can argue that it is taking too much cpu. At the end of the the day a move to a new platform can be worthwhile, but only as long as the full costs and benefits are taken into account. ** The information in this E-Mail is confidential and may be legally privileged. It may not represent the views of Scottish and Southern Energy plc. 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. **
AW: Bare Metal Restore Intel [Virus checked]
Thanks Phill! Question to restoration step #1: Ensure server has same name and IP details as the live server But it should not be a member of the original domain at this time, correct? best regards Juraj Salak
Re: TDP SQL sessions wants to write to same tape...
if its same node with collocation turned on it might be max mount points value that should be increased (im not sure if this is aplicable for SQL TDP) goran. - Original Message - From: Niklas Lundstrom [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Friday, February 13, 2004 10:04 AM Subject: TDP SQL sessions wants to write to same tape... Hello I've been running a backup of a SQL server db but I took too long so I increased the stripe-parameter to 2 so it would utilize 2 sessions and 2 tape drives for the backup. However when the backup starts both sessions wants to write to the same volume, leaving one of the session in a media-wait state for the whole backup and the backup fails after 12h. 12,064 BPX-T- RecvW0 S 20.5 K 62.6 G Node TDP MSS- ROBUR22_SQL cp/Ip QL 12,066 BPX-T- MediaW 13.0 H 5.2 K 2.5 M Node TDP MSS- ROBUR22_SQL cp/Ip QL What can I do to fix this??? Regards Niklas Lundstrvm Swedbank
Re: Bare Metal Restore Intel [Virus checked]
Gooday Krzysztof, this is an abridged version of our official doc: (See attached file: Win2K DR Bare Metal Restore abridged.doc) It has been tested from Dell to IBM and vice versa and works ok, you may have to run a Win2k install\repair at the end if all else fails. Hope it helps Phil Jones Technical Specialist United Biscuits Tel (external) 0151 4735972 Tel (internal) 755 5972 e-mail: [EMAIL PROTECTED] |-+ | | Krzysztof WOZNIAK| | | [EMAIL PROTECTED]| | | U.AU| | | Sent by: ADSM: | | | Dist Stor| | | Manager | | | [EMAIL PROTECTED]| | | .EDU| | || | || | | 13/02/2004 00:49 | | | Please respond to| | | ADSM: Dist Stor | | | Manager | | || |-+ --| | | | To: [EMAIL PROTECTED] | | cc: | | Subject: Re: Bare Metal Restore Intel | --| So would I Regards, -- Mr Krzysztof Wozniak,-_|\ E-mail: [EMAIL PROTECTED] Edith Cowan University / \ Phone: 61-8-9273 8026 Churchlands WA, 6018 $_,-._/Fax: 61-8-9273 8000 Australia o -Original Message- From: Bradberry, Kenneth [mailto:[EMAIL PROTECTED] Sent: Friday, 13 February 2004 12:15 AM To: [EMAIL PROTECTED] Subject: Re: Bare Metal Restore Intel Phil, I would be interested in that procedure as well. Thanks, Ken Bradberry -Original Message- From: Phil Jones [mailto:[EMAIL PROTECTED] Sent: Thursday, February 12, 2004 10:34 AM To: [EMAIL PROTECTED] Subject: Re: Bare Metal Restore Intel Henrik, we have just tested this on WIN2K and have a procedure I can let you have if you e-mail me directly ([EMAIL PROTECTED]) it isn;'t using ITSM though. Phil Jones |-+ | | Henrik Hansson | | | [EMAIL PROTECTED]| | | LBINT.COM | | | Sent by: ADSM: | | | Dist Stor| | | Manager | | | [EMAIL PROTECTED]| | | .EDU| | || | || | | 12/02/2004 14:46 | | | Please respond to| | | ADSM: Dist Stor | | | Manager | | || |-+ - -- ---| | | | To: [EMAIL PROTECTED] | | cc: | | Subject: Bare Metal Restore Intel | - -- ---| Hello TSM'ers I know that a bare metal restore on a W2K system works fine as long as the restore is doen to a similar system, hardware vice. But do anyone know how to do the same to a system with different hardware? I've tried it but haven't succeded. The system don't boot but give me a system error. 1. Have anyone done such a restore to a diffrent hardware system? 2. Does anyone know if ITSM will support such in the future. I know that veritas have a product that accomplish this. Med Vänlig Hälsning/ Best Regards _ Henrik Hansson Win2K DR Bare Metal Restore abridged.doc Description: MS-Word document
SV: TDP SQL sessions wants to write to same tape...
Hello No problems with moutpoints ,and the pool is collocated. Perhaps I should change it to collocate by filespace instead. Thats sounds like a solution actually /Niklas -Ursprungligt meddelande- Från: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] För goran Skickat: den 13 februari 2004 10:27 Till: [EMAIL PROTECTED] Ämne: Re: TDP SQL sessions wants to write to same tape... if its same node with collocation turned on it might be max mount points value that should be increased (im not sure if this is aplicable for SQL TDP) goran. - Original Message - From: Niklas Lundstrom [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Friday, February 13, 2004 10:04 AM Subject: TDP SQL sessions wants to write to same tape... Hello I've been running a backup of a SQL server db but I took too long so I increased the stripe-parameter to 2 so it would utilize 2 sessions and 2 tape drives for the backup. However when the backup starts both sessions wants to write to the same volume, leaving one of the session in a media-wait state for the whole backup and the backup fails after 12h. 12,064 BPX-T- RecvW0 S 20.5 K 62.6 G Node TDP MSS- ROBUR22_SQL cp/Ip QL 12,066 BPX-T- MediaW 13.0 H 5.2 K 2.5 M Node TDP MSS- ROBUR22_SQL cp/Ip QL What can I do to fix this??? Regards Niklas Lundstrvm Swedbank
TSM showing 2 tapes in one drive...?
We are having lots of problems with LTO1 drives across a SAN, one particular strange thing I have seen is the following with a q mo; ANR8330I LTO volume PH0492 is mounted R/W in drive DRIVE06 (/dev/rmt14), status: IN USE. ANR8330I LTO volume PH0494 is mounted R/W in drive DRIVE04 (/dev/rmt13), status: IN USE. ANR8330I LTO volume PH0098 is mounted R/W in drive DRIVE08 (/dev/rmt15), status: IN USE. ANR8329I LTO volume SH0488 is mounted R/W in drive DRIVE08 (/dev/rmt7), status: IDLE. ANR8330I LTO volume SH0017 is mounted R/W in drive DRIVE03 (/dev/rmt4), status: IN USE. ANR8330I LTO volume SH0398 is mounted R/W in drive DRIVE08 (/dev/rmt7), status: IN USE. ANR8330I LTO volume SH0382 is mounted R/W in drive DRIVE04 (/dev/rmt1), status: IN USE. ANR8330I LTO volume 000360 is mounted R/O in drive DRIVE07 (/dev/rmt9), status: IN USE. ANR8379I Mount point in device class ULTRIUM1 is waiting for the volume mount to complete, status: WAITING FOR VOLUME. ANR8329I LTO volume SH0489 is mounted R/W in drive DRIVE05 (/dev/rmt5), status: IDLE. ANR8329I LTO volume SH0487 is mounted R/W in drive DRIVE09 (/dev/rmt10), status: IDLE. Notice, 2 entries for DRIVE08 on /dev/rmt7.. has anyone come across anything similar before? Or have any ideas as to what is causing it? Thanks, Matt. -Original Message- From: Nicolas Launay [EMAIL PROTECTED]@EME Sent: Thursday, January 15, 2004 10:28 AM To: [EMAIL PROTECTED] Subject: Web server deconnection Hi, a little question: when I use the web console to manage the TSM server, I have to reconnect if I don't use it during 1 or 2 minutes...It's painful... Is there a place to set it? Thank you ___ 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 the Powergen Group 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 the Powergen Group. Registered addresses: Powergen UK plc, 53 New Broad Street, London, EC2M 1SL Registered in England Wales No. 2366970 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: TSM showing 2 tapes in one drive...?
maybe misconfigured home element addresses in tape paths configuration ? check them out ! have you been having problems with switches ? goran. - Original Message - From: Warren, Matthew (Retail) [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Friday, February 13, 2004 12:20 PM Subject: TSM showing 2 tapes in one drive...? We are having lots of problems with LTO1 drives across a SAN, one particular strange thing I have seen is the following with a q mo; ANR8330I LTO volume PH0492 is mounted R/W in drive DRIVE06 (/dev/rmt14), status: IN USE. ANR8330I LTO volume PH0494 is mounted R/W in drive DRIVE04 (/dev/rmt13), status: IN USE. ANR8330I LTO volume PH0098 is mounted R/W in drive DRIVE08 (/dev/rmt15), status: IN USE. ANR8329I LTO volume SH0488 is mounted R/W in drive DRIVE08 (/dev/rmt7), status: IDLE. ANR8330I LTO volume SH0017 is mounted R/W in drive DRIVE03 (/dev/rmt4), status: IN USE. ANR8330I LTO volume SH0398 is mounted R/W in drive DRIVE08 (/dev/rmt7), status: IN USE. ANR8330I LTO volume SH0382 is mounted R/W in drive DRIVE04 (/dev/rmt1), status: IN USE. ANR8330I LTO volume 000360 is mounted R/O in drive DRIVE07 (/dev/rmt9), status: IN USE. ANR8379I Mount point in device class ULTRIUM1 is waiting for the volume mount to complete, status: WAITING FOR VOLUME. ANR8329I LTO volume SH0489 is mounted R/W in drive DRIVE05 (/dev/rmt5), status: IDLE. ANR8329I LTO volume SH0487 is mounted R/W in drive DRIVE09 (/dev/rmt10), status: IDLE. Notice, 2 entries for DRIVE08 on /dev/rmt7.. has anyone come across anything similar before? Or have any ideas as to what is causing it? Thanks, Matt. -Original Message- From: Nicolas Launay [EMAIL PROTECTED]@EME Sent: Thursday, January 15, 2004 10:28 AM To: [EMAIL PROTECTED] Subject: Web server deconnection Hi, a little question: when I use the web console to manage the TSM server, I have to reconnect if I don't use it during 1 or 2 minutes...It's painful... Is there a place to set it? Thank you ___ 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 the Powergen Group 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 the Powergen Group. Registered addresses: Powergen UK plc, 53 New Broad Street, London, EC2M 1SL Registered in England Wales No. 2366970 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: TSM showing 2 tapes in one drive...?
We encountered this before, also in a san-environment. (TSM 5.1.1.0) ANR8330I 3590 volume DCE142 is mounted R/W in drive V2_3590E1A_13_AD471 (/dev/rmt3), status: IN USE. ANR8330I 3590 volume DCE208 is mounted R/W in drive V2_3590E1A_13_AD471 (/dev/rmt3), status: IN USE. With query drive f=d or show library you will see which tape is really mounted. Stopping and starting the storage-agent didn't fix it for us. We had to restart the TSM server to get rid of this zombie-mount. Also because TSM refused to use all the drives in the device-class. Reclamations failed due to lack of mountpoints. Jeroen -Original Message- From: Warren, Matthew (Retail) [mailto:[EMAIL PROTECTED] Sent: vrijdag 13 februari 2004 12:20 To: [EMAIL PROTECTED] Subject: TSM showing 2 tapes in one drive...? We are having lots of problems with LTO1 drives across a SAN, one particular strange thing I have seen is the following with a q mo; ANR8330I LTO volume PH0492 is mounted R/W in drive DRIVE06 (/dev/rmt14), status: IN USE. ANR8330I LTO volume PH0494 is mounted R/W in drive DRIVE04 (/dev/rmt13), status: IN USE. ANR8330I LTO volume PH0098 is mounted R/W in drive DRIVE08 (/dev/rmt15), status: IN USE. ANR8329I LTO volume SH0488 is mounted R/W in drive DRIVE08 (/dev/rmt7), status: IDLE. ANR8330I LTO volume SH0017 is mounted R/W in drive DRIVE03 (/dev/rmt4), status: IN USE. ANR8330I LTO volume SH0398 is mounted R/W in drive DRIVE08 (/dev/rmt7), status: IN USE. ANR8330I LTO volume SH0382 is mounted R/W in drive DRIVE04 (/dev/rmt1), status: IN USE. ANR8330I LTO volume 000360 is mounted R/O in drive DRIVE07 (/dev/rmt9), status: IN USE. ANR8379I Mount point in device class ULTRIUM1 is waiting for the volume mount to complete, status: WAITING FOR VOLUME. ANR8329I LTO volume SH0489 is mounted R/W in drive DRIVE05 (/dev/rmt5), status: IDLE. ANR8329I LTO volume SH0487 is mounted R/W in drive DRIVE09 (/dev/rmt10), status: IDLE. Notice, 2 entries for DRIVE08 on /dev/rmt7.. has anyone come across anything similar before? Or have any ideas as to what is causing it? Thanks, Matt. -Original Message- From: Nicolas Launay [EMAIL PROTECTED]@EME Sent: Thursday, January 15, 2004 10:28 AM To: [EMAIL PROTECTED] Subject: Web server deconnection Hi, a little question: when I use the web console to manage the TSM server, I have to reconnect if I don't use it during 1 or 2 minutes...It's painful... Is there a place to set it? Thank you ___ 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 the Powergen Group 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 the Powergen Group. Registered addresses: Powergen UK plc, 53 New Broad Street, London, EC2M 1SL Registered in England Wales No. 2366970 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: TDP SQL sessions wants to write to same tape...
Niklas, Goran is correct. You need to make sure that MAXNUMMP for the NODENAME you are using for your SQL backups is set to at least to the number of stripes you are using. Also, turning on collocation by filespace will ensure that data for different stripes remains on different tapes so that the restores will also be able to read from separate tapes at the same time. From Chapter 3 of the User's Guide: - The maxnummp parameter for register or update node must be at least the maximum number of stripes to be used for backup or restore when removable media such as tapes are used or if migration occurs during the backup or restore operation. The default value is 1. This value is the maximum number of mount points a node can have at one time. If other backups or restores may occur at the same time, the value of this parameter must be large enough to allow for all of the needed mount points. - The collocate parameter for define stgpool should be set to filespace to ensure that individual data stripes stay on separate removable volumes. The default value is no. Not doing so may require move operations to make the data for each stripe of a restore simultaneously accessible. There is also a nice IBM KB article (1145253) describing more details. Go here: www.ibm.com Search for this (include the double quotes in the search window): DP for SQL : Data Striping Del ADSM: Dist Stor Manager [EMAIL PROTECTED] wrote on 02/13/2004 04:04:00 AM: Hello I've been running a backup of a SQL server db but I took too long so I increased the stripe-parameter to 2 so it would utilize 2 sessions and 2 tape drives for the backup. However when the backup starts both sessions wants to write to the same volume, leaving one of the session in a media-wait state for the whole backup and the backup fails after 12h. 12,064 BPX-T- RecvW0 S 20.5 K 62.6 G Node TDP MSS- ROBUR22_SQL cp/Ip QL 12,066 BPX-T- MediaW 13.0 H 5.2 K 2.5 M Node TDP MSS- ROBUR22_SQL cp/Ip QL What can I do to fix this??? Regards Niklas Lundström Swedbank
Re: Solaris backup performance
There has been a lot of discussion in the last year on this mailing list about using raw LVs vs. mounted filesystems, both for the Solaris TSM server and Solaris TSM client. Also, check your routing tables. -- Mark Stapleton ([EMAIL PROTECTED]) -Original Message- From: Bill Boyer [mailto:[EMAIL PROTECTED] Sent: Thu 2/12/2004 19:27 To: [EMAIL PROTECTED] Cc: Subject: Solaris backup performance TSM client 5.2.2.0 on a Solaris 7 server, gigabit fibre Ethernet adapter. TSM Server 5.2.2.1 on AIX 5.2 p630 with fibre gigabit Ethernet. Different VLAN. During the backup of this client (actually 4 out of 11 Solaris clients) the backup just drags along. Looking at the sessions on the server we see the session in RecvW state, but the wait time just goes up and up..sometimes in the double-digits before more data goes in. Doing a large FTP to that server (130MB) took just a few seconds. The other 7 Solaris clients, same TSM client, same OS level, backup like you would expect over gbit. According to the switch, the ports which are configured for autonegotiate, are at full speed and duplex. Anyone got ideas? Searching the archive brings hits on 10/100 ethernet adapters not being set correctly. Bill Boyer Some days you are the bug, some days you are the windshield. - ??
Re: Migration of TSM server from OS390 or Z-OS to a UNIX or Windows platform
Hi all One best difference of TSM running on OS/390 or Z/OS is that his cpu hungry. Use WLM giving a fraction number of SRU service units and all will be good. Claudio Almeida Favor responder a ADSM: Dist Stor Manager [EMAIL PROTECTED] Enviado Por: ADSM: Dist Stor Manager [EMAIL PROTECTED] Para: [EMAIL PROTECTED] cc: Assunto:Re: Migration of TSM server from OS390 or Z-OS to a UNIX or Windows platform [EMAIL PROTECTED] wrote The idea of moving off of OS/390 is because we are taking too much CPU and weekly IPLs. Why weekly ipls? One of the big advantages of mainframe technology is that ipls are (should be) infrequent If your TSM is in a sharing lpar the TSM dispatching priority can be set so that it does not impact on higher profile work. I say higher profile because backups are generally not regarded as important, until they are needed. If your processor/s cannot truly cope with the workload, what about an upgrade, and maybe a separate lpar for TSM, so that nobody can argue that it is taking too much cpu. At the end of the the day a move to a new platform can be worthwhile, but only as long as the full costs and benefits are taken into account. ** The information in this E-Mail is confidential and may be legally privileged. It may not represent the views of Scottish and Southern Energy plc. 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: TDP SQL sessions wants to write to same tape...
thank you - Original Message - From: Del Hoobler [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Friday, February 13, 2004 1:00 PM Subject: Re: TDP SQL sessions wants to write to same tape... Niklas, Goran is correct. You need to make sure that MAXNUMMP for the NODENAME you are using for your SQL backups is set to at least to the number of stripes you are using. Also, turning on collocation by filespace will ensure that data for different stripes remains on different tapes so that the restores will also be able to read from separate tapes at the same time. From Chapter 3 of the User's Guide: - The maxnummp parameter for register or update node must be at least the maximum number of stripes to be used for backup or restore when removable media such as tapes are used or if migration occurs during the backup or restore operation. The default value is 1. This value is the maximum number of mount points a node can have at one time. If other backups or restores may occur at the same time, the value of this parameter must be large enough to allow for all of the needed mount points. - The collocate parameter for define stgpool should be set to filespace to ensure that individual data stripes stay on separate removable volumes. The default value is no. Not doing so may require move operations to make the data for each stripe of a restore simultaneously accessible. There is also a nice IBM KB article (1145253) describing more details. Go here: www.ibm.com Search for this (include the double quotes in the search window): DP for SQL : Data Striping Del ADSM: Dist Stor Manager [EMAIL PROTECTED] wrote on 02/13/2004 04:04:00 AM: Hello I've been running a backup of a SQL server db but I took too long so I increased the stripe-parameter to 2 so it would utilize 2 sessions and 2 tape drives for the backup. However when the backup starts both sessions wants to write to the same volume, leaving one of the session in a media-wait state for the whole backup and the backup fails after 12h. 12,064 BPX-T- RecvW0 S 20.5 K 62.6 G Node TDP MSS- ROBUR22_SQL cp/Ip QL 12,066 BPX-T- MediaW 13.0 H 5.2 K 2.5 M Node TDP MSS- ROBUR22_SQL cp/Ip QL What can I do to fix this??? Regards Niklas Lundstrvm Swedbank
Server schedmode query
All our backups should run schedmode prompted. OS390 2 10 server runningTSM 4.2.4 Two problem Winnt 5.0 clients running TSM 4.2.3 Every night the scheduled backup kicks in as per normal for both clients, but in both cases an earlier unscheduled backup is already running. Both clients have schedmode prompted in their options files Have not been able to find out the cause of the unscheduled backup, other clients with the same configuration behave normally. Anyone got any thoughts on likely cause of this annoying behaviour? Currently server default option of schedmode any is used. Question is, if I set the server option to prompted, will this prevent the rogue sessions starting? Any other implications if I do this ? thanks, John ** The information in this E-Mail is confidential and may be legally privileged. It may not represent the views of Scottish and Southern Energy plc. 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. **
TSM archive behaviour
Hello, I'm currently trying to convince the TSM developers of adding a different behaviour to the archive functionality. We intend to use our TSM environment not only for backup purposes, but also for archival. Archiving, from our point of view, is a user centric service that should enable the user (i.e. owner of a particular TSM node) to access his/her data from an arbitrary system, as long as a TSM client is available. From earlier versions of TSM we knew that archive sets written by UNIX or Windows clients are mutually invisible - not a nice behavior, but not a problem. Now we realized that writing an archive set by the Windows TSM client - this being a unicode client - makes the archive *inaccessible* by any non-unicode client, i.e. any UNIX client. By this, a user who might have archived a lot of stuff from UNIX systems has an easy way to block himself from his data. On the best case, we then have manual admin action to give back the data to a user - and such a person won't come a second time! Perhaps it's necessary to distinguish the restore and retrieve operations, to our understanding of these at least: I see that a restore has to regenerate not only data, but also all filesystem meta data (ACLs, NTFS permissions etc.) In contrast to this, due to our user centric view of the archival functionality an exact filesystem restoration might be less important. Is there anyone willing to second this request to Tivoli? Best regards, Thomas http://www.rz.rwth-aachen.de/staff/eifert
adsm restore problem
we have a problem restore a back from adsm this morning the is using adms the gig card.. root su - sbl2008v db2 restore db db2008v use adsm. ( into db2008v redirect) this error we get SQL2032N The 14 parameter is not valid. what does this mean thanks Roland Priest AIX Administrator email [EMAIL PROTECTED] office 856-489-4255 office 1800-767-5822 ext.4255 Cell 856-296-6086
ODP: adsm restore problem
use tsm instead adsm -Wiadomo oryginalna- Od: Roland Priest [mailto:[EMAIL PROTECTED] Wysano: 13 lutego 2004 14:41 Do: [EMAIL PROTECTED] Temat: adsm restore problem we have a problem restore a back from adsm this morning the is using adms the gig card.. root su - sbl2008v db2 restore db db2008v use adsm. ( into db2008v redirect) this error we get SQL2032N The 14 parameter is not valid. what does this mean thanks Roland Priest AIX Administrator email [EMAIL PROTECTED] office 856-489-4255 office 1800-767-5822 ext.4255 Cell 856-296-6086
Re: Help!! dsmserv.dsk not readable
I am running Windows 2K cluster, TSM 4.2. Early yesterday morning the server crashed and would not start (on either node of the cluster). When I try and start it manually I get: ANR0212E. Unable to read disk definition file: dsmserv.dsk ... The reason for the crash may be spilling over into the reason you cannot restart. In many cases, a failing server will write a dsmserv.err (or similarly named error log) in its server directory, giving some indication of cause. I would check your system for general environmental health problems, such as full disk partitions or disk usability problems (which would include the server home directory, the db and recovery log volumes, and the stgpool disk volumes). We hope you were using TSM mirroring, to improve your chances of restarting without db recovery. Richard Sims http://people.bu.edu/rbs
Re: Stgpool backup script
I use the following shell script function to wail until the number of
backup processes are down to a specified number:
#
# waitonbkp function - waits until fewer than $maxconcurrent
# bkps are running;
# checks after 15 seconds then every 5
minutes
function waitonbkp {
waitime=15
while (( $bkps = $maxconcurrent ))
do
sleep $waitime
waitime=300
let bkps=$((`dsmadmc -id=$ID -pass=$PW q pro | grep Backup
Storage Pool |
wc -l`))
echo `date`, Number of storage pool backups running =
$bkps
done
}
[EMAIL PROTECTED] 2/12/2004 10:37:15 AM
Currently my backup script is sequential. I have been wondering if
there is a way to use all my available drives but I don't want to go
the
way of using maxpr=2 because some of my backups are very large files
like 60+ GB in size, I could be doing other things while that goes on.
I would like to run two different backup stgpools and check every so
often, if there is only one process running start another backup
stgpool.
When all my storage ppols are backed up, kick off the dbbackup
I think I can handle most of the script through ifs and gotos but my
problem is determining how many processes are currently running. The
SQL return codes don't seem to give me the results of a statement,
unless I am reading the return codes wrong.
So far what I have in mind (not exact syntax), and I have 4 drives so
I
want to run 2 concurrent backups
If [processes] = 2 goto reschedule
If [processes] = 1 goto startanotherbackup
If [processes] = 0 and allbackupscomplete goto dbbackup, volhist,
devconfig
I think that I would control what backups I have already done through
passing of script parameters.
Am I off my rocker, or is something like this possible?
Greg Redell
Great-West Life Annuity Insurance Co.
Phone: 314-543-7009
Email: [EMAIL PROTECTED]
Re: ODP: adsm restore problem
does not work.. Roland Priest AIX Administrator email [EMAIL PROTECTED] office 856-489-4255 office 1800-767-5822 ext.4255 Cell 856-296-6086 [EMAIL PROTECTED] 02/13/04 08:46AM use tsm instead adsm -Wiadomosc oryginalna- Od: Roland Priest [mailto:[EMAIL PROTECTED] Wyslano: 13 lutego 2004 14:41 Do: [EMAIL PROTECTED] Temat: adsm restore problem we have a problem restore a back from adsm this morning the is using adms the gig card.. root su - sbl2008v db2 restore db db2008v use adsm. ( into db2008v redirect) this error we get SQL2032N The 14 parameter is not valid. what does this mean thanks Roland Priest AIX Administrator email [EMAIL PROTECTED] office 856-489-4255 office 1800-767-5822 ext.4255 Cell 856-296-6086
Re: linux AMD64 client?
I thought the BA was required, and I'm not sure why the download site has the API, but not the BA. Can I use the x86 BA with the 64-bit API? Will that work on a RHEL3 AMD64 machine? Thanks, Alex On Thu, 12 Feb 2004, Alexander Lazarevich wrote: That has only TIVsm-API.x86_64.rpm. Still doesn't have the BA. I need this: TIVsm-BA.x86_64.rpm Any other ideas? Alex On Thu, 12 Feb 2004, Zoltan Forray/AC/VCU wrote: Have you tried here: ftp://service.boulder.ibm.com/storage/tivoli-storage-management/patches/client/v5r2/Linux/LinuxAMD64/v522/ ADSM: Dist Stor Manager [EMAIL PROTECTED] wrote on 02/12/2004 12:32:32 PM: We have a new Redhat Linux Advanced Server 3 Workstation AMD64 client, but I can't seem to find the TSM client for it. Server is 5.1.6.5 on windows 2K server. Looking for the client in: ftp://ftp.software.ibm.com/storage/tivoli-storage-management/ Looking in maintenance, which is where I normally find things, I only see the 64-bit Itanium client. No AMD64. In patches, I do see the API for AMD64, but no BA, which is what I really need. Any idea if it's available yet? Thanks, Alex --- --- Alex Lazarevich | Systems Administrator | Imaging Technology Group Beckman Institute | University of Illinois | www.itg.uiuc.edu --- ---
Re: TSM Gui
Does the userid running the GUI have the same authorization level as the CLI that did the archive? [EMAIL PROTECTED] 2/12/2004 11:17:56 AM I'm running TSM 5.1.6 client on W2K. TSM Server is v5.1.1.6 running on Unix. I have archives running command line on the client. When I try to retrieve thru the GUI, no archives are displayed. Anyone have any ideas as to why?? Thanks, Pattie
Re: TSM Gui
Make sure the gui is using the same option file. Eddie Jones 770-953-1959 ext.2824 The greatest lesson in life is to know that even fools are right sometimes. - Sir Winston Spencer Churchill David E Ehresman [EMAIL PROTECTED]To: [EMAIL PROTECTED] LLE.EDU cc: Sent by: ADSM: Subject: Re: TSM Gui Dist Stor Manager [EMAIL PROTECTED] .EDU 02/13/2004 08:59 AM Please respond to ADSM: Dist Stor Manager Does the userid running the GUI have the same authorization level as the CLI that did the archive? [EMAIL PROTECTED] 2/12/2004 11:17:56 AM I'm running TSM 5.1.6 client on W2K. TSM Server is v5.1.1.6 running on Unix. I have archives running command line on the client. When I try to retrieve thru the GUI, no archives are displayed. Anyone have any ideas as to why?? Thanks, Pattie ---***---
Re: ODP: adsm restore problem
we have a problem restore a back from adsm this morning the is using adms the gig card.. root su - sbl2008v db2 restore db db2008v use adsm. ( into db2008v redirect) this error we get SQL2032N The 14 parameter is not valid. what does this mean It will help us help you if you post specifying your software environment including the OS and software level of the involved components.
Re: TSM Disaster Recovery Testing
Run the DRM command, prepare Then look at its output. David [EMAIL PROTECTED] 2/12/2004 7:45:36 PM We are in the process of setting up to do a test of our disaster recovery server. does anyone out there know what I run to find out what tapes I would need to restore a specific server? we would like to ship the tapes from the vault offsite prior to the actual test and I can't remember what the script is to find them. Thanx Tammy Schellenberg Systems Administrator, MCP Prospera Credit Union email: [EMAIL PROTECTED] DID: 604-864-6578 Chaos, panic, disorder - my work here is done. This email and any files transmitted with it are confidential and are intended solely for the use of the individual or entity to whom they are addressed. If you are not the original recipient or the person responsible for delivering the email to the intended recipient, be advised that you have received this email in error, and that any use, dissemination, forwarding, printing, or copying of this email is strictly prohibited. If you receive this email in error, please immediately notify the sender. Please note that this financial institution neither accepts nor discloses confidential member account information via email. This includes password related inquiries, financial transaction instructions and address changes.
ESS model 27
People, Environment Z/os 1.4 TSM 5.1.6 We will be moving our TSM server environment from ESS F20s (18 gb disks) to ESS 800s (146gb disks) in the near future Currently I have 99 addresses, all emulating 3390-3 disks that provide for database volumes, recovery logs and storage pools. With the new 800s, I will be using either 3390-9 or 3390-27 emulation giving the number of disk address as either 33 or 11. I am interested in the experience of anyone using ESS 800s with the 146gb disks. Did you go with 3390-9 or 3390-27 Did you go with very large TSM logical volumes. Any recommendations? thanks, John ** The information in this E-Mail is confidential and may be legally privileged. It may not represent the views of Scottish and Southern Energy plc. 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. **
Here is MS article on controlling .pst lock time OUTLOOK 2000
I received this in response to a question to IBM on possible solutions. I did not know that MS had published this. It applies to OUTLOOK 2000. We are currently working with MS on getting this to work with OUTLOOK 2003. Currently in our environment OUTLOOK 2003 NEVER lets go of the .pst files. I believe that is a bug.. This procedure does work with OUTLOOK 2000 in our shop. Matt The *.pst file is locked by Outlook while it is used continues to be locked for 30 minutes (by default) of inactivity. There is to configure to release the lock earlier than 30 minutes of activity, which could give a chance to TSM to backup the file. I would recommend that you take a look at a Microsoft article which discusses this issue. This is Microsoft KB Article 222328, titled OL2000: (CW) How to Change File LockTimeout Value for PST Inactivity which can be found on the Microsoft support website at http://support.microsoft.com/default.aspx?scid=fh;EN-US;KBHOWTO .
exclude questions
Why, in the Backup-Archive Clients Installation and User's Guide v5.2 for Unix does it recommend having the following as a minimum in the backup.excl file. exclude /unix/yet to come across a directory called unix on solaris, aix or linux.. so what do these two unix statements do? exclude.dir /unix/ exclude /.../coreI know what this does And finally, we've implemented the following (//.../*) in a backup.excl list and proven that it does work, however, it's not documented anywhere in the manuals so we don't want to deploy companywide until we get confirmation that there are no adverse effects. The first line excludes any file systems that may be added to a client without our knowledge. However, it was excluding / (root) as well. Note: we put the extra / in front of root, and it now works. Does anyone have any insight? exclude /*/.../* include //.../* 31VER_31DAYS include /var/.../* 31VER_31DAYS include /orabackup/.../* 31VER_31DAYS include /orahome/.../* 31VER_31DAYS include /orapirelarch/.../* 31VER_31DAYS include /app/lzrchk/.../* 31VER_31DAYS exclude /.../core exclude.fs /tmp exclude.fs /etc/mnttab exclude.fs /var/run exclude.fs /dev/fd exclude.fs /etc/mnttab exclude.fs /proc exclude.fs /orapirel01 exclude.fs /orapirel02 exclude.fs /orapirel03 == If you are not an intended recipient of this e-mail, please notify the sender, delete it and do not read, act upon, print, disclose, copy, retain or redistribute it. Click here for important additional terms relating to this e-mail. http://www.ml.com/email_terms/ ==
mountlimit=drives
Hi: Sessions and processes seem to be sinlge threading using a single drive in a 4 drive library. the dev is set to mountlimit=drive. anyone know what else might cause this bottleneck? As shown below, library with 4 drives only shows a mount waiting on a volume when another is dismounting. tsm: BACKUPq mount ANR8379I Mount point in device class 3494BTAPE is waiting for the volume mount to complete, status: WAITING FOR VOLUME. ANR8331I 3590 volume 001038 is mounted R/W in drive 3590RMT4 (/dev/rmt4), status: DISMOUNTING. ANR8334I 2 matches found. Device Class Name: 3494BTAPE Device Access Strategy: Sequential Storage Pool Count: 7 Device Type: 3590 Format: DRIVE Est/Max Capacity (MB): 40,960.0 Mount Limit: DRIVES Mount Wait (min): 60 Mount Retention (min): 5 Label Prefix: ADSMVOL Library: IBM3494B Directory: Server Name: Retry Period: Retry Interval: Shared: Last Update by (administrator): ADMIN Last Update Date/Time: 02/12/04 11:34:44
[no subject]
Greetings! Anybody have piece of information on compatibility of NS600 backups on TSM 5.1?
Solaris 8 client dsm.sys file question.
Folks, I was looking through our documentation and I find that I have not documented a good example of what a dsm.sys file for a Solaris client should be. It looks like on our systems our txnbytelimit, tcpbuffsize tcpwindowsize are all over the board. Anybody have a good standard dsm.sys file for Solaris 8 to share? - Client version TSM 5.2.0.4 - Server version TSM 5.2.1.3 - Nice fast dedicated backup network. Thanks, Ben
IC27346 and message ANS4018E
Windows 2000 5.2.2.0 client Windows 2000 TSM server 5.2.1.2 During the backup of a network attached drive, we see ANS4018E messages in the error log on the client. Looking in the help and the latest Messages manual doesn't show this message. Searching on IBM only gave me 3 hits that were old. Searching ADSM-L archives gave me lots of stuff!! Andy's emails on APAR IC27346 seems to hit the nail on the head. The APAR discusses the USEUNICODEFILENAMES option. That options isn't in the 5.2.2 client manual. Doing a QUERY OPT on the client doesn't list that. I can add it to the DSM.OPT file and not get an error starting the client. The filespaces on this node are not unicode, but will this option actually DO anything?? It's not documented in the client manual or help for the 5.2.2 client. Bill Boyer Some days you are the bug, some days you are the windshield. - ??
Re: ESS model 27
Hi John, I can't give you specific TSM mod 27 experience, but we use mod27's heavily on our 800 for DB2 and it screams. No performance problems, but you should know we are using dynamic PAV's. I would have no hesitation using mod27's for about anything. Dave Nicholson John Naylor [EMAIL PROTECTED] Sent by: ADSM: Dist Stor Manager [EMAIL PROTECTED] 02/13/2004 10:04 AM Please respond to ADSM: Dist Stor Manager To: [EMAIL PROTECTED] cc: Subject:ESS model 27 People, Environment Z/os 1.4 TSM 5.1.6 We will be moving our TSM server environment from ESS F20s (18 gb disks) to ESS 800s (146gb disks) in the near future Currently I have 99 addresses, all emulating 3390-3 disks that provide for database volumes, recovery logs and storage pools. With the new 800s, I will be using either 3390-9 or 3390-27 emulation giving the number of disk address as either 33 or 11. I am interested in the experience of anyone using ESS 800s with the 146gb disks. Did you go with 3390-9 or 3390-27 Did you go with very large TSM logical volumes. Any recommendations? thanks, John ** The information in this E-Mail is confidential and may be legally privileged. It may not represent the views of Scottish and Southern Energy plc. 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. **
TSM Server 4.2.2.10 from AIX 4.3 to TSM Server 5.2 on SUN Solaris 9
Hello I need to know how to migrate TSM Server 4.2.2.10 from AIX Operating System to TSM server 5.2 on Sun Solaris 9 Operating System. We currently have TSM Server 4.2.2.10 (32 bit) on AIX 4.3. I believe we should do the migrate from TSM server AIX to Sun Solaris first, then go from TSM Server 4.2.2.10 to TSM 5.2, but I'm not sure. Please give me some advice or best ways to do that. Any hints and tips are very welcome and appreciated. Thanks in advance. Juan R. This communication is for use by the intended recipient and contains information that may be privileged, confidential or copyrighted under law. If you are not the intended recipient, you are hereby formally notified that any use, copying or distribution of this e-Mail, in whole or in part, is strictly prohibited. Please notify the sender by return e-Mail and delete this e-Mail from your system. Unless explicitly and conspicuously stated in the subject matter of the above e-Mail, this e-Mail does not constitute a contract offer, a contract amendment, or an acceptance of a contract offer. This e-Mail does not constitute consent to the use of sender's contact information for direct marketing purposes or for transfers of data to third parties. This email has been scanned for all viruses by the MessageLabs service.
LAN free backup giving timeout error on drive
I have 3584 library on one client window 2000(TDP for SAL)is configured on lan free,sometimes I am getting these errors on actlog: 2/11/04 21:30:37 ANR0408I Session 440 started for server STORAGESQL (Windows) (Tcp/Ip) for library sharing. 02/11/04 21:30:55 ANR8337I LTO volume T7 mounted in drive DRIVE4 (/dev/rmt3). 02/11/04 21:31:33 ANR0403I (Session: 434, Origin: STORAGESQL) Session 1404 ended for node HTTXDS008DB (TDP MSSQL). 02/11/04 21:32:33 ANR8325I (Session: 434, Origin: STORAGESQL) Dismounting volume T00020 - 1 minute mount retention expired. 02/11/04 21:32:39 ANR8336I (Session: 434, Origin: STORAGESQL) Verifying label of LTO volume T00020 in drive DRIVE1 (\\.\tape0). 02/11/04 21:32:47 ANR8220W TCP/IP driver is unable to set the window size to 1048576 for client 172.30.146.17. The default value will be used. 02/11/04 21:32:47 ANR0408I Session 441 started for server STORAGESQL (Windows) (Tcp/Ip) for library sharing. 02/11/04 21:32:47 ANR0409I Session 441 ended for server STORAGESQL (Windows). 02/11/04 21:33:52 ANR8220W TCP/IP driver is unable to set the window size to 1048576 for client 172.30.146.17. The default value will be used. 02/11/04 21:33:52 ANR0408I Session 442 started for server STORAGESQL (Windows) (Tcp/Ip) for library sharing. 02/11/04 21:33:52 ANR8336I Verifying label of LTO volume T00020 in drive DRIVE1 (/dev/rmt0). 02/11/04 21:33:52 ANR8468I (Session: 434, Origin: STORAGESQL) LTO volume T00020 dismounted from drive DRIVE1 (\\.\tape0) in library 3584LIB. 02/11/04 21:33:52 ANR0409I Session 442 ended for server STORAGESQL (Windows). 02/11/04 21:37:03 ANR8304E (Session: 434, Origin: STORAGESQL) Time out error on drive DRIVE4 (\\.\tape3) in library 3584LIB. 02/11/04 21:37:03 ANR8336I Verifying label of LTO volume T7 in drive DRIVE4 (/dev/rmt3). 02/11/04 21:37:25 ANR8468I LTO volume T7 dismounted from drive DRIVE4 (/dev/rmt3) in library 3584LIB. 02/11/04 21:37:25 ANR1401W (Session: 434, Origin: STORAGESQL) Mount request denied for volume T7 - mount failed. 02/11/04 21:37:25 ANR0409I Session 440 ended for server STORAGESQL (Windows). more... (ENTER to continue, 'C' to cancel) 02/11/04 21:37:26 ANR8220W TCP/IP driver is unable to set the window size to 1048576 for client 172.30.146.17. The default value will be used. 02/11/04 21:37:26 ANR0408I Session 443 started for server STORAGESQL (Windows) (Tcp/Ip) for library sharing. 02/11/04 21:37:26 ANR8337I (Session: 434, Origin: STORAGESQL) LTO volume T00020 mounted in drive DRIVE1 (\\.\tape0). 02/11/04 21:37:26 ANR0409I Session 443 ended for server STORAGESQL (Windows). -- 02/12/04 12:17:18 ANR8337I (Session: 697, Origin: STORAGESQL) LTO volume T00017 mounted in drive DRIVE2 (\\.\tape1). 02/12/04 12:18:35 ANR8336I (Session: 697, Origin: STORAGESQL) Verifying label of LTO volume T00017 in drive DRIVE2 (\\.\tape1). 02/12/04 12:19:08 ANR8468I (Session: 697, Origin: STORAGESQL) LTO volume T00017 dismounted from drive DRIVE2 (\\.\tape1) in library 3584LIB. 02/12/04 12:30:33 ANR2017I Administrator VIVEKJ issued command: QUERY ACTLOG begind=-2 se=tape
Re: TSM Server 4.2.2.10 from AIX 4.3 to TSM Server 5.2 on SUN Solaris 9
About a year ago I was involved in moving a 40GB TSM database from AIX 4.3 to Solaris 8. The first thing that we did was upgrade the TSM on the AIX box to the, then, current TSM version which was 5.1. A server-to-server export would have taken, quite literally, months. So the previous the database backup was restored with the dsmserv commands. I am at home and won't have all the details till I go to work on Tuesday. I can give you some good advice on this subject. Something that I certainly do remember is the necessity put database, recovery log, and stgpool volumes on raw disks. Juan Jose Reale [EMAIL PROTECTED] wrote:Hello I need to know how to migrate TSM Server 4.2.2.10 from AIX Operating System to TSM server 5.2 on Sun Solaris 9 Operating System. We currently have TSM Server 4.2.2.10 (32 bit) on AIX 4.3. I believe we should do the migrate from TSM server AIX to Sun Solaris first, then go from TSM Server 4.2.2.10 to TSM 5.2, but I'm not sure. Please give me some advice or best ways to do that. Any hints and tips are very welcome and appreciated. Thanks in advance. Juan R. This communication is for use by the intended recipient and contains information that may be privileged, confidential or copyrighted under law. If you are not the intended recipient, you are hereby formally notified that any use, copying or distribution of this e-Mail, in whole or in part, is strictly prohibited. Please notify the sender by return e-Mail and delete this e-Mail from your system. Unless explicitly and conspicuously stated in the subject matter of the above e-Mail, this e-Mail does not constitute a contract offer, a contract amendment, or an acceptance of a contract offer. This e-Mail does not constitute consent to the use of sender's contact information for direct marketing purposes or for transfers of data to third parties. This email has been scanned for all viruses by the MessageLabs service. - Post your free ad now! Yahoo! Canada Personals
Re: IC27346 and message ANS4018E
During the backup of a network attached drive, we see ANS4018E messages in the error log on the client. Looking in the help and the latest Messages manual doesn't show this message. ... Bill - You must not be using a Macintosh workstation... ;-) The msg is in the 5.2 Messages manual that I'm PDF-browsing; but the manual says little more than the file name being too long, and to consult your platform B/A manual for the length limits. If you're seeing this just sporadically, then you may have a few rogue files on the Windows box. You might try running a commercial disk and file system checker to find any abnormalities out there, to identify if not fix them. Richard Sims
Re: Solaris backup performance
Bill, It sounds like we are fighting a similar problem. We upgraded the last of our TSM servers from AIX4.3.3/TSM5.1.1.0 to AIX5.2ML2/TSM5.2.1.3 on Tuesday. This TSM server has the largest load of our servers. Both the TSM server and this particular client have GB interfaces (the Solaris host has a SysKonnect GB interface). We are having ~very~ serious problems as a 1.5TB database backup from the Solaris host has doubled in the time it takes to get done. We too see the RecW on the sessions which is atypical. We are sweating bullets, and I have opened calls with IBM (for the OS) and Tivoli, but have yet to get a resolution. We have the Solaris client push the data to the TSM server in 6 threads, each of these threads goes directly to a 3595 tape drive. So a real blast of data from one client. Before the upgrade we were hitting almost 70MB/second, but now we flatline at about 45MB/second. We did not have jumbo frames on, just a regular 1500 MTU size. Since we upgraded both the OS and the TSM server at the same time, we are unsure of which changed introduced the problem. At this point, my gut feeling is that the OS somehow cannot run packets through the TCP stack as fast as before. With an entstat -d en? command on the TSM GB interface, I see many many No Resource errors being logged when the GB is running hard. IBM network support says that those errors may be caused by the application not handling the packets from the TCP stack properly. Just as I was composing this, we turned on Jumbo frames on the TSM server, the switches in between and on the client. Our 6-thread push is now running almost as fast as before, but we are still getting those No resource errors on the TSM GB interface. My feeling is still an OS problem with the TCP stack when it is being pushed hard. Ben -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Bill Boyer Sent: Thursday, February 12, 2004 6:28 PM To: [EMAIL PROTECTED] Subject: Solaris backup performance TSM client 5.2.2.0 on a Solaris 7 server, gigabit fibre Ethernet adapter. TSM Server 5.2.2.1 on AIX 5.2 p630 with fibre gigabit Ethernet. Different VLAN. During the backup of this client (actually 4 out of 11 Solaris clients) the backup just drags along. Looking at the sessions on the server we see the session in RecvW state, but the wait time just goes up and up..sometimes in the double-digits before more data goes in. Doing a large FTP to that server (130MB) took just a few seconds. The other 7 Solaris clients, same TSM client, same OS level, backup like you would expect over gbit. According to the switch, the ports which are configured for autonegotiate, are at full speed and duplex. Anyone got ideas? Searching the archive brings hits on 10/100 ethernet adapters not being set correctly. Bill Boyer Some days you are the bug, some days you are the windshield. - ??
Re: Stgpool backup script
= In article [EMAIL PROTECTED], David E Ehresman [EMAIL PROTECTED] writes: [EMAIL PROTECTED] 2/12/2004 10:37:15 AM I would like to run two different backup stgpools and check every so often, if there is only one process running start another backup stgpool. When all my storage ppols are backed up, kick off the dbbackup I use the following shell script function to wail until the number of backup processes are down to a specified number: Why not just kick off all the work you need to do? The processes that can't grab a mount point will happily wait around. I've got probably 40 DISK stgpools that I backup and migrate every day. My TSM script that kicks them off is included below: when it starts, it initiates a bunch of backup processes, some of which fail immediately (no data in disk pool) some of which check and find all up to date, some of which do work. This method saves you logic and actlog lines of your script constantly polling, and it further uses the tape drives during the lag between when a process completes, and when your script next polls. - Allen S. Rout /* stgpool backup script */ /* for device class 'DISK' */ /* /* /* This script generated by /u/adsm/bin/gen-backup-script /* at 2004-02-13 05:05:04 /* on spnode05 /* /* */ backup stgpool sm-disk sm-c1 maxproc=1 backup stgpool uaa-disk uaa-c1 maxproc=1 backup stgpool counsel-disk counsel-c1 maxproc=1 backup stgpool mse-disk mse-c1 maxproc=1 backup stgpool mbi-disk mbi-c1 maxproc=1 backup stgpool path-disk path-c1 maxproc=1 backup stgpool erp-disk erp-c1 maxproc=1 backup stgpool erp-disk erp-itc maxproc=2 backup stgpool runs-disk runs-c1 maxproc=1 backup stgpool doce-disk doce-c1 maxproc=1 backup stgpool nersp-disk nersp-c1 maxproc=1 backup stgpool glmail-disk nersp-c1 maxproc=1 backup stgpool nersp-disk nersp-itc maxproc=2 backup stgpool edify-disk edify-c1 maxproc=1 backup stgpool edify-disk edify-itc maxproc=1 backup stgpool admin-disk admin-c1 maxproc=1 backup stgpool atcs-disk atcs-c1 maxproc=1 backup stgpool atcs-disk atcs-itc maxproc=1 backup stgpool hp-disk hp-c1 maxproc=1 backup stgpool afn-disk afn-c1 maxproc=1 backup stgpool deleted-users-disk deleted-users-C1 maxproc=1 backup stgpool novell-disk novell-c1 maxproc=1 backup stgpool novell-disk novell-itc maxproc=1 backup stgpool registrar-disk registrar-c1 maxproc=1 backup stgpool thecenter-disk thecenter-c1 maxproc=1 backup stgpool thecenter-disk thecenter-itc maxproc=1 backup stgpool uff-disk uff-c1 maxproc=1 backup stgpool workstations-disk workstations-c1 maxproc=1 backup stgpool workstations-disk workstations-itc maxproc=1 backup stgpool vi-disk vi-itc maxproc=1 backup stgpool vi-disk vi-c1 maxproc=1 backup stgpool zoo-disk zoo-c1 maxproc=1 backup stgpool zoo-disk zoo-itc maxproc=1 backup stgpool lawnet-disk lawnet-c1 maxproc=1 /* EOF */
Tape mount failures result in schedule failure
Hi, The environment is TSM/StorageAgent/Win2000 5.2.2, IBM 3584 LTO library. Activity log indicate that session 237 failed to mount a tape volume 293AGHL2 in drive mt3.0.0.3, showing repeated ANR8779E (Session: 237, Origin: SP02B_STA) Unable to open drive mt3.0.0.3, error number=2. (SESSION: 237) so after 5 minutes got ANR1401W (Session: 237, Origin: SP02B_STA) Mount request denied for volume 293AGHL2 - mount failed. (SESSION: 237) It then mounted the volume successfully in drive mt6.0.0.3. 3 minutes after that, session 255 started to mount 298AGHL2 in mt6.0.0.3, resulting in repeated ANR8779E (Session: 255, Origin: SP18A_STA) Unable to open drive mt6.0.0.3, error number=170. (SESSION: 255) It then mounted the volume successfully in drive mt5.0.0.3. Is this behavior normal for tape libraries? It is an indication of some problem with the drives? Where can I find the meaning of the error number 2 and 170? Both tape mounts were requests by scheduled backup and it seems to me as a result of the tape mount failures, the scheduled got a return code 12 and showed up as failed. Is this assessment correct? Thanks in advance to anyone who can shed some light on this. Regards, David Zhu TSM Support [EMAIL PROTECTED] Tel: 416-503-7853
data move question
TSM 5.1.6.5 server on windows 2K server SP4. Adaptec 29160 controller. Overland Neo 4100 with 2 X LTO-2 SCSI drives. 31 LTO2 tapes. One of our drives, MT1.0.0.3, keeps going offline with the following error: 02/13/2004 12:00:39 ANR8944E Hardware or media error on drive MT1.0.0.3 (mt1.0.0.3) (OP=READ, Error Number=1117, CC=305, KEY=04, ASC=44, ASCQ=00, SENSE=F0.00.04.00.00.24.47.0E.00.00.00.- 00.44.00.00.00.30.20.00.00.00.00., Description=Drive failure). Refer to Appendix D in the 'Messages' manual for recommended action. One particular tape keeps making the drive fail - ITG017L2. When I move data off that tape, the server ALWAYS mounts that tape into MT1.0.0.3. The drive then fails with the error above and the drive is marked as offline. Yet the tape reports no read or write errors. So I'm not sure where the problem lies: tape or drive. I have a suspicion it is the tape, what I need to do is force tape ITG017L2 into the other drive, MT2.0.0.3, and try moving the data from that other drive. If MT2.0.0.3 fails the same way, then I'm almost certain it's a bad tape. Is there a way to force the server to put tape ITG017L2 into drive MT2.0.0.3 for a move data? Thanks in advance, Alex
Performance Comparison of JFS vs RAW STGPools
Greetings! Does anybody have Stgpool bigger than 4TB? If so how is it laid out? Amar
Re: Bare Metal Restore Intel
In order to restore Win2K or Windows 2003 you have to know about the In-Place Upgrade process. This is run when you boot from an Install CD and then pick the Repair option that is after you press F8 to accept the license agreement. This is very important because if you pick Repair before the license agreement then you are running the recovery console which is not what you want. Refer to MS's KB article 292175 - How to Perform an In-Place Upgrade of Windows 2000 for more information on this process. Note that it is very important that you use an Install CD that has been slip streamed with the proper service pack. In other words if the system you are restoring had SP4. Then you need to have an Install with SP4 slip streamed into it for best results. Now, using the base Install CD from MS without slip streaming will work but sometimes it doesn't and I have found that when it doesn't work a slipstreamed CD will. I have used this process with TSM to restore to different RAID adapters, different vendors, MPS to ACPI and back. We have even recently used this process to restore a single CPU server to a Dual. This has been something I couldn't get to work in the past and using the slip stream CD seemed to be the trick. I can state without a doubt that this will work with TSM. I do have full documented procedures on how to do all this on Win2K and Win2003. I also have the old NT4.0 doc. Unfortunately, because I am a consultant I can't give it away. However, I will list the KB articles that I used to come up with the procedures. Simply replace NTBackup with TSM and you should be able to get this stuff done. 249694 - How to Move a Windows 2000 Installation to Different Hardware - This is the old article that I used to come up with my documentation. Note that it doesn't really state anything about recovery but the steps are the same. 263532 - How to perform a disaster recovery restoration of Active Directory on a computer with a different hardware configuration - This document is the latest one out there. As you can see it actually states disaster recovery. 292175 - How to Perform an In-Place Upgrade of Windows 2000 - Both of the above 2 articles refer to In-Place Upgrade. This is the step that I was talking to you about which I use in my documents. Note that it doesn't state this but I believe best results are found when using a Win2K CD with a service pack slipstreamed in it for the CD you use for the In-Place Upgrade. Henrik Hansson [EMAIL PROTECTED] wrote: Hello TSM'ers I know that a bare metal restore on a W2K system works fine as long as the restore is doen to a similar system, hardware vice. But do anyone know how to do the same to a system with different hardware? I've tried it but haven't succeded. The system don't boot but give me a system error. 1. Have anyone done such a restore to a diffrent hardware system? 2. Does anyone know if ITSM will support such in the future. I know that veritas have a product that accomplish this. Med Vdnlig Hdlsning/ Best Regards _ Henrik Hansson - Do you Yahoo!? Yahoo! Finance: Get your refund fast by filing online
Re: Stgpool backup script
Why not just kick off all the work you need to do? Because I have an obligation to keep at least one tape drive free for restores and/or ad hoc backups.
Re: data move question
Leave MT1.0.0.3 offline and reissued the move data. It will then have to pick another drive to try the mount. [EMAIL PROTECTED] 2/13/2004 2:14:14 PM TSM 5.1.6.5 server on windows 2K server SP4. Adaptec 29160 controller. Overland Neo 4100 with 2 X LTO-2 SCSI drives. 31 LTO2 tapes. One of our drives, MT1.0.0.3, keeps going offline with the following error: 02/13/2004 12:00:39 ANR8944E Hardware or media error on drive MT1.0.0.3 (mt1.0.0.3) (OP=READ, Error Number=1117, CC=305, KEY=04, ASC=44, ASCQ=00, SENSE=F0.00.04.00.00.24.47.0E.00.00.00.- 00.44.00.00.00.30.20.00.00.00.00., Description=Drive failure). Refer to Appendix D in the 'Messages' manual for recommended action. One particular tape keeps making the drive fail - ITG017L2. When I move data off that tape, the server ALWAYS mounts that tape into MT1.0.0.3. The drive then fails with the error above and the drive is marked as offline. Yet the tape reports no read or write errors. So I'm not sure where the problem lies: tape or drive. I have a suspicion it is the tape, what I need to do is force tape ITG017L2 into the other drive, MT2.0.0.3, and try moving the data from that other drive. If MT2.0.0.3 fails the same way, then I'm almost certain it's a bad tape. Is there a way to force the server to put tape ITG017L2 into drive MT2.0.0.3 for a move data? Thanks in advance, Alex
9940B drive performance question
We are implementing some 9940B drives and have just begun testing. I was wondering if anyone might share what speeds they are seeing in MB/s or GB/hr for large file backups directly to tape and tape to tape transfers of large files? We are hoping to see 85 - 90 GB/hr or better when backing up uncompressed large 100GB database files.. Any other information would be interesting as well? - Do you Yahoo!? Yahoo! Finance: Get your refund fast by filing online
Re: 9940B drive performance question
From: TSM_User [mailto:[EMAIL PROTECTED] I was wondering if anyone might share what speeds they are seeing in MB/s or GB/hr for large file backups directly to tape and tape to tape transfers of large files? We are hoping to see 85 - 90 GB/hr or better when backing up uncompressed large 100GB database files.. === IIRC, the theoretical maximum throughput of a 9940B drive is 15MB/sec uncompressed, which is 54GB/hr. I wouldn't hold my breath... -- Mark Stapleton ([EMAIL PROTECTED])
Re: 9940B drive performance question
No, the Data transfer rate for 9940B uncompressed is 30 MB/s or ~105 GB/hr. The Data transfer rate compressed is 70 MB/s or ~ 246 GB/hr. See http://www.storagetek.com/products/product_page38.html#specifications if you have any questions on this. The reason I mentioned that the data was not compressed was because with drive compression we hope to achieve even better than 30 MB/s. Stapleton, Mark [EMAIL PROTECTED] wrote: From: TSM_User [mailto:[EMAIL PROTECTED] I was wondering if anyone might share what speeds they are seeing in MB/s or GB/hr for large file backups directly to tape and tape to tape transfers of large files? We are hoping to see 85 - 90 GB/hr or better when backing up uncompressed large 100GB database files.. === IIRC, the theoretical maximum throughput of a 9940B drive is 15MB/sec uncompressed, which is 54GB/hr. I wouldn't hold my breath... -- Mark Stapleton ([EMAIL PROTECTED]) - Do you Yahoo!? Yahoo! Finance: Get your refund fast by filing online
Re: Tape mount failures result in schedule failure
Hi David, With regard to the ANR1401 Error, when a TSM volume fills up on an LTO Generation II drive, the drive does not reset its EOT (end-of-tape) flag. Subsequently, when a scratch volume is being mounted in the same drive and TSM tries to write the BOT (beginning-of-tape) information, the drive returns to the driver (and then TSM) that it is at the EOT (end-of-tape) and therefore TSM is unabe to write to the tape. In the TSM actlog, all you get is ANR1401W indicating that volume failed to mount. This is an LTO II drive microcode problem which is fixed at microcode 37E1 level and above. The LTO Generation II drive firmware must be updated to 37E1 level or above. I am sure that others on the list will have an answer to your other issues J. Neal Certified Tivoli Administrator From: Zhu, David [EMAIL PROTECTED] Reply-To: ADSM: Dist Stor Manager [EMAIL PROTECTED] To: [EMAIL PROTECTED] Subject: Tape mount failures result in schedule failure Date: Fri, 13 Feb 2004 13:48:20 -0500 Hi, The environment is TSM/StorageAgent/Win2000 5.2.2, IBM 3584 LTO library. Activity log indicate that session 237 failed to mount a tape volume 293AGHL2 in drive mt3.0.0.3, showing repeated ANR8779E (Session: 237, Origin: SP02B_STA) Unable to open drive mt3.0.0.3, error number=2. (SESSION: 237) so after 5 minutes got ANR1401W (Session: 237, Origin: SP02B_STA) Mount request denied for volume 293AGHL2 - mount failed. (SESSION: 237) It then mounted the volume successfully in drive mt6.0.0.3. 3 minutes after that, session 255 started to mount 298AGHL2 in mt6.0.0.3, resulting in repeated ANR8779E (Session: 255, Origin: SP18A_STA) Unable to open drive mt6.0.0.3, error number=170. (SESSION: 255) It then mounted the volume successfully in drive mt5.0.0.3. Is this behavior normal for tape libraries? It is an indication of some problem with the drives? Where can I find the meaning of the error number 2 and 170? Both tape mounts were requests by scheduled backup and it seems to me as a result of the tape mount failures, the scheduled got a return code 12 and showed up as failed. Is this assessment correct? Thanks in advance to anyone who can shed some light on this. Regards, David Zhu TSM Support [EMAIL PROTECTED] Tel: 416-503-7853 _ Optimize your Internet experience to the max with the new MSN Premium Internet Software. http://click.atdmt.com/AVE/go/onm00200359ave/direct/01/
Re: Tape mount failures result in schedule failure
Hi Neal, I am also getting same errors, my storage node is windows2000(TDP for SQL)backup is through LAN free,how to know frivesare gen1 or gen2? my microcode is: $ lscfg -vl rmt0 DEVICELOCATION DESCRIPTION rmt0 1D-08-01 IBM 3580 Ultrium Tape Drive (FCP) ManufacturerIBM Machine Type and Model..ULT3580-TD2 Serial Number...1110028439 Device Specific.(FW)38D0 httxds009[/home/vivekj]$ lscfg -vl smc0 DEVICELOCATION DESCRIPTION smc0 1D-08-01 IBM 3584 Library Medium Changer (FCP) ManufacturerIBM Machine Type and Model..03584L32 Serial Number...078144940401 Device Specific.(FW)3480 is it ok? error I am getting: 2/12/04 13:28:07 ANR8779E (Session: 704, Origin: STORAGESQL) Unable to open drive \\.\tape3, error number=170. 02/11/04 21:37:25 ANR1401W (Session: 434, Origin: STORAGESQL) Mount request denied for volume T7 - mount failed. On Sat, 14 Feb 2004 Jim Neal wrote : Hi David, With regard to the ANR1401 Error, when a TSM volume fills up on an LTO Generation II drive, the drive does not reset its EOT (end-of-tape) flag. Subsequently, when a scratch volume is being mounted in the same drive and TSM tries to write the BOT (beginning-of-tape) information, the drive returns to the driver (and then TSM) that it is at the EOT (end-of-tape) and therefore TSM is unabe to write to the tape. In the TSM actlog, all you get is ANR1401W indicating that volume failed to mount. This is an LTO II drive microcode problem which is fixed at microcode 37E1 level and above. The LTO Generation II drive firmware must be updated to 37E1 level or above. I am sure that others on the list will have an answer to your other issues J. Neal Certified Tivoli Administrator From: Zhu, David [EMAIL PROTECTED] Reply-To: ADSM: Dist Stor Manager [EMAIL PROTECTED] To: [EMAIL PROTECTED] Subject: Tape mount failures result in schedule failure Date: Fri, 13 Feb 2004 13:48:20 -0500 Hi, The environment is TSM/StorageAgent/Win2000 5.2.2, IBM 3584 LTO library. Activity log indicate that session 237 failed to mount a tape volume 293AGHL2 in drive mt3.0.0.3, showing repeated ANR8779E (Session: 237, Origin: SP02B_STA) Unable to open drive mt3.0.0.3, error number=2. (SESSION: 237) so after 5 minutes got ANR1401W (Session: 237, Origin: SP02B_STA) Mount request denied for volume 293AGHL2 - mount failed. (SESSION: 237) It then mounted the volume successfully in drive mt6.0.0.3. 3 minutes after that, session 255 started to mount 298AGHL2 in mt6.0.0.3, resulting in repeated ANR8779E (Session: 255, Origin: SP18A_STA) Unable to open drive mt6.0.0.3, error number=170. (SESSION: 255) It then mounted the volume successfully in drive mt5.0.0.3. Is this behavior normal for tape libraries? It is an indication of some problem with the drives? Where can I find the meaning of the error number 2 and 170? Both tape mounts were requests by scheduled backup and it seems to me as a result of the tape mount failures, the scheduled got a return code 12 and showed up as failed. Is this assessment correct? Thanks in advance to anyone who can shed some light on this. Regards, David Zhu TSM Support [EMAIL PROTECTED] Tel: 416-503-7853 _ Optimize your Internet experience to the max with the new MSN Premium Internet Software. http://click.atdmt.com/AVE/go/onm00200359ave/direct/01/
Re: Tape mount failures result in schedule failure
Hi Bab, Based on the machine type and model of the tape drive that you supplied, your drive is an LTO2 model. You will want to verify your firmware level and update it if needed. If your firmware is at the correct level, then you will want to check other factors such as bad tape, faulty drive, etc. I hope this helps. J. Neal From: bab [EMAIL PROTECTED] Reply-To: bab [EMAIL PROTECTED] To: [EMAIL PROTECTED] Subject: Re: Tape mount failures result in schedule failure Date: Fri, 13 Feb 2004 21:52:56 - Hi Neal, I am also getting same errors, my storage node is windows2000(TDP for SQL)backup is through LAN free,how to know frivesare gen1 or gen2? my microcode is: $ lscfg -vl rmt0 DEVICELOCATION DESCRIPTION rmt0 1D-08-01 IBM 3580 Ultrium Tape Drive (FCP) ManufacturerIBM Machine Type and Model..ULT3580-TD2 Serial Number...1110028439 Device Specific.(FW)38D0 httxds009[/home/vivekj]$ lscfg -vl smc0 DEVICELOCATION DESCRIPTION smc0 1D-08-01 IBM 3584 Library Medium Changer (FCP) ManufacturerIBM Machine Type and Model..03584L32 Serial Number...078144940401 Device Specific.(FW)3480 is it ok? error I am getting: 2/12/04 13:28:07 ANR8779E (Session: 704, Origin: STORAGESQL) Unable to open drive \\.\tape3, error number=170. 02/11/04 21:37:25 ANR1401W (Session: 434, Origin: STORAGESQL) Mount request denied for volume T7 - mount failed. On Sat, 14 Feb 2004 Jim Neal wrote : Hi David, With regard to the ANR1401 Error, when a TSM volume fills up on an LTO Generation II drive, the drive does not reset its EOT (end-of-tape) flag. Subsequently, when a scratch volume is being mounted in the same drive and TSM tries to write the BOT (beginning-of-tape) information, the drive returns to the driver (and then TSM) that it is at the EOT (end-of-tape) and therefore TSM is unabe to write to the tape. In the TSM actlog, all you get is ANR1401W indicating that volume failed to mount. This is an LTO II drive microcode problem which is fixed at microcode 37E1 level and above. The LTO Generation II drive firmware must be updated to 37E1 level or above. I am sure that others on the list will have an answer to your other issues J. Neal Certified Tivoli Administrator From: Zhu, David [EMAIL PROTECTED] Reply-To: ADSM: Dist Stor Manager [EMAIL PROTECTED] To: [EMAIL PROTECTED] Subject: Tape mount failures result in schedule failure Date: Fri, 13 Feb 2004 13:48:20 -0500 Hi, The environment is TSM/StorageAgent/Win2000 5.2.2, IBM 3584 LTO library. Activity log indicate that session 237 failed to mount a tape volume 293AGHL2 in drive mt3.0.0.3, showing repeated ANR8779E (Session: 237, Origin: SP02B_STA) Unable to open drive mt3.0.0.3, error number=2. (SESSION: 237) so after 5 minutes got ANR1401W (Session: 237, Origin: SP02B_STA) Mount request denied for volume 293AGHL2 - mount failed. (SESSION: 237) It then mounted the volume successfully in drive mt6.0.0.3. 3 minutes after that, session 255 started to mount 298AGHL2 in mt6.0.0.3, resulting in repeated ANR8779E (Session: 255, Origin: SP18A_STA) Unable to open drive mt6.0.0.3, error number=170. (SESSION: 255) It then mounted the volume successfully in drive mt5.0.0.3. Is this behavior normal for tape libraries? It is an indication of some problem with the drives? Where can I find the meaning of the error number 2 and 170? Both tape mounts were requests by scheduled backup and it seems to me as a result of the tape mount failures, the scheduled got a return code 12 and showed up as failed. Is this assessment correct? Thanks in advance to anyone who can shed some light on this. Regards, David Zhu TSM Support [EMAIL PROTECTED] Tel: 416-503-7853 _ Optimize your Internet experience to the max with the new MSN Premium Internet Software. http://click.atdmt.com/AVE/go/onm00200359ave/direct/01/ _ Get some great ideas here for your sweetheart on Valentine's Day - and beyond. http://special.msn.com/network/celebrateromance.armx
Re: mountlimit=drives
Hi Lawrence, This may sound basic, but have you checked to make sure that the other drives are online from a Tivoli perspective? If you issue the q drive command, tivoli will show you the drive statuses. J. Neal From: Lawrence Clark [EMAIL PROTECTED] Reply-To: ADSM: Dist Stor Manager [EMAIL PROTECTED] To: [EMAIL PROTECTED] Subject: mountlimit=drives Date: Fri, 13 Feb 2004 10:27:17 -0500 Hi: Sessions and processes seem to be sinlge threading using a single drive in a 4 drive library. the dev is set to mountlimit=drive. anyone know what else might cause this bottleneck? As shown below, library with 4 drives only shows a mount waiting on a volume when another is dismounting. tsm: BACKUPq mount ANR8379I Mount point in device class 3494BTAPE is waiting for the volume mount to complete, status: WAITING FOR VOLUME. ANR8331I 3590 volume 001038 is mounted R/W in drive 3590RMT4 (/dev/rmt4), status: DISMOUNTING. ANR8334I 2 matches found. Device Class Name: 3494BTAPE Device Access Strategy: Sequential Storage Pool Count: 7 Device Type: 3590 Format: DRIVE Est/Max Capacity (MB): 40,960.0 Mount Limit: DRIVES Mount Wait (min): 60 Mount Retention (min): 5 Label Prefix: ADSMVOL Library: IBM3494B Directory: Server Name: Retry Period: Retry Interval: Shared: Last Update by (administrator): ADMIN Last Update Date/Time: 02/12/04 11:34:44 _ Optimize your Internet experience to the max with the new MSN Premium Internet Software. http://click.atdmt.com/AVE/go/onm00200359ave/direct/01/
FW: TSM 5.1.7.0 Missing STK L700 Library
In reference to original post, we finally were able to redefine library and drives (addresses had all changed). Now we're getting these 'Changer Failure' errors. Has anyone seen these before? They are show-stoppers apparently, because we are dead in the water. 02/13/2004 04:01:25 ANR1002I Migration for storage pool DISKPOOL will be retried in 60 seconds. 02/13/2004 04:01:51 ANR8943E Hardware or media error on library L700LIB (OP=6C03, CC=304, KEY=04, ASC=40, ASCQ=02, SENSE=70.00.04.00.00.00.00.0C.00.00.00.00.40.02.00.00.00- .00.00.00., Description=Changer failure). Refer to Appendix D in the 'Messages' manual for recommended action. 02/13/2004 04:02:01 ANR8945W Scratch volume mount failed 000478. 02/13/2004 04:02:01 ANR8381E LTO volume 000478 could not be mounted in drive DRIVE3 (/dev/rmt12). 02/13/2004 04:02:01 ANR1404W Scratch volume mount request denied - mount failed. 02/13/2004 04:02:01 ANR1021W Migration process 37 terminated for storage pool DISKPOOL - storage media inaccessible. 02/13/2004 04:02:01 ANR0985I Process 37 for MIGRATION running in the BACKGROUND completed with completion state FAILURE at 04:02:01. Thanks! Kelli Jones Chesterfield County IST [EMAIL PROTECTED] -Original Message- From: Survoy, Bernard J [mailto:[EMAIL PROTECTED] Sent: February 13, 2004 9:21 AM To: Jones, Kelli Subject: RE: TSM 5.1.7.0 Missing STK L700 Library Kelli, It's been a while, how are you. Couple of things: I'm assuming AIX doesn't see the device at all??? 1. In AIX, define TSM devices, add a library, but you need to know the AIX adapter and SCSI address of the library, so see #2. 2. As far as the address of the library goes, that should be viewable from the Operators panel. 3. You now be able to define to AIX via SMIT, device special file name should be /dev/lb0 4. TSM PATH and LIBRARY definitions should be OK, worst case is you'll have to delete and redefine, but I wouldn't think you should have to. The library going MIA after code load, depends on is it MIA to AIX or MIA to TSM? I don't think the SCSI inquiry string would have changed (which is what the TSM device driver uses to determine what kind of library it is). Contact me if you want to discuss further. Thanks, Bernie Survoy Consulting Systems Engineer Phone: 216 615-9324 Cell: 330 321-3787 [EMAIL PROTECTED] StorageTek -Original Message- From: Jones, Kelli [mailto:[EMAIL PROTECTED] Sent: February 12, 2004 6:05 PM Subject: TSM 5.1.7.0 Missing STK L700 Library Need help on missing library... It was defined as a Tivoli Storage device in AIX 5 because it is an STK L700 library. Vendor loaded microcode..library is now MIA. Can't remember how to come up with Parent connector addresses. Running TSM 5.1.7.0...TSM Support guy didn't know AIX and could not help me Any help would be appreciated! Thanks, K. Jones Chesterfield VA
Re: Question on Restoration from DBSNAPSHOT
Milton, We recently introduced disaster recovery, and I pondered this for a while. The outcome is that we store the DBSNAPSHOT off site, as one can recover to a point in time. In our case VIA a SAN to another robot. We keep the full backup + any incremental within the local robot to avoid time delay. Prior to introducing DR, I remember one evening when we had to recover the database and it took two hours before we got the tape into the robot. One soon learns. Kind Regards Mike Wiggan, TCS/14 IT Infrastructure Integration Specialist Petroleum Devlopment Oman LLC ([EMAIL PROTECTED]) -Original Message- From: Johnson, Milton [IT] [mailto:[EMAIL PROTECTED] Sent: Thursday, February 12, 2004 20:06 To: [EMAIL PROTECTED] Subject: Question on Restoration from DBSNAPSHOT All, TSM: Storage Management Server for AIX-RS/6000 - Version 4, Release 2, Level 1.7 OS: AIX 4.3.3 ML 9 Log Mode: RollForward (Upgrade project planned in near future, but that's another story) Everyday I do a full backup of the database to 3590E tape, immediately followed by a DBSNAPSHOT to a file on disk. The 3590E tape promptly goes offsite. My question is if I experience a loss of the database can I then restore from the DBSNAPSHOT and recover to the point of failure using the RECOVERY LOG? I would like to avoid the time delay of returning the 3590E tape, containing the database backup, from the vault. Anyone done this? Thanks, H. Milton Johnson UNIX Systems Administrator - USCC San Antonio, TX Email: [EMAIL PROTECTED]
