Re: How to Incorporate a CDL into TSM environment?
Richard Rhodes said: I'd love to have a couple vtl's. When we've priced them out they come out to be much more costly (several times) that of tape for our environment. We keep lots of old/stale data around which drives seems to drive the cost of the VTL way up. I was hoping possibly use a vtl for only primary data with the new feature of TSM v5.4, but that's not going to work out. VTL cost (even after dedupe) will never compare with the cost of tape media alone, so tape will always be a cheaper medium if you take it out of the library. When I say that VTLs are close to the price of tape, I mean close to the price of a similarly-sized, fully-populated-with-media tape library. I personal opinion is that VTL's are a stop-gap solution. I think compression and de-dupe have much wider application within a normal disk subsystem where it could apply to a much wider range of situations. Pretty much everybody who is following the industry believes it will morph into the intelligent disk target industry. VTL will continue to be a personality they offer, but as other backup software products are better able to back up to filesystems (TSM does it just fine), more VTL vendors will offer a filesystem interface. Right now, the only one that does a filesystem interface and de-dupe is Data Domain. (Copan has a filesystem interface, but I don't think they're doing de-dupe through it yet. Any day now.) This is the bit problem I see with Tape. It seems to me that the latest generations of tape drives have rated speeds that almost defy the any ability to supply them with data. I almost which I could purchase a modern tape drive that actually was slower. Mmm... LTO-4: 120 MB/s native speed, 180 MB/s typical with compression. (I'm using 1.5:1 compression, which is what I see most often as an average actual compression ratio.) So... It wants 180 MB/s, and I've supposed to feed that with a 60-80 MB/s GbE connection. (The only saving grace of modern tape drives is that they have variable speeds. The LTO-4, for example, can go as slow as about 40 MB/s plus compression.) The problem is capacity. As vendors push capacity, they do so by pushing the bits closer together. As they do that, the drive gets faster.
Cannot get tapes labelled in 3584 SCSI library: help
Hey Everyone, I am trying to add virtual tapes into TSM scsi library cdlb_dev which is actually a virtual library for which I am emulating an IBM 3584 and IBM LTO2 tape media and I am getting the following error: Date/Time Message -- 06/11/07 15:03:14 ANR0984I Process 820 for LABEL LIBVOLUME started in the BACKGROUND at 15:03:14. (SESSION: 253882, PROCESS: 820) 06/11/07 15:03:14 ANR8799I LABEL LIBVOLUME: Operation for library CDLB_DEV started as process 820. (SESSION: 253882, PROCESS: 820) 06/11/07 15:03:14 ANR0609I LABEL LIBVOLUME started as process 820. (SESSION: 253882, PROCESS: 820) 06/11/07 15:03:14 ANR8439I SCSI library CDLB_DEV is ready for operations. (SESSION: 253882, PROCESS: 820) 06/11/07 15:03:14 ANR8323I 001: Insert ANY volume DB R/W into entry/exit port of library CDLB_DEV within 60 minute(s); issue 'REPLY' along with the request ID when ready. (SESSION: 253882, PROCESS: 820) This is on a TSM 5.3.4.2 server. Library CDLB_DEV Library Name: CDLB_DEV Library Type: SCSI ACS Id: Private Category: Scratch Category: WORM Scratch Category: External Manager: Shared: No LanFree: ObeyMountRetention: Primary Library Manager: WWN: 2002000D77BD375D Serial Number: 0011815699830401 Source Name: TSMDEV Source Type: SERVER Destination Name: CDLB_DEV Destination Type: LIBRARY Library: Node Name: Device: /dev/smc0 External Manager: LUN: Initiator: 0 Directory: On-Line: Yes I entered the command: label libvol cdlb_dev db checkin=scratch. Can anyone tell me what I might be doing wrong? Any help/suggestions are appreciated. Thanks in advance! Joni Moyer Highmark Storage Systems, Storage Mngt Analyst III Phone Number: (717)302-9966 Fax: (717) 302-9826 [EMAIL PROTECTED]
Antwort: Cannot get tapes labelled in 3584 SCSI library: help
try q reply and reply xxx label=xxx Christian Demnitz Joni Moyer [EMAIL PROTECTED] Gesendet von: ADSM: Dist Stor Manager ADSM-L@VM.MARIST.EDU 12.06.2007 14:05 Bitte antworten an ADSM: Dist Stor Manager ADSM-L@VM.MARIST.EDU An ADSM-L@VM.MARIST.EDU Kopie Thema Cannot get tapes labelled in 3584 SCSI library: help Hey Everyone, I am trying to add virtual tapes into TSM scsi library cdlb_dev which is actually a virtual library for which I am emulating an IBM 3584 and IBM LTO2 tape media and I am getting the following error: Date/Time Message -- 06/11/07 15:03:14 ANR0984I Process 820 for LABEL LIBVOLUME started in the BACKGROUND at 15:03:14. (SESSION: 253882, PROCESS: 820) 06/11/07 15:03:14 ANR8799I LABEL LIBVOLUME: Operation for library CDLB_DEV started as process 820. (SESSION: 253882, PROCESS: 820) 06/11/07 15:03:14 ANR0609I LABEL LIBVOLUME started as process 820. (SESSION: 253882, PROCESS: 820) 06/11/07 15:03:14 ANR8439I SCSI library CDLB_DEV is ready for operations. (SESSION: 253882, PROCESS: 820) 06/11/07 15:03:14 ANR8323I 001: Insert ANY volume DB R/W into entry/exit port of library CDLB_DEV within 60 minute(s); issue 'REPLY' along with the request ID when ready. (SESSION: 253882, PROCESS: 820) This is on a TSM 5.3.4.2 server. Library CDLB_DEV Library Name: CDLB_DEV Library Type: SCSI ACS Id: Private Category: Scratch Category: WORM Scratch Category: External Manager: Shared: No LanFree: ObeyMountRetention: Primary Library Manager: WWN: 2002000D77BD375D Serial Number: 0011815699830401 Source Name: TSMDEV Source Type: SERVER Destination Name: CDLB_DEV Destination Type: LIBRARY Library: Node Name: Device: /dev/smc0 External Manager: LUN: Initiator: 0 Directory: On-Line: Yes I entered the command: label libvol cdlb_dev db checkin=scratch. Can anyone tell me what I might be doing wrong? Any help/suggestions are appreciated. Thanks in advance! Joni Moyer Highmark Storage Systems, Storage Mngt Analyst III Phone Number: (717)302-9966 Fax: (717) 302-9826 [EMAIL PROTECTED]
Define path problems
Hi All, I am having problems with replacing a SCSI LTO tape drive in my 3584 library. Usually a routine procedure, but this time I am having major difficulties. Whenever I try to redefine the path for this particular drive I get the following error: ANR8972E DEFINE PATH: Unable to find the element number for drive DRIVE3 in library 3584LIB I have been talking with both TSM software support, and hardware support, and still not much luck. The drive is being detected by the server properly, and the library detects the drive fine as well. We have tried two different drives as well. I did notice the library specialist does report a different serial number than the library itself reports though.. The server is Windows 2000. Has anyone seen this before? Any ideas??? Take Care, Chris Chris McKay Systems Administrator York Catholic District School Board __ This message is for the sole use of the intended recipients and may contain confidential and privileged information. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not an intended recipient, please contact the sender by reply email and destroy all copies of the original message. Thank you for your cooperation.
Re: Define path problems
Hi, By any change has there been a hardware change? - delete drive from ITSM config, - reboot Windows - define drive serial=autodetect - define path to drive Regards, Karel -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Chris McKay Sent: dinsdag 12 juni 2007 14:25 To: ADSM-L@VM.MARIST.EDU Subject: Define path problems Hi All, I am having problems with replacing a SCSI LTO tape drive in my 3584 library. Usually a routine procedure, but this time I am having major difficulties. Whenever I try to redefine the path for this particular drive I get the following error: ANR8972E DEFINE PATH: Unable to find the element number for drive DRIVE3 in library 3584LIB I have been talking with both TSM software support, and hardware support, and still not much luck. The drive is being detected by the server properly, and the library detects the drive fine as well. We have tried two different drives as well. I did notice the library specialist does report a different serial number than the library itself reports though.. The server is Windows 2000. Has anyone seen this before? Any ideas??? Take Care, Chris Chris McKay Systems Administrator York Catholic District School Board __ This message is for the sole use of the intended recipients and may contain confidential and privileged information. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not an intended recipient, please contact the sender by reply email and destroy all copies of the original message. Thank you for your cooperation. ÿþD i t b e r i c h t i s v e r t r o u w e l i j k e n k a n g e h e i m e i n f o r m a t i e b e v a t t e n e n k e l b e s t e m d v o o r d e g e a d r e s s e e r d e . I n d i e n d i t b e r i c h t n i e t v o o r u i s b e s t e m d , v e r z o e k e n w i j u d i t o n m i d d e l l i j k a a n o n s t e m e l d e n e n h e t b e r i c h t t e v e r n i e t i g e n . A a n g e z i e n d e i n t e g r i t e i t v a n h e t b e r i c h t n i e t v e i l i g g e s t e l d i s m i d d e l s v e r z e n d i n g v i a i n t e r n e t , k a n A t o s O r i g i n n i e t a a n s p r a k e l i j k w o r d e n g e h o u d e n v o o r d e i n h o u d d a a r v a n . H o e w e l w i j o n s i n s p a n n e n e e n v i r u s v r i j n e t w e r k t e h a n t e r e n , g e v e n w i j g e e n e n k e l e g a r a n t i e d a t d i t b e r i c h t v i r u s v r i j i s , n o c h a a n v a a r d e n w i j e n i g e a a n s p r a k e l i j k h e i d v o o r d e m o g e l i j k e a a n w e z i g h e i d v a n e e n v i r u s i n d i t b e r i c h t . O p a l o n z e r e c h t s v e r h o u d i n g e n , a a n b i e d i n g e n e n o v e r e e n k o m s t e n w a a r o n d e r A t o s O r i g i n g o e d e r e n e n / o f d i e n s t e n l e v e r t z i j n m e t u i t s l u i t i n g v a n a l l e a n d e r e v o o r w a a r d e n d e L e v e r i n g s v o o r w a a r d e n v a n A t o s O r i g i n v a n t o e p a s s i n g . D e z e w o r d e n u o p a a n v r a a g d i r e c t k o s t e l o o s t o e g e z o n d e n . T h i s e - m a i l a n d t h e d o c u m e n t s a t t a c h e d a r e c o n f i d e n t i a l a n d i n t e n d e d s o l e l y f o r t h e a d d r e s s e e ; i t m a y a l s o b e p r i v i l e g e d . I f y o u r e c e i v e t h i s e - m a i l i n e r r o r , p l e a s e n o t i f y t h e s e n d e r i m m e d i a t e l y a n d d e s t r o y i t . A s i t s i n t e g r i t y c a n n o t b e s e c u r e d o n t h e I n t e r n e t , t h e A t o s O r i g i n g r o u p l i a b i l i t y c a n n o t b e t r i g g e r e d f o r t h e m e s s a g e c o n t e n t . A l t h o u g h t h e s e n d e r e n d e a v o u r s t o m a i n t a i n a c o m p u t e r v i r u s - f r e e n e t w o r k , t h e s e n d e r d o e s n o t w a r r a n t t h a t t h i s t r a n s m i s s i o n i s v i r u s - f r e e a n d w i l l n o t b e l i a b l e f o r a n y d a m a g e s r e s u l t i n g f r o m a n y v i r u s t r a n s m i t t e d . O n a l l o f f e r s a n d a g r e e m e n t s u n d e r w h i c h A t o s O r i g i n s u p p l i e s g o o d s a n d / o r s e r v i c e s o f w h a t e v e r n a t u r e , t h e T e r m s o f D e l i v e r y f r o m A t o s O r i g i n e x c l u s i v e l y a p p l y . T h e T e r m s
Re: Define path problems
We did recently update the firmware on both the library, and the drives, also updated the changer and tape device drivers on the server as well. ADSM: Dist Stor Manager ADSM-L@VM.MARIST.EDU writes: Hi, By any change has there been a hardware change? - delete drive from ITSM config, - reboot Windows - define drive serial=autodetect - define path to drive Regards, Karel -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Chris McKay Sent: dinsdag 12 juni 2007 14:25 To: ADSM-L@VM.MARIST.EDU Subject: Define path problems Hi All, I am having problems with replacing a SCSI LTO tape drive in my 3584 library. Usually a routine procedure, but this time I am having major difficulties. Whenever I try to redefine the path for this particular drive I get the following error: ANR8972E DEFINE PATH: Unable to find the element number for drive DRIVE3 in library 3584LIB I have been talking with both TSM software support, and hardware support, and still not much luck. The drive is being detected by the server properly, and the library detects the drive fine as well. We have tried two different drives as well. I did notice the library specialist does report a different serial number than the library itself reports though.. The server is Windows 2000. Has anyone seen this before? Any ideas??? Take Care, Chris Chris McKay Systems Administrator York Catholic District School Board __ This message is for the sole use of the intended recipients and may contain confidential and privileged information. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not an intended recipient, please contact the sender by reply email and destroy all copies of the original message. Thank you for your cooperation. __ This message is for the sole use of the intended recipients and may contain confidential and privileged information. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not an intended recipient, please contact the sender by reply email and destroy all copies of the original message. Thank you for your cooperation.
Re: Cannot get tapes labelled in 3584 SCSI library: help
Hi Joni, did you try the previous suggestions using the reply command? Also, John Schneider wrote Greetings, This is not the syntax for a CDL, since it does not have an I/O door. Why are you trying to label only one tape, anyway, when you want to label them all? The syntax should be: label libvol cdlb_dev search=yes labelsource=barcode checkin=scratch This will label all the virtual tapes with the virtual barcode label. On a CDL, it takes just a few seconds per tape to label these, not 1-2 minutes apiece like it does on a real tape drive. Best Regards, John D. Schneider Sr. System Administrator - Storage Sisters of Mercy Health System 3637 South Geyer Road St. Louis, MO. 63127 Email: [EMAIL PROTECTED] Office: 314-364-3150, Cell: 314-486-2359 Internet [EMAIL PROTECTED] To ADSM-L Sent by: ADSM-L@VM.MARIST.EDU cc 12/06/2007 13:05 Subject [ADSM-L] Cannot get tapes labelled in 3584 SCSI library: help Please respond to ADSM-L@VM.MARIST.EDU Hey Everyone, I am trying to add virtual tapes into TSM scsi library cdlb_dev which is actually a virtual library for which I am emulating an IBM 3584 and IBM LTO2 tape media and I am getting the following error: Date/Time Message -- 06/11/07 15:03:14 ANR0984I Process 820 for LABEL LIBVOLUME started in the BACKGROUND at 15:03:14. (SESSION: 253882, PROCESS: 820) 06/11/07 15:03:14 ANR8799I LABEL LIBVOLUME: Operation for library CDLB_DEV started as process 820. (SESSION: 253882, PROCESS: 820) 06/11/07 15:03:14 ANR0609I LABEL LIBVOLUME started as process 820. (SESSION: 253882, PROCESS: 820) 06/11/07 15:03:14 ANR8439I SCSI library CDLB_DEV is ready for operations. (SESSION: 253882, PROCESS: 820) 06/11/07 15:03:14 ANR8323I 001: Insert ANY volume DB R/W into entry/exit port of library CDLB_DEV within 60 minute(s); issue 'REPLY' along with the request ID when ready. (SESSION: 253882, PROCESS: 820) This is on a TSM 5.3.4.2 server. Library CDLB_DEV Library Name: CDLB_DEV Library Type: SCSI ACS Id: Private Category: Scratch Category: WORM Scratch Category: External Manager: Shared: No LanFree: ObeyMountRetention: Primary Library Manager: WWN: 2002000D77BD375D Serial Number: 0011815699830401 Source Name: TSMDEV Source Type: SERVER Destination Name: CDLB_DEV Destination Type: LIBRARY Library: Node Name: Device: /dev/smc0 External Manager: LUN: Initiator: 0 Directory: On-Line: Yes I entered the command: label libvol cdlb_dev db checkin=scratch. Can anyone tell me what I might be doing wrong? Any help/suggestions are appreciated. Thanks in advance! Joni Moyer Highmark Storage Systems, Storage Mngt Analyst III Phone Number: (717)302-9966 Fax: (717) 302-9826 [EMAIL PROTECTED] This message and any attachments (the message) is intended solely for the addressees and is confidential. If you receive this message in error, please delete it and immediately notify the sender. Any use not in accord with its purpose, any dissemination or disclosure, either whole or partial, is prohibited except formal approval. The internet can not guarantee the integrity of this message. BNP PARIBAS (and its subsidiaries) shall (will) not therefore be liable for the message if modified. - Ce message et toutes les pieces jointes (ci-apres le message) sont etablis a l'intention exclusive de ses destinataires et sont confidentiels. Si vous recevez ce message par erreur, merci de le detruire et d'en avertir immediatement l'expediteur. Toute utilisation de ce message non conforme a sa destination, toute diffusion ou toute publication, totale ou partielle, est interdite, sauf autorisation expresse. L'internet ne permettant pas d'assurer l'integrite de ce message, BNP PARIBAS (et ses
Re: Cannot get tapes labelled in 3584 SCSI library: help
Hi Matthew! No, for some weird reason I didn't get those responses, but I was finally able to label the volumes with: label libvol cdlb_dev search=yes volrange=db,db0209 labelsource=barcode. Thank you everyone for your responses! I really appreciate the help! Joni Moyer Highmark Storage Systems, Storage Mngt Analyst III Phone Number: (717)302-9966 Fax: (717) 302-9826 [EMAIL PROTECTED] Matthew Warren [EMAIL PROTECTED] Sent by: ADSM: Dist Stor Manager ADSM-L@VM.MARIST.EDU 06/12/2007 08:56 AM Please respond to ADSM: Dist Stor Manager ADSM-L@VM.MARIST.EDU To ADSM-L@VM.MARIST.EDU cc Subject Re: Cannot get tapes labelled in 3584 SCSI library: help Hi Joni, did you try the previous suggestions using the reply command? Also, John Schneider wrote Greetings, This is not the syntax for a CDL, since it does not have an I/O door. Why are you trying to label only one tape, anyway, when you want to label them all? The syntax should be: label libvol cdlb_dev search=yes labelsource=barcode checkin=scratch This will label all the virtual tapes with the virtual barcode label. On a CDL, it takes just a few seconds per tape to label these, not 1-2 minutes apiece like it does on a real tape drive. Best Regards, John D. Schneider Sr. System Administrator - Storage Sisters of Mercy Health System 3637 South Geyer Road St. Louis, MO. 63127 Email: [EMAIL PROTECTED] Office: 314-364-3150, Cell: 314-486-2359 Internet [EMAIL PROTECTED] To ADSM-L Sent by: ADSM-L@VM.MARIST.EDU cc 12/06/2007 13:05Subject [ADSM-L] Cannot get tapes labelled in 3584 SCSI library: help Please respond to ADSM-L@VM.MARIST.EDU Hey Everyone, I am trying to add virtual tapes into TSM scsi library cdlb_dev which is actually a virtual library for which I am emulating an IBM 3584 and IBM LTO2 tape media and I am getting the following error: Date/Time Message -- 06/11/07 15:03:14 ANR0984I Process 820 for LABEL LIBVOLUME started in the BACKGROUND at 15:03:14. (SESSION: 253882, PROCESS: 820) 06/11/07 15:03:14 ANR8799I LABEL LIBVOLUME: Operation for library CDLB_DEV started as process 820. (SESSION: 253882, PROCESS: 820) 06/11/07 15:03:14 ANR0609I LABEL LIBVOLUME started as process 820. (SESSION: 253882, PROCESS: 820) 06/11/07 15:03:14 ANR8439I SCSI library CDLB_DEV is ready for operations. (SESSION: 253882, PROCESS: 820) 06/11/07 15:03:14 ANR8323I 001: Insert ANY volume DB R/W into entry/exit port of library CDLB_DEV within 60 minute(s); issue 'REPLY' along with the request ID when ready. (SESSION: 253882, PROCESS: 820) This is on a TSM 5.3.4.2 server. Library CDLB_DEV Library Name: CDLB_DEV Library Type: SCSI ACS Id: Private Category: Scratch Category: WORM Scratch Category: External Manager: Shared: No LanFree: ObeyMountRetention: Primary Library Manager: WWN: 2002000D77BD375D Serial Number: 0011815699830401 Source Name: TSMDEV Source Type: SERVER Destination Name: CDLB_DEV Destination Type: LIBRARY Library: Node Name: Device: /dev/smc0 External Manager: LUN: Initiator: 0 Directory: On-Line: Yes I entered the command: label libvol cdlb_dev db checkin=scratch. Can anyone tell me what I might be doing wrong? Any help/suggestions are appreciated. Thanks in advance! Joni Moyer Highmark Storage Systems, Storage Mngt Analyst III Phone Number: (717)302-9966 Fax: (717) 302-9826 [EMAIL PROTECTED] This message and any attachments (the message) is intended solely for the addressees and is confidential. If you receive this message in error, please delete it and immediately notify the sender. Any use not in accord with its purpose, any dissemination or disclosure, either whole or partial, is prohibited except formal approval. The internet can not guarantee the integrity of this message. BNP PARIBAS (and its subsidiaries) shall (will) not therefore be liable for the message
Re: Define path problems
It sounds like the serial information to me. Did you try the serial=autodetect when defining it? I had to do this the last time I added some LTO3 drives. On 6/12/07, Chris McKay [EMAIL PROTECTED] wrote: We did recently update the firmware on both the library, and the drives, also updated the changer and tape device drivers on the server as well. ADSM: Dist Stor Manager ADSM-L@VM.MARIST.EDU writes: Hi, By any change has there been a hardware change? - delete drive from ITSM config, - reboot Windows - define drive serial=autodetect - define path to drive Regards, Karel -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Chris McKay Sent: dinsdag 12 juni 2007 14:25 To: ADSM-L@VM.MARIST.EDU Subject: Define path problems Hi All, I am having problems with replacing a SCSI LTO tape drive in my 3584 library. Usually a routine procedure, but this time I am having major difficulties. Whenever I try to redefine the path for this particular drive I get the following error: ANR8972E DEFINE PATH: Unable to find the element number for drive DRIVE3 in library 3584LIB I have been talking with both TSM software support, and hardware support, and still not much luck. The drive is being detected by the server properly, and the library detects the drive fine as well. We have tried two different drives as well. I did notice the library specialist does report a different serial number than the library itself reports though.. The server is Windows 2000. Has anyone seen this before? Any ideas??? Take Care, Chris Chris McKay Systems Administrator York Catholic District School Board __ This message is for the sole use of the intended recipients and may contain confidential and privileged information. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not an intended recipient, please contact the sender by reply email and destroy all copies of the original message. Thank you for your cooperation. __ This message is for the sole use of the intended recipients and may contain confidential and privileged information. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not an intended recipient, please contact the sender by reply email and destroy all copies of the original message. Thank you for your cooperation.
Re: Define path problems
Yes, I tried both serial and element=autodetect ADSM: Dist Stor Manager ADSM-L@VM.MARIST.EDU writes: It sounds like the serial information to me. Did you try the serial=autodetect when defining it? I had to do this the last time I added some LTO3 drives. On 6/12/07, Chris McKay [EMAIL PROTECTED] wrote: We did recently update the firmware on both the library, and the drives, also updated the changer and tape device drivers on the server as well. ADSM: Dist Stor Manager ADSM-L@VM.MARIST.EDU writes: Hi, By any change has there been a hardware change? - delete drive from ITSM config, - reboot Windows - define drive serial=autodetect - define path to drive Regards, Karel -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Chris McKay Sent: dinsdag 12 juni 2007 14:25 To: ADSM-L@VM.MARIST.EDU Subject: Define path problems Hi All, I am having problems with replacing a SCSI LTO tape drive in my 3584 library. Usually a routine procedure, but this time I am having major difficulties. Whenever I try to redefine the path for this particular drive I get the following error: ANR8972E DEFINE PATH: Unable to find the element number for drive DRIVE3 in library 3584LIB I have been talking with both TSM software support, and hardware support, and still not much luck. The drive is being detected by the server properly, and the library detects the drive fine as well. We have tried two different drives as well. I did notice the library specialist does report a different serial number than the library itself reports though.. The server is Windows 2000. Has anyone seen this before? Any ideas??? Take Care, Chris Chris McKay Systems Administrator York Catholic District School Board __ This message is for the sole use of the intended recipients and may contain confidential and privileged information. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not an intended recipient, please contact the sender by reply email and destroy all copies of the original message. Thank you for your cooperation. __ This message is for the sole use of the intended recipients and may contain confidential and privileged information. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not an intended recipient, please contact the sender by reply email and destroy all copies of the original message. Thank you for your cooperation. __ This message is for the sole use of the intended recipients and may contain confidential and privileged information. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not an intended recipient, please contact the sender by reply email and destroy all copies of the original message. Thank you for your cooperation.
Re: How to Incorporate a CDL into a TSM environment?
On Mon, 11 Jun 2007 23:50:20 +0100, Neil Schofield [EMAIL PROTECTED] said: - We still need to take into account the overhead of the reclaimable space on a virtual tape. This can be managed by varying the reclamation thresholds, but not eliminated. With a pure disk VTL, you can keep reclamation thresholds more stringent than would otherwise be the case, modulo pending status. It's entirely possible to pack huge tracts of land into PENDING, if you set reclaim threshold low enough. - A pending delete volume will still occupy an underlying disk capacity equivalent to its size. Yes. You want this. :) - Since the conversion of a pending delete volume to a scratch tape takes place purely in the TSM database, a virtual scratch tape will also occupy the full disk space on the VTL. until it is re-used. This I don't know about. So am I correct in thinking that in the whole scratch, filling, full, reclaim, pending, delete, scratch lifecycle of a storage pool volume, the only time that we get the benefit of the over-provisioning is when it's filling? If the volume continues to use space when it's returned to scratch, then it's only at the -first- filling cycle you get that. That doesn't seem quite right, methinks. - Allen S. Rout
Re: Next IBM TSM web seminar June 14th
When you follow the link below, the description says June 13th at 10:00 Central, not June 14th: Windows Active Directory Restore using TSM Backup-Archive (PJS716189) Event ID: PJS716189 Leader: Rick Smith Date: 13 June 2007 Time: 10:00 AM (GMT -05:00) Central Time (US Canada) Duration: 2h 00m Can somebody please clarify? Best Regards, John D. Schneider Sr. System Administrator - Storage Sisters of Mercy Health System 3637 South Geyer Road St. Louis, MO. 63127 Email: [EMAIL PROTECTED] Office: 314-364-3150, Cell: 314-486-2359 -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Darrius Plantz Sent: Monday, June 11, 2007 10:31 AM To: ADSM-L@VM.MARIST.EDU Subject: [ADSM-L] Next IBM TSM web seminar June 14th Windows Active Directory for TSM Backup/Archive Clients This Support Technical Exchange presentation will cover restoring a Windows Active Directory on Windows 2003 using the Tivoli Storage Manager Backup/Archive Clients. Please prepare your system at this url prior to attending, as we are also premiering a new web seminar technology: http://asp22.centra.com/SiteRoots/main/SystemCheck/SystemCheck.jhtml? Please call into the phone conference and join the e-meeting 10 minutes early. Web conference URL: http://asp22.centra.com/GA/main/001ed7ac0112c6d5b6479f3e Password: tiv0li View presentation: http://www.ibm.com/support/docview.wss?rs=0uid=swg27009876 - Looking for a deal? Find great prices on flights and hotels with Yahoo! FareChase.
Re: How to Incorporate a CDL into TSM environment?
On Tue, 12 Jun 2007 03:20:18 -0400, Curtis Preston [EMAIL PROTECTED] said: Pretty much everybody who is following the industry believes it will morph into the intelligent disk target industry. I see this trend too. It makes me think of ATM. Remember ATM? :) Oy, I sound like an old fart. Sorry. Topical, topical: The problem I see with the intelligent disk target notion is that, the smarter you try to get, the more management you have to do, and the more statistical duplication you have to push under the covers. How would you feel if you had to map and tune RAID-5 regions between platters? And, (and here's the psychological kicker) the more you are out of control of the actual processes. This does not offend most administrators of e.g. windows file-service servers: the performance required is sufficiently modest, and the demand sufficiently diffuse, that things like Which platters is this coming from never arise. But if you really want to understand your performance and bottlenecks, then you're in vendor motel land, with extra-price tools to help you. :) It's a storage cloud, and just trust us, it'll all work out. ATM. For administrators accustomed to operating the presented interface, this is not worrying. For administrators accustomed to understanding and controlling the underlying behavior, it is disconcerting, and in the way. This doesn't mean it won't be a great way to make money. The advantage to selling restricted and concealing interfaces is that you can access a market which is incompetent to challenge you, and each flaw in product version N can be a sales opportunity for N.1. Witness Windows. - Allen S. Rout
Re: How to Incorporate a CDL into TSM environment?
Hi Everyone! I have successfully completed the following: Defined a scsi library: cdlb_dev Defined a path from the tsm server to the cdl library: define path tsmdev cdlb_dev srctype=server desttype=library device=/dev/smc0 Define LTO drives for the cdl library: define drive cdlb_dev lto2-27 Define tape paths for the lto2 virtual drives: define path tsmdev lto2-27 srctype=server desttype=drive library=cdlb_dev device=/dev/rmt27 Define a device class for the cdl library: define devclass lto2_cdlb library=cdlb_dev devtype=lto format=ultrium2 mountlimit=drives Define a cdl storage pool: define stgpool cdlb_aix lto2_cdlb pool=primary maxsize=5G maxscratch=100 next=tape_aix hi=90 lo=70 reclaim=50 reclaimpr=1 collocate=no migdelay=30 migpr=1 (I have set the mgdelay to 30 so that we keep 30 days of backups within the cdl until it moves to onsite tape) Label virtual volumes: label libvol cdlb_dev search=yes checkin=scratch volrange=db,db00209 labelsource=barcode In order to start using the cdl and the cdl storage pool cdlb_aix in the order of: aix (disk pool) -- cdlb_aix (cdl aix primary sequential storage pool) -- tape_aix (primary sequential storage pool which is physical lto2 tape) -- copy_aix (offsite lto2 tape pool for offsite disaster recovery purposes) Would I just have to update the aix disk pool's next storage pool to be: cdlb_aix? And then the data will stay on the cdl for 30 days since I have the migdelay set to 30? And what order does it make sense to migrate and backup the data? Scenerio 1 Client backup to aix disk pool Migrate data to cdlb_aix backup cdlb_aix to copy_aix backup tape_aix to copy_aix Migrate cdlb_aix to tape_aix after 30 days Will I ever need to run a job to backup the aix disk pool to the copy_aix pool? Scenerio 2 Client backup to aix disk pool Backup aix disk pool to copy_aix Migrate data from aix disk pool to cdlb_aix storage pool backup cdlb_aix to copy_aix backup tape_aix to copy_aix Migrate cdlb_aix to tape_aix after 30 days Any suggestions are greatly appreciated! Thanks! Joni Moyer Highmark Storage Systems, Storage Mngt Analyst III Phone Number: (717)302-9966 Fax: (717) 302-9826 [EMAIL PROTECTED] Allen S. Rout [EMAIL PROTECTED] Sent by: ADSM: Dist Stor Manager ADSM-L@VM.MARIST.EDU 06/12/2007 10:00 AM Please respond to ADSM: Dist Stor Manager ADSM-L@VM.MARIST.EDU To ADSM-L@VM.MARIST.EDU cc Subject Re: How to Incorporate a CDL into TSM environment? On Tue, 12 Jun 2007 03:20:18 -0400, Curtis Preston [EMAIL PROTECTED] said: Pretty much everybody who is following the industry believes it will morph into the intelligent disk target industry. I see this trend too. It makes me think of ATM. Remember ATM? :) Oy, I sound like an old fart. Sorry. Topical, topical: The problem I see with the intelligent disk target notion is that, the smarter you try to get, the more management you have to do, and the more statistical duplication you have to push under the covers. How would you feel if you had to map and tune RAID-5 regions between platters? And, (and here's the psychological kicker) the more you are out of control of the actual processes. This does not offend most administrators of e.g. windows file-service servers: the performance required is sufficiently modest, and the demand sufficiently diffuse, that things like Which platters is this coming from never arise. But if you really want to understand your performance and bottlenecks, then you're in vendor motel land, with extra-price tools to help you. :) It's a storage cloud, and just trust us, it'll all work out. ATM. For administrators accustomed to operating the presented interface, this is not worrying. For administrators accustomed to understanding and controlling the underlying behavior, it is disconcerting, and in the way. This doesn't mean it won't be a great way to make money. The advantage to selling restricted and concealing interfaces is that you can access a market which is incompetent to challenge you, and each flaw in product version N can be a sales opportunity for N.1. Witness Windows. - Allen S. Rout
volume owner
Hello, I noticed that when I do a query ' q libv' , it shows a list of volumes with 'Private ' and 'Scratch' status. We have two instances, TSMSky and TSMSun shared the same library 3584. My question is ... 1) how do you designate ownership to volumes? 2) does the ownership change back to null, once it has returned to scratch? then TSMSky or TSMSun can claim the scratch for their use later? 3) If TSM Sky ran out of scratch volumes, will it move automatically to TSMSun to use those scratch volumes under ownership of TSMSun? tsm: TSMSkyq libv Library Name Volume Name Status Owner Last Use HomeDevice Element Type --- -- -- - --- -- SkyLTO CA0001 Scratch 1,282 LTO SkyLTO CA0002 Scratch 1,283 LTO SkyLTO CA0003 PrivateTSMSkyData 1,284 LTO SkyLTO CA0004 PrivateTSMSunData 1,288 LTO SkyLTO CA0005 Scratch 1,291 LTO SkyLTO CA0006 PrivateTSMSky Data 1,292 LTO SkyLTO CA0007 PrivateTSMSkyData 1,307 LTO SkyLTO CA0008 Scratch 1,323 LTO SkyLTO CA0009 PrivateTSMSunData 1,325 LTO SkyLTO CA0010 PrivateTSMSunData 1,326 LTO SkyLTO CA0011 Scratch 1,344 LTO Thank you. Avy Wong Business Continuity Administrator Mohegan Sun 1 Mohegan Sun Blvd Uncasville, CT 06382 ext 28164 ** The information contained in this message may be privileged and confidential and protected from disclosure. If the reader of this message is not the intended recipient, or an employee or agent responsible for delivering this message to the intended recipient, you are hereby notified that any dissemination, distribution, or copy of this communication is strictly prohibited. If you have received this communication in error, please notify us immediately by replying to the message and deleting it from your computer. **
Re: How to Incorporate a CDL into a TSM environment?
ADSM: Dist Stor Manager ADSM-L@VM.MARIST.EDU wrote on 06/12/2007 09:30:58 AM: On Mon, 11 Jun 2007 23:50:20 +0100, Neil Schofield [EMAIL PROTECTED] said: - Since the conversion of a pending delete volume to a scratch tape takes place purely in the TSM database, a virtual scratch tape will also occupy the full disk space on the VTL. until it is re-used. When DataDomain was in for a dog_and_pony_show the other day I asked about this. They claimed to be working with IBM to become application aware, so that they could release internal VTL storage when a tape goes scratch. I can see how this could be done, but I'll believe it when I see it. Rick - The information contained in this message is intended only for the personal and confidential use of the recipient(s) named above. If the reader of this message is not the intended recipient or an agent responsible for delivering it to the intended recipient, you are hereby notified that you have received this document in error and that any review, dissemination, distribution, or copying of this message is strictly prohibited. If you have received this communication in error, please notify us immediately, and delete the original message.
Re: Fw: How to Incorporate a CDL into TSM environment?
As I see it, there are two areas where you get performance hits when restoring from non-collocated volumes: 1) Tapes Mounts: In my experience my VTL makes this problem insignificant. 2) Spinning Sequential Media: Yes, VTL volumes are sequential and if you define your tapes as 50GB native and then with compression get 100GB written to the tape, you may have to spin through 99.9GB of data to retrieve a 0.1Gb file. However if you define 10GB volumes you only have to spin through 1/5 of the data to reach your 0.1GB file. Also with smaller volumes you are more likely to get natural collocation because a client that writes directly to tape is more likely to fill up a tape. Obviously if you define smaller and smaller volumes at some point you will have a tape mount bottle neck. Just one way to manage the trade offs. H. Milton Johnson -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Nicholas Cassimatis Sent: Monday, June 11, 2007 12:45 PM To: ADSM-L@VM.MARIST.EDU Subject: [ADSM-L] Fw: How to Incorporate a CDL into TSM environment? A couple of comments about what Wanda said about collocation and VTL's: At some point, you do have a finite number of mount points defined for your VTL. Even if virtual tape mounts are near instant, there is still some overhead. A large number of clients mounting virtual tape after virtual tape after virtual tape will have some sort of negative effect on the overall throughput of their sessions. I'm not saying it will be significant, but it could get there, depending on the VTL technology. A few milliseconds here, a few there, and a controller that gets bogged down under the mount request queue, you could cause yourself some issues. And don't forget that virtual tapes are the same as physical tapes in one major factor - they're sequential! So non-collocated storage pools could have multiple clients asking for the same virtual tape, so there would be a wait queue for the virtual tape. A VTL doesn't resolve this type of contention, as it's at the TSM level. I would argue that the cost of creating collocated volumes in a VTL is negligible, and still has benefits on the restore side. To echo a number of others comments in the thread - if you don't plan it out right, it's not going to work. That goes for just about anything, from vacations to VTL's! Nick Cassimatis - Forwarded by Nicholas Cassimatis/Raleigh/IBM on 06/11/2007 01:33 PM - And you don't have to collocate in a VTL, since there is zero effective tape mount time.
Re: How to Incorporate a CDL into a TSM environment?
I can't speak for everybody's product out there, but the EMC CDL (EDL) releases the used pages from the virtual volume as soon as you begin to overwrite the virtual volume from the beginning. One thing that does this is a Label Libvolume. It would be a simple script to look at all scratch tapes in the virtual library once a day, and issue a Label Libvolume on each scratch. Even in a large VTL this script would run quickly and have no impact on overall performance. Having said that, I personally don't think it is necessarily a wise thing to oversubscribe a VTL. By oversubscribe I mean to define, say, 150 virtual tapes when there would only be space for 100 virtual tapes if they were actually full. I had a customer do this once, and when the CDL became completely full TSM started getting I/O errors on all their virtual tapes, and everything went belly up, and there was no way to tell from a TSM perspective beforehand that they were getting close to full. If you are going to do this, you better set up CDL alerts and monitor the product, because TSM cannot help you monitor capacity. If you define 100 virtual tapes to a CDL that has 100 virtual tapes worth of capacity, then 'Q STGPOOL' will tell you how close to full the storage pool is, and be accurate about it. If you don't collocate this storage pool, then you ought to get virtual tapes completely filling up before you mount other virtual tapes, and thus get a fairly accurate picture of your resource consumption. Then if your reclamation is keeping up, you should be getting back scratch tapes often enough to keep up with demand. If you see the number of virtual scratch tapes deminishing over time, you are either not reclaming agressively enough, or you are outgrowing the CDL capacity and need to upgrade. Best Regards, John D. Schneider Sr. System Administrator - Storage Sisters of Mercy Health System 3637 South Geyer Road St. Louis, MO. 63127 Email: [EMAIL PROTECTED] Office: 314-364-3150, Cell: 314-486-2359 -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Richard Rhodes Sent: Tuesday, June 12, 2007 10:11 AM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] How to Incorporate a CDL into a TSM environment? ADSM: Dist Stor Manager ADSM-L@VM.MARIST.EDU wrote on 06/12/2007 09:30:58 AM: On Mon, 11 Jun 2007 23:50:20 +0100, Neil Schofield [EMAIL PROTECTED] said: - Since the conversion of a pending delete volume to a scratch tape takes place purely in the TSM database, a virtual scratch tape will also occupy the full disk space on the VTL. until it is re-used. When DataDomain was in for a dog_and_pony_show the other day I asked about this. They claimed to be working with IBM to become application aware, so that they could release internal VTL storage when a tape goes scratch. I can see how this could be done, but I'll believe it when I see it. Rick - The information contained in this message is intended only for the personal and confidential use of the recipient(s) named above. If the reader of this message is not the intended recipient or an agent responsible for delivering it to the intended recipient, you are hereby notified that you have received this document in error and that any review, dissemination, distribution, or copying of this message is strictly prohibited. If you have received this communication in error, please notify us immediately, and delete the original message.
Re: How to Incorporate a CDL into a TSM environment?
VTL and over subscription as I understand it. Definition: When (tape volume size) X (number of defined volumes) native capacity of VTL you have over subscribed. If you try to fill-up all your defined volumes to their defined native capacity you will fail as you will run out of space on your VTL. Why would one want to over subscribe? If you define a large tape volume size (i.e. 100GB), and only want to write 10GB to a tape then yes it would be neat if the VTL only allocated the actual space written to virtual tape volume (i.e. 10GB). When would this be beneficial in the TSM application? 1) TSM DB backups: Why waste a 100GB volume for one 20GB backup? 2) Using Collocation: If you collocate a client with 50GB of space then why waste a 100GB volume on the client? But the problem is as you point out, when you move a tape from pending to scratch the getting the VTL to reclaim the space previously allocated to the virtual tape volume involves: A) Checking out the scratch volume from TSM (so it will not attempt to use it during the following steps) B) Delete the volume from the VTL (this returns the space to the VTL) C) Redefining tape volume to the VTL D) Checking in and labeling the redefined volume into TSM (I imagine that a VTL could replace steps B C by truncating a volume, but you would still have to get TSM to rewrite the truncated label.) This is not a procedure I wanted to manage in a manual or automated manner, so I chose the following: 1) Define small virtual tape volumes (i.e. 10GB) 2) Do not use collocation 3) Do not over subscribe I have found tape mount time to be insignificant and the smaller virtual tape sizes to makes collocation unnecessary. This is just my way of managing the trade offs. Thanks, H. Milton Johnson -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Neil Schofield Sent: Monday, June 11, 2007 5:50 PM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] How to Incorporate a CDL into a TSM environment? Hi there We too are in the throes of a debate about virtual vs. physical tape libraries. On the VTL side, much is made of the ability to over-provision the disk capacity - eg a 100Gb virtual tape will only occupy as much space on disk as has been written to it. As a result, so the theory goes, we need only consider the occupancy when sizing the VTL. In a TSM environment, this seems to be wrong on a number of counts. - We still need to take into account the overhead of the reclaimable space on a virtual tape. This can be managed by varying the reclamation thresholds, but not eliminated. - A pending delete volume will still occupy an underlying disk capacity equivalent to its size. - Since the conversion of a pending delete volume to a scratch tape takes place purely in the TSM database, a virtual scratch tape will also occupy the full disk space on the VTL. until it is re-used. So am I correct in thinking that in the whole scratch, filling, full, reclaim, pending, delete, scratch lifecycle of a storage pool volume, the only time that we get the benefit of the over-provisioning is when it's filling? In our current physical tape environment (with collocation at the node level), only about 20% of volumes are filling. Ignoring de-dupe for now, does it seem reasonable to base the sizing for a replacement on the total physical tape capacity of the existing library and some estimates of expected growth. Regards Neil Schofield Yorkshire Water Services Ltd. - Are you a cactus or a sponge? Go to the on-line quiz at http://www.yorkshirewater.com/becool to find out how water efficient you are. Only available in Yorkshire. YORKSHIRE WATER - WINNER OF THE UTILITY OF THE YEAR AWARD 2004, 2005 AND 2006 The information in this e-mail is confidential and may also be legally privileged. The contents are intended for recipient only and are subject to the legal notice available at http://www.keldagroup.com/email.htm Yorkshire Water Services Limited Registered Office Western House Halifax Road Bradford BD6 2SZ Registered in England and Wales No 2366682
Re: volume owner
Hi, 1) You can change ownership of a scratch volume by using the 'upd libv owner= stat=' command. See help upd libv 2) Yes, the volumes used by the library client (TSMSun) will be return to the scratch pool. The scratch pool is managed by the library manager and both ITSM servers can use tapes from the same scratch pools. 3) TSMSky is the library manager and as such managing the total number of scratch tapes. If TSMSky is running out of scratch tapes, there are no scratch tapes available. Not something you would like to see happen. The q libv command will not work on the library client. Regards, Karel -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Avy Wong Sent: dinsdag 12 juni 2007 17:24 To: ADSM-L@VM.MARIST.EDU Subject: volume owner Hello, I noticed that when I do a query ' q libv' , it shows a list of volumes with 'Private ' and 'Scratch' status. We have two instances, TSMSky and TSMSun shared the same library 3584. My question is ... 1) how do you designate ownership to volumes? 2) does the ownership change back to null, once it has returned to scratch? then TSMSky or TSMSun can claim the scratch for their use later? 3) If TSM Sky ran out of scratch volumes, will it move automatically to TSMSun to use those scratch volumes under ownership of TSMSun? tsm: TSMSkyq libv Library Name Volume Name Status Owner Last Use HomeDevice Element Type --- -- -- - --- -- SkyLTO CA0001 Scratch 1,282 LTO SkyLTO CA0002 Scratch 1,283 LTO SkyLTO CA0003 PrivateTSMSkyData 1,284 LTO SkyLTO CA0004 PrivateTSMSun Data 1,288 LTO SkyLTO CA0005 Scratch 1,291 LTO SkyLTO CA0006 PrivateTSMSky Data 1,292 LTO SkyLTO CA0007 PrivateTSMSky Data 1,307 LTO SkyLTO CA0008 Scratch 1,323 LTO SkyLTO CA0009 PrivateTSMSun Data 1,325 LTO SkyLTO CA0010 PrivateTSMSun Data 1,326 LTO SkyLTO CA0011 Scratch 1,344 LTO Thank you. Avy Wong Business Continuity Administrator Mohegan Sun 1 Mohegan Sun Blvd Uncasville, CT 06382 ext 28164 ** The information contained in this message may be privileged and confidential and protected from disclosure. If the reader of this message is not the intended recipient, or an employee or agent responsible for delivering this message to the intended recipient, you are hereby notified that any dissemination, distribution, or copy of this communication is strictly prohibited. If you have received this communication in error, please notify us immediately by replying to the message and deleting it from your computer. ** ÿþD i t b e r i c h t i s v e r t r o u w e l i j k e n k a n g e h e i m e i n f o r m a t i e b e v a t t e n e n k e l b e s t e m d v o o r d e g e a d r e s s e e r d e . I n d i e n d i t b e r i c h t n i e t v o o r u i s b e s t e m d , v e r z o e k e n w i j u d i t o n m i d d e l l i j k a a n o n s t e m e l d e n e n h e t b e r i c h t t e v e r n i e t i g e n . A a n g e z i e n d e i n t e g r i t e i t v a n h e t b e r i c h t n i e t v e i l i g g e s t e l d i s m i d d e l s v e r z e n d i n g v i a i n t e r n e t , k a n A t o s O r i g i n n i e t a a n s p r a k e l i j k w o r d e n g e h o u d e n v o o r d e i n h o u d d a a r v a n . H o e w e l w i j o n s i n s p a n n e n e e n v i r u s v r i j n e t w e r k t e h a n t e r e n , g e v e n w i j g e e n e n k e l e g a r a n t i e d a t d i t b e r i c h t v i r u s v r i j i s , n o c h a a n v a a r d e n w i j e n i g e a a n s p r a k e l i j k h e i d v o o r d e m o g e l i j k e a a n w e z i g h e i d v a n e e n v i r u s i n d i t b e r i c h t . O p a l o n z e r e c h t s v e r h o u d i n g e n , a a n b i e d i n g e n e n o v e r e e n k o m s t e n w a a r o n d e r A t o s O r i g i n g o e d e r e n e n / o f d i e n s t e n l e v e r t z i j n m e t u i t s l u i t i n g v a n a l l e a n d e r e v o o r w a a r d e n d e L e v e r i n g s v o o r w a a r d e n
Fw: How to Incorporate a CDL into TSM environment?
I'm not looking at the spinning through the volume to find the file, I'm focused on the fact that a volume can only be accessed by one client at a time. You have to read the data to be restored, which takes time. If you have one client reading the volume, any other access to that volume has to queue up. With a slow client (or a fast one pulling a large file), you can develop some access contention, which is a bottleneck that collocation resolves. That's why I still see collocation playing with VTL's. It all comes back to Why do you want a VTL? which is another way of asking, What problem are you trying to solve/avoid? I'm sure there are people who are getting VTL's because they have to spend their budget or they lose it - and the rest of us are jealous of them for that! But, as with most other technologies, implementing a VTL just moves the bottleneck/weakest link to another spot, which may not be the best solution for a given environment. Nick Cassimatis - Forwarded by Nicholas Cassimatis/Raleigh/IBM on 06/12/2007 11:41 AM - ADSM: Dist Stor Manager ADSM-L@VM.MARIST.EDU wrote on 06/12/2007 11:13:30 AM: As I see it, there are two areas where you get performance hits when restoring from non-collocated volumes: 1) Tapes Mounts: In my experience my VTL makes this problem insignificant. 2) Spinning Sequential Media: Yes, VTL volumes are sequential and if you define your tapes as 50GB native and then with compression get 100GB written to the tape, you may have to spin through 99.9GB of data to retrieve a 0.1Gb file. However if you define 10GB volumes you only have to spin through 1/5 of the data to reach your 0.1GB file. Also with smaller volumes you are more likely to get natural collocation because a client that writes directly to tape is more likely to fill up a tape. Obviously if you define smaller and smaller volumes at some point you will have a tape mount bottle neck. Just one way to manage the trade offs. H. Milton Johnson
Re: Fw: How to Incorporate a CDL into TSM environment?
Yes a virtual tape volume can be accessed only by one client at a time and if two processes/clients try to access the same volume at the same time one process/client must wait. Again smaller volume sizes decreases the chance that a contention would happen and also decrease the contention duration. Why a VTL? With us we found that when we out grew our physical library we would have to have to buy over 30 physical drives in order to be able to do backups, restores, cut off-site tapes and reclaim on/off site tapes in the time allowed. That amounted to some serious money, more than our VTL costs. When you also take into account the costs of the much larger DISKPOOL a physical tape library requires, growing a physical tape library in a TSM environment is not cheap. The VTL footprint is also smaller which also should considered in the total cost of ownership. Sorry, but we had to justify our VTL purchase. Thanks, H. Milton Johnson -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Nicholas Cassimatis Sent: Tuesday, June 12, 2007 10:55 AM To: ADSM-L@VM.MARIST.EDU Subject: [ADSM-L] Fw: How to Incorporate a CDL into TSM environment? I'm not looking at the spinning through the volume to find the file, I'm focused on the fact that a volume can only be accessed by one client at a time. You have to read the data to be restored, which takes time. If you have one client reading the volume, any other access to that volume has to queue up. With a slow client (or a fast one pulling a large file), you can develop some access contention, which is a bottleneck that collocation resolves. That's why I still see collocation playing with VTL's. It all comes back to Why do you want a VTL? which is another way of asking, What problem are you trying to solve/avoid? I'm sure there are people who are getting VTL's because they have to spend their budget or they lose it - and the rest of us are jealous of them for that! But, as with most other technologies, implementing a VTL just moves the bottleneck/weakest link to another spot, which may not be the best solution for a given environment. Nick Cassimatis - Forwarded by Nicholas Cassimatis/Raleigh/IBM on 06/12/2007 11:41 AM - ADSM: Dist Stor Manager ADSM-L@VM.MARIST.EDU wrote on 06/12/2007 11:13:30 AM: As I see it, there are two areas where you get performance hits when restoring from non-collocated volumes: 1) Tapes Mounts: In my experience my VTL makes this problem insignificant. 2) Spinning Sequential Media: Yes, VTL volumes are sequential and if you define your tapes as 50GB native and then with compression get 100GB written to the tape, you may have to spin through 99.9GB of data to retrieve a 0.1Gb file. However if you define 10GB volumes you only have to spin through 1/5 of the data to reach your 0.1GB file. Also with smaller volumes you are more likely to get natural collocation because a client that writes directly to tape is more likely to fill up a tape. Obviously if you define smaller and smaller volumes at some point you will have a tape mount bottle neck. Just one way to manage the trade offs. H. Milton Johnson
Old clients
Hello TSMers, Does any one have a TSM server 5.4 backing up old TSM clients(4.1, 4.2 and 5.1) AIX 4.3 , HPUX, windows NT 4.0 I am planning to upgrade from 5.2 to 5.4 Your help is greatly appreciated. TIA, Best regards, Daad - Be smarter than spam. See how smart SpamGuard is at giving junk email the boot with the All-new Yahoo! Mail - Ask a question on any topic and get answers from real people. Go to Yahoo! Answers.
Date correction: Next IBM TSM web seminar June 13TH!
The date I posted yesterday was incorrect, it is instead June 13th. Please update your calendars. Topic: Windows Active Directory for TSM Backup/Archive Clients This Support Technical Exchange presentation will cover restoring a Windows Active Directory on Windows 2003 using the Tivoli Storage Manager Backup/Archive Clients. Please prepare your system at this url prior to attending, as we are also premiering a new web seminar technology: http://asp22.centra.com/SiteRoots/main/SystemCheck/SystemCheck.jhtml? Please call into the phone conference and join the e-meeting 10 minutes early. Web conference URL: http://asp22.centra.com/GA/main/001ed7ac0112c6d5b6479f3e Password: tiv0li View presentation: http://www.ibm.com/support/docview.wss?rs=0uid=swg27009876 - Yahoo! oneSearch: Finally, mobile search that gives answers, not web links.
Re: Define path problems
Just an update for this issue. The problem has been resolved. It seems like it was a library firmware issue. The fix was to downgrade the firmware to version 5770. The replaced drive then updated properly, and the proper serial number was displayed using the web interface. By downgrading the library firmware it did give me problems with my other gen 2 fiber drives though, so firmware was then brought back up to the highest level. After this I was then able to define the drive properly, and bring it back online. Hopefully future firmware revisions will address this. Thanks to all for the info. Cheers, Chris Chris McKay writes: Yes, I tried both serial and element=autodetect ADSM: Dist Stor Manager ADSM-L@VM.MARIST.EDU writes: It sounds like the serial information to me. Did you try the serial=autodetect when defining it? I had to do this the last time I added some LTO3 drives. On 6/12/07, Chris McKay [EMAIL PROTECTED] wrote: We did recently update the firmware on both the library, and the drives, also updated the changer and tape device drivers on the server as well. ADSM: Dist Stor Manager ADSM-L@VM.MARIST.EDU writes: Hi, By any change has there been a hardware change? - delete drive from ITSM config, - reboot Windows - define drive serial=autodetect - define path to drive Regards, Karel -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Chris McKay Sent: dinsdag 12 juni 2007 14:25 To: ADSM-L@VM.MARIST.EDU Subject: Define path problems Hi All, I am having problems with replacing a SCSI LTO tape drive in my 3584 library. Usually a routine procedure, but this time I am having major difficulties. Whenever I try to redefine the path for this particular drive I get the following error: ANR8972E DEFINE PATH: Unable to find the element number for drive DRIVE3 in library 3584LIB I have been talking with both TSM software support, and hardware support, and still not much luck. The drive is being detected by the server properly, and the library detects the drive fine as well. We have tried two different drives as well. I did notice the library specialist does report a different serial number than the library itself reports though.. The server is Windows 2000. Has anyone seen this before? Any ideas??? Take Care, Chris Chris McKay Systems Administrator York Catholic District School Board __ This message is for the sole use of the intended recipients and may contain confidential and privileged information. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not an intended recipient, please contact the sender by reply email and destroy all copies of the original message. Thank you for your cooperation. __ This message is for the sole use of the intended recipients and may contain confidential and privileged information. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not an intended recipient, please contact the sender by reply email and destroy all copies of the original message. Thank you for your cooperation. __ This message is for the sole use of the intended recipients and may contain confidential and privileged information. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not an intended recipient, please contact the sender by reply email and destroy all copies of the original message. Thank you for your cooperation.
Re: Date correction: Next IBM TSM web seminar June 13TH!
What time on the 13th. please. Thanks Justin Case -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Darrius Plantz Sent: Tuesday, June 12, 2007 1:14 PM To: ADSM-L@VM.MARIST.EDU Subject: Date correction: Next IBM TSM web seminar June 13TH! The date I posted yesterday was incorrect, it is instead June 13th. Please update your calendars. Topic: Windows Active Directory for TSM Backup/Archive Clients This Support Technical Exchange presentation will cover restoring a Windows Active Directory on Windows 2003 using the Tivoli Storage Manager Backup/Archive Clients. Please prepare your system at this url prior to attending, as we are also premiering a new web seminar technology: http://asp22.centra.com/SiteRoots/main/SystemCheck/SystemCheck.jhtml? Please call into the phone conference and join the e-meeting 10 minutes early. Web conference URL: http://asp22.centra.com/GA/main/001ed7ac0112c6d5b6479f3e Password: tiv0li View presentation: http://www.ibm.com/support/docview.wss?rs=0uid=swg27009876 - Yahoo! oneSearch: Finally, mobile search that gives answers, not web links.
Re: Define path problems
good to know thanks! On 6/12/07, Chris McKay [EMAIL PROTECTED] wrote: Just an update for this issue. The problem has been resolved. It seems like it was a library firmware issue. The fix was to downgrade the firmware to version 5770. The replaced drive then updated properly, and the proper serial number was displayed using the web interface. By downgrading the library firmware it did give me problems with my other gen 2 fiber drives though, so firmware was then brought back up to the highest level. After this I was then able to define the drive properly, and bring it back online. Hopefully future firmware revisions will address this. Thanks to all for the info. Cheers, Chris Chris McKay writes: Yes, I tried both serial and element=autodetect ADSM: Dist Stor Manager ADSM-L@VM.MARIST.EDU writes: It sounds like the serial information to me. Did you try the serial=autodetect when defining it? I had to do this the last time I added some LTO3 drives. On 6/12/07, Chris McKay [EMAIL PROTECTED] wrote: We did recently update the firmware on both the library, and the drives, also updated the changer and tape device drivers on the server as well. ADSM: Dist Stor Manager ADSM-L@VM.MARIST.EDU writes: Hi, By any change has there been a hardware change? - delete drive from ITSM config, - reboot Windows - define drive serial=autodetect - define path to drive Regards, Karel -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Chris McKay Sent: dinsdag 12 juni 2007 14:25 To: ADSM-L@VM.MARIST.EDU Subject: Define path problems Hi All, I am having problems with replacing a SCSI LTO tape drive in my 3584 library. Usually a routine procedure, but this time I am having major difficulties. Whenever I try to redefine the path for this particular drive I get the following error: ANR8972E DEFINE PATH: Unable to find the element number for drive DRIVE3 in library 3584LIB I have been talking with both TSM software support, and hardware support, and still not much luck. The drive is being detected by the server properly, and the library detects the drive fine as well. We have tried two different drives as well. I did notice the library specialist does report a different serial number than the library itself reports though.. The server is Windows 2000. Has anyone seen this before? Any ideas??? Take Care, Chris Chris McKay Systems Administrator York Catholic District School Board __ This message is for the sole use of the intended recipients and may contain confidential and privileged information. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not an intended recipient, please contact the sender by reply email and destroy all copies of the original message. Thank you for your cooperation. __ This message is for the sole use of the intended recipients and may contain confidential and privileged information. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not an intended recipient, please contact the sender by reply email and destroy all copies of the original message. Thank you for your cooperation. __ This message is for the sole use of the intended recipients and may contain confidential and privileged information. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not an intended recipient, please contact the sender by reply email and destroy all copies of the original message. Thank you for your cooperation.
Re: Fw: How to Incorporate a CDL into TSM environment?
On Tue, 12 Jun 2007 12:16:27 -0400, Johnson, Milton [EMAIL PROTECTED] said: Why a VTL? With us we found that when we out grew our physical library we would have to have to buy over 30 physical drives in order to be able to do backups, restores, cut off-site tapes and reclaim on/off site tapes in the time allowed. That amounted to some serious money, more than our VTL costs. I'm interested in the details on this. The VTL is disk-only, or is it tape backed? I'm confused about how you need fewer tape-head-hours when you virtualize processes. - Allen S. Rout
