Veritas NetBackup (tm) Server / Enterprise Server Device Mappings Package for UNIX / Linux

  • Article ID:100015983
  • Modified Date:
  • Product(s):

Problem

Veritas NetBackup (tm) Server / Enterprise Server Device Mappings Package for UNIX / Linux

Solution

This package (v1.146) contains an update to the NetBackup mappings files. The files external_robotics.txt and external_types.txt are used by the NetBackup Enterprise Media Manager database to determine which protocols and settings to use to communicate with storage devices. They are also used by the Device Configuration Wizard to automatically configure new devices.

This package enables functionality for the following devices or solutions:

  • NetBackup Accelerator support enabled for Quest OpenStorage solutions
  • Quest DR 13g Series VTL 
The presence of a device or solution that is enabled in the file external_types.txt does not indicate, expressed or implied, support of the device or solution on the target NetBackup/Enterprise Media Manager platform.  Refer to the NetBackup Hardware and Cloud Storage Compatibility List (HCL), found below in the Related Documents section, for a current list of supported devices and solutions.
 
Veritas recommends downloading and installing this package:
  • Before discovering and configuring devices with the Device Configuration Wizard. If your configuration contains a device in the list above, installation of this package is required to properly configure that device.
  • If you use the NetBackup Accelerator feature with non-Veritas OpenStorage storage servers.
These files work with NetBackup 7.7.x and 8.x.x releases.

Note:  To load NetBackup device mappings files onto a NetBackup Appliance running in a Master Server role, contact Veritas Support and ask the representative to refer to Article 000107907.
 
**************************************
 
UNIX / Linux Installation Instructions
 
**************************************
 
These instructions assume that NetBackup is installed in the default location of /usr/openv/.  If NetBackup is installed in a different location, substitute that path for /usr/openv/ in the instructions below:
 
1. Download and extract the new mappings file package to a temporary directory:
 
tar -xvf Mappings_v1146.tar
 
This will create three files in the temporary location:
 
  • Readme.txt
  • external_types.txt
  • external_robotics.txt
2. Copy the external_types.txt file from the temporary location to /usr/openv/var/global on the Master/EMM Server.
 
cp /temp_dir/external_types.txt /usr/openv/var/global/
 
(For NetBackup High Availability environments, copy the file to the shared disk.)
 
3. Copy the external_robotics.txt file from the temporary location to /usr/openv/var/global on the Master/EMM Server, each media server that controls a robot, and each media server from which robot inventories will be run.
 
cp /temp_dir/external_robotics.txt /usr/openv/var/global/
 
(For NetBackup High Availability environments, copy the file to the shared disk.)
 
4. 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/EMM Server.  Use the command format below:
 
/usr/openv/volmgr/bin/tpext -loadEMM
/usr/openv/volmgr/bin/tpext -get_dev_mappings
 
5. Restart Device Manager (ltid) on each Media Server.
 
6. 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:
 
/usr/openv/volmgr/bin/tpext -get_dev_mappings_ver
 

Downloads

Was this content helpful?

Get Support