Netbackup Backup flow

nbpem initiates backup when the job is due. nbpem uses nbproxy to get the backup
policy information from bpdbm.
When the job is due nbpem sends a request to nbjm to start a job
nbjm communicates with bpjobd and the job becomes visible in activity monitor.
Once the job is added in job database, nbjm requests resources from nbrb.
nbrb secures resources from nbemm and then notifies nbjm that the resources have
been allocated.
After the resource allocation is done, the job becomes active in activity monitor.
nbjm then uses bpcompatd to open connection with bpcd on media server by using PBX
and vnetd.
bpcd them starts bpbrm on media server
The bpbrm service then communicates with bpcd on the client to start bpbkar
process.
The bpbrm also starts the bptm process.
Incase of tape backups bptm reserves the drive and issues a mount request to ltid.
Incase of disk, bptm directly communicates with the disk.
bpbkar sends the backup data through bptm to either disk or tape.
When the backup completes, nbjm is notified and it sends a message to bpjobd after
which the job shows completed in activivty monitor.
nbjm also notifies the nbpem which recalculates the time for the next schedule for
backup job.

###################################################################################
#######################################################################
*ports required for Netbackup client communication

1556, 13782 & 13724

###################################################################################
#######################################################################
*ports used for deduplication

1556, 10082 & 10102

10082 - This is the NetBackup Deduplication Engine (spoold). Responsible for

checking Data Integrity and managing fingerprint cache
10102 - This is the NetBackup Deduplication Manager (spad). Responsible for
maintaining the configuration and controls internal processes, optimized
duplication, security, and event escalation

###################################################################################
#######################################################################

*Adding hostid certificates in Netbackup

1) To check if CA certificate already exists on client

/usr/open/netbackup/bin/nbcertcmd -displayCACertDetail -server mymaster

2) if CA Certificate state is not trusted then it must be retrived from Backup

server.

/usr/open/netbackup/bin/nbcertcmd -listCACertDetails

3)Then deploy the certiciate

/usr/open/netbackup/bin/nbcertcmd -getCACertificate -server mymaster

4) to confirm if the certiciate is deployed run the below command and compare the
certificates
/usr/open/netbackup/bin/nbcertcmd -displayCACertDetail -server mymaster

###################################################################################
#######################################################################

Commands to generate dr file incase of disaster.

Command Syntax:

For catalog backup on tape:

bpimport -drfile -id <MediaID> -drfile_dest <Destination Directory>

For catalog backup on OST device:

bpimport -drfile -stype <Storage_Server_Type> -dp <Disk Pool Name> -drfile_dest

<Destination Directory>

###################################################################################
#######################################################################

Netbackup DR pachage

A disaster recovery package is created during each catalog backup. The package is
encrypted with the passphrase that you set.
The disaster recovery package contains the following information:
Security certificates and private keys of the master server and the NetBackup CA
(Certificate Authority)
Information about the hosts in the domain
Security settings

###################################################################################
#######################################################################

Configuring Oracle Backups

Using the Netbackup script

Link the Netbackup Library

/usr/openv/netbackup/bin/oracle_link

Update below details in script

1. ORACLE_HOME=/db/oracle/product/ora102
2. ORACLE_SID=ora102
3. ORACLE_USER=ora102
4. TARGET_CONNECT_STR=sys/manager

Add the send paramenters

SEND 'NB_ORA_SERV=<master server name>,NB_ORA_CLIENT=<oracle server
name>,NB_ORA_POLICY= backup policy name'

Configuring Backup Policy

###################################################################################
####################################################################
Diskpool Commands
# /usr/openv/netbackup/bin/admincmd/nbdevquery -listdp -stype PureDisk -U

# /usr/openv/netbackup/bin/admincmd/nbdevquery -listdv -stype PureDisk -dp PDPool01

-U

# /usr/openv/netbackup/bin/admincmd/nbdevconfig -changestate -stype PureDisk -dp

PDPool01 -dv PDVolume01 -state RESET

###################################################################################
####################################################################
SLP cheatsheet

A storage lifecycle policy (SLP) is a storage plan for a set of backups and
provides additional staging locations, including all supported disk types, VTL and
tape. We can provide additional staging retentions and classification of backup
data as well.

Netbackup Storage Lifecycle Management Service (nbstserv) is responsible for SLP

(Storage Lifecycle Policy)

To view a detailed list of all SLPs within the system

# /usr/openv/netbackup/bin/admincmd/nbstl -L

The following command will list all images been processed via a SLP and are still
retained within the catalog.
# /usr/openv/netbackup/bin/admincmd/nbstlutil stlilist -L

Activate / Inactivate SLP operations

# /usr/openv/netbackup/bin/admincmd/nbstlutil inactive -lifecycle <name>
# /usr/openv/netbackup/bin/admincmd/nbstlutil inactive -backupid <value>
# /usr/openv/netbackup/bin/admincmd;nbstlutil active -lifecycle <name>
# /usr/openv/netbackup/bin/admincmd/nbstlutil active -backupid <value>

Show status on Incomplete copies of Lifecycle Managed images

# /usr/openv/netbackup/bin/admincmd/nbstlutil stlilist -lifecycle <name>
# /usr/openv/netbackup/bin/admincmd/nbstlutil stlilist -backupid <value>

###################################################################################
####################################################################
Configure SAN Client

1)Install HBA on both FT media server and SAN client.

2)Connect the HBA port on the NetBackup FT media server & SAN Client on the same
Fibre Channel switch.
3)Performing zoning of the SAN client and NetBackup FT media server so that they
are in same zone.

Start nbhba mode on the media server by running the following command:
#/usr/openv/netbackup/bin/admincmd/nbftsrv_config -nbhba
Installing nbhba driver. Are you sure you want to unload QLogic driver: qla2300?
[y,n] (y)
/usr/sbin/update_drv-v-d-i "pci1077,2312.1077.12a" qlc
Done copying driver into system directories. Done adding driver.
MUST REBOOT TO COMPLETE INSTALLATION.

Reboot the host.

Display the QLogic HBA ports on the media server by using the following command

#/usr/openv/netbackup/bin/admincmd/nbhba -l
1 2312 21:00:00:E0:8B:83:9D:A1 "QLA2342" 0 0 101
2 2312 21:01:00:E0:8B:A3:9D:A1 "QLA2342" 1 0 101

Mark the ports as targets by using the following command:

/usr/openv/netbackup/bin/admincmd/nbhba -modify -wwn 21:00:00:E0:8B:83:9D:A1 -mode
target
/usr/openv/netbackup/bin/admincmd/nbhba -modify -wwn 21:01:00:E0:8B:A3:9D:A1 -mode
target

Run the nbftsrv_config script.

/usr/openv/netbackup/bin/admincmd/nbftsrv_config
Installing the Jungo driver and Fibre Transport Server. The following automatic
startup and shutdown scripts (respectively) have been installed. They will cause
the NetBackup Fibre Transport Server daemon to be automatically shutdown and
restarted each time the system boots.
/etc/rc.d/rc2.d/S21nbftserver
/etc/rc.d/rc3.d/S21nbftserver
/etc/rc.d/rc5.d/S21nbftserver
/etc/rc.d/rc0.d/K03nbftserver
/etc/rc.d/rc1.d/K03nbftserver
/etc/rc.d/rc6.d/K03nbftserver
It may be necessary to temporarily unload your QLogic drivers to free up the ports
for the nbhba drivers. This is an optional step. If you choose not to do this, you
may not have access to all of the HBA ports until a subsequent reboot. Would you
like to uninstall and reinstall your native QLogic drivers now? [y,n] (y) y

The Qlogic drivers must be unloaded temporarily so that the stub driver
(ql2300_stub) can bind to the marked HBA ports during this session. To unload the
QLogic driver, answer y.

Are you sure you want to unload QLogic driver: qla2300? [y,n] (y) y
Removing qla2300.
Adding qla2300.
Adding qla2xxx.

To start the QLogic SANsurfer agent, answer y.

Would you like to start the SANsurfer agent (qlremote)? [y,n] (y) y
Starting qlremote agent service Started SANsurfer agent.
/etc/udev/permissions.d/50-udev.permissions updated with Jungo WinDriver
permissions.
NetBackup Fibre Transport Server started.

To ensure that the FT server always starts after a computer reboot, answer y.

Would you like to make these changes persist after a reboot? [y,n] (y) y
Running mkinitrd.
Previous initrd image is saved at /boot/initrd-3.0.9-11.ELsmp.img.12-21-
09.12:37:03.
NetBackup SAN Client Configuration on Clients
Verify that the Symantec PBX service is active on the client.
On the client, run the following command to enable the SAN Client Fibre Transport
Service (nbftclnt):UNIX and Linux:
/usr/openv/netbackup/bin/bpclntcmd -sanclient 1

Reboot Client

To enable NetBackup FT media server in appliance

NetBackup Appliance WebGUI - Settings>Fiber Transport>Select Enable SAN Client FT
media server
NetBackup Appliance CLISH - Settings>Fiber Transport SAN CLient Enable

###################################################################################
#######################################################################
Commands to check connectivity

**Error code 25

On Master and client

bptestbpcd -verbose -debug -client <client hostname>
bpclntcmd -hn <client hostname> or <master hostname>
bpclntcmd -ip <client hostname> or <master hostname>

On client
bpclntcmd -pn

On client increase the verbossity for bpcd logs

perform telnet to port 13782

** Error code 58
Check if the server is up and running
Check if the Netbackup client service is running

** Error code 156

For VM Backups
Check if any stale snapshot on the VM's
Check if VMwareTools is installed and is of the latest version on the VM
Check if the datastore hosting the VM has enough space
Check if the VM requires disk consolidation

For Filesystem Backups

Check if the VSS writers on the server are stable.

** Error code 2074

Verify if the diskpool is down.
# /usr/openv/netbackup/bin/admincmd/nbdevquery -listdp -stype PureDisk -U

Try to get it online

# /usr/openv/netbackup/bin/admincmd/nbdevconfig -changestate -stype PureDisk -dp
PDPool01 -dv PDVolume01 -state RESET

Check if the media server is online.

Check if the NetBackup services are online