Re: TS3310 and T038 Write Protect Message

Whereas you've verified that the write-protect tab is properly set for R/W, you need to examine your logging to see if there is one drive or multiple exhibiting the Write Protected condition. If one drive, there may be a sensor issue. If multiple, it may be a microcode defect issue. LTO5 is

TS3310 and T038 Write Protect Message

Thanks. Yes, I have already ascertained that it is more than one drive - all 4 in fact. It is looking like a firmware issue the more things I try. Fortunately this is not in production yet so can 'play a bit' but we need it in production asap. I will probably have to test the drives like you

Re: TS3310 and T038 Write Protect Message

On Jan 25, 2011, at 7:48 AM, BENSHADE wrote: Thanks. Yes, I have already ascertained that it is more than one drive - all 4 in fact. It is looking like a firmware issue the more things I try. Fortunately this is not in production yet so can 'play a bit' but we need it in production asap.

inconsistencies between tsm and tape labels

Have a tape A00521 which TSM states is part of stgpool nt_tape It was last written on 12/28/2010. During last reclaim we got an 813 abend in Z/OS IEC149I 813-04,IFG0195H,ADSM,SERVER,SYS01467,0911,A00521,NT.BFS, LBL=OMSC.BFS T01D10E Close Bypassed/NOT processed, Open NOT seen: Vol=A00521,

Directory layout for tsm server v6.2 on linux platform

Finally got the tsm server install to run on our redhat enterprise linux v6 server. I am now confused on what the correct directory layout should be for a server instance. I went through the manual process of creating an instance, but when finished, there were a number of problems. 1.

3494 tape dismount problem

TSM 5.5.2 on Windows 3494 classic (aka old) tape library with TCP/IP connection for the robot, four fibre-connected 3592-E05 drives. A couple of times a week, a tape gets left in drive 4; always that drive, different cartridges. I say left instead of stuck, as there are no dismount errors in

Re: 3494 tape dismount problem

Did you check to make sure the drive is securely tightened down... I had a 3494 that the little screws to tighten the drive's slide rails would be loose and as the gripper would come forward to grab the tape, rather than the tape going into the gripper, it would push the tape drive back just a

Re: 3494 tape dismount problem

I haven't used them in a while but there may be a mtlib command that could check to see if the 3494 still shows the tape mounted in the drive after you get the ANR8468I message. -Original Message- From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Prather, Wanda

Re: 3494 tape dismount problem

Will do! Thanks Dwight! -Original Message- From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Dwight Cook Sent: Tuesday, January 25, 2011 4:02 PM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] 3494 tape dismount problem Did you check to make sure the drive is

Exchange 2010 and TDP / VSS

I browsed the fine manual but was hoping to gain a little insight from other experiences. I understand that it's no longer a streaming backup, it's a VSS software snap. Does anyone know how long the Exchange DB's are in a guessed state? Does it depend on the DB size or does VSS get a snap and

Re: Exchange 2010 and TDP / VSS

I browsed the fine manual but was hoping to gain a little insight from other experiences. I understand that it's no longer a streaming backup, it's a VSS software snap. Does anyone know how long the Exchange DB's are in a guessed state? Do you mean quiesced state? Writes to the disk are

Volume unavailable.

Hi Great forum, some very good answers. I learn a lot. I have a volume, the volume is unavailable: 08:11:05 TSMSRV01 : q vol * acc=unavail Volume Name Storage Device EstimatedPct Volume

Re: Volume unavailable.

Hi Alex, Check whether the volume is available in the Tape library list? If you try to restore data from volume which is not physically available in the tape library, system will mark it as unavailable. You need to get the tape from offsite, load it to your tape library and change

auto deploy 6.2.2 client

Hi I 'm having problems with the auto deploy feature in Admin Center 6.2.2. There seems to be a problem with case sensitive filenames. Admin Center succeeds with downloading the older clients, but not the 6.2.2 client. The file names Admin Center tries to download are:

Re: Volume unavailable.

Hi Alex, did you check your TSM server's activity log for responses/error messages related to the 'upd vol' and 'checkin' commands you gave? There might be more useful information to find. best regards, Rainer -Original Message- From: ADSM: Dist Stor Manager