09-22-2015 10:26 PM
Hi All,
I'm new here in Netbackup. Kindly help me out to fix this issue.
We are using Netbackup 7.5, in our environment both the master and media server are the same, we have 4 drives out of which 2 drives goes down frequently.
We had even tried to start up the drive manually but again its going down.
Kindly help me out in this issue, with the basic troubleshooting too..
Solved! Go to Solution.
10-05-2015 01:58 AM
So... now you have a problem with the robot....
The OS has lost connection to the robot. One of these could be the issue:
It is probably time that you log a call with the hardware vendor.
Almost 2 weeks and close to 40 comments later and we are no closer to finding a solution than the day you started this discussion......
10-05-2015 02:04 AM
Dear Marianne,
I had already logged a call with h/w vendor and shared the library logs, they had mentioned there is no h/w errors, and they had mentioned the 3drives shows cleaning needed.
Clean the drives using cleaning tapes and rebot the TL is what they had sugested.
As i'm new to symantec as well as TL i'm stugling out here. :(
10-05-2015 02:48 AM
Have you tried in the meantime to see why the OS lost connection to the robot?
When troubleshooting devices, best to 'forget' about NetBackup and troubleshoot at OS-level.
To quote from an old Status 84 In-depth Troubleshooting doc:
As an application, NetBackup has no direct access to a device, instead relying on the operating system (OS) to handle any communication with the device.
This means that during a write operation NetBackup asks the OS to write to the device and report back the success or failure of that operation. If there is a failure, NetBackup will merely report that a failure occurred, and any troubleshooting should start at the OS level.
If the OS is unable to perform the write, there are three likely causes; OS configuration, a problem on the SCSI path, or a problem with the device.
10-05-2015 09:43 PM
Dear All,
I found drive control shows AVR (which means the robot is not communicating with the backup server)
i had run 'scan' from cmd and got the attached output (2days before when i run the scan cmd i got the diff output)..
10-05-2015 09:46 PM
Kindly help me out how can i make sure that its the issue in communication between the robot and the backup server and how what steps to do further??
10-05-2015 11:26 PM
Reboot the library (proper power cycle, off/ on) and the robot control host as well.
Do you then see the library in :
1) Device manager
2) scan
(1) MUST work before (2) will work.
10-05-2015 11:30 PM
10-05-2015 11:52 PM
Thanks Marianne and mph, as the DC in remote and I have to go there physically and check the physical connectivity and reboot.
Will update if it works.
10-06-2015 12:25 AM
Martin/Marianne,
Do you have any links (SOP) to reboot the IBM ULT3580-HH5 TL gracefull shutdown and starting up?
Which will help me out for gracefull shutdown and start
10-06-2015 12:40 AM
Search IBM site or Google for IBM ULT3580-HH5 TL user manual.
10-08-2015 12:12 AM
10-08-2015 12:30 AM
Right-click on the Active job in Activity Monitor and select Cancel.
10-09-2015 01:46 AM
Dear Marianne & All,
Thanks for your help.
After rebooting the TL. The communication between the robot and the backup server worked, once the communication happened, I tried cleaning the drives in IBM TL itself (not in symantec). All drive cleaning is done, now the drive is up and running fine.
Once again thanks all..
10-09-2015 02:21 AM
10-09-2015 09:02 AM
Surely not just yet? Isn't there the question of a split solution, like six ways ! :D