12-10-2014 07:05 AM
unable to allocate resources for diagnostics
I get the above error when I attempt to diagonise drives.
Any ideas?
Scan shows all the drives
Info:
Symantec Netbackup 7.5.0.6
Windows server 2008 r2 is the OS
Solved! Go to Solution.
12-11-2014 01:46 AM
As per my post above - the best test is to perform backups and restores.
I have also suggested that you have a look at the steps listed for diagnostics in NBU Admin Guide.
But in all honesty - I have NEVER seen anyone using these NBU diagnostics.
Do backups and restores to test your devices or use the tools provided by the library vendor.
12-10-2014 08:37 AM
Is this the "diagnstic" when right clicking on a drive in the device monitor ?
What type of robot do you have (model and vendor) ?
As I re-call only TLD types of robots are supported -but I may be wrong.
12-10-2014 08:38 AM
Never used that before, just tried it on i500 and it failed with error 810 even though the library was just serviced and backups are running fine.
12-10-2014 10:02 AM
Hi,
Is the Master and media servers are same..?
did you try with vmoprcmd -d and tpconfig -d commands
are the drives are showing online or AVR mode..?
also try nbemmcmd -getemmserver
Please paste all these reports here.
12-10-2014 10:40 AM
Do you have test media in order to perform diagnostics?
Have you reviewed the steps to be followed in NBU Admin Guide I?
If I may ask - what is the purpose of the diagnostics test?
Best possible test for a tape drive and media is a backup and restore.
12-10-2014 01:49 PM
Please use the diagnostics that are supplied by your drive manufacturer.
Follow the instructions found in the documentation for your hardware.
If the drives are part of a robotic library there is usually a nice interface to check for alerts and pull log files.
If the drive is a standalone drive you will have to download the software from the manufacturers website and install on the media server that is physically attached to the drives.
Work with your hardware supplier to resolve hardware issues.
12-11-2014 12:39 AM
I tried vmoprcmd -d and tpconfig -d commands.
Both shows all drives and status is UP. They are all online.
nbemmcmd -getemmserver returns error. 'nbemmcmd' not recognised
12-11-2014 12:40 AM
TLD
12-11-2014 12:44 AM
nbemmcmd -getemmserver returns error. 'nbemmcmd' not recognised
This command has nothing to do with physical devices and/or diagnostics.
nbemmcmd command is in <install-path>\veritas\netbackup\bin\admincmd.
If you have a W2008 server, open cmd with 'Run as Administrator'.
12-11-2014 12:50 AM
The purpose:
I removed the drives and added them again and wanted to check if they were fine.
12-11-2014 01:46 AM
As per my post above - the best test is to perform backups and restores.
I have also suggested that you have a look at the steps listed for diagnostics in NBU Admin Guide.
But in all honesty - I have NEVER seen anyone using these NBU diagnostics.
Do backups and restores to test your devices or use the tools provided by the library vendor.
12-11-2014 06:00 AM
The status has nothing to do with the health of the drive. UP means that Netbackup will send jobs to that device. If you determine that the drive needs servicing, by using the manufacturers diagnostic tools, then you want to set the device to DOWN until the drive is fixed or replaced. This will prevent Netbackup from trying to use the faulty hardware.