Library not 'ready' in 7.5.2?

Question

Recently, within the past couple of weeks, our library will either never go ready, or take a very long time to go ready after a reboot. Two things have happened since this began, one is uprade to 7.5.2 (build 463), and of course, an update to our tape library (Spectralogic T950). I have a sev1 open with Legato, but have gotten nowhere - their official response is that there is nothing that they can do. Nice. Even if it is a problem with the library, Networker support should be able to tell me what Networker is looking for (from the T950) in order to make it "ready". STill waiting on that one.

Anyone have any ideas??

masonb · Accepted Answer

David,

For the library to become ready within NetWorker it must be able to gain the status of all the drives and "slots (or volumes)" within it. If there is a hardware issue with one of the drives or any volume status cannot be reported for some reason the library will not become ready within the software. I would start by checking the library is reporting online from the panel or Web interface, then check the drive status with the mt command from the NetWorker server or storage node. and also see if you can compare the output from sjirdtag b.t.l (where b.t.l is the scsi address of the robotic arm - can be seen in inquire or jukebox resource via NMC usually with that of library web interface or see if you can see anything which looks incorrect.

These changes were made to stop NetWorker getting out of sync when the software was stopped and manual changes were made on the library we did not know about. It has caused some issues on Customer sites with hardware issues etc making some libraries not ready as the status checks cannot complete.

Regards,

Bill Mason

SME - Advanced Technical Support

EMC Global Services

Problem Resolution and Escalation Management (PREM)

BURA Software Solutions Group (BSSG)

Office: 44 (0) 208-758-6452

North America Support Line: 1-877-534-2867

mason_bill@emc.com

Please note my regular working hours are Monday to Friday, 07:30am to 14:00 pm GMT, 16:00 pm to 18:00 pm GMT

Please submit all new cases, updates or attachments to existing cases via EMC Powerlink http://powerlink.emc.com/

For new issues & questions, EMC Customer Service is pleased to offer you the support option of Live Chat 24x7 for select products.

To interact with our technical support professionals please visit the Networker Support landing page and select ‘Live Chat’ under Additional Resources.

For a single location for you to gain access to all key Support-related resources on Powerlink related to Networker & Avamar, please check out the appropriate landing page:

EMC Networker Support landing page at: https://support.emc.com/products/NetWorker

EMC Avamar Support landing page at: https://support.emc.com/products/Avamar

Satisfied customers are my top priority. For service feedback & comments, please contact my manager:

Mary ODonoghue - ODonoghue_Mary@emc.com

Holger_Inf · Answer

You can eliminate the option, that the reason is the update of NetWorker to 7.5.2, if you check the old version again.

Just stop services, move nsr directory to a new name/safe place and install the pre-update veriosn (which one was it?)

configure the library and check if it become ready that fast as you expect it.

On which OS and architecture does your NetWorker run?

noladave · Answer

Bill, thank you for your response.&#xa0;&#xa0; My complaint on this board Wednesday yielded a call from a service manager Thursday, and he was able to send my ticket to a 2nd tier engineer, and within 5 minutes of discussion, he realized it was a SCSI address issue.&#xa0;&#xa0; This apparently (not 100% sure) was caused from applying Windows updates Tuesday night.&#xa0;&#xa0; We believe there was something in the Windows update that caused this, so we are searching for the right update to remove.In the meantime, if this happens again, all we have to do is run the inquire command, find the right scsci address for the control port of the library, and then it will go into a 'ready' state within seconds.&#xa0; The 100% correct fix, is to delete the libarary and recreate it, so we will be keeping our reboots to a minimum until this gets resolved.Now the real fun begins looking through all of the windows updates...&#xa0; Thanks,- Dave.

NetWorker

Library not "ready" in 7.5.2?

Was this post helpful?