Unable to determine robot type

These instructions assume that NetBackup is installed in the default location of C:\Program Files\VERITAS\.  If NetBackup is installed in a different location, substitute that path for C:\Program Files\VERITAS\ in the instructions below:

1. Download and extract the new mappings file package to a temporary folder.  This will create three files in the temporary location:

Readme.txt (this file)

external_robotics.txt

external_types.txt

2. Copy the external_types.txt file from the temporary location to C:\Program Files\VERITAS\NetBackup\var\global\ on the Master Server or the EMM Server.

(For NetBackup High Availability environments, copy the file to the shared disk.)

3. Copy the external_robotics.txt file from the temporary location to C:\Program Files\VERITAS\NetBackup\var\global\ on the master server, EMM Server, each media server that controls a robot, and each media server from which robot inventories will be run.

(For NetBackup High Availability environments, copy the file to the shared disk.)

4. Bring up a command window with Start -> Run -> Type "cmd". Enter the following commands in that command window.

5. Update the NetBackup Enterprise Media Manager database with the new device mappings version. This only needs to be done once and must be run from the Master Server or the EMM Server.  Use the command format below that corresponds to the installed version of NetBackup:

NetBackup 7.x and 6.5:  C:\Program Files\VERITAS\Volmgr\bin\tpext -loadEMM

6. For Media Servers running 6.0_MP4 and earlier, manually update each Media Server with the new device mappings.  (On Media Servers running 7.x, 6.5 or 6.0_MP5 and later, this command is not needed since ltid will update the device mappings when it starts.)  This command must be run on each 6.0_MP4 and earlier Media Server that has devices attached:

C:\Program Files\VERITAS\Volmgr\bin\tpext -get_dev_mappings

7. Restart Device Manager (ltid) on each Media Server.  

8. Verify that the version that is now stored in the Enterprise Media Manager database is the same as what is in the file stored on the Media Server: