Re: Copy a backup
On Wednesday 31 March 2004 09:22, Steve Harris wrote: Time to weigh in here. 1. DB2 backups are API backups. Generate backupset will not work. 2. DB2 backups are different to other backups. the db2adutl program is used to expire them. TSM holds indefinitely until db2adutl explicity deletes. It seems I'm confused too! :) I forgot that DB2 stores it's backups as *uniquely* named objects, not *consistently* named objects. Since each backup object is uniquely named, the retention policy needs to be set to keep one copy of each object forever, and to immediately expire the data when it is eventually deleted. So the DB2 Management Class should look like this: Backup copy group: VE = 1, VD = 0, RE = 0, RO = 0; Archive copy group: RD = NoLimit; The DB2 admin (or a script) then uses the db2adutl command to tell TSM which backups and logs are no longer required (ie. it tells TSM they were deleted, and then TSM policy expires the object). This is described in the Redbook Backing up DB2 using Tivoli Storage Manager sg246247, section 7.4 in particular. I guess I was thinking of some horrible mix of DB2 and Domino. Sorry for the disinformation. :) Regards, Steven P. So what is necessary is to examine your DB2 processes and the way that db2adutl is run. If you are scripting it to do the deletions (there is a delete after so many days parameter) then you will need to revisit that for your Friday exceptions. That said, if you want to keep another copy of your DB2 backup, without taking another backup, then you can retrieve the Db2 backup from TSM to a disk file, again using arguments to db2adutl, and then you can back that up to TSM again by the usual backup or archive mechanism. Now there is a DB2 control file that holds details of backups. whether you will be able to restore 12 months hence and need to also keep a copy of the control information is a question for your DB2 DBA. Regards Steve Harris AIX and TSM Admin Queensland Health, Brisbane Australia -- Steven Pemberton Senior Enterprise Management Consultant IBK, Senetas Group Mobile: +61/0 418 335 136 | Phone: +61/3 9820 5811 | Fax: +61/3 9820 9907 Level 1, 11 Queens Road, Melbourne, Victoria, 3004, Australia http://www.senetas.com.au | http://www.ibk.com.au | http://www.datum.com.au
Re: Copy a backup
Noone said anything about wanting to be able to restore. The stated requirement was to satisfy the auditors by making a copy of the backup. [EMAIL PROTECTED] 3/30/2004 1:16:05 PM DB2 will not be able to restore this data from a BACKUPSET. You will probably have to backup the DB2 database(s) again under a different nodename that is bound to a different management class pointing to this storage pool. Bill Boyer DSS, Inc. -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] Behalf Of David E Ehresman Sent: Tuesday, March 30, 2004 1:00 PM To: [EMAIL PROTECTED] Subject: Re: Copy a backup GENERATE BACKUPSET [EMAIL PROTECTED] 3/29/2004 7:06:15 AM Good Day TSMers, Please HELP..we do db2 backups to TSM on a daily basis. What I would like to do to satify our auditors is make a copy of the backup taken on Friday nights to a storage pool that I've called weekly. I do not want to move the data, but make a copy of that backup set taken as at the friday night. How can I go about doing thisAny Ideas ?? Your assistance will be greatly appreciated. Lindy Crawford Information Technology Nedbank Corporate - Property and Asset Finance Tel : 031 - 3642185 Fax : 031 - 3642946 Cell: 083 632 5982 Email : [EMAIL PROTECTED] mailto:[EMAIL PROTECTED]
Gen1 to Gen2 Upgrade/coexist
Am using an LTO 3583 with 2 scsi Gen1 drives and GEN1 cartridges. Planning to upgrade to 4 fiber Gen2 drives in the 3583. The SCSI drives will be removed. The current data exists on over 150 gen1 cartridges and hence do not plan to move to gen2 cartridges immediately. The setup is directly attached to the pSeries servers running AIX 5.1 and TSM Server Got some queries 1. Will Gen2 drives be able to read and write(new as well as append to existing tapes) on the existing gen1 cartridges without problem? 2. What speed will I get out of the new setup? Gen2 speed or Gen1 speed? 3. If I coexist the new gen2 drives with the existing gen1 drives where can I get stuck? Anyone experienced in this kind of a scenario? Anoop
Tsm client sending more than network bandwidth. What's up?
Tsm server v5.1.6.2 on solaris 2.8 Client 3.1.7 on solaris 2.6 Attached through a 100mb ethernet interface. It appears that tsm is getting 104 mb network throughput. The admin for the client machine (who is also our main tcp/pi routing guy) asks how this is possible? Note that compression is not a factor here. Extract from dsmsched.log follows: dsmsched.log --- 03/29/04 17:05:52 Total number of objects inspected: 120,782 03/29/04 17:05:52 Total number of objects backed up:1,363 . . . 03/29/04 17:05:52 Total number of bytes transferred: 989.99 MB 03/29/04 17:05:52 Data transfer time: 77.42 sec 03/29/04 17:05:52 Network data transfer rate:13,093.72 KB/sec 03/29/04 17:05:52 Aggregate data transfer rate: 2,938.10 KB/sec 03/29/04 17:05:52 Objects compressed by:0% Gary Lee Senior Operating Systems Analyst Ball State University phone 765-285-1310
Re: Gen1 to Gen2 Upgrade/coexist
Hi. 1.Gen 2 will be able to write on the Gen1 Cartridges (I done it with LTO 3582 ) 2.according to IBM spec sheets Gen1 is 15-30 MB/s, but with LTO2 Drives its 20-40 MB/s writing on LTO2 cartridges. 3.I not sure if LTO1 drive can write on LTO2 cartridge, but if it can, u can change the format to drive instead of LTO in the Device Class. I hope it answer your questions. Original Message- From: Anoop Das [mailto:[EMAIL PROTECTED] Sent: Wednesday, March 31, 2004 3:40 PM To: [EMAIL PROTECTED] Subject: Gen1 to Gen2 Upgrade/coexist Am using an LTO 3583 with 2 scsi Gen1 drives and GEN1 cartridges. Planning to upgrade to 4 fiber Gen2 drives in the 3583. The SCSI drives will be removed. The current data exists on over 150 gen1 cartridges and hence do not plan to move to gen2 cartridges immediately. The setup is directly attached to the pSeries servers running AIX 5.1 and TSM Server Got some queries 1. Will Gen2 drives be able to read and write(new as well as append to existing tapes) on the existing gen1 cartridges without problem? 2. What speed will I get out of the new setup? Gen2 speed or Gen1 speed? 3. If I coexist the new gen2 drives with the existing gen1 drives where can I get stuck? Anyone experienced in this kind of a scenario? Anoop
Re: Gen1 to Gen2 Upgrade/coexist
... 1. Will Gen2 drives be able to read and write(new as well as append to existing tapes) on the existing gen1 cartridges without problem? ... Bookmark www.lto.org . In http://www.lto.org/newsite/html/about_faqs.html see Q9: What are the backward compatibility characteristics of the Ultrium format Generation 2? Richard Simshttp://people.bu.edu/rbs
Re: Tsm client sending more than network bandwidth. What's up?
... It appears that tsm is getting 104 mb network throughput. The admin for the client machine (who is also our main tcp/pi routing guy) asks how this is possible? ... Your network guy should know this, but... Applications do not perform network data transfer: the network component of the operating system does. The application (in this case, TSM) knows only the rate at which it has been able to hand over data to be sent out. It is beyond its purview to know that the data has actually gone out. With very large data transfers, the rate seen by the application can approximate reality, but with smaller samples, the stats can be more skewed. Your TSM transaction size is also a factor here, in handshaking. See also Network data transfer rate in http://people.bu.edu/rbs/ADSM.QuickFacts where I have notes about the effect. Richard Sims
Re: Gen1 to Gen2 Upgrade/coexist
see below. Cordiali saluti Gianluca Mariani Tivoli TSM Global Response Team, Roma Via Sciangai 53, Roma phones : +39(0)659664598 +393351270554 (mobile) [EMAIL PROTECTED] The Hitch Hiker's Guide to the Galaxy says of the Sirius Cybernetics Corporation product that it is very easy to be blinded to the essential uselessness of them by the sense of achievement you get from getting them to work at all. In other words and this is the rock solid principle on which the whole of the Corporation's Galaxy-wide success is founded -their fundamental design flaws are completely hidden by their superficial design flaws... Anoop Das [EMAIL PROTECTED] Sent by: ADSM: Dist Stor Manager [EMAIL PROTECTED] 31/03/2004 15.40 Please respond to ADSM: Dist Stor Manager To [EMAIL PROTECTED] cc Subject Gen1 to Gen2 Upgrade/coexist Am using an LTO 3583 with 2 scsi Gen1 drives and GEN1 cartridges. Planning to upgrade to 4 fiber Gen2 drives in the 3583. The SCSI drives will be removed. The current data exists on over 150 gen1 cartridges and hence do not plan to move to gen2 cartridges immediately. The setup is directly attached to the pSeries servers running AIX 5.1 and TSM Server Got some queries 1. Will Gen2 drives be able to read and write(new as well as append to existing tapes) on the existing gen1 cartridges without problem? yes 2. What speed will I get out of the new setup? Gen2 speed or Gen1 speed? using LTO1 tapes on LTO2 drives you'll get speeds inbetween the two.you will have to test for your specific environment. 3. If I coexist the new gen2 drives with the existing gen1 drives where can I get stuck? you have to get the feature upgrade for the 3583.it needs to be partitioned in separate libraries for LTO1 and 2 drives.then you have to assign the storage columns to the separate libraries.LTO1 drives cannot write LTO2 media.TSM will see two medium changers(libraries). Anyone experienced in this kind of a scenario? Anoop
Re: Gen1 to Gen2 Upgrade/coexist
Please send the url we cant see nothing -Original Message- From: Gianluca Mariani1 [mailto:[EMAIL PROTECTED] Sent: Wednesday, March 31, 2004 4:26 PM To: [EMAIL PROTECTED] Subject: Re: Gen1 to Gen2 Upgrade/coexist see below. Cordiali saluti Gianluca Mariani Tivoli TSM Global Response Team, Roma Via Sciangai 53, Roma phones : +39(0)659664598 +393351270554 (mobile) [EMAIL PROTECTED] The Hitch Hiker's Guide to the Galaxy says of the Sirius Cybernetics Corporation product that it is very easy to be blinded to the essential uselessness of them by the sense of achievement you get from getting them to work at all. In other words and this is the rock solid principle on which the whole of the Corporation's Galaxy-wide success is founded -their fundamental design flaws are completely hidden by their superficial design flaws... Anoop Das [EMAIL PROTECTED] Sent by: ADSM: Dist Stor Manager [EMAIL PROTECTED] 31/03/2004 15.40 Please respond to ADSM: Dist Stor Manager To [EMAIL PROTECTED] cc Subject Gen1 to Gen2 Upgrade/coexist Am using an LTO 3583 with 2 scsi Gen1 drives and GEN1 cartridges. Planning to upgrade to 4 fiber Gen2 drives in the 3583. The SCSI drives will be removed. The current data exists on over 150 gen1 cartridges and hence do not plan to move to gen2 cartridges immediately. The setup is directly attached to the pSeries servers running AIX 5.1 and TSM Server Got some queries 1. Will Gen2 drives be able to read and write(new as well as append to existing tapes) on the existing gen1 cartridges without problem? yes 2. What speed will I get out of the new setup? Gen2 speed or Gen1 speed? using LTO1 tapes on LTO2 drives you'll get speeds inbetween the two.you will have to test for your specific environment. 3. If I coexist the new gen2 drives with the existing gen1 drives where can I get stuck? you have to get the feature upgrade for the 3583.it needs to be partitioned in separate libraries for LTO1 and 2 drives.then you have to assign the storage columns to the separate libraries.LTO1 drives cannot write LTO2 media.TSM will see two medium changers(libraries). Anyone experienced in this kind of a scenario? Anoop
Re: Gen1 to Gen2 Upgrade/coexist
no url. I just added the answers after the questions. see if they are more visible now: 1. Will Gen2 drives be able to read and write(new as well as append to existing tapes) on the existing gen1 cartridges without problem? yes 2. What speed will I get out of the new setup? Gen2 speed or Gen1 speed? using LTO1 tapes on LTO2 drives you'll get speeds inbetween the two.you will have to test for your specific environment. 3. If I coexist the new gen2 drives with the existing gen1 drives where can I get stuck? you have to get the feature upgrade for the 3583.it needs to be partitioned in separate libraries for LTO1 and 2 drives.then you have to assign the storage columns to the separate libraries.LTO1 drives cannot write LTO2 media.TSM will see two medium changers(libraries). Cordiali saluti Gianluca Mariani Tivoli TSM Global Response Team, Roma Via Sciangai 53, Roma phones : +39(0)659664598 +393351270554 (mobile) [EMAIL PROTECTED] The Hitch Hiker's Guide to the Galaxy says of the Sirius Cybernetics Corporation product that it is very easy to be blinded to the essential uselessness of them by the sense of achievement you get from getting them to work at all. In other words and this is the rock solid principle on which the whole of the Corporation's Galaxy-wide success is founded -their fundamental design flaws are completely hidden by their superficial design flaws... Amos Hagay [EMAIL PROTECTED] Sent by: ADSM: Dist Stor Manager [EMAIL PROTECTED] 31/03/2004 16.40 Please respond to ADSM: Dist Stor Manager [EMAIL PROTECTED] To [EMAIL PROTECTED] cc Subject Re: Gen1 to Gen2 Upgrade/coexist Please send the url we cant see nothing -Original Message- From: Gianluca Mariani1 [mailto:[EMAIL PROTECTED] Sent: Wednesday, March 31, 2004 4:26 PM To: [EMAIL PROTECTED] Subject: Re: Gen1 to Gen2 Upgrade/coexist see below. Cordiali saluti Gianluca Mariani Tivoli TSM Global Response Team, Roma Via Sciangai 53, Roma phones : +39(0)659664598 +393351270554 (mobile) [EMAIL PROTECTED] The Hitch Hiker's Guide to the Galaxy says of the Sirius Cybernetics Corporation product that it is very easy to be blinded to the essential uselessness of them by the sense of achievement you get from getting them to work at all. In other words and this is the rock solid principle on which the whole of the Corporation's Galaxy-wide success is founded -their fundamental design flaws are completely hidden by their superficial design flaws... Anoop Das [EMAIL PROTECTED] Sent by: ADSM: Dist Stor Manager [EMAIL PROTECTED] 31/03/2004 15.40 Please respond to ADSM: Dist Stor Manager To [EMAIL PROTECTED] cc Subject Gen1 to Gen2 Upgrade/coexist Am using an LTO 3583 with 2 scsi Gen1 drives and GEN1 cartridges. Planning to upgrade to 4 fiber Gen2 drives in the 3583. The SCSI drives will be removed. The current data exists on over 150 gen1 cartridges and hence do not plan to move to gen2 cartridges immediately. The setup is directly attached to the pSeries servers running AIX 5.1 and TSM Server Got some queries 1. Will Gen2 drives be able to read and write(new as well as append to existing tapes) on the existing gen1 cartridges without problem? yes 2. What speed will I get out of the new setup? Gen2 speed or Gen1 speed? using LTO1 tapes on LTO2 drives you'll get speeds inbetween the two.you will have to test for your specific environment. 3. If I coexist the new gen2 drives with the existing gen1 drives where can I get stuck? you have to get the feature upgrade for the 3583.it needs to be partitioned in separate libraries for LTO1 and 2 drives.then you have to assign the storage columns to the separate libraries.LTO1 drives cannot write LTO2 media.TSM will see two medium changers(libraries). Anyone experienced in this kind of a scenario? Anoop
Spam: LTO2 Qusetion ?
Hi all. I would like to know if there is any difference between IBM LTO2 Cartridges to HP LTO2 Cartridges ? Because with the price there is difference . AH
LTO2 Question
Hi all. I would like to know if there is any difference between IBM LTO2 Cartridges to HP LTO2 Cartridges. Because with the price there is difference. AH
LTO
Hi all. I would like to know if there is any difference between IBM LTO2 Cartridges to HP LTO2 Cartridges. Because with the price there is a difference. AH
Library sharing
Trying to get ATL library sharing working between two TSM AIX servers. I think I finally got the definitions correct..at least they seem to function. However, I can't get the library client (capella) to use the drives. Every time it does, I get these errors in the activity log: 03/31/2004 09:54:13 ANR8779E Unable to open drive /dev/rmt1, error number=46. (SESSION: 2663, PROCESS: 11) The library manager says the tape is mounted and ready. 03/31/2004 09:52:25 ANR8337I 3590 volume 070330 mounted in drive ATL-DRIVE2 (/dev/rmt1). 03/31/2004 09:52:25 ANR9791I Volume 070330 in library 3494ATL ownership is changing from TSM-AGENA to TSM-CAPELLA. Any suggestions on what might be wrong ? AIX messages says the -46 is Drive Not Ready. These are FC / SAN attached 3590E1A drives.
Re: Library sharing
Hi, From my experience with 3584 Library, the rmt devices should be The same on both machines e.g. server_1 /dev/rmt1 /dev/rmt2 etc... And also on the library client /dev/rmt1 ... AH -Original Message- From: Zoltan Forray/AC/VCU [mailto:[EMAIL PROTECTED] Sent: Wednesday, March 31, 2004 5:46 PM To: [EMAIL PROTECTED] Subject: Library sharing Trying to get ATL library sharing working between two TSM AIX servers. I think I finally got the definitions correct..at least they seem to function. However, I can't get the library client (capella) to use the drives. Every time it does, I get these errors in the activity log: 03/31/2004 09:54:13 ANR8779E Unable to open drive /dev/rmt1, error number=46. (SESSION: 2663, PROCESS: 11) The library manager says the tape is mounted and ready. 03/31/2004 09:52:25 ANR8337I 3590 volume 070330 mounted in drive ATL-DRIVE2 (/dev/rmt1). 03/31/2004 09:52:25 ANR9791I Volume 070330 in library 3494ATL ownership is changing from TSM-AGENA to TSM-CAPELLA. Any suggestions on what might be wrong ? AIX messages says the -46 is Drive Not Ready. These are FC / SAN attached 3590E1A drives.
Re: Library sharing
Hi, Can be, but don't have to be the same... In the past I saw some machines with different device names for the same devices and it worked well with ITSM (on Windows). Regards, Karel -Oorspronkelijk bericht- Van: Amos Hagay [mailto:[EMAIL PROTECTED] Verzonden: woensdag 31 maart 2004 17:46 Aan: [EMAIL PROTECTED] Onderwerp: Re: Library sharing Hi, From my experience with 3584 Library, the rmt devices should be The same on both machines e.g. server_1 /dev/rmt1 /dev/rmt2 etc... And also on the library client /dev/rmt1 ... AH -Original Message- From: Zoltan Forray/AC/VCU [mailto:[EMAIL PROTECTED] Sent: Wednesday, March 31, 2004 5:46 PM To: [EMAIL PROTECTED] Subject: Library sharing Trying to get ATL library sharing working between two TSM AIX servers. I think I finally got the definitions correct..at least they seem to function. However, I can't get the library client (capella) to use the drives. Every time it does, I get these errors in the activity log: 03/31/2004 09:54:13 ANR8779E Unable to open drive /dev/rmt1, error number=46. (SESSION: 2663, PROCESS: 11) The library manager says the tape is mounted and ready. 03/31/2004 09:52:25 ANR8337I 3590 volume 070330 mounted in drive ATL-DRIVE2 (/dev/rmt1). 03/31/2004 09:52:25 ANR9791I Volume 070330 in library 3494ATL ownership is changing from TSM-AGENA to TSM-CAPELLA. Any suggestions on what might be wrong ? AIX messages says the -46 is Drive Not Ready. These are FC / SAN attached 3590E1A drives.
Re: LTO2 Question
We've tested both and didn't see a significant difference in performance. We had the IBM drives in a 3584 and the HP drives in a L700, both fiber drives. The tests were against the same servers, the same data. MK -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Amos Hagay Sent: Wednesday, March 31, 2004 9:32 AM To: [EMAIL PROTECTED] Subject: LTO2 Question Hi all. I would like to know if there is any difference between IBM LTO2 Cartridges to HP LTO2 Cartridges. Because with the price there is difference. AH
Re: Library sharing
When you define the PATHs on the TSM server for the storage agent on the client node, the device= is the name of the tape drive on the client, not on the server. You need to match the drive name on the TSM server to the correct device name on the client node, then use that in the DEFINE PATH. So on your TSM server: If library 3584 drive LTO1 points to the /dev/rmt1 device and on the storage agent client SA1 that same physical drive is the /dev/rmt3 device you would use: define path SA1 LTO1 srctype=server desttype=drive library=3584 device=/dev/rmt3 Bill Boyer DSS, Inc. -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] Behalf Of Karel Bos Sent: Wednesday, March 31, 2004 10:54 AM To: [EMAIL PROTECTED] Subject: Re: Library sharing Hi, Can be, but don't have to be the same... In the past I saw some machines with different device names for the same devices and it worked well with ITSM (on Windows). Regards, Karel -Oorspronkelijk bericht- Van: Amos Hagay [mailto:[EMAIL PROTECTED] Verzonden: woensdag 31 maart 2004 17:46 Aan: [EMAIL PROTECTED] Onderwerp: Re: Library sharing Hi, From my experience with 3584 Library, the rmt devices should be The same on both machines e.g. server_1 /dev/rmt1 /dev/rmt2 etc... And also on the library client /dev/rmt1 ... AH -Original Message- From: Zoltan Forray/AC/VCU [mailto:[EMAIL PROTECTED] Sent: Wednesday, March 31, 2004 5:46 PM To: [EMAIL PROTECTED] Subject: Library sharing Trying to get ATL library sharing working between two TSM AIX servers. I think I finally got the definitions correct..at least they seem to function. However, I can't get the library client (capella) to use the drives. Every time it does, I get these errors in the activity log: 03/31/2004 09:54:13 ANR8779E Unable to open drive /dev/rmt1, error number=46. (SESSION: 2663, PROCESS: 11) The library manager says the tape is mounted and ready. 03/31/2004 09:52:25 ANR8337I 3590 volume 070330 mounted in drive ATL-DRIVE2 (/dev/rmt1). 03/31/2004 09:52:25 ANR9791I Volume 070330 in library 3494ATL ownership is changing from TSM-AGENA to TSM-CAPELLA. Any suggestions on what might be wrong ? AIX messages says the -46 is Drive Not Ready. These are FC / SAN attached 3590E1A drives.
Re: Library sharing
Well, in this case, it isn't, sortof... I don't have *ANY* path statements on the client, that refer to these drives. All that is defined on the client is the SHARED LIBRARY. This is another TSM server, not just a storage agent. The path statements on the library manager are duplicated for the client, pointing to the client as the SOURCE serverand yes, both sets of definitions point to the same /dev/rmtx. I am beginning to wonder if it has to do with the different levels of ATAPE. The client is much newer (8.4.1.0) while the library manager is 8.3.x. ADSM: Dist Stor Manager [EMAIL PROTECTED] wrote on 03/31/2004 11:07:04 AM: When you define the PATHs on the TSM server for the storage agent on the client node, the device= is the name of the tape drive on the client, not on the server. You need to match the drive name on the TSM server to the correct device name on the client node, then use that in the DEFINE PATH. So on your TSM server: If library 3584 drive LTO1 points to the /dev/rmt1 device and on the storage agent client SA1 that same physical drive is the /dev/rmt3 device you would use: define path SA1 LTO1 srctype=server desttype=drive library=3584 device=/dev/rmt3 Bill Boyer DSS, Inc. -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] Behalf Of Karel Bos Sent: Wednesday, March 31, 2004 10:54 AM To: [EMAIL PROTECTED] Subject: Re: Library sharing Hi, Can be, but don't have to be the same... In the past I saw some machines with different device names for the same devices and it worked well with ITSM (on Windows). Regards, Karel -Oorspronkelijk bericht- Van: Amos Hagay [mailto:[EMAIL PROTECTED] Verzonden: woensdag 31 maart 2004 17:46 Aan: [EMAIL PROTECTED] Onderwerp: Re: Library sharing Hi, From my experience with 3584 Library, the rmt devices should be The same on both machines e.g. server_1 /dev/rmt1 /dev/rmt2 etc... And also on the library client /dev/rmt1 ... AH -Original Message- From: Zoltan Forray/AC/VCU [mailto:[EMAIL PROTECTED] Sent: Wednesday, March 31, 2004 5:46 PM To: [EMAIL PROTECTED] Subject: Library sharing Trying to get ATL library sharing working between two TSM AIX servers. I think I finally got the definitions correct..at least they seem to function. However, I can't get the library client (capella) to use the drives. Every time it does, I get these errors in the activity log: 03/31/2004 09:54:13 ANR8779E Unable to open drive /dev/rmt1, error number=46. (SESSION: 2663, PROCESS: 11) The library manager says the tape is mounted and ready. 03/31/2004 09:52:25 ANR8337I 3590 volume 070330 mounted in drive ATL-DRIVE2 (/dev/rmt1). 03/31/2004 09:52:25 ANR9791I Volume 070330 in library 3494ATL ownership is changing from TSM-AGENA to TSM-CAPELLA. Any suggestions on what might be wrong ? AIX messages says the -46 is Drive Not Ready. These are FC / SAN attached 3590E1A drives.
Re: Library sharing
make sure that /dev/rmt1 on source server is the same drive as /dev/rmt1 on the client server We discovered that they didn't always come in the same. It sound like the server to server communications is working fine. Becky -Original Message- From: Zoltan Forray/AC/VCU [mailto:[EMAIL PROTECTED] Sent: Wednesday, March 31, 2004 10:27 AM To: [EMAIL PROTECTED] Subject: Re: Library sharing Well, in this case, it isn't, sortof... I don't have *ANY* path statements on the client, that refer to these drives. All that is defined on the client is the SHARED LIBRARY. This is another TSM server, not just a storage agent. The path statements on the library manager are duplicated for the client, pointing to the client as the SOURCE serverand yes, both sets of definitions point to the same /dev/rmtx. I am beginning to wonder if it has to do with the different levels of ATAPE. The client is much newer (8.4.1.0) while the library manager is 8.3.x. ADSM: Dist Stor Manager [EMAIL PROTECTED] wrote on 03/31/2004 11:07:04 AM: When you define the PATHs on the TSM server for the storage agent on the client node, the device= is the name of the tape drive on the client, not on the server. You need to match the drive name on the TSM server to the correct device name on the client node, then use that in the DEFINE PATH. So on your TSM server: If library 3584 drive LTO1 points to the /dev/rmt1 device and on the storage agent client SA1 that same physical drive is the /dev/rmt3 device you would use: define path SA1 LTO1 srctype=server desttype=drive library=3584 device=/dev/rmt3 Bill Boyer DSS, Inc. -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] Behalf Of Karel Bos Sent: Wednesday, March 31, 2004 10:54 AM To: [EMAIL PROTECTED] Subject: Re: Library sharing Hi, Can be, but don't have to be the same... In the past I saw some machines with different device names for the same devices and it worked well with ITSM (on Windows). Regards, Karel -Oorspronkelijk bericht- Van: Amos Hagay [mailto:[EMAIL PROTECTED] Verzonden: woensdag 31 maart 2004 17:46 Aan: [EMAIL PROTECTED] Onderwerp: Re: Library sharing Hi, From my experience with 3584 Library, the rmt devices should be The same on both machines e.g. server_1 /dev/rmt1 /dev/rmt2 etc... And also on the library client /dev/rmt1 ... AH -Original Message- From: Zoltan Forray/AC/VCU [mailto:[EMAIL PROTECTED] Sent: Wednesday, March 31, 2004 5:46 PM To: [EMAIL PROTECTED] Subject: Library sharing Trying to get ATL library sharing working between two TSM AIX servers. I think I finally got the definitions correct..at least they seem to function. However, I can't get the library client (capella) to use the drives. Every time it does, I get these errors in the activity log: 03/31/2004 09:54:13 ANR8779E Unable to open drive /dev/rmt1, error number=46. (SESSION: 2663, PROCESS: 11) The library manager says the tape is mounted and ready. 03/31/2004 09:52:25 ANR8337I 3590 volume 070330 mounted in drive ATL-DRIVE2 (/dev/rmt1). 03/31/2004 09:52:25 ANR9791I Volume 070330 in library 3494ATL ownership is changing from TSM-AGENA to TSM-CAPELLA. Any suggestions on what might be wrong ? AIX messages says the -46 is Drive Not Ready. These are FC / SAN attached 3590E1A drives.
?Linux TSM service to backup 100 clients to disk-tape?
Hi Linux TSM Sys.Admins! None of you responded to my previous query, so I'm trying again. We are considering to use RedHat EL 3.0 on IA32/64 platform (rather than AIX on p-series) to host an additional I/O intensive TSM service (to split our current service and handle half of future growth.) We are hoping to build based upon others' experiences. Are you already using or actively planning to use Linux (RedHat EL 3?) to host an I/O intensive TSM service similar to any described under the recent ADSM-L thread, Sizing an AIX platform and tape libraries? If not, do you have a Linux TSM service backing up 100 clients to disk - tape storage? Please describe what you have and what limits you think might apply to your set up (or reply w/ a phone# if you would rather just talk.) Thanks for any advice you care to share! -- [EMAIL PROTECTED] (203.432.6693) = = = from my previous posting= = = We believe we are approaching the maximum that can be achieved w/ TSM:v5.2.1.3 OS: AIX 5.1 (64bit) CPU:IBM 7025-6F1 w/ 4 * 750Mhz proc's + 3GB RAM SAN:1 Gb w/ EMC Symmetrix 8830 LAN:1 Gb Ethernet ATL:IBM 3494 w/ 6 * 3590E drives IBM 3584 w/ 4 * 3580 LTO1 + 2 * 3580 LTO2 drives This configuration is successfully supporting our current ITS TSM service (see details below), but we believe we either need a major performance boost or to split this load onto an additional host platform: Linux, Win*, or must we remain w/ AIX for I/O performance? to handle expected additional growth. Which platform have you chosen (or would you choose) for similar TSM service? Yale ITS TSM Service: Active Clients: 2400 = 3d, 2500 = 7d, 2700 = 35days Servers:151 WinNT,2K* 105 Linux 20 Solaris 9 AIX 7 SQL-BT (Oracle) 3 Mac 2 TDP's: MSSQL,MSexchg: 2 + 1 [new]2 Personals: 2549 WinNT,2K*,XP 2230 Win98,ME26 Mac183 Linux 50 Solaris 5 AIX,DEC*X,HPUX,IRIX: 1 ea. [new] 51 Expected growth: +500-600 clients for several years +20% data for existing clients/year? TSM DB: 75.7% of 160GB BAckup DB w/ LTO1 HCmpr. takes 2.3h EXPIre Inv examines ~6M obj, deletes ~1M obj. in 8-9h Disk STGpools: 600 + 180GB Nightly Backup Period: 15:30-08:00+ Weeknight Backup Load: 500-650GB+ Thanks for any experience/insight you are willing to share with us! -- [EMAIL PROTECTED] (203.432.6693)
Sanity check for DB/2 backup options?
I've been investigating what options we have for fun tricks to play with our DB/2 backups to TSM. The major obstacle to many of our desires seems to be that the environment and options files are set at the time that the instance -starts-. Thus, (for instance) it's not possible to point your running instance at a new node definition, cut a backup which you would like to treat differently, and then put it back. We think that the only options we have for doing this involve dropping stuff onto DASD, or restarting the instance several times. Does that sound right to those others of you who are doing DB/2? - Allen S. Rout
Re: Library sharing
Then substitute storage agent client for library client. You define the paths on the library manager server. The PATHS reference the library client servername, the library name (which I believe must be the same name) and the drive names as defined on the library manager server. You then use the DEVICE= to point to the /dev/rmtx device on the library client server that matches the same device on the library manager server. Let's say on the TSM library manager server: Library:3584 Drive: LTO1/dev/rmt1 Drive: LTO2/dev/rmt2 Your library client server name is LIBCLIENT (or whatever) and you have the following drives: /dev/rmt3 Which is the same device as /dev/rmt1 on the library manager server /dev/rmt4 Which is the same device as /dev/rmt2 on the library manager server If these are fibre, you'll have to get the WWN names (lsattr -El rmtx) on both/all server and create a matrix that shows which is which on each server. Then on the library manager server: define path libclient lto1 srctype=server desttype=drive library=3584 device=/dev/rmt3 define path libclient lto2 srctype=server desttype=drive library=3584 device=/dev/rmt4 Clear as mud, right? -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] Behalf Of Zoltan Forray/AC/VCU Sent: Wednesday, March 31, 2004 11:27 AM To: [EMAIL PROTECTED] Subject: Re: Library sharing Well, in this case, it isn't, sortof... I don't have *ANY* path statements on the client, that refer to these drives. All that is defined on the client is the SHARED LIBRARY. This is another TSM server, not just a storage agent. The path statements on the library manager are duplicated for the client, pointing to the client as the SOURCE serverand yes, both sets of definitions point to the same /dev/rmtx. I am beginning to wonder if it has to do with the different levels of ATAPE. The client is much newer (8.4.1.0) while the library manager is 8.3.x. ADSM: Dist Stor Manager [EMAIL PROTECTED] wrote on 03/31/2004 11:07:04 AM: When you define the PATHs on the TSM server for the storage agent on the client node, the device= is the name of the tape drive on the client, not on the server. You need to match the drive name on the TSM server to the correct device name on the client node, then use that in the DEFINE PATH. So on your TSM server: If library 3584 drive LTO1 points to the /dev/rmt1 device and on the storage agent client SA1 that same physical drive is the /dev/rmt3 device you would use: define path SA1 LTO1 srctype=server desttype=drive library=3584 device=/dev/rmt3 Bill Boyer DSS, Inc. -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] Behalf Of Karel Bos Sent: Wednesday, March 31, 2004 10:54 AM To: [EMAIL PROTECTED] Subject: Re: Library sharing Hi, Can be, but don't have to be the same... In the past I saw some machines with different device names for the same devices and it worked well with ITSM (on Windows). Regards, Karel -Oorspronkelijk bericht- Van: Amos Hagay [mailto:[EMAIL PROTECTED] Verzonden: woensdag 31 maart 2004 17:46 Aan: [EMAIL PROTECTED] Onderwerp: Re: Library sharing Hi, From my experience with 3584 Library, the rmt devices should be The same on both machines e.g. server_1 /dev/rmt1 /dev/rmt2 etc... And also on the library client /dev/rmt1 ... AH -Original Message- From: Zoltan Forray/AC/VCU [mailto:[EMAIL PROTECTED] Sent: Wednesday, March 31, 2004 5:46 PM To: [EMAIL PROTECTED] Subject: Library sharing Trying to get ATL library sharing working between two TSM AIX servers. I think I finally got the definitions correct..at least they seem to function. However, I can't get the library client (capella) to use the drives. Every time it does, I get these errors in the activity log: 03/31/2004 09:54:13 ANR8779E Unable to open drive /dev/rmt1, error number=46. (SESSION: 2663, PROCESS: 11) The library manager says the tape is mounted and ready. 03/31/2004 09:52:25 ANR8337I 3590 volume 070330 mounted in drive ATL-DRIVE2 (/dev/rmt1). 03/31/2004 09:52:25 ANR9791I Volume 070330 in library 3494ATL ownership is changing from TSM-AGENA to TSM-CAPELLA. Any suggestions on what might be wrong ? AIX messages says the -46 is Drive Not Ready. These are FC / SAN attached 3590E1A drives.
Trying to collect backup history of clients
hi, We have TSM 5.1.6.2 on Solaris 2.8. I am trying to collect the backup history attempts for my clients. I have my activity log stored for 14 days. Most of my backups are scheduled but some are scripted from the client side. also we have randomization enabled. What would be the most appropriate way to collect data on backups attempted/succeeded. thanks, Bala Krishnamurthy [EMAIL PROTECTED]
Re: Month End Strategies (TDP for Exchange)
Thanks for all the responses. Yeah this is exactly what I was thinking about doing. There is something that I'm not clear on though. I can set up a separate storage pool and management class that would retain the monthly backup's of exchange for X number of years. I have to send these tapes offsite and do not want to keep a copy onsite unless there is a way to expire the onsite copy after 30 days. Is this at all possible? I suppose I could just send all the tapes used in the month end storage pool offsite along with the DRMEDIA. I'm not sure what it will be like tracking the tapes though. Is this a viable solution or am I missing something? *** Wayne Prasek I.T. Support Analyst (Server) 204-985-1694 [EMAIL PROTECTED] *** -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Coats, Jack Sent: March 30, 2004 2:44 PM To: [EMAIL PROTECTED] Subject: Re: Month End Strategies (TDP for Exchange) I have been thinking over this option for someone else. One option is to set up a separate tape pool (with copy pool if you want two copies), and set up a management class for it that expires data after x years. Only do a monthly backup of Exchange to this pool. And make the copypool version if that is in our requiremets. Just a thought. ... Let us know what you figure out! -Original Message- From: Wayne Prasek [SMTP:[EMAIL PROTECTED] Sent: Tuesday, March 30, 2004 11:20 AM To: [EMAIL PROTECTED] Subject: Month End Strategies (TDP for Exchange) I'm wondering what the best strategy to get a month end backup of Exchange going. We would like to keep the backup for an indefinite amount of time (most likely a few years). The backup tape(s) will be sent offsite. Currently we have a nightly backup of Exchange which expires after 30 days. I have a couple ideas on how to accomplish this. I want to hear what other people are doing. Thanks in advance. *** Wayne Prasek I.T. Support Analyst (Server) 204-985-1694 [EMAIL PROTECTED] ***
Re: Library sharing
This just gets stranger. I tried using TAPEUTIL to look at the serial no. of the drives. When I do a CLOSE of the drive, I also get the ERR 46. Something is awry ! Bill Boyer [EMAIL PROTECTED] Sent by: ADSM: Dist Stor Manager [EMAIL PROTECTED] 03/31/2004 12:08 PM Please respond to ADSM: Dist Stor Manager [EMAIL PROTECTED] To [EMAIL PROTECTED] cc Subject Re: Library sharing Then substitute storage agent client for library client. You define the paths on the library manager server. The PATHS reference the library client servername, the library name (which I believe must be the same name) and the drive names as defined on the library manager server. You then use the DEVICE= to point to the /dev/rmtx device on the library client server that matches the same device on the library manager server. Let's say on the TSM library manager server: Library:3584 Drive: LTO1/dev/rmt1 Drive: LTO2/dev/rmt2 Your library client server name is LIBCLIENT (or whatever) and you have the following drives: /dev/rmt3 Which is the same device as /dev/rmt1 on the library manager server /dev/rmt4 Which is the same device as /dev/rmt2 on the library manager server If these are fibre, you'll have to get the WWN names (lsattr -El rmtx) on both/all server and create a matrix that shows which is which on each server. Then on the library manager server: define path libclient lto1 srctype=server desttype=drive library=3584 device=/dev/rmt3 define path libclient lto2 srctype=server desttype=drive library=3584 device=/dev/rmt4 Clear as mud, right? -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] Behalf Of Zoltan Forray/AC/VCU Sent: Wednesday, March 31, 2004 11:27 AM To: [EMAIL PROTECTED] Subject: Re: Library sharing Well, in this case, it isn't, sortof... I don't have *ANY* path statements on the client, that refer to these drives. All that is defined on the client is the SHARED LIBRARY. This is another TSM server, not just a storage agent. The path statements on the library manager are duplicated for the client, pointing to the client as the SOURCE serverand yes, both sets of definitions point to the same /dev/rmtx. I am beginning to wonder if it has to do with the different levels of ATAPE. The client is much newer (8.4.1.0) while the library manager is 8.3.x. ADSM: Dist Stor Manager [EMAIL PROTECTED] wrote on 03/31/2004 11:07:04 AM: When you define the PATHs on the TSM server for the storage agent on the client node, the device= is the name of the tape drive on the client, not on the server. You need to match the drive name on the TSM server to the correct device name on the client node, then use that in the DEFINE PATH. So on your TSM server: If library 3584 drive LTO1 points to the /dev/rmt1 device and on the storage agent client SA1 that same physical drive is the /dev/rmt3 device you would use: define path SA1 LTO1 srctype=server desttype=drive library=3584 device=/dev/rmt3 Bill Boyer DSS, Inc. -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] Behalf Of Karel Bos Sent: Wednesday, March 31, 2004 10:54 AM To: [EMAIL PROTECTED] Subject: Re: Library sharing Hi, Can be, but don't have to be the same... In the past I saw some machines with different device names for the same devices and it worked well with ITSM (on Windows). Regards, Karel -Oorspronkelijk bericht- Van: Amos Hagay [mailto:[EMAIL PROTECTED] Verzonden: woensdag 31 maart 2004 17:46 Aan: [EMAIL PROTECTED] Onderwerp: Re: Library sharing Hi, From my experience with 3584 Library, the rmt devices should be The same on both machines e.g. server_1 /dev/rmt1 /dev/rmt2 etc... And also on the library client /dev/rmt1 ... AH -Original Message- From: Zoltan Forray/AC/VCU [mailto:[EMAIL PROTECTED] Sent: Wednesday, March 31, 2004 5:46 PM To: [EMAIL PROTECTED] Subject: Library sharing Trying to get ATL library sharing working between two TSM AIX servers. I think I finally got the definitions correct..at least they seem to function. However, I can't get the library client (capella) to use the drives. Every time it does, I get these errors in the activity log: 03/31/2004 09:54:13 ANR8779E Unable to open drive /dev/rmt1, error number=46. (SESSION: 2663, PROCESS: 11) The library manager says the tape is mounted and ready. 03/31/2004 09:52:25 ANR8337I 3590 volume 070330 mounted in drive ATL-DRIVE2 (/dev/rmt1). 03/31/2004 09:52:25 ANR9791I Volume 070330 in library 3494ATL ownership is changing from TSM-AGENA to TSM-CAPELLA. Any suggestions on what might be wrong ? AIX messages says the -46 is Drive Not Ready. These are FC / SAN attached 3590E1A drives.
Re: Trying to collect backup history of clients
Also make sure your Event Record Retention Period: is set to more than 14 days... We have our at 32 to catch a full month. -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] Behalf Of Balasubramanian Krishnamurthy Sent: Wednesday, March 31, 2004 11:33 AM To: [EMAIL PROTECTED] Subject: Trying to collect backup history of clients hi, We have TSM 5.1.6.2 on Solaris 2.8. I am trying to collect the backup history attempts for my clients. I have my activity log stored for 14 days. Most of my backups are scheduled but some are scripted from the client side. also we have randomization enabled. What would be the most appropriate way to collect data on backups attempted/succeeded. thanks, Bala Krishnamurthy [EMAIL PROTECTED]
Re: TSM, Solaris and Fibre connected drives ?
We are going through two IBM2109 switches, with each drive attached to both switches for failover purposes. You still need to add the drives to the appropriate zones using the wwn's. I'm not really aware of any good documentation that covers this, but if you find something please pass it over. Once you've configured the zones, you should be able to issue: cfgadm -al and you'll see output similar to this: c2::5005076300406311 tape connectedconfigured failing c2::5005076300406657 tape connectedconfigured failing c2::5005076300406687 tape connectedconfigured failing c2::5005076300406ae8 tape connectedconfigured failing c2::50050763004072a8 tape connectedconfigured failing c2::5005076300806311 tape connectedconfigured failing c2::5005076300806657 tape connectedconfigured failing c2::5005076300806687 tape connectedconfigured failing c2::5005076300806ae8 tape connectedconfigured failing c2::50050763008072a8 tape connectedconfigured failing This is non-operational so the tape devices are in a failing condition currently. After the c2:: entry you can see the wwn's for each tape drive. Tying those back to the st entries is a little more difficult. One way to determine which is which (at least in 5.2.2.1) is to define the drives using the st entry and define a path to the drive. Once you've done that, the wwn for the drive will be displayed in q dr f=d: Library Name: 3494 Drive Name: 10H1A Device Type: 3590 On-Line: Yes Read Formats: 3590H-C,3590H-B,3590E-C,3590E-B,3 3590C,3590B Write Formats: 3590H-C,3590H-B Element: Drive State: EMPTY Allocated to: WWN: 500507636311 Serial Number: 000A1357 Last Update by (administrator): LDAHL Last Update Date/Time: 03/12/04 10:52:59 and if you issue q path f=d: Source Name: TSM05 Source Type: SERVER Destination Name: 10H1A Destination Type: DRIVE Library: 3494 Node Name: Device: /dev/rmt/10st External Manager: LUN: Initiator: 0 Directory: On-Line: Yes Last Update by (administrator): LDAHL You can then correlate that /dev/rmt/10st corresponds to the drive with WWN: 500507636311. It's not the most straightforward but it works. I believe one of my system administrators may have developed a workaround and I'll check with him when he gets back (he's in a training class). Hope this helps. One last note, it appears that every time the system is rebooted it creates new /dev/rmt entries. This is extremely bothersome being it keeps adding the entries with a higher numerical number. Not sure if we're doing something wrong on that issue yet. Still working out the bugs... Luke 818-354-7117 Farren Minns wrote: Was that going through a switch or are the fibre drives directly connected? The reason I ask is that I'm unsure how the OS picks up the new devices through a switch. We have a SAN, and I'm used to the fact that you have to tell the SAN which LUNS are available to which host (using the WWN), but as far as I'm aware, you don't do any such thing with drives. Do you know of any decent TSM documentation that covers this at all? Thanks Farren |+---+| || Luke Dahl || || [EMAIL PROTECTED]|| || Sent by: ADSM: Dist Stor | To:[EMAIL PROTECTED] | || Manager| cc: | || [EMAIL PROTECTED] | Subject:Re: TSM, | || | Solaris and Fibre connected drives ? | || 03/29/2004 05:41 PM || || Please respond to ADSM:|| || Dist Stor Manager || || || |+---+| We're doing exactly the same thing now only we're on TSM 5.2.2.1. Just finished some preliminary
Re: Tape library eval
I am using the ADIC Scalar 1000 with LTO-1 drives. It has been a great performer for me. I am comfortable with ADIC from years of using their products and also it helps my confort level that IBM OEMs the Scalar 24 and Scalar 100 units as the 3582 and 3583 libraries. -Original Message- From: Bull, Thomas L. [mailto:[EMAIL PROTECTED] Sent: Thursday, March 25, 2004 5:19 AM To: [EMAIL PROTECTED] Subject: Tape library eval Hello - I will soon be purchasing a new library, and am evaluating an Overland NEO 4100 and StorageTek L80. Both appear to be very good and are well suited for my environment. I like the Overland's scalability. Does anyone have any experience with either of these libraries, and if so, how is the support? thanks, Tom Bull Partners Healthcare System, Inc.
Re: TSM, Solaris and Fibre connected drives ?
Hi Farren, A quick update. I was mistaken about a couple of things. The st entries are created again with a higher numerical value only when you make changes to the system configuration (adding additional cards, modifying the zone and removing and re-adding devices, etc.). Also, if you run cfgadm -al as root the devices will list the appropriate condition value (I wasn't logged in as root when I ran it to give you the output). Hope this helps, give me a call if you have any other questions or think I can offer any other assistance. Luke 818-645-5684 Farren Minns wrote: Was that going through a switch or are the fibre drives directly connected? The reason I ask is that I'm unsure how the OS picks up the new devices through a switch. We have a SAN, and I'm used to the fact that you have to tell the SAN which LUNS are available to which host (using the WWN), but as far as I'm aware, you don't do any such thing with drives. Do you know of any decent TSM documentation that covers this at all? Thanks Farren |+---+| || Luke Dahl || || [EMAIL PROTECTED]|| || Sent by: ADSM: Dist Stor | To:[EMAIL PROTECTED] | || Manager| cc: | || [EMAIL PROTECTED] | Subject:Re: TSM, | || | Solaris and Fibre connected drives ? | || 03/29/2004 05:41 PM || || Please respond to ADSM:|| || Dist Stor Manager || || || |+---+| We're doing exactly the same thing now only we're on TSM 5.2.2.1. Just finished some preliminary testing. TSM still uses the /dev/rmt/*st entries for the drives. There are two st entries for each drive being they have two fiber ports. We had some issues with our fiber cards not supporting the drives - we went from Qlogic to Emulex and don't have any issues now. Other than that it was pretty straightforward. Once you have defined a drive and a path, you can see the wwn and trace that back to the drive to come up with a matrix so you know which st entry belongs to each drive. Luke Farren Minns wrote: Hi TSMers Running TSM 5.1.6.2 on a Sun E250 presently connected to 3494 lib with 2 SCSI 3590 drives (H1A). I have a question for you. We will soon be changing the SCSI attached drives for fibre attached models (still going to be 3590 H1A in the 3494 lib) which will be connected to a Brocade switch. Now, I have very little experience with fibre drives and was wondering what the steps were both with Solaris (if anybody can help) and TSM. I am used to adding SCSI devices to Solaris and then using the /dev/rmt/??? format to define the drives to TSM, but I'm assuming this is total different with fibre drives. I am assuming that the World Wide Name convention will be used somewhere. Can anyone give me any advice or good documentation pointers etc. Many thanks in advance Farren Minns - John Wiley Sons Ltd
Re: Tape library eval
Just remember that ADIC uses different firmware that what IBM uses. This has caused me some problems. R. -Original Message- From: Levinson, Donald A. [mailto:[EMAIL PROTECTED] Sent: Wednesday, March 31, 2004 10:44 AM To: [EMAIL PROTECTED] Subject: Re: Tape library eval I am using the ADIC Scalar 1000 with LTO-1 drives. It has been a great performer for me. I am comfortable with ADIC from years of using their products and also it helps my confort level that IBM OEMs the Scalar 24 and Scalar 100 units as the 3582 and 3583 libraries. -Original Message- From: Bull, Thomas L. [mailto:[EMAIL PROTECTED] Sent: Thursday, March 25, 2004 5:19 AM To: [EMAIL PROTECTED] Subject: Tape library eval Hello - I will soon be purchasing a new library, and am evaluating an Overland NEO 4100 and StorageTek L80. Both appear to be very good and are well suited for my environment. I like the Overland's scalability. Does anyone have any experience with either of these libraries, and if so, how is the support? thanks, Tom Bull Partners Healthcare System, Inc.
tsm and old nodes
i have a number of tsm clients that no longer exist physically, either the server was replaced and node name is different on new server or the server was merged with another server i want to keep the data but i have noticed that these clients still occupy a license. i have in a few cases, exported the node, deleted the file space, deleted the node and marked the tape in the event i ever have to get data of it via the inport function is this the best way to handle this kind of situation how do others handle this i tried once to reallocate the old filespace so that the new server had references to the old filespace and the current filespace. that process is too cumbersome i have some more nodes that dont exist any more and i was going to export them like i did the others Tim Brown Systems Specialist Central Hudson Gas Electric 284 South Ave Poughkeepsie, NY 12601 Email: [EMAIL PROTECTED] Phone: 845-486-5643 Fax: 845-486-5921
A Grumble, and a hint.
Good day all. I'm doing some DR exercises, and I just made a somewhat irritating observation. After you have DSMSERV FORMAT [...] If you DSMSERV RESTORE DB then the process gives you a dumb look. You have to do DSMSERV RESTORE DB [ date and time parameters ] which _appear_ to require that you specify the point in time of the last DB backup. However, if you get it wrong (too recent or such) then the restore goes perfectly nicely, and picks up the most recent backup available. In fact, if you specify TOD=01/01/2200 TOT=00:00:00 That is, midnight, Jan 1 of 2200, or even TOD=TODAY TOT=NOW it works JUST fine. Now why couldn't those otherwise bright folks have made 'tod=today, tot=now' the default values of those options, and just accept 'RESTORE DB' as meaning get me the best you can. Dumb bunnies. - Allen S. Rout - Grumpy afternoon.
SAPR3 anomalies with occupancy
Folks I need some help understanding this... I have a 4.2.3 TSM server running on AIX 4.3.3 with a 5.1.6 TSM client running on AIX 5.1 The DB shows there are 878 archive files from the following select statement but when I look at the occupancy it only shows a total of 372 files. And I don't even think the Archive table keeps track of the files in the Copypool. Could someone please try to explain the discrepancy? And more troubling than that, and purhaps a reason for the discrepancy, is that when I look at each archived file ( select * from archives ...) from this node I see more than half of them are in the /tdp filespace of which 'q occ' shows no occupancy at all l! tsm: ADSMselect count(*) from archives where node_name='DEVEL_DB' ANR2963W This SQL query may produce a very large result table, or may require a significant amount of time to compute. Do you wish to proceed? (Yes (Y)/No (N)) y Unnamed[1] --- 878 tsm: ADSMq fi devel_db Node NameFilespaceFSID Platform Filespace Is Files- Capacity Pct Name Type pace (MB) Util Unicode? --- --- -- - - DEVEL_DB /tdp1 TDPR3AIX API:XINTV3 No 0.0 0.0 DEVEL_DB /tdpmux 2 TDPR3AIX API:XINTV3 No 0.0 0.0 tsm: ADSMq occ devel_db Physical Logical Space Space Node Name Type Filespace FSID Storage Number of OccupiedOccupied Name Pool Name Files (MB)(MB) -- -- -- - -- -- DEVEL_DBArch /tdpmux2 SAP_PROD_CPOOL186 963,156.55 963,156.55 DEVEL_DBArch /tdpmux2 SAP_PROD_TPOOL186 963,156.55 963,156.55 James (J) Holdren E-Business Storage Management - Enterprise Storage Services - Service Delivery Center / South - IBM Global Services Pager: 800-759- pin 1061062 Office: 919-543-2213 t/l 441-2213 Fax: 919-543-9196
Re: tsm and old nodes
Just a thought: Restore the files to another server, run a backup, whack the files. Then your standard retention period for that server/directory as defined in your mgt class will apply. For instance, we would do this by restoring this to one of our Netapps and then backing it up. At least the data would be there, dunno about how it'd handle any system object data... HTH, Mike Bantz Systems Administrator Research Systems, Inc -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] Behalf Of Tim Brown Sent: Wednesday, March 31, 2004 1:56 PM To: [EMAIL PROTECTED] Subject: tsm and old nodes i have a number of tsm clients that no longer exist physically, either the server was replaced and node name is different on new server or the server was merged with another server i want to keep the data but i have noticed that these clients still occupy a license. i have in a few cases, exported the node, deleted the file space, deleted the node and marked the tape in the event i ever have to get data of it via the inport function is this the best way to handle this kind of situation how do others handle this i tried once to reallocate the old filespace so that the new server had references to the old filespace and the current filespace. that process is too cumbersome i have some more nodes that dont exist any more and i was going to export them like i did the others Tim Brown Systems Specialist Central Hudson Gas Electric 284 South Ave Poughkeepsie, NY 12601 Email: [EMAIL PROTECTED] Phone: 845-486-5643 Fax: 845-486-5921
Re: tsm and old nodes
Given that TSM is licensed by processor now and not node (the internal licensing does not seem to have cought up with the new model) you should be able to have as many node definitions as you want. Retired nodes have 0 processors and therefore require 0 licenses. The TSM 'managed system for LAN' license field should be updated to 'managed system for LAN CPU' to be in line with the actual license model. This is my take on the issue anyway. If the above holds true, I would not worry about moving any of the old node data. Just leave it as it is. David Smith Technical Specialist Business Services and Resources -Original Message- From: ADSM: Dist Stor Manager on behalf of Tim Brown Sent: Thu 4/1/2004 6:56 AM To: [EMAIL PROTECTED] Cc: Subject: tsm and old nodes i have a number of tsm clients that no longer exist physically, either the server was replaced and node name is different on new server or the server was merged with another server i want to keep the data but i have noticed that these clients still occupy a license. i have in a few cases, exported the node, deleted the file space, deleted the node and marked the tape in the event i ever have to get data of it via the inport function is this the best way to handle this kind of situation how do others handle this i tried once to reallocate the old filespace so that the new server had references to the old filespace and the current filespace. that process is too cumbersome i have some more nodes that dont exist any more and i was going to export them like i did the others Tim Brown Systems Specialist Central Hudson Gas Electric 284 South Ave Poughkeepsie, NY 12601 Email: [EMAIL PROTECTED] Phone: 845-486-5643 Fax: 845-486-5921
