Symantec NetBackup (tm) Server / Enterprise Server 6.x and 7.x Device Mappings Package for UNIX / Linux 1.122

Article:TECH227192  |  Created: 2014-12-18  |  Updated: 2014-12-18  |  Article URL http://www.symantec.com/docs/TECH203427
Article Type
Technical Solution

Product(s)

Environment

Issue



Symantec NetBackup (tm) Server / Enterprise Server 6.x and 7.x Device Mappings Package for UNIX / Linux 1.122


Solution



This package 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 introduces new device support for the following devices:

  • NetBackup Accelerator support enabled for Quantum OpenStorage solutions  
The presence of a device in the file external_types.txt does not indicate, expressed or implied, support of the device on the target NetBackup/Enterprise Media Manager platform.  Refer to the NetBackup Hardware Compatibility List (HCL), found below in the Related Documents section, for a current list of supported devices.
 
Symantec 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-Symantec OpenStorage storage servers.
 These files are for NetBackup 6.0 / 6.5 / 7.0 / 7.1 / 7.5 / 7.6 only and will not work with earlier NetBackup releases.
 
**************************************
 
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_v1122.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 Server or the 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 server, 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 Server or the EMM Server.  Use the command format below that corresponds to the installed version of NetBackup:
 
NetBackup 6.5/7.0/7.1/7.5/7.6:  /usr/openv/volmgr/bin/tpext -loadEMM
 
NetBackup 6.0:  /usr/openv/volmgr/bin/tpext
 
5. For Media Servers running 6.0_MP4 and earlier, manually update each Media Server with the new device mappings.  (On Media Servers running 7.6, 7.5, 7.1, 7.0, 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::
 
/usr/openv/volmgr/bin/tpext -get_dev_mappings
 
6. Restart Device Manager (ltid) on each Media Server.
 
7. 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
 

 


Attachments

Mappings_v1122.tar (140 kBytes)


Article URL http://www.symantec.com/docs/TECH203427


Terms of use for this information are found in Legal Notices