Netbackup Error 297 and more

Not sure why you went this far as status 297 does not seem to be serious.
Nothing to do with 'disc' or devices, but with tapes (media).

Extract from Status Guide manual:

NetBackup status code: 297

Message: all volumes are not available to eject
Explanation: This error occurs when an try is made to eject a non-existent or bad
media ID during the eject phase of the following: a Vault session, a vlteject
command, or a vltopmenu command.

Possible reasons for this error are as follows:
■ The bad media ID was added by means of the vlt_ejectlist_notify script.
■ The bad media ID is already in the MAP or not in the robotic library.
■ The bad media ID is in a robotic drive.
■ The bad media ID is in transit in the robotic library.

Recommended Action: Remove or correct the defective media ID from the
vlt_ejectlist_notify script and rerun the Vault session. If the bad media ID is
in the MAP or a drive or in transit, something is misconfigured.

Are there any hardware related errors in Windows Event Viewer?

Is Windows Removable Storage Manager service stopped and disabled?

Can the Windows Device Manager see the robot?

(Best to delete existing Medium Changer and Tape Drives, then rescan to ensure correct info is seen at OS level.)

If devices are not seen in Device Manager, you need to check the robot display panel for errors and also physical connection.
Try to reboot the robot.

If Device Manager sees the devices, see if they respond to scsi_commands.
From cmd, cd to <install-path>\veritas\volmgr\bin.
Run 'scan' command.

If nothing is displayed, there is something wrong with the hardware - either connection or devices.
Log a call with your hardware support team.

Only when 'scan' reports the robot and tape drive(s) should you add the devices back in NBU.
Start the Device Config Wizard in the main section of the GUI.

PS: 
You (and your management) are hopefully aware that Microsoft will shortly be ending W2003 support?

Thanks for the detailed info 4 days later.

Your opening post did not include the error message. 
Unkown drive name (297)

There are different status codes for NBU, Media Manager , Device Configuration, Robotic Status codes, robotic error codes.

Sorry, was sadly gone without possiblity of a computer close by

https://support.symantec.com/en_US/article.TECH160255.html
 

As the firmware has been updated, the drive will need to be deleted and re-added into NetBackup.

according to the support file thats why i did as i did

Issue began that we had a No Pathing issue and i noticed in the event viewver in Windows that we had some hardware issues, so i called in the Support ( procedures ) and we found out that we had some Hardware issues in one of the tapes.
This issue is resolved and then we did a Firmware update thats when we started to get the error message
Quote from the article:
After upgrading the tape drive firmware, the drives remain in a DOWN state in Netbackup. Attempting to UP the drive returns the following error

Unkown drive name (297)

Thats when i tried to delete the drive NetBackup Administration Console > Media and Device managment > Devices > Drives and remove it from there and readd it

Im a complete novice with Netbackup so im not sure if i have even searched the correct error data bases, but its spoton with our error message, sorry if i didnt clarify it as im not to sure what information to give out yet.

About the Windows Server 2003 we are going to upgrade it at the end of summer but thanks for the warning :)

Regards.

OK, how many robots do you have and how many drivs ?

Are these drives shared between media servers.

Running vmoprmcd command will show this, it is in the <install path>\veritas\volmgr\bin directory - run this command on the master and add the output as an attachment to this thread.

Ideally, run nbsu -c -t

cd <install path>\veritas\netbackup\bin\support

Run the command above, the output is put into the output dir, have a look in there and collect the output for the date you ran the command (could be more than one output in there if it has been run in the past).

Also, check in windows device manager that the OS sees all the drives - this is vital.

If it's a simple setup (eg one robot and not shared across more than a few media servers) I would personnally just delete everything and reconfigure, but this is dependant on the OS of each media server seeing all the devices (drives) correctly.

Only one Drive for now, we will get a replacement drive in a few work days as a replacement we got one Robot i will run the command tomorrow as im at another client for the rest of the day.

Reconfiging is a option according to my supervisor at this company if needed but i will fill in with more information tomorrow when im back at the company.

 

Apart from Status Code extract for NBU status code 297, the rest of my post regarding devices is still applicable (that is actually what I typed up initially and afterwards looked at the NBU Status Code manual) :

Are there any hardware related errors in Windows Event Viewer?

Is Windows Removable Storage Manager service stopped and disabled?

Can the Windows Device Manager see the robot?

(Best to delete existing Medium Changer and Tape Drives, then rescan to ensure correct info is seen at OS level.)

If devices are not seen in Device Manager, you need to check the robot display panel for errors and also physical connection.
Try to reboot the robot.

If Device Manager sees the devices, see if they respond to scsi_commands.
From cmd, cd to <install-path>\veritas\volmgr\bin.
Run 'scan' command.

If nothing is displayed, there is something wrong with the hardware - either connection or devices.
Log a call with your hardware support team.

Only when 'scan' reports the robot and tape drive(s) should you add the devices back in NBU.
Start the Device Config Wizard in the main section of the GUI.

Update
mph999:
i ran run nbsu -c -t in the correct path and recieved alot of information, been reading throu most of the logs not entirely sure what to look for exact but i can't spot any specific errors

Windows Device manager: I Can see the Medium Charger and the Tape device

The Design is quite simple that we got Robot connected to the backup server, no media or anything else so its quite simple.

Marianne:

No hardware related errors in Event Viewer

Windows Removable Storage manager service is stopped and disabled, we also Shutdown the server + Robot after this, rebooted the robot so it initialize before starting the server again

Robot shows up in Device manager

Scan command shows information about both robot and tape drive
In the Netbackup Admin console it still shows the Robot however with two drives that got the text
[Unused element address]

************************************************************
*********************** SDT_TAPE    ************************
*********************** SDT_CHANGER ************************
************************************************************
------------------------------------------------------------
Device Name  : "Changer0"
Passthru Name: "Changer0"
Volume Header: ""
Port: 3; Bus: 0; Target: 0; LUN: 1
Inquiry    : "IBM     3573-TL         C.30"
Vendor ID  : "IBM     "
Product ID : "3573-TL         "
Product Rev: "C.30"
Serial Number: "00X4U78B4508_LL0"
WWN          : ""
WWN Id Type  : 0
Device Identifier: "IBM     3573-TL         00X4U78B4508_LL0"
Device Type    : SDT_CHANGER
NetBackup Robot Type: 8
Removable      : Yes
Device Supports: SCSI-5
Number of Drives : 2
Number of Slots  : 43
Number of Media Access Ports: 3
Drive 1 Serial Number      : "1210390426"
Drive 2 Serial Number      : "1210390426"
Flags : 0x0
Reason: 0x0