Veritas Netbackup version

Find the Netbackup version

bash-3.00# /opt/openv/netbackup/bin/admincmd/bpgetconfig | grep VERSIONINFO
VERSIONINFO = “SunOS” “5.10″ “Unknown” “NetBackup” “6.5″ 650000

 

bash-3.00# cat /usr/openv/netbackup/version
HARDWARE SOLARIS
VERSION NetBackup 6.5.3
RELEASEDATE Fri Oct 31 00:23:11 CDT 2008
BUILDNUMBER 20081030

 

bash-3.00# cat /usr/openv/netbackup/bin/version
NetBackup-Solaris10 6.5.3

Read Full Post »

Veritas NetBackup scan Tape devices

Use /usr/openv/volmgr/bin/scan command for tape drive details. Check the output to determine if all the drives are being reported correctly.

bash-3.00# /usr/openv/volmgr/bin/scan
************************************************************
*********************** SDT_TAPE    ************************
*********************** SDT_CHANGER ************************
*********************** SDT_OPTICAL ************************
************************************************************
————————————————————
Device Name  : “/dev/rmt/1cbn”
Passthru Name: “/dev/sg/c0tw500308c001611804l1″
Volume Header: “”
Port: -1; Bus: -1; Target: -1; LUN: -1
Inquiry    : “IBM     ULTRIUM-TD2     5AT0″
Vendor ID  : “IBM     “
Product ID : “ULTRIUM-TD2     “
Product Rev: “5AT0″
Serial Number: “xxxxxxxxxx”
WWN          : “IBM     ULTRIUM-TD2     F00181100D”
WWN Id Type  : 1
Device Identifier: “IBM     ULTRIUM-TD2     F00181100D”
Device Type    : SDT_TAPE
NetBackup Drive Type: 10
Removable      : Yes
Device Supports: SCSI-3
Flags : 0×0
Reason: 0×0
————————————————————
Device Name  : “/dev/rmt/0cbn”
Passthru Name: “/dev/sg/c0tw500308c001611804l2″
Volume Header: “”
Port: -1; Bus: -1; Target: -1; LUN: -1
Inquiry    : “IBM     ULTRIUM-TD2     5AT0″
Vendor ID  : “IBM     “
Product ID : “ULTRIUM-TD2     “
Product Rev: “5AT0″
Serial Number: “xxxxxxxxxx”
WWN          : “IBM     ULTRIUM-TD2     F001811013″
WWN Id Type  : 1
Device Identifier: “IBM     ULTRIUM-TD2     F001811013″
Device Type    : SDT_TAPE
NetBackup Drive Type: 10
Removable      : Yes
Device Supports: SCSI-3
Flags : 0×0
Reason: 0×0
————————————————————
Device Name  : “/dev/sg/c0tw500308c001611803l1″
Passthru Name: “/dev/sg/c0tw500308c001611803l1″
Volume Header: “”
Port: -1; Bus: -1; Target: -1; LUN: -1
Inquiry    : “ADIC    Scalar i2000    402A”
Vendor ID  : “ADIC    “
Product ID : “Scalar i2000    “
Product Rev: “402A”
Serial Number: “ADIC205100785_LL0″
WWN          : “ADIC    205100785_LL0           “
WWN Id Type  : 1
Device Identifier: “ADIC    203100255_LL0           “
Device Type    : SDT_CHANGER
NetBackup Robot Type: 8
Removable      : Yes
Device Supports: SCSI-3
Number of Drives : 7
Number of Slots  : 72
Number of Media Access Ports: 12
Drive 1 Serial Number      : “xxxxxxxxx”
Drive 2 Serial Number      : “xxxxxxxxx”
Drive 3 Serial Number      : “xxxxxxxxx”
Flags : 0×0
Reason: 0×0
————————————————————
Device Name  : “/dev/rmt/3cbn”
Passthru Name: “/dev/sg/c0tw500308c001611803l2″
Volume Header: “”
Port: -1; Bus: -1; Target: -1; LUN: -1
Inquiry    : “IBM     ULTRIUM-TD2     53Y2″
Vendor ID  : “IBM     “
Product ID : “ULTRIUM-TD2     “
Product Rev: “53Y2″
Serial Number: “xxxxxxxxxx”
WWN          : “IBM     ULTRIUM-TD2     F001811001″
WWN Id Type  : 1
Device Identifier: “IBM     ULTRIUM-TD2     F001811001″
Device Type    : SDT_TAPE
NetBackup Drive Type: 10
Removable      : Yes
Device Supports: SCSI-3
Flags : 0×0
Reason: 0×0

…truncated

Use /usr/openv/volmgr/bin/sgscan to detect tape drives

bash-3.00# /usr/openv/volmgr/bin/sgscan
#
#WARNING: detected StorEdge Network Foundation connected devices not in
#         SG configuration file:
#
#    Device World Wide Port Name 500000e01042ff61
#    Device World Wide Port Name 500000e0101fae61
#    Device World Wide Port Name 50800200001b7fa9
#
#    See /usr/openv/volmgr/MediaMgr_DeviceConfig_Guide.txt chapter
#    “Special configuration for “Sun StorEdge Network Foundation” HBA/Driver”
#    for information on how to use sg.build and sg.install to
#    configure these devices
#

/dev/sg/c0t6l0: Cdrom: “TOSHIBA DVD-ROM SD-M1401″
/dev/sg/c0tw500308c001611803l0: Array-controller: “ADIC    Scalar i2000″
/dev/sg/c0tw500308c001611803l1: Changer: “ADIC    Scalar i2000″
/dev/sg/c0tw500308c001611803l2: Tape (/dev/rmt/3): “IBM     ULTRIUM-TD2″
/dev/sg/c0tw500308c001611803l3: Tape (/dev/rmt/2): “IBM     ULTRIUM-TD2″
/dev/sg/c0tw500308c001611804l0: Array-controller: “ADIC    Scalar i2000″
/dev/sg/c0tw500308c001611804l1: Tape (/dev/rmt/1): “IBM     ULTRIUM-TD2″
/dev/sg/c0tw500308c001611804l2: Tape (/dev/rmt/0): “IBM     ULTRIUM-TD2″

Use /usr/openv/volmgr/bin/tpautoconf -report_disc command to report discrepancies between detected devices and the EMM database.

tpautoconf is normally used by the Device Configuration wizard to automatically discover and configure devices. The wizard calls tpautoconf with a different set of options.

#/usr/openv/volmgr/bin/tpautoconf -report_disc

=========== Missing Device or no local control path (Robot) ===========
Defined as robotic TLD(0)
Inquiry = “ADIC    Scalar i2000    402A”
Serial Number = ADIC204100621_LL0
Robot Control Host = host1
Drive = 18, Drive Name = drive18, Serial Number = F0016FE057
Drive = 19, Drive Name = drive19, Serial Number = F0016FE07D
Drive = 20, Drive Name = drive20, Serial Number = F0016FE023

Hosts configured for this device:
  Host = host2
  Host = host1
======================= Missing Device (Drive) =======================
Drive Name = drive20
Drive Path = /dev/rmt/0cbn
Inquiry = “IBM     ULTRIUM-TD2     5AT0″
Serial Number = F0016FE057
TLD(0) definition Drive = 20
Hosts configured for this device:
  Host = host2
======================= Missing Device (Drive) =======================
Drive Name = drive19
Drive Path = /dev/rmt/1cbn
Inquiry = “IBM     ULTRIUM-TD2     5AT0″
Serial Number =F0016FE07D
TLD(0) definition Drive = 19
Hosts configured for this device:
  Host = host2
======================= Missing Device (Drive) =======================
Drive Name = drive18
Drive Path = /dev/rmt/2cbn
Inquiry = “IBM     ULTRIUM-TD2     5AT0″
Serial Number =F0016FE057
TLD(0) definition Drive = 18
Hosts configured for this device:
  Host = host2

luxadm performs a variety of control and query tasks depending on the command line arguments and options used. The following option finds and displays information of individual FC_AL devices including the logical pathname, the WWNs and enclosure names.

bash-3.00# luxadm probe
Found Enclosure:
SUNWGS INT FCBPL   Name:FCloop   Node WWN:50200400051b1fa9   Logical Path:/dev/es/ses0

Found Fibre Channel device(s):
  Node WWN:500308c001637402  Device Type:Tape device
    Logical Path:/dev/rmt/0n
    Logical Path:/dev/rmt/3n
  Node WWN:500308c001637402  Device Type:Tape device
    Logical Path:/dev/rmt/1n
  Node WWN:500308c001637402  Device Type:Tape device
    Logical Path:/dev/rmt/2n
  Node WWN:500308c001637409  Device Type:Tape device
    Logical Path:/dev/rmt/4n
  Node WWN:500308c001637409  Device Type:Tape device
    Logical Path:/dev/rmt/5n
  Node WWN:500308c001637409  Device Type:Tape device
    Logical Path:/dev/rmt/6n

Read Full Post »

How to rebuild the /dev/sg/* and /dev/rmt/* devices on a Solaris Master or Media server- Without rebooting

Here are the basic steps to rebuild the /dev/sg/* and /dev/rmt/* devices on a Solaris server without rebooting.

1.  Create a backup copy of the current st.conf file:
# cp /kernel/drv/st.conf /kernel/drv/st.conf.bak

2.  Move the existing sg.conf to a backup (this must be a move, otherwise a later step will fail):
# mv /kernel/drv/sg.conf /kernel/drv/sg.conf.bak

3.  Create a backup copy of the current devlink.tab file:
# cp /etc/devlink.tab /etc/devlink.tab.bak

4.  Delete SCSI targets/LUNs from the /kernel/drv/st.conf file:

# This line adds support for Fibre Channel Tapes
name=”st” parent=”fp” target=0;
name=”st” class=”scsi” target=0 lun=0;
name=”st” class=”scsi” target=0 lun=1;
name=”st” class=”scsi” target=1 lun=0;
name=”st” class=”scsi” target=1 lun=1;
name=”st” class=”scsi” target=2 lun=0;
name=”st” class=”scsi” target=2 lun=1;
name=”st” class=”scsi” target=3 lun=0;
name=”st” class=”scsi” target=3 lun=1;
name=”st” class=”scsi” target=4 lun=0;
name=”st” class=”scsi” target=4 lun=1;

Remove all the entries so no duplicates are added later

5.  Delete SCSI targets/LUNs from /etc/devlink.tab.  This is typically the section near the end of the file and the entries are typically of the form:

# begin SCSA Generic devlinks file – creates nodes in /dev/sg
type=ddi_pseudo;name=sg;addr=0,0;       sg/c\N0t0l0
type=ddi_pseudo;name=sg;addr=0,1;       sg/c\N0t0l1
type=ddi_pseudo;name=sg;addr=0,2;       sg/c\N0t0l2
type=ddi_pseudo;name=sg;addr=0,3;       sg/c\N0t0l3
type=ddi_pseudo;name=sg;addr=0,4;       sg/c\N0t0l4
type=ddi_pseudo;name=sg;addr=0,5;       sg/c\N0t0l5
type=ddi_pseudo;name=sg;addr=0,6;       sg/c\N0t0l6
type=ddi_pseudo;name=sg;addr=0,7;       sg/c\N0t0l7
type=ddi_pseudo;name=sg;addr=0,8;       sg/c\N0t0l8
type=ddi_pseudo;name=sg;addr=1,0;       sg/c\N0t1l0
type=ddi_pseudo;name=sg;addr=1,1;       sg/c\N0t1l1
type=ddi_pseudo;name=sg;addr=1,2;       sg/c\N0t1l2
type=ddi_pseudo;name=sg;addr=1,3;       sg/c\N0t1l3
type=ddi_pseudo;name=sg;addr=1,4;       sg/c\N0t1l4
type=ddi_pseudo;name=sg;addr=1,5;       sg/c\N0t1l5
type=ddi_pseudo;name=sg;addr=1,6;       sg/c\N0t1l6
type=ddi_pseudo;name=sg;addr=1,7;       sg/c\N0t1l7
type=ddi_pseudo;name=sg;addr=1,8;       sg/c\N0t1l8
type=ddi_pseudo;name=sg;addr=2,0;       sg/c\N0t2l0
type=ddi_pseudo;name=sg;addr=2,1;       sg/c\N0t2l1
type=ddi_pseudo;name=sg;addr=2,2;       sg/c\N0t2l2
type=ddi_pseudo;name=sg;addr=2,3;       sg/c\N0t2l3
type=ddi_pseudo;name=sg;addr=2,4;       sg/c\N0t2l4
type=ddi_pseudo;name=sg;addr=2,5;       sg/c\N0t2l5
type=ddi_pseudo;name=sg;addr=2,6;       sg/c\N0t2l6

Remove all

6.  Change to the appropriate directory to run commands:
# cd /usr/openv/volmgr/bin/driver

7.  Generate the configuration files (st.conf, sg.conf and sg.links):
../sg.build all -mt <max_target> -ml <max_lun>

. ./sg.build all -mt 2 -ml 3

8.  Append the generated st.conf entries to the OS configuration file:
# cat st.conf >> /kernel/drv/st.conf

9.  Unload the sg driver:
# rem_drv sg

10. Use the provided script to re-create the /kernel/drv/sg.conf file, append the SCSA entries to /etc/devlink.tab and reload the sg driver:
# ./sg.install

11. Now sgscan should see the appropriate devices:
# /usr/openv/volmgr/bin/sgscan all conf -v

 

VERITAS NetBackup ™ 5.0 Media Manager Device Configuration Guide for UNIX

Read Full Post »

Veritas NetBackup Error: bpcd libstdc++-libc6.2-2.so.3 64bit Linux Server

Exact Error Message
bpcd: error while loading shared libraries: libstdc++-libc6.2-2.so.3: cannot open shared object file: No such file or directory

Details:

Overview:
In Veritas NetBackup ™ Enterprise Server 5.x or 6.0, master servers may be unable to connect to the bpcd daemon on Linux clients using the administration console or may have backups failing with timeout errors.  This can also occur for the bpps and bmrsetupclient commands during the installation of NetBackup 6.0 clients.  These errors occur when the binaries on the client cannot load shared libraries.  Specifically, this is the result of the standard C++  compatibility libraries not being installed. In order to provide support for earlier versions of Linux, the NetBackup binaries were built with earlier versions of the C++ compatibility libraries, which may not have been installed on the problem client.
Troubleshooting:
To verify that the libraries are not installed, telnet to the bpcd port on the client from the master with the following command:

# telnet client 13782

If the libraries are not present, the output will be as follows:

# telnet <client name> 13782

Trying x.x.x.x

Connected to <client name>

Escape character is '^]'.

bpcd: error while loading shared libraries: libstdc++-libc6.2-2.so.3:

cannot open shared object file: No such file or directory

Connection closed by foreign host.

During a NetBackup 6.0 installation the following errors may appear if the standard C++ compatibility libraries are not installed.
/usr/openv/netbackup/bin/bpps: error while loading shared libraries: libstdc++-libc6.2-2.so.3: cannot open shared object file: No such file or directory
/usr/openv/netbackup/bin/bmrsetupclient: error while loading shared libraries: libstdc++-libc6.2-2.so.3: cannot open shared object file: No such file or directory
Log Files:  n/a
Resolution:
The solution is to install the standard C++ compatibility libraries in order to satisfy this library dependency. The version of Linux on the client will determine what RPM or software package needs to be installed.  Also check the Veritas NetBackup ™ OS Compatibility lists in the Related Documents section, below, to ensure the RedHat version is supported with the version of NetBackup that is running. 

For RedHat 4.0 Clients

The location of the required standard C++ compatibility library has been changed in RedHat 4.0 distributions. There is a different RPM that is required in order to install the library required for these binaries to run. Install the compat-libstdc++-296-2.96.132.7.2.i386.rpm package, which is located on the RedHat 4.0 Installation Disc 3.  

For RedHat 3.0 AS/ES/WS Clients

Install the compat-libstdc++-7.3-2.96.122.i386.rpm package, which is located on RedHat 3.0 Installation Disc 3 in ./RedHat/RPMS/compat-libstdc++-7.3-2.96.122.i386.rpm

For RedHat 9.0 Clients

Install the compat-libstdc++-7.3-2.96.118.i386.rpm package.

For RedHat 8.0 Clients

Install the compat-libstdc++7.3-2.96.110.I386.rpm package.

Depending on the version of Linux, the installation may require additional supporting packages to be installed long with the compat-libstdc++ package.  Contact RedHat support for assistance with locating and installing the correct version of the RedHat standard C++ compatibility RPMs as well as any other required packages.  An online search for RPMs is also available at the following Web site:  http://www.rpmfind.net/

Related Documents:
283789: GENERAL ERROR: Getting an error regarding the libncurses.so.5 library when trying to install a license key on a 64-bit Linux server
http://support.veritas.com/docs/283789
263839: Veritas NetBackup ™ 5.x Operating System Compatibility (updated July 16 2007)
http://support.veritas.com/docs/263839
278064: Veritas NetBackup ™ 6.x Operating System Compatibility List (Updated January 14, 2008)
http://support.veritas.com/docs/278064
251712: VERITAS NetBackup ™ DataCenter and NetBackup BusinesServer 4.5 Operating System Compatibility List (Updated December 2, 2005)
http://support.veritas.com/docs/251712

Supplemental Material:

Error Code: 58
NetBackup Error 58: can’t connect to client

Read Full Post »