Re: [ADSM-L] Replacing tape drives (or "there has to be a better way")

Subject: Re: [ADSM-L] Replacing tape drives (or "there has to be a better way")
Date: 2009-07-09 06:57:27
From: Nicholas Rodolfich
Permanent Link: http://www.backupinsight.com/openservices/ml/5c93d47f1

Sean,

Not much help to offer here but, I have been involved in many LTO drive=

replacements in 3584s and have never changed any hardware serial number=
.
The only serial number that needs to change is the one TSM is using in =
its
drive definition which should automatically get picked up on the TSM dr=
ive
redefine if your hardware firmware is operating properly. I would have =
CE
run a full calibrate on your library and check your firmware levels on
library and drives for currency.

Regards,

Nicholas


"ADSM: Dist Stor Manager"  wrote on 07/09/2009
08:14:28 AM:

> [image removed]
>
> Re: [ADSM-L] Replacing tape drives (or "there has to be a better way"=
)
>
> Hart, Charles A
>
> to:
>
> ADSM-L
>
> 07/09/2009 08:16 AM
>
> Sent by:
>
> "ADSM: Dist Stor Manager" 
>
> Please respond to "ADSM: Dist Stor Manager"
>
> Dumb ? - But I was under the impression that the TS3500 (3584)'s driv=
e
> Serial Numbers were tied to the Drive Cage (rail) so the SN and WWN w=
ere
> static... Maybe I'm thinking 3494 w/ 3592 Drives.
>
> -----Original Message-----
> From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf=
 Of
> Baker, Jane
> Sent: Thursday, July 09, 2009 2:52 AM
> To: ADSM-L@VM.MARIST.EDU
> Subject: Re: [ADSM-L] Replacing tape drives (or "there has to be a
> better way")
>
>
>
> We use LTO2 & LTO3 in a 3584 and the CE always sets the serial number=
 to
> match the old one so that we don't have this problem, same as Sean.
>
> Regards,
> Jane.
>
>
>
> -----Original Message-----
> From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf=
 Of
> Len Boyle
> Sent: 08 July 2009 18:30
> To: ADSM-L@VM.MARIST.EDU
> Subject: Re: [ADSM-L] Replacing tape drives (or "there has to be a
> better way")
>
> In fact we found out that for lto-3 and lto-4 tape drives in an IBM 3=
584
> library,  it is required that they change the serial number to match =
the
> old tape drive. Because IBM tracks the drives by serial number for ma=
int
> contracts. This we found when the serial numbers that we send in for =
a
> maint contract renewal were kicked out as field engineering  had not
> been updating the serial numbers. But not for lto-2 tape drives.
>
> len
>
> -----Original Message-----
> From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf=
 Of
> Sean English
> Sent: Wednesday, July 08, 2009 11:47 AM
> To: ADSM-L@VM.MARIST.EDU
> Subject: Re: [ADSM-L] Replacing tape drives (or "there has to be a
> better way")
>
> Zoltan,
>
> The majority of our TSM servers are AIX and we do have a setup where =
we
> share multiple library clients with one library.  When we have IBM CE=
s
> come out and replace drives, they just change the serial number on th=
e
> new drive to match the old drive they are replacing.  Apparently ther=
e
> is a way to do that on the drive itself.
>
> Thanks,
> Sean
>
>
>
>
>
>
> Zoltan Forray/AC/VCU 
> Sent by: "ADSM: Dist Stor Manager" 
> 07/08/2009 11:30 AM
> Please respond to
> "ADSM: Dist Stor Manager" 
>
>
> To
> ADSM-L@VM.MARIST.EDU
> cc
>
> Subject
> [ADSM-L] Replacing tape drives (or "there has to be a better way")
>
>
>
>
>
>
> I need thoughts/suggestions/help on how to deal with SAN attached tap=
e
> drive replacements when a library is shared amongst 5-servers.
>
> We just has a drive replaced, therefore giving us a new serial number=

> (3494ATL - TS1130).  All servers that use these drives/libraries are
> RedHat Linux and use very current lin_tape drivers.
>
> Currently, the method we use is to bounce each server so the system
> rescans the SAN and gets the new serial number.
>
> In the past, just stopping the TSM server and then restarting the
> lin_tape driver would often be enough. Now with the latest lin_tape
> drivers, I don't see the lin_taped daemon running any more.
>
> Yes, I have tried updating the paths on the library manager server an=
d
> telling it to autodetect but that didn't help.
>
> There has to be a better way!  If you have a similar configuration, h=
ow
> do you handle this scenario?
>
>
> Please check that this email is addressed to you. If not, you should
> delete it immediately as its contents may be confidential and its
> disclosure, copying or distribution unlawful.
>
> C. & J. Clark International Limited takes steps to prevent the
> transmission of electronic viruses but responsibility for screening
> incoming messages and the risk of such transmission lies with the
> recipient.
>
> C. & J. Clark International Limited Trading as Clarks Registered in
> England number 141015.
> Registered office 40 High Street, Street, Somerset. BA16 0EQ. England=
.
>
> This message has been scanned for viruses by BlackSpider MailControl =
-
> www.blackspider.com
>
> This e-mail, including attachments, may include confidential and/or
> proprietary information, and may be used only by the person or entity=

> to which it is addressed. If the reader of this e-mail is not the
intended
> recipient or his or her authorized agent, the reader is hereby notifi=
ed
> that any dissemination, distribution or copying of this e-mail is
> prohibited. If you have received this e-mail in error, please notify =
the
> sender by replying to this message and delete this e-mail immediately=
.=