Has two parts, netbackup and volume manger.

Netbackup

Controls backup/restoring data

Interfaces (GUI)

  • jnbSA - java based administration console
  • bpadm - character based menu interface
  • xbpadm - for configuring and managing (older versions - now discontinued)
  • bp - character based menu interface for backups/restores

daemons

  • bprd - netbackup request daemon. Can be started from either xbpadm or from path/netbackup/bin/initbprd and stopped from xbpadm
  • bpdbm - database daemon . Start using path/netbackup/bin/initbprd, stop using bpdbm -terminate

The database must be backed up using bpbackup and restored using bprestore

Volume Manager

Controls the volumes and devices vmadm - can be used for managing volumes and devices. It calls tpconfig for configuring devices. (these tasks can also be carried out via the java GUI).

Daemons

  • ltid - device management daemon. Started with path/volmgr/bin/ltid. Stopped from vmadm/jnbSA screens.
  • avid - automatic volume recognition daemon. Started with path/volmgr/bin/vmd . Stopped from vmadm/jnbSA screens.

Installation and Configuration steps

Server Install (Solaris)

 1. Insert CD
 2. cd /cdrom_path;pkgadd -d . SUNWmmgr SUNWnetbp
 3. /usr/openv/netbackup/bin/install_bp (for Solaris, install for other Unix
    platforms)
 4. update .profile adding netbackup directories to $PATH and $MANPATH
 5. Copy /usr/openv/netbackup/bin/goodies/S77netbackup to appropriate start
    script location for Unix version
 6. Copy /usr/openv/netbackup/bin/goodies/K77netbackup to appropriate start
    script location for Unix version
 7. Apply any patches that come with the Netbackup media

Device/tape configuration

 1. Configure drives using tpconfig
       1. Add robot (if applicable)
       2. Add tape drive
 2. Add tape volumes using vmadm
       1. Add new volume pool
       2. Add volumes to pool

Netbackup configuration

 1. Add storage unit using bpadm (must have been created by tpconfig first)
 2. Define class (backup policy) with bpadm
       1. Attributes (general settings)
       2. Clients (clients to backup)
       3. Schedules (when to backup)
       4. Files (files to backup)
 3. Install client software (client must have been defined in the previous
    step first)
       1. From master server run /usr/openv/netbackup/bin/install_client_files
          ftp client user
       2. On client run /tmp/bp/bin/client_config

Netbackup daemons/programs

  • bpps -a - shows status of daemons
  • tpconfig - configures devices
  • vmadm - configures tapes
  • bpadm - configures backups
  • bpmon - monitors backups

These tasks can also be done using the java console.

Netbackup Tips

Scratching a tape

   /usr/openv/netbackup/bin/admincmd/bpexpdate -ev TAPE_ID -d0 -force -host MEDIA_MANAGER
 /usr/openv/volmgr/bin/vmchange -p 2 -m TAPE_ID
 

Tape Library Replacement

If the tape library chasis is replaced, the serial number will change. The tape library will therefore need to be deleted and added back in to netbackup. This is most easily achieved using the GUI as follows:

  delete robot -> delete tape drives
add robot -> add drives (associated with robot)

Useful Diagnostic Commands

To check communications, on the master run:

  /usr/openv/netbackup/bin/admincmd/bptestbpcd -client <client_name>
  

Or for more verbose information

 /usr/openv/netbackup/bin/admincmd/bptestbpcd -client <client_name> -verbose -debug
  

This will check that the master can connect to the agent on the specified client. You can also check that the client can communicate with the master running the following command on the client:

 /usr/openv/netbackup/bin/bpclntcmd -pn
 

Response should be something along the lines of

 expecting response from server themaster
  theclient.justsomestuff.co.uk theclient 10.44.163.107 46901

If you suspect that there may be same name resolution issues, the following will check if the specified hostname is cached in the netbackup cache

  /usr/openv/netbackup/bin/bpclntcmd -hn <hostname> 
  

Or to check an IP address

 /usr/openv/netbackup/bin/bpclntcmd -ip <ipaddr>
 

You can clear the cache as follows:

 /usr/openv/netbackup/bin/bpclntcmd -clear_host_cache
  

To run a report to find any DNS related issues for netbackup clients run

 /usr/openv/netbackup/bin/support/nbdna
  

Storage Lifecycle Policies (SLP)

Checking the status of a SLP image

  /usr/openv/netbackup/bin/admincmd/nbstlutil list -backupid <the-backup-id> -U
  
Checking Images on Disk (Data Domain)

1. get the disk pool names

  /usr/openv/netbackup/bin/admincmd/nbdevquery -listdp
  

This returns something like the following

  V7.5 dp_ost_dd03arr01p 1 50883.75 50883.75 1 100 98 180 dd03arr01p
  V7.5 dp_ost_dd13arr01p 1 50947.87 50947.87 1 100 98 180 dd13arr01p
  V7.5 dp_ost_dd03arr02p 1 86601.67 86601.67 1 100 98 180 dd03arr02p
  V7.5 dp_ost_dd13arr02p 1 86488.45 86488.45 1 100 98 180 dd13arr02p

2. Field 2 of the output is the disk pool name. To check the images on one of the Data Domains, enter

 /usr/openv/netbackup/bin/admincmd/bpimmedia -dp dp_ost_dd13arr02p -stype DataDomain -l -legacy
 

3. To get more details of the image, use field 4, the backup id as follows:

 /usr/openv/netbackup/bin/admincmd/bpimagelist -backupid  somehost_1378848822 -l
 

4. A list of files on the image can be found as follows:

 /usr/openv/netbackup/bin/admincmd/bpflist -backupid somehost_1378848822 -d 01/01/2015 00:00:01 -e 08/26/2015 06:00:00 -rl 9999 
 

(Note: you need to specify the date range and -rl or it will come up with “entity not found”)

More usefully, the following script will display the backupid, schedule, size and expiry date

  #!/bin/bash
  # List images on data domain and expiry date
  DATADOMAIN=your_data_domain
  bpimmedia -dp $DATADOMAIN -stype DataDomain -l -legacy | awk '{ if ( $1 == "IMAGE" ) print "bpimagelist -backupid "$4" -l" }'|sh | awk '{ if ( $1 == "IMAGE" ) print $6,$11,$16,$19 }' | while read IMAGE SCHED EXPDATE SIZE
  do
  EXPIRY=`bpdbm -ctime $EXPDATE | cut -d "=" -f2`
  echo "$IMAGE $SCHED $SIZE $EXPIRY"
  done

List backup images for a client since a specified date

 bpcatlist -client client-name -since Aug 20
 

Manipulating policies and schedules

bppllist can be used to list policies, bpplsched to list policy details and bpplschedrep to change policy details.

In the script below, all policies starting with SRV1 that have a monthly schedule are updated to use SLP MY_MONTHLY_SLP

 #!/bin/bash
 #
 # Update netbackup policies
 
 bppllist | grep SRV1 | while read POLICY
 do
   bpplsched $POLICY -U | grep -q Monthly
   if [ $? -eq 0 ]
   then
    echo "Updating Monthly schedule for Policy $POLICY "
    bpplschedrep $POLICY Monthly -residence MY_MONTHLY_SLP
   fi
 done
 

Useful robtest commands

robtest can be used to check the status of a tape library/robot

 s s - show slots
 s d - show drives
 s p - show mail slots
 m s3 p1 - move the tape from slot 3 to mail slot 1
 

Another useful command for checking tape libaries is scan. Both robtest and scan are locates in /usr/openv/volmgr/bin (assuming standard install).

Recent Changes

Contribute to this wiki

Why not help others by sharing your knowledge? Contribute something to this wiki and join out hall of fame!
Contact us for a user name and password