VERITAS NetBackup

Walk through Document

June - 2011
 Contents
 NetBackup Software
 NetBackup Architecture
 Roles and duties of Master, Media and client
 NetBackup Environmental Setup (Master, Media, Clients, tape drives, library, robot,
media, Disk setup)
 Hardware setup / Configuration
o Tape drives configuration
o Storage unit
o Multiplexing
o Storage unit group
o Volume configuration
o Volume Group
o Volume pool
o Robot Inventory
o Advanced Robot Inventory Options
 Policy Management
o Attributes
o Scheduling
o Backup selections
o Client list
 NetBackup Catalog
 NetBackup 6.x Backup process (Daemon flow)
 NetBackup 6.x Installation (on Solaris and Windows)
 NetBackup for MS-SQL
 NetBackup for Oracle
 NetBackup for NDMP
 NetBackup common error codes occurrences during the backup process.
NetBackup Software
Architecture
Basically in NetBackup we see three different levels. Hence we call NetBackup as 3-Tire
architecture software.

1. Management Level
2. Execution Level
3. Clients

Management Level: This level manages the NetBackup operations. This maintains a database
which contains information required to manage the day to day operations. Based on this
information it instructs the execution level to execute the operation.

This level maintains a different logging which provides us the detailed information of the
operations it carries out.
Execution Level: This level executes the instructions provided by Management level. This level
captures its activities in a log which helps us in tracking out of its activities.

Clients: This level contains the data to be backed up.

Note: NetBackup software is formerly said to have 3-Tier architecture. With introduction of EMM server
with NetBackup 6.x the architecture of NBU is not clearly confirmed either as 3-tier or 4-tier.

In NetBackup the server that performs operations of Management level is called as “NetBackup
Master Server”. In a NetBackup setup we have only one master server and the server that
performs all the execution part is called as “NetBackup Media Server”. In the end the servers
that hold data that is to be backed up are known as “NetBackup Clients”.

We have three different software packages for three levels.

1. NetBackup Master server software

2. NetBackup Media server software
3. NetBackup Client software

The Server that holds Master server software is known as Master server. Similarly the server
that holds media server software is known as media server and the server that holds client
software is known as NetBackup client.

By default NetBackup Media server software and client software are integrated in Master
server software. Hence a server installed with Master server software will also act as a media
server and client.

Also media server software is integration of Media server software and Client software. Hence
a media server can also be a client (but not Master).

NetBackup Client Software

NetBackup Media Server software

NetBackup Master Server software

Fig: NetBackup Architecture (3-tier)

Roles of Master, Media and NetBackup Client

Role of Master server:

 Holds hardware and OS information NetBackup Master, Media and clients

 Holds backup medium information (disk, tapes etc)
 Holds the details of the data that needs to be backed up.
 Holds the backup scheduling information and type of backup information
 Holds the information of data backed up.
 Holds the information and status of the backup hardware (disk, tapes, tape libraries etc)
 Based on the information of what data needs to be backed up master server instructs
media server to perform the backup operation.

Role of Media server:

 Based on the instructions given by Master server, media server arranges the storage
(tape or disk) and communicates with client to get the data written to the storage.
 It captures the activities involved in doing so. These are known as logs.
 Once the backup/restore operation is done it informs Master about it.
 Media server is the server which actually writes data to storage.

Client:

 The server that holds data to be backed up is known as client.

 This is responsible to provide data information to master and media server.
 Also it sends the data in chunks to media server.

NetBackup software is formerly said to have 3-Tier architecture. With introduction of EMM server with
NetBackup 6.x the architecture of NBU is not clearly confirmed either as 3-tier or 4-tier.
NetBackup Environmental Setup
Entire NetBackup environment is categorized into 5 parts.

1. Master Server
2. Media server(s)
3. Client(s) or SAN Media server(s)
4. Tape libraries, disk libraries, Tape drives and tape, disks
5. Network

Note: A huge client installed with media server software with a SAN media server license key is
called the SAN media server. Tape drives are directly connected to SAN media servers to move
data from disk to tape drives over FC excluding the slow network. SAN media server cannot be
used to backup data on other clients. Hence SAN media server is a server that backs up its own
data alone.
A Simple environment has only Master server, Media servers, clients and standalone disks or
tape drives. Master, Media and clients are connected in LAN. With standalone tape drives
directly connected to Media servers.

Stand alone tape drive need manual intervention to inject the tape and pick up the ejected
tape. These standalone tape drives are not recommended in huge environments where more
number of tapes being utilized per day.

Hence concept of Library is been introduced. Library is a closed box that contains slots – To
accommodate tapes, tape drives and a robot. Robot is a electro-Mechanical device that can
perform the actions like, moving tapes from slots to drives and vice versa. Some times from one
slot to another slot. This robot is replaced by Human in case of Standalone tape drives.

As huge data is processed across tape drives and media servers normal LAN cable is not used.
Instead FC Cable (Fiber Channel Cable) is used. Data is transmitted in the form of light through
FC. The principle used in FC is “Total Internal Reflection”. In order to convert the electrical data
signal into light we use transducers (Devices that convert one form of energy into another). We
use HBA cards to convert electrical signal to light and vice versa.

In order to reduce the complexity of the Network and increase the effective communication we
use intelligent devices such as Switches. Based on predefined settings these switches establish
a loss less communication between two devices on request.

In NetBackup environment all the media servers are connected to a Switch to which robot and
tape drives are connected.

A SAN Media server is a media server that is configured to take its own data backup. We
generally opt for a SAN media server if a client (server that holds data to be backed up) has
huge data (usually 1TB) on it. This makes drives free for backups of other small client. A
separate tape drive(s) has to be connected to this client and install Media server software to
make this Client a SAN Media server.
Hardware setup / Configuration
Following steps are involved in configuring tape drives

1. Connectivity (Tape Drive – SAN Switch – NetBackup Media server)

2. OS Driver configuration
3. NetBackup Device Driver Configuration
4. Tape Drive configuration/Addition
5. Storage Units
6. Storage Unit group

Tape Drive connectivity:

Tape drives are provided with both SCSI and FC ports for connectivity to servers. Latest tape drives are
provided with only FC ports (2 in number).

Tape Library Server Tape Drive

In either of the cases shown above the tape drive(s) are directly connected to server using a FC cable. In
order to connect FC cable the server should have HBA (Host Bus Adapter) which consists of FC ports.

Most Operating systems has default tape drive drivers which identifies the connected device, else the
OS drivers provided by the Tape Drive vendor has to be installed on the server.

How to identify whether OS has detected the connected tape drives?

Windows : System->Device Manager -> Hardware -> Tape drives

Solaris: ls –ltr /dev/rmt/*cbn
AIX: ls –ltr /dev/rmt*
If drives are not visible following steps has to be followed. (Involve field support, SAN and Server ops
team in confirming/performing the below)

1. Drive status has to be checked from Library web console/library CLI and make sure that drive is
online with no errors.
2. Check the cable connectivity between Tape drive to SAN switch
3. Confirm the respective zoning configuration.
4. Check the cable connectivity between SAN switch and NetBackup media server.
5. Confirm the HBA functionality with Server ops team
6. Reboot the server with reconfigure option enabled.

Once devices are visible from OS end, we require NetBackup Device drivers to be installed in order for
NetBackup to use the drives connected to and detected by OS.

Windows: NetBackup Device Drivers

Solaris: SG Drivers
AIX: OV Pass Drivers

Device configuration steps on Solaris machine:

1. cd /usr/openv/volmgr/bin/driver
2. /usr/openv/volmgr/bin/[Link] –all –mt 15 –ml 1 (Targets and lun size depends on the type of
storage attached – library [mt 15 ml 1]or VTL [mt 15 ml 18])
3. cat /usr/openv/volmgr/bin/driver/[Link] > /kernel/drv/[Link]
4. /usr/sbin/rem_drv sg
5. /usr/bin/rm -f /kernel/drv/[Link]
6. /usr/openv/volmgr/bin/driver/[Link]

Run the below command to test whether the desired tape drives / robots are visible to NetBackup or
not

/usr/openv/volmgr/bin/tpautoconf –t
<Lists the tape drives>

/usr/openv/volmgr/bin/tpautoconf –r
<Lists the robot or medium changer>

Note: NetBackup services should be up and running fine while running this command.
Note: ACS robot is not visible to OS as robot is not physically connected to NetBackup server, else it is
connected to ACSLS server.
Configuring a Robot Manually

Adding a robot on robot control host

/usr/openv/volmgr/bin/tpconfig -add -robot robnum -robtype robtype -robpath devfile [-nh
ndmp_hostname]

Ex:
Robot type: TLD
Robot Number: 0
Robot Path: /dev/c0t0xxxxxx

#tpconfig –add –robot 0 –robtype tld –robpath /dev/c0t0xxxxxx

Adding a robot on non-robot control host

/usr/openv/volmgr/bin/tpconfig -add -robot robnum -robtype robtype -cntlhost cntlhost

Ex:
Robot type: ACS
Robot Number: 1
ACLS Server: acls_server

#tpconfig –add –robot 1 –robtype acs –cntlhost acls_server

Configuring a Tape Drive Manually

/usr/openv/volmgr/bin/tpconfig -add -drive -type drvtype -path drivepath

[-nh ndmp_hostname] [-vhname optical_volume_header_drive_name]
[-asciiname asciidrivename] [-index drvindex]] [-shared [yes|no]]
[-cleanfreq hours] [-comment comment] [-drstatus UP | DOWN | DISABLED]
[-scsi_protection [SPR | SR | NONE] [-robot robnum -robtype robtype]
[-noverify] [-robdrnum robdrvnum | -VendorDrvName venddrvname | -ACS
acsnum -LSM lsmnum -PANEL panelnum -DRIVE drivenum] [-preview]

Ex 1:
Tape Drive type: hcart3
Drive path: /dev/rmt/0cbn
Robot type: TLD
Robot number: 0
Robot drive number: 1
#tpconfig –add –drive –type hcart3 –path /dev/rmt/0cbn –asciiname Tape_Drive_1 –shared no –
drstatus UP –robot 0 –robtype tld –robdrnum 1
Ex 2:
Tape Drive type: hcart4
Drive path: /dev/rmt/1cbn
Robot type: ACS
Robot number: 1
ACS = 0 ; LSM = 0 ; PANEL = 1 ; DRIVE = 2

#tpconfig –add –drive –type hcart –path /dev/rmt/0cbn –asciiname Tape_Drive_1 –shared no –drstatus
UP –robot 1 –robtype acs –ACS 0 –LSM 0 –PANEL 1 –DRIVE 2

Note 1: The robot definition should exist and checked prior to adding the drive associated to it. Or else
the tape drive will be configured as a standalone tape drive.
Note 2: The HCART4 tape drives and tapes are configured as HCART type in NetBackup.
Note 3: Use the command “tpconfig” without any switches to enter into menu based configuration

Automatic robot (Medium changer) and tape drive configuration:

Run the below command to configure all the devices (Robot and Tape drives) detected by NetBackup
with default automatic steps.

#/usr/openv/volmgr/bin/tpautoconf –a

CAUTION: Please go through the command properties and syntax in commands pdf before using the
command. Do not use the above command to add/modify the properties of individual or group of
drives/devices when all devices are not to be added. Also do not use the above command in an existing
environment.

Restart the NBU services on master and media servers to reflect the changes/configurations
made

Run the following command (either from master/media server) to check whether the devices
configurations are reflected in EMM server.

#/usr/openv/volmgr/bin/vmoprcmd –d –h <Media server name>

Once all the devices are configured on all media servers, Storage Units and Storage unit groups can be
configured.
Tape Storage Unit has to meet the following conditions/requirements.

 Drive belong to one media server can be grouped under a single storage unit
 Drives of same type can be grouped under a single storage unit
Storage Units
Creating a storage unit

The following sections describe different methods to create a storage unit.

 To create a storage unit with the Device Configuration Wizard

1 In the NetBackup Administration Console tree, select the Master Server or Media and Device
Management.
2 From the list of wizards in the Details pane, click Configure Storage Devices and follow the
wizard instructions. For help while running the wizard, click the Help button in the wizard
screen.

 To create a storage unit from the Actions menu

1 In the NetBackup Administration Console, select NetBackup Management > Storage. Storage
unit information appears in the Details pane.
2 Click Actions > New > Storage Unit. The New Storage Unit dialog box appears.
3 Complete the fields on the New Storage Unit dialog box.
4 Click OK to add the storage unit to the configuration.

 To create a storage unit by copying an existing storage unit

1 In the NetBackup Administration Console, select NetBackup Management > Storage. Storage
unit information appears in the Details pane.
2 Select a storage unit in the Details pane.
3 Click Actions > Copy Storage Unit. The Copy Storage Unit dialog box appears.
4 Complete the fields in the Copy Storage Unit dialog box.

Changing storage unit settings

Symantec suggests that changes be made only during periods when no backup activity is
expected for the policies that use the affected storage units.
To change storage unit settings

1 In the NetBackup Administration Console, select NetBackup Management > Storage. Storage
unit information appears in the Details pane.
2 Double-click the storage unit you want to change from those listed in the Details pane.
3 Complete the fields on the Change Storage Unit dialog box.
Deleting storage units

To delete a storage unit from a NetBackup configuration means to delete the label that
NetBackup associates with the physical storage.

To delete a storage unit does not prevent files from being restored that were written to that
storage unit, provided that the storage has not been physically removed and the backup image
has not expired.

To delete a BasicDisk or Media Manager storage unit 1 Use the Catalog utility to expire any
images that exist on the storage unit. This removes the image from the NetBackup catalog.

■ Do not manually remove images from the BasicDisk or Media Manager storage unit.
■ Once the images have been expired, they cannot be restored unless the images are imported.

NetBackup automatically deletes any image fragments from a disk storage unit or a disk pool.
This generally occurs within seconds of expiring an image. However, to make sure that all of the
fragments have been deleted, check the directory on the storage unit to make sure that it is
empty.

2 Select the Storage utility, then Storage Units.

3 In the Details pane, select the storage unit you want to delete. Hold down the Control or Shift
key to select multiple storage units.
4 Select Edit > Delete.
5 In the confirmation dialog box, select the storage units to delete.
6 Click OK.
7 Modify any policy that uses a deleted storage unit to use another storage unit. To delete a
storage unit that references a disk pool. If a storage unit points to disk pool, the storage unit
can be deleted without impacting the disk pool.

Multiplexing

Allowing more than one backup job to use the tape drive simultaneously is called
multiplexing. The Symantec suggested value is 1. The value may vary in between 1 and 32.

More multiplexing value increases the difficulty in retrieving the data during the restores.

Lower values are suggested for DB backups and higher multiplexing values are suggested for file
system backups.
Storage Unit Group
Storage unit groups allow you to identify specific storage units as a group. A storage unit group
name can be specified in a policy in the same way that individual storage units can be specified.
When a storage unit group is used in a policy, only the storage units that are specified in the
group are candidates for the backup.

Storage unit selection criteria within a group

The storage unit selection criteria determine the order that storage units are selected when
they are included in a group. Choose from one of the following selection criteria.

 Prioritized

NetBackup chooses the first storage unit in the list that is not busy, down, or out of media. Also,
the storage unit must not have reached the maximum concurrent jobs setting. When one of the
specified conditions occurs, the next storage unit in the list is examined until NetBackup finds
an available storage unit. If one is not available or if one does not have enough available space,
the job fails and is not queued. (Default.)

 Failover

NetBackup chooses the first storage unit in the list that is not down, out of media, or full. If a
storage unit is only busy, the policy waits to write to it. The other storage units are used as
failovers. NetBackup queues a job to wait for the first storage unit if the maximum concurrent
jobs setting is reached.

 Round robin

NetBackup chooses the least recently selected storage unit in the list as each new job is started.
If a storage unit is not available, or if no unit has available space, the job fails and is not queued.
NetBackup does not continue to select the same storage unit.

 Load balance

The Load balance option allows NetBackup to select storage units based on a capacity-managed
approach. NetBackup avoids sending jobs to busy media servers.
The selection is based on the following factors:
1 The rank of the media server. NetBackup considers the number of processes that are running
on each CPU along with the memory thresholds on each server to determine the rank of a
media server. If the free memory drops below a determined threshold, or if the number of
running processes per CPU rises above a determined threshold, then the overall rank of the
media server drops.

2 The number of jobs on the media server. NetBackup considers the number of scheduled jobs
on each media server.

3 Whether the media server has enough disk space to accommodate the estimated size of the
image NetBackup estimates the size of any new or current jobs on each media server and
determines whether the jobs will fit on a given volume. NetBackup estimates the amount of
space that the job may require, based on previous backup history. If no history is available, the
high water mark for the storage unit serves as a guide.

When is the Load balance option available?

Load balance cannot be selected for a storage unit group that includes a BasicDisk storage unit.
Also, a BasicDisk storage unit cannot be included in an existing storage unit group with Load
balance enabled.

Creating a storage unit group

To create a storage unit group

1. In the NetBackup Administration Console, expand NetBackup Management > Storage.

2. Right-click Storage Unit Groups and select New. The New Storage Unit Group dialog box
appears.
3. Enter a storage unit group name for the new storage unit group.

Note: The storage unit group name is case-sensitive.

4. Add to or remove storage units from the group:

a. To add storage units to the group, select the storage units from the Storage units not
in the group list. Click Add.
 b. To remove storage units from the group, select the storage units from the Storage
units in group list. Click Remove.
c. Storage units are listed in order of priority: The units at the top of the list having the
highest priority in the group. To change the priority of a storage unit, select the
storage unit and click Increase Priority or Decrease Priority.

Note: SnapVault, NearStore, and PureDisk storage units cannot be included in storage unit
groups.

5. Choose how storage units are to be selected within the group:

 Prioritized: Choose the first storage unit in the list that is not busy, down, or out of
media.
 Failover: Choose the first storage unit in the list that is not down or out of media.
 Round Robin: Choose the least recently selected storage unit in the list.
 Load Balance: Symantec recommends the Load Balance criteria for disk staging storage
units within a storage unit group.

6. Click OK.

Deleting a storage unit group

To delete a storage unit group

1. In the NetBackup Administration Console, select NetBackup Management > Storage >
Storage Unit Groups.
2. Select the storage unit group you want to delete from those listed in the Details pane. Hold
down the Control or Shift key to select multiple storage units.
3. Select Edit > Delete. A confirmation dialog box appears.
4. Click OK.
Volume or Media configuration

Media ID Generation tab

To use media ID generation rules, the robot must support barcodes and the robot cannot be an
API robot.

Media ID generation rules lets you override the default media ID naming method. The default
method uses the last six characters of the barcode label from the tape. You can control how
NetBackup creates media IDs by defining the rules that specify which characters of a barcode
label to use for the media ID.

 To add a rule, click New and then configure the rule in the dialog box.
 To change a rule, select the rule, click Change and then change the rule in the Change
Media ID Generation Rule dialog. You cannot change the robot number or barcode
length of a rule. To change those properties, you must first delete the old rule and then
add a rule.

 To delete a rule, select the rule, click Delete, and then click OK in the confirmation
dialog. You can select and delete multiple rules with one operation.
Adding volumes

Several methods exist to add new volumes to NetBackup, as follows:

1. Adding volumes by using the Volume Configuration Wizard

2. Adding volumes using a robot inventory update
3. Adding volumes using the Actions menu

To help you determine which method to use, review the following

Adding volumes by using the Volume Configuration Wizard

Use this wizard to do the following:

1. Inventory robots: An inventory operation:

o Identifies media in a robot (including new media in an existing robot)
o Adds that media to the NetBackup configuration
2. Add volumes for stand-alone drives.
3. Update the Enterprise Media Manager (EMM) database.

After the wizard configures media, each media has a unique media ID in the EMM database.
The wizard uses the default media type for the drive to create the media type.

Review the limitations in the wizard help before you configure volumes.

To start the Volume Configuration Wizard

In the NetBackup Administration Console, select Media and Device Management  Configure
Volumes.

Adding volumes using a robot inventory update

A robot inventory update generates media IDs for new volumes as follows:

1. If the robot supports barcodes and the new volumes have readable barcode labels,
NetBackup generates media IDs based on one of the following:
 a. The last six characters of the barcodes (the default method). New volumes are
assigned a media type, volume pool, maximum number of mounts (or maximum
cleanings), and description.
b. The characters that you specify if you use media ID naming rules.
2. If the robot does not support barcodes or the volumes do not have readable barcodes,
media IDs are based on a prefix that you specify.

To add volumes using a robot inventory update

1. Insert the volume(s) into the robotic library.

2. In the NetBackup Administration Console, select Media and Device Management  Media
 Robots.
3. Select the robotic library where you inserted the volume.
4. Select Actions > Inventory Robot.
5. In the Inventory Robot dialog, select Update volume configuration.
6. For more options, click Advanced Options.
7. To clear any previous display in the Results section, click Clear Results.
8. Click Start to start the update.

Adding volumes using the Actions menu

Note: Symantec recommends using the Volume Configuration Wizard or a robot inventory to
add volumes.

To add volumes using the Actions menu

1. For new volumes in a robotic library, insert them into the proper slots.
2. In the NetBackup Administration Console, select Media and Device Management > Media.
3. Select Actions > New > Volumes.
4. In the Add Volumes dialog, specify the attributes for the volumes.

Note: Be careful when you specify properties. You cannot change some properties later, such as
the media ID or type. If you specify them incorrectly, you must delete the volume and add it
again.

The Apply button adds the volume without closing the dialog or refreshing the display. You can
add another volume by modifying the dialog contents and then click Apply or OK.
If the robot has a barcode reader, NetBackup does the following:

 Adds the volume to the EMM database using the specified media ID.
 Reads the barcode of each new volume.
 Adds the barcodes as attributes in the EMM database.

Freezing and unfreezing media

A frozen volume is unavailable for future backups. A frozen volume never expires, even after
the retention period ends for all backups on the media. The media ID is never deleted from the
NetBackup media catalog, and it remains assigned to NetBackup.

A frozen volume is available for restores. If the backups have expired, you must import the
backups first.

To freeze or unfreeze media

1. In the NetBackup Administration Console, select Media and Device Management > Media.
2. In the Volumes list, select the volume that you want to freeze or unfreeze.
3. Select Actions > Freeze or Actions > Unfreeze.
4. In the dialog box, click OK.

Suspending and un-suspending media

You cannot use a suspended volume for backups until retention periods for all backups on it
have expired. At that time, NetBackup deletes the suspended volume from the NetBackup
media catalog and unassigns it from NetBackup. A suspended volume is available for restores. If
the backups have expired, you must import the backups first.

To suspend or UN-suspend media

1. In the NetBackup Administration Console, select Media and Device Management > Media.
2. In the Volumes list, select the volume that you want to freeze or unfreeze.
3. Select Actions > Suspend or Actions > Un-suspend.
4. In the dialog box, click OK.
NetBackup Media Basics

In NetBackup environment any configured media is categorized based on below two criteria

1. Physical location of tape

2. Utilization of a tape

The categorization based on “Physical location of tape” comes up with concept called “Volume Group”.
A volume group indicates where the tape is in, whether it is in library and ready for use or out of library
(Offsite – any tape out of library is considered as offsite).

Volume group name is user defined and will add more sense to the location of a tape.

Example:

A tape which is inside tape library

A tape which is outside tape library

 Tape ejected manually

 Tape ejected by VAULT.

From the examples shown above we can clearly observe the difference. For a tape which is inside library
we can see volume group as “00_000_ACS” which is a user defined name indicating that the tape is
inside library. For a tape which is inside library we can see some more info like robot type and robot
number as well.

Volume Group for a tape which is out if silo (library) is either “-----“or “<User defined name>”.

Now coming to media categorization based of utilization of tapes. Here comes the concept of “Volume
pool”. Volume pool is a logical partition of all the configured media. This is required in order to
categorize and identify the data backed up with in a NetBackup environment.

Default NetBackup volume pools:

NetBackup
Datastore
None
Catalog

Note: Each and every tape in a NetBackup environment contains Volume Group and Volume pool.
Volume group defines the location of the tape and volume pool defines where and how the tape is being
utilized.

Scratch Pool:

Before we speak of Scratch pool, will just see what a scratch tape is.

Any tape which is configured in a NetBackup environment and do not carry any valid backup image of
any client backed up in the NetBackup environment is called a Scratch tape. Simply a tape which does
not carry known information to a master server is called a scratch tape to that master server.

These tapes contain no data on them. They can be used for any kind of backup.

Note: A tape containing valid data belong to one NetBackup environment will act as a scratch tape in
another NetBackup environment.

Scratch pool: A volume pool which lists out all the scratch media. Scratch pool is unique and has a
unique feature i.e. whenever all the data on a tape expires irrespective of the volume group (Tape
location) the tape is moved automatically into this pool.
How to Identify a Scratch Pool

1. Right click on Volume pool and select “Change”

2. Check whether the check box indicating “Scratch pool” is selected or not. If selected it is considered
as Scratch pool.
Robot Inventory

Updating the volume database with the available tapes in the tape library is called Inventory or
Robot Inventory.

Performing the robot inventory

Step 1:

Expand Media and Device Management

Expand Media

Expand Robots – Right click on the robot number for which inventory has to be performed.

Select “Inventory Robot…”

Step 2:

A pop window appears.

Select appropriate “Device Host” and “Robot”

Select radio button “Update Volume Configuration”. – This option updates the volume
database.
Check the check box “Empty media access port prior to update”. – This option moves the tapes
from library CAP/MAP (cartridge access port / media access port) to library slots prior updating
the volume database.

Click “start” Button to perform the inventory. Upon completion of inventory the results will be
displayed in results tab.
Advanced Robot Inventory Options
Media Settings tab

Use the Media Settings tab of the Advanced Robot Inventory Options dialog box to do the
following:

 Specify the volume group for existing media

 Specify media options for new media

Barcode Rules tab

Use the Barcode Rules tab of the Advanced Robot Inventory Options dialog box to configure
rules for assigning attributes to new volumes added to a robot. These rules are used when you
specify Use barcode rules on the Media Settings tab.

 To add a rule, click New and then configure the rule in the dialog box.
 To change a rule, select the rule, click Change, and then change the rule in the Change
Barcode Rule dialog box. You cannot change the barcode tag of a barcode rule. You
must first delete the old rule and then add a rule with a new barcode tag.
 To delete a rule, select the rule, click Delete, and then click OK in the confirmation
dialog. You can select and delete multiple rules with one operation.
Barcode tag - The barcode tag is a unique string of characters from the barcode that identifies
the type of media.

Maximum mounts - The maximum number of mounts (or cleanings) that are allowed for the
volume. For data volumes, a value of 0 means the volume can be mounted an unlimited
number of times. For cleaning tapes, 0 means the cleaning tape is not used. To avoid a value of
0 for cleaning tapes, use barcodes for your cleaning media that cannot be confused with
barcodes for data media.

Media type - The media type to assign to the media.

Volume pool - Specifies the volume pool for the new media.
If you use a barcode rule and the Media Settings tab Volume pool field is set to:
 DEFAULT, the volume is assigned to the pool you specify in this Volume pool setting.
 A specific volume pool, the Volume pool setting on the Media Settings tab overrides this
Volume pool setting.
Policies
Policies define the rules that NetBackup follows when clients are backed up. A backup
policy can apply to one or more clients. Every client must be in at least one backup policy. The
best approach to configure backup policies is to divide clients into groups according to the
backup requirements and archive requirements. Then, create a policy for each group.

Policy Attributes tab

The settings on the Attributes tab determine the characteristics of all the backups that
NetBackup performs according to the selected policy. The following items are a few of the
attributes that are defined on the Policy Attributes tab:

 Whether the selected policy is currently active or what date and time the policy goes into
effect.
 The type of backup policy, which primarily defines the type of clients the policy backs up.
 The priority that NetBackup gives to the backups for the selected policy relative to other
policies.
 The storage unit that NetBackup uses to back up the clients in the selected policy.
 Snapshot Client attributes, if Snapshot Client is installed.

The following sections describe the settings on the Attributes tab. Policy attributes are
configurable depending on the type of policy and the options that are installed.

Policy type

The Policy type attribute determines the purpose of the policy. Usually, the Policy type
determines the type of clients that can be backed up by this policy. Not all policy types serve to
back up clients. (Vault, for example.) Select the type of policy from the drop-down list.

The Policy type of an existing policy may be changed. However, the existing schedules may
become invalid for the new policy type. If the schedules become invalid, NetBackup displays an
alert notice. NetBackup then either deletes the invalid schedules or changes the schedules to
an equivalent type.

Data classification
Select a Data Classification if you want the backup to go to a storage unit that stores backups of
a particular classification. For example, a gold backup must go to a storage unit with a gold data
classification. A Data Classification selection is optional. If no classification is indicated, the
policy uses the storage units and groups that the Policy storage attribute indicates. If a data
classification is selected, all the images that the policy creates are tagged with the classification
ID.

Policy storage

The Policy storage attribute specifies the storage destination for the policy’s data. Select the
storage destination from the drop-down list. If configured, the drop-down list may contain
storage units, storage lifecycle policies, and storage unit groups.

Policy volume pool

The Policy volume pool attribute specifies the default volume pool where the backups for the
policy are stored. A volume pool is a group of media that is grouped together for use by a single
application. The volume pool is protected from access by other applications and users.

Select a volume pool name from the list of volume pools. Whenever a new volume is required,
it is allocated from the volume pool indicated.

Checkpoint restart for backup jobs

The 'Take checkpoints every' check box specifies whether NetBackup takes checkpoints during a
backup job. Indicate how often the policy should take checkpoints. Checkpoints during a backup
are beneficial if a backup fails. Without Take checkpoints every enabled, a failed backup restarts
from the beginning of the job. By taking checkpoints periodically during the backup, NetBackup
can retry a failed backup from the beginning of the last checkpoint rather than restart the
entire job.

Note that checkpoints cannot occur while a file is backed up. Checkpoints are saved at file
boundaries, and point to the next file in the list. The Schedule backup attempts Global
Attributes host property indicates the number of times that NetBackup tries a failed backup.

Policy types MS-Windows-NT (for Windows clients) and Standard (for UNIX clients) support this
policy attribute. To see if this feature is supported for a specific agent or option, refer to the
manual for that agent or option.
Limit jobs per policy

The Limit jobs per policy attribute limits the number of jobs that NetBackup performs
concurrently when the policy is run. By default, the check box is clear, and NetBackup performs
an unlimited number of backup jobs concurrently. Other resource settings can limit the number
of jobs. A configuration can contain enough devices so that the number of concurrent backups
affects performance. To specify a lower limit, select the check box and specify a value from 1 to
999.

Job priority

The Job priority attribute specifies the priority that a policy has it competes with other policies
for backup resources. To have a higher priority means that NetBackup assigns the first available
drive to the first client in the policy with the highest priority. To set the priority, enter a number
in the Job priority field (maximum 99999). The default for all policies is 0, the lowest priority
possible. Any policy with a priority greater than zero has priority over the default setting.

Media owner

Active only for Media Manager type storage units or if the Policy storage attribute is Any
Available. The Media Owner property specifies which media server or server group should own
the media on which backup images for this policy are written.

You can specify the following for Media Owner:

 Any (default), allows NetBackup to choose the media owner. NetBackup chooses a media
server or a server group (if one is configured).
 None specifies that the media server that writes the image to the media owns the media.
No media server is specified explicitly, but you want a media server to own the media.
 A server group. Specify a server group. A server group allows only those servers in the group
to write to the media on which backup images for this policy are written. All server groups
that are configured in the NetBackup environment appear in the drop-down list.

Active Go into effect at

To activate the policy, select the Active check box. The policy must be active for NetBackup to
use the policy. The Go into effect at attribute specifies when the policy can begin to schedule
backups. For example, if today is Monday and you enter Wednesday at 12:00 AM, the policy
does not run until that time or later. Use the Go into effect at attribute to configure a series of
policies in advance of when the policies need to become active.

To deactivate a policy, clear the Active check box. Inactive policies appear in gray in the
Administration Console. To resume backups, recheck the Active check box. Make sure that the
Go into effect at date and time is set to the time that you want to resume backups.

If the schedule is to be used for a catalog archive, the policy must not be active. The Active
check box must be clear.

Backup network drives

The Backup network drives attribute is for use on single user systems, Win95, Win98, and ME.
These operating systems are not supported with this version of NetBackup. The preferred
method for backing up data from a machine other than a NetBackup client is to use UNC paths.
UNC paths are more precise and indicate exactly what should be backed up. When Backup
network drives or UNC paths are used, the network drives must be available to the service
account that the NetBackup Client service logs into at startup. By default, the startup account is
set to System. You must change this account on each Windows client that is backed up that
contains data that is shared from another machine.

Backup network drives must be checked when policies back up to CD ROM drives. For
scheduled backups, the file list must indicate at least the first level of folders to be backed up.
For example, D:\Folder1 instead of only D:\

Note: Mapped drive letters cannot be backed up. Drive letters do not appear in the Backup,
Archive, and Restore console when backups are browsed.

Follow NFS

The Follow NFS attribute specifies whether NetBackup is to back up or archive any NFS-
mounted files that are named in the backup selection list or by the user in the case of a user
backup or archive. Clear the check box to prevent the backup or archive of NFS mounted files.

Note: The Follow NFS attribute applies only to UNIX clients in certain policy types. NetBackup
allows it to be selected in those instances only.
Advantages of the Follow NFS attribute

The Follow NFS setting eliminates the need to locate and log on to the systems where the files
reside. If the files are mounted on the NetBackup client, you can back up, archive, and restore
them by working from the NetBackup client. You must have the necessary permissions on the
NFS mount. Use this capability to back up the systems that the NetBackup client software does
not support.

Disadvantages of the Follow NFS attribute

Generally, do not back up NetBackup clients over NFS. Back up and archive files on the NFS
server where the files physically reside. NFS backups have lower performance and sometimes
encounter problems. Multiple backups can result in the following situations: if files are backed
up at the host where they physically reside and by the local NFS clients that mount the files. If
Follow NFS is selected, you may want to use the policy only for the files and clients that are
backed up or archived over NFS.

Cross mount points

The Cross mount points attribute controls whether NetBackup crosses file system boundaries
during a backup on UNIX clients.

Select Cross mount points to have NetBackup back up all files and directories in the selected
path, regardless of the file system. For example, if you specify root(/) as the file path,
NetBackup backs up root(/) and all files and directories under rootin the tree. NetBackup
specifically excludes mapped directories even if Follow NFS and Cross mount points are
enabled. To back up mapped directories, include the directories in the file list.

Clear Cross mount points for NetBackup to back up only the files that are in the same file
system as the selected file path. Prohibit NetBackup from crossing mount points to back up
root(/) without backing up all the file systems that are mounted on root. (For example, /usr and
/home.)

Do not cross mount points to back up a media server that uses mount points to any disk storage
that contains backup images. If the policy crosses mount points, the NetBackup backup images
that reside on that disk storage are backed up. The NetBackup BasicDisk disk type and the
Enterprise Disk Option disk types use mount points for disk storage.
Allow multiple data streams

The Allow multiple data streams attribute specifies that NetBackup can divide automatic
backups for each client into multiple jobs. The directives, scripts, or templates in the backup
selection list specify whether each job can back up only a part of the backup selection list. Since
the jobs are in separate data streams, they can occur concurrently.

The directives, scripts, or templates in the backup selection list determine the number of
streams (backup jobs) that start for each client. The list also determines how the backup
selection list is divided into separate streams.

The following settings determine the number of streams that can run concurrently:

Number of available storage units

Multiplexing settings
Maximum jobs parameters

Multiple data stream jobs consist of a parent job to perform stream discovery, and children jobs
for each stream. In the Activity Monitor, the children jobs display the Job ID of the parent job.
Parent jobs display a dash (-) in the Schedule column.

Note: If this attribute is enabled, and a file system is in a client’s exclude list, a NetBackup job
appears in the Activity Monitor for the excluded file system. However, no files in the excluded
file system are backed up by the job.

Schedules tab

The schedules that are defined on the Schedules tab determine when backups occur for the
policy that is selected. Each schedule also includes various criteria, such as how long to retain
the backups. NetBackup has two categories of schedules:

Automatic schedules back up the items that are listed in the backup selection list on all clients
in the policy. The items are backed up according to the timetables that are set up in the
schedules.

User schedules specify the times when users can start user backups and archives from the
clients. A user archive is a special type of backup that deletes the files from the user disk if the
backup is successful. An archive is useful to free disk space while keeping a copy for future use.
From the policy Schedules tab, perform the following tasks:

To create a new schedule click new.

To edit a schedule, select the schedule and click Change.
To delete a schedule, select the schedule and click Delete.

Schedule attributes appear on four tabs:

 Attributes tab: Schedule the time and frequency at which a task runs, along with other
scheduled attributes.
 Start Window tab: Schedule the time of each day that a task runs.
 Exclude Dates tab: Indicate the dates that a task should not run.
 Calendar Schedule tab: Schedule the run days for a task by indicating specific dates,
recurring weekdays, and recurring days of the month. (This tab appears only when Calendar
is selected as the Schedule type.)

Clients tab
The Clients tab contains a list of clients to be backed up (or acted upon) by the selected policy.
A client must be included in the list of at least one backup policy to be backed up. A client can
be placed in more than one backup policy can be useful. For example, place the client name in
two policies to back up different sets of files on the client according to different policy rules.
NetBackup software can be installed on UNIX client machines from the Clients tab

Backup Selections tab

The Backup Selections tab lists the files, directories, directives, scripts, and the templates that
are backed up with this policy. NetBackup uses the same backup selection list for all of the
clients that are backed up according to the policy. Every file on the list does not need to exist on
all of the clients. NetBackup backs up the files that it finds that are on the backup selections list.
Each client, however, must contain at least one of the files in the backup selections list or the
client backup fails with a status 71. The policy backup selections list does not apply to user
backups or archives. For user backups and archives, users select the objects to back up before
they start the operation.
 NetBackup Catalog
NetBackup Catalog is the internal databases of NetBackup which maintains a complete record of
Hardware, Hardware configuration, Hardware Status, client backup history etc.

NetBackup catalog is majorly categorized in to three sections.

1. Image Database
2. Relational Database
3. Configuration files

Image Database

Image Database has the NetBackup client’s backup information. This DB resides under the directory
“/usr/openv/netbackup/db/images”. The image DB is in the flat file form.

How DB holds the data of each backup.

/usr/openv/netbackup/db/images

Client 1 Client 2 Client 3 Client n

D-C time D-C time D-C time

1 2 n

POLICY_CTIME_BTYPE File
POLICY_CTIME_BTYPE.f File

POLICY_CTIME_BTYPE File
POLICY_CTIME_BTYPE.f File

etc
C-Time:

C-Time is a 10 digit decimal number where 0 represents the time “31st Dec, 1969 – [Link]”. As the C-
Time values increases the number of seconds elapsed increases from the start time.

Example: the C-Time 0000003600 represents the time “31st Dec, 1969 – [Link]”.

The Directory C-Time is a directory named with the modified C-time of the backup start time. The D-C
time (Directory name) has the first 4 digits (from left) similar to the Backup start C-Time and rest 6 digits
are zeros.

Example:

Let the backup C-Time be “1267356267”, the backup image file for this particular backup resides under
the D-C time directory named “1267000000”.

The files residing under the D-C Time directories are the actual files that consists of detailed information
of the backup.

These files are of two types

1. Image file (POLICY_CTIME_BTYPE)

2. Full file (POLICY_CTIME_BTYPE.f)

The image file consists of high level information of the backup, as in the client name, policy name, policy
type, schedule name, schedule type, retention, multiplexing level used, backup start time, elapsed time
in seconds, expiry date, tapes used, number of copies used etc.

The full file (Files file) consists of detailed information of each file that was backed up. This is a binary file
and is not in human readable format. This size of this file goes as higher as 10 GB.

NetBackup Relational Data Base

The following two Databases are considered to be NetBackup Relational Database. These Databases are
Sybase Databases.

NBDB
BMRDB
NBDB – NetBackup Database is nothing but NetBackup Enterprise Media Manager Database (NB EMM
DB). This database replaces the Volume Database, Media Database and Global Database which were
part of catalog in NetBackup 5.1 and earlier versions.

Following Files are considered to be set of DB files related to EMM (NBDB).

/usr/openv/db/data/[Link]
/usr/openv/db/data/[Link]
/usr/openv/db/data/EMM_DATA.DB
/usr/openv/db/data/EMM_INDEX.DB

Following files are considered to be set of BMR DB files. These does exist only if BMR option is enabled
(installed).

/usr/openv/db/data/[Link]
/usr/openv/db/data/[Link]
/usr/openv/db/data/BMR_DATA.DB
/usr/openv/db/data/BMR_INDEX.DB

Configuration files

Apart from Image DB and Relational DB the catalog has few other configuration files.

/usr/openv/db/data/[Link]
/usr/openv/var/global/[Link]
/usr/openv/var/global/[Link]

Note: The catalog backup process copies this data to /usr/openv/db/staging and backs up the copy.
NetBackup 6.x Backup Process (Daemon Flow)

NetBackup 6.5 Daemon flow

Before starting with the daemon flow, lets discuss what information is required if we want to take a
backup manually and what process we follow.

Requirements:

1. Server name

2. What to be backed up?

3. Where to backup? (tape drive and tape number[media id])

4. When to backup? (scheduling)

5. Backup type (full/differential or cumulative)

6. Retention period

Process we follow (manually)

1. On specified time, communication with the server is checked thoroughly.

2. On successful communication tests, we arrange specified tape drive with specified tape in it.

3. Select the data on the client based on the backup type.

4. Start moving the selected data on to tape.

5. Once data is moved on to tape successfully eject the tape and secure it till the retention period.

NetBackup also follows similar process. Here are the steps and respective responsible daemons.
 NetBackup Daemon flow – Manual Backup with neither multi-streaming nor snapshots

Master Server:
NBPEM fetches the
policy, schedule and START
client details from DB
NB Catalog

BPRD accepts the user

NetBackup Database request and passes the
BPRD – Backup request Daemon
information to NBPEM

2
BPDBM NBPEM NBPEM Initiates NBJM and
Backup Data Base Manager NetBackup Policy Execution Manager passes the policy, schedule
and client details

NBJM requests BPJOBD for a

JOBID to record the progress 3

4
BPJOBD NBJM
Backup JOB DAEMON NetBackup JOB Manager

NBJM initiates BPCD

on client to check
the communication
NBEMM
EMM between master and
NetBackup Enterprise
DB Media Manager client machine
5 6

BPCD
NBRB Backup Client Daemon
NetBackup Resource Broker
NBRB provides tape drive
name and media id to NBJM Client machine
EMM Server by taking storage unit name
and volume pool name from
NBJM.
7

NBJM initiates BPCD and

there by BPBRM on
corresponding media server.
 Client Machine
Media Server
BPCD
Backup Client daemon

9
BPBRM BPCD
Backup Restore Manager Backup Client daemon

8
12
BPTM
Backup Tape Manager
BPBKAR
10 Backup Archive and
11 Restore
13
LTID BPTM Child BUFFER
Tape library Daemon Backup Tape Manager Child

BUFFER

14

0. User provides policy, schedule and client name to bprd

1. Bprd calls nbpem and provides the data to nbpem

2. Nbpem fetches the complete information of the provided data with the help of bpdbm

3. Nbpem calls nbjm and provides the policy, client and schedule details
4. Nbjm gets a jobid for the task with the help of bpjobd

5. From policy information, nbjm fetches storage unit and volume pool name, and from schedule

6. details it fetches retention, type of backup and multiplexing which are provided to nbrb to get
tape drive name and media id.

7. Nbjm talks to bpcd on client to check the communication

Now nbjm has the following information
- Client name
- Backup selection
- Backup type
- Tape drive name
- Media id
- Media server name (is retrieved from storage unit details)
- Retention period
8. All this information is provided to bpbrm of the respective media server.

9. Bpbrm initiates bptm to get the specified tape drive ready with the specified tape in it.

10. Bpbrm talks to bpcd on client to check the communication between media and client machine.

11. Bptm initiates the Ltid daemon – which is a script (daemon) that can manage the robotic
operations, which will arrange the tape drive and tape ready for the backup.

12. Bptm initiates a child process to handle the request.

13. Bpcd on client initiates bpbkar - which will collect the specified data on client .

14. Bpbkar collects the data on to its own buffer which is transferred to bptm child which will store
the data in its buffer.

15. Once the media server buffer is full the data from buffer is sent to tape by bptm child process.
Installation of NetBackup 6.x software on UNIX
server

Pre-Installation Software Requirements

 Open a support case with Symantec.

 NetBackup License Key Requirements
 NetBackup Supportability (Server Hardware, OS, Robots, drives, tapes) – Check release
notes
 NetBackup software CDs or dumps
 NetBackup options and agent software CDs or dumps.
 VERITAS recommends that you remove any other vendor backup software currently
configured on your system before installing this product. Other vendor backup software
can negatively affect how NetBackup installs and functions.
 For reasonable performance of the NetBackup-Java interfaces, you need 512 MB of
RAM, of which 256 MB are available to the interface program (jnbSA or jbpSA).
 Ensure that you have the minimum screen resolution configuration is 1024x768, 256
colors.
 Ensure that you have the root password for the server.
 Ensure that the gzip and gunzip commands are installed on the local system, and that
the directories where the commands are installed are part of the root user’s PATH
environment variable setting

For further details please refer to Installation guide for UNIX.

NetBackup Installation

NetBackup installation has two parts.

1. Installation of VERITAS Private Branch Exchange (PBX)

1.1 Loginto server as root

1.2 Mount software CD/DVD or Copy the software to local disk
1.3 cd /<cdrom>/
 1.4 Run the command “./installics”
1.5 Follow the instructions and complete the installation
1.6 Verify PBX service
Ps –ef | grep –I pbx
This will list a process/service called “VERITAS_PBX”
2. NetBackup base software installation

To install the NetBackup Software, insert the NetBackup server software CD in the drive.
See the NetBackup 6.x Installation guide for UNIX and Linux for directions and guidelines
for mounting the NetBackup software CDs on the respective platforms

2.1 Launch NetBackup 6.x installation program and enter the appropriate responses to
proceed with the installation.
2.2 Enter the NetBackup License Key
a. Further progress is prohibited until a valid key is entered
b. A license key is required for all servers
c. On the master server we must enter license keys for any additional
NetBackup software product options or agents used on this server
2.3 If we are installing Master server
a. Enter the configured name of the master server
b. Enter the names of the media servers
c. Enter the name of Enterprise Media Manager (EMM) server
d. Answer “y” to the prompt asking if you want to start the processes
2.4 If you are installing media server
a. Enter the configured name of the media server
b. Answer “n” to the prompt asking if this is a master server
c. Enter the name of the master server
d. Enter the name of the EMM server
2.5 Install any NetBackup options and agents.

After the initial installation is complete, we can install any other NetBackup agents and
options by following the instructions in the NetBackup guide that comes with the
product.
Installation of NetBackup 6.x software on Windows
server
To install the NetBackup Software, insert the NetBackup server software CD in the drive.
See the NetBackup 6.x Installation guide for UNIX and Linux for directions and guidelines
for mounting the NetBackup software CDs on the respective platforms

1. Launch NetBackup 6.x installation program and enter the appropriate responses to
proceed with the installation.
2. Enter the NetBackup License Key
a. Further progress is prohibited until a valid key is entered
b. A license key is required for all servers
c. On the master server we must enter license keys for any additional
NetBackup software product options or agents used on this server
3. If we are installing Master server software
a. Click Next and Install the as needed to install the product
b. Deselect “Launch NetBackup Administration Console now” and click Finish
4. If we are installing Media server software
a. Return to the NetBackup license Key and Server type screen
b. Re-enter the license key
c. Select Media server and click Next
d. Expand windows agent/option computers, select the remote server, and click
next.
5. Install any NetBackup options and agents.

After the initial installation is complete, we can install any other NetBackup agents and
options by following the instructions in the NetBackup guide that comes with the
product.
NetBackup for MS-SQL Database

Note: MS SQL database can be installed only on Windows Boxes.

STEP 1

1. Install Windows base client software in the MS SQL server.

2. Create a MS SQL policy with the following features
a. Attributes
i. Policy Type – MS-SQL-Server
b. Schedules
i. Application Backup schedule – This is a USER schedule used by MS-SQL script to initiate
the database backups and the window should be defined for 24 X 7.
ii. Automatic Backup schedule – This a NetBackup schedule to initiate/ execute the MS-
SQL script (batch file) and the backup window is defined as per client request.
c. Client – Add the NetBackup name of the MS-SQL server with appropriate hardware and OS.
d. Backup selections – Add the NetBackup backup batch script name with complete path. The batch
script is yet to be created in the client so, do not make any entries at moment.
3. Log into MS-SQL server / NetBackup client with Admin rights
4. Start -> All Programs -> Veritas NetBackup -> NetBackup Agents -> NetBackup MS-SQL Client

5. Login Parameter has to be provided if this is the first time the user has logged in to the Ms-SQL server.
  Select the hostname of the SQL server application (SQL Server name need not to be

same as SQL server application name) from the drop down list.

 Keep the instance as Default

 Initially the SQL server version, Security and Host type are shown as “UnKnown” and

grayed out.

 Provide the user id and password.

Note: These logins are logins for MS-SQL application and is recommended to have “sa”

permissions (System Administrator) to the databases.

If the logins are valid then the SQL server version, Security and Host type will have valid

information as shown in the figure.

Basic configuration of the NetBackup MS SQL Database is done. Now we need to create a backup batch script.

STEP 2

Creating Backup Batch script

1. In NetBackup Ms-SQL client, go to

 Start -> All Programs -> Veritas NetBackup -> NetBackup Agents -> NetBackup MS-SQL Client

2. File -> Backup SQL Server objects (or press F2)

 Select the type of Backup (Full, Full Differential, Transaction log)

 Opt

o All - to take backup of all the databases listed in the database list.

o Selected - to take backup of only those selected.

o All but selected – to take backup of those databases which are not selected.
  Stripes – the number defines how many databases has to be backed up in parallel. It is

recommended to use only odd numbers and most recommended to use only 1.

 Choose “Do not resume unsuccessful backup” from drop down list for Resume options for this

selection.

 Enter the MS SQL NetBackup policy name (This is case sensitive) that we created at very

beginning

 Most importantly

 Most importantly opt for save option (not Launch immediately) at the left down corner of the

pop-up window and then click OK.

 Since we used save option, we will be asked to provide the save location.

o Default Location: C:\Program files\Veritas\NetBackup\DbExt\MsSql\, if “C:\Program

files” is the NetBackup client install path.

o File has to be saved as a batch file, i.e. [Link].

With this we completed creating the backup batch file.

STEP 3

Edit the backup selections of the MS – SQL NetBackup policy with the complete path of the backup batch file we

created in the client.

Example: “C:\Program Files\Veritas\NetBackup\DbExt\MsSql\[Link]”

Note: MS-SQL database restores can be done from client only using a restore script. See VERITAS NetBackup

For Microsoft SQL Server Administrator’s Guide for more details and restore procedure.
NetBackup for Oracle
UNIX Oracle Clients

 Installation
 Post installation configuration
 Oracle NetBackup policy settings
 Logging

Prerequisites

 Root access on master/media server.

 Valid NetBackup for Oracle license should exist on master server.
 NetBackup for Oracle *.tar and version files must exist under the path
“/usr/openv/netbackup/dbext/” on master/media server from which the software is intended
to push.
 Communication and authentication to the client from the master/media server should be fine.
Detail description on the communication required is mentioned at the end of this document.
 Client should exist in at least one policy of any type.

Installation Steps

1. /usr/openv/netbackup/bin/admincmd/bpplclients | grep –i clientname > filename

2. /usr/openv/netbackup/bin/update_dbclients Oracle -ClientList filename
Follow the onscreen steps to complete the installation.
Verification

The following files must exist after a successful installation.

=====================================================================================
Operating System Architecture NBU binary files
=====================================================================================
AIX 32-bit libobk.a
AIX 64-bit libobk.a64
HP-UX 32-bit [Link]
HP-UX 64-bit libobk.sl64
Linux 32-bit [Link]
Linux 64-bit libobk.so64
Solaris (SPARC) and Digital UNIX 32-bit [Link].1
Solaris (SPARC) 64-bit libobk.so64.1
=====================================================================================

Post Installation configuration (All steps should be done by oracle DBA)

1. Log onto client as an oracle user.

2. Shutdown the oracle databases (Down time- not more than 10 minutes).
3. Run the script “/usr/openv/netbackup/bin/oracle_link”
4. Develop the RMAN script.

Policy Details

Policy Type: Oracle

Schedules:
Application Backup Schedule –
 RMAN script uses this schedule to initiate user backups
 Backup Window: 24 x 7
Automatic Backup Schedule –
 NetBackup uses this schedule to schedule the backup/initiate the RMAN script
 This is an optional schedule if the backup is initiated from client using cron scheduler
 Backup Window: As per requirement.
Note: Both Automatic and Application backup schedules are recommended to have same retention.

Backup Selection: RMAN Script with complete path on OS.

Logging

1. RMAN logs
Make sure that everything is fine from Oracle DB end.
2. /usr/openv/netbackup/logs/dbclient
Log exists on NetBackup oracle client; this will show us the problems with NetBackup side.
3. /usr/openv/netbackup/logs/bphdb
Log exists on NetBackup oracle client; this will show us the problems with NetBackup and
oracle db linking.

Windows Oracle Clients

 Installation
 Post installation configuration
 Oracle NetBackup policy settings
 Logging

Installation:
No special agent installation required as in the case for UNIX oracle clients. All the DB agents are
integrated in the NetBackup client software.

Post Installation configuration

Once NetBackup client software and Oracle application is installed on Windows Oracle client, it is
recommended.
Else we can restart the NetBackup and then Oracle application services to have successful linking.

Oracle NetBackup policy settings

These are similar to that of UNIX servers.

Logging

1. RMAN logs
Make sure that everything is fine from Oracle DB end.
2. <Install Path>\Veritas\netbackup\logs\dbclient
Log exists on NetBackup oracle client; this will show us the problems with NetBackup side.
3. <Install Path>\Veritas\netbackup\logs\bphdb
Log exists on NetBackup oracle client; this will show us the problems with NetBackup and
oracle db linking.
NetBackup for NDMP
NetBackup for NDMP

NetBackup for NDMP is an optional NetBackup application. It enables NetBackup to use the
Network Data Management Protocol (NDMP) to initiate and control backups and restores of Network
Attached Storage (NAS) systems.

NDMP Terminology

NDMP client
An NDMP client is an NDMP-compliant backup application (also known as a Data Management
Application or DMA) that is an NDMP server application client. An NDMP client sends commands to the
NDMP server application to control the backups and restores on an NDMP host. NetBackup for NDMP
allows NetBackup to act as an NDMP client.

NetBackup for NDMP server

A NetBackup for NDMP server is a NetBackup master or media server on which NetBackup for NDMP
software is installed.

NDMP host
A NAS system that serves files to clients using HTTP, FTP, CIFS, or NFS protocols. It also runs an NDMP
server application that communicates with NDMP client backup software to configure and perform
backup and restore tasks. NAS systems provide fast, multi-protocol file access and cost effective data
storage to workstations and servers in the network or across the Internet. In a NetBackup configuration,
the NDMP host is considered a client of NetBackup. However, NetBackup client software is never
installed on an NDMP host.

NDMP server application

An NDMP server application runs on an NDMP host and runs backup, restore, and device control
commands that it receives from an NDMP-conformant backup application. The backup application
(NetBackup) is considered an NDMP client.
A separate instance of an NDMP server process exists for each connection to an NDMP client. That is, if
two backups are in progress, an NDMP server process exists for each backup.
NDMP storage unit
An NDMP storage unit stores the backup data for an NDMP host. The tape drives in this storage unit
attach directly to the NDMP host or can be configured on a SAN.

Note that NDMP storage units cannot be used to store data for non-NDMP hosts, and NetBackup disk
storage units cannot be used for NDMP tasks.

Types of NDMP backup

The NDMP server application on the NDMP host performs backups and restores of the NDMP host,
directed by commands from an NDMP client (NetBackup). Backups can be conducted in any of the
following ways:

 NDMP local backup

 NDMP three-way backup
 Backup to a Media Manager storage unit on the NetBackup server

NDMP local backup

The NetBackup for NDMP server initiates the backup. The data travels from the NDMP host’s disk to a
storage device that is attached to the same host. Or the storage device is available on a SAN.
NDMP three-way backup

The NetBackup for NDMP server initiates the backup. Data travels over the network in the following
manner: from an NDMP host to a storage device that is attached to another NDMP host on the local
network or available on a SAN.

Backup to Media Manager storage units (remote NDMP)

The data travels over the network in the following manner: from an NDMP host to a Media Manager-
type storage device that is attached to a NetBackup media server or available on the SAN. The
NetBackup drive(s) must be in Media Manager storage units (not NDMP storage units).
Installing NetBackup for NDMP

UNIX NBU servers

Prerequisites:

 NetBackup for NDMP license

 Following software packages
o NetBackup_6.5_UnixOptions.tar
o NB_DMP_6.[Link]

Installation Procedure:

1. tar –xvf NetBackup_6.5_UnixOptions.tar

2. cd NetBackup_6.5_UnixOptions
3. ./install
4. Select Add-on Product Software
5. Select NDMP to install the base NDMP software.
6. tar –xvf NB_DMP_6.[Link]
7. ./NB_Update_install
8. Install NDMP Patch that suits the NBU master/media server version.

Windows NBU server Servers

NetBackup for NDMP is part of the core NetBackup product

Configuration of NDMP hosts

1. /usr/openv/volmgr/bin/set_ndmp_attr –auth <NAS filer name>

 Provide User name
 Provide password and confirm the same
2. /usr/openv/volmgr/bin/set_ndmp_attr –verify <NAS Filer name>

Choose the type of NDMP backup implemented, Local/Three-way/Remote. Accordingly configure the
tape drives and there by NDMP storage unit. (For remote the STU is media manager/disk STU is used)

Create a policy of type NDMP with NDMP hosts (HW= NDMP and OS= NDMP) mentioned in the client
list.

Note: Make sure a full backup is always kicked for the first time for each backup selection.
NetBackup common error codes occurrences
during backup process.
Step 1: Backup initiation

Step 2: Master server searches the catalog for the policy, schedule and client details which
are provided.

1. 230: the specified class does not exist in the configuration database

2. 237: the specified schedule does not exist in an active class in the configuration
database

3. 239: the specified client does not exist in the specified class

4. 247: the specified class is not active

Troubleshooting steps: Verify the provided policy (using bppllist <policy name> -U), schedule
(bpplsched <policy name> -label <schedule name> -U) and client names (using bpplclients |
grep –I <client name> & bppllist –U –byclient <client name>)

Step3: Master server requests the EMM server to get a tape drive and a tape

1. 96: no media available

2. 219/800/830/2000: resource request failed

3. 196: Backup window closed – If EMM server couldn’t allocate resources

within the specified backup window for a scheduled backup.

Troubleshooting steps:

Tape drive resource failure

1. get the storage unit (using bppllist <policy name> | grep ^RES)

2. Get the details of the storage unit (using bpstulist –label <stu name> -L or bpstulist –
group <stug> -L and then use the –label option to fetch the information)

3. Tape drive status on the media server mentioned in the STU (vmoprcmd –d –h <mdia
server name>)

4. Go through the tape drive configuration steps and verify the current tape drive
configuration.
 5. If configurations ar fine, then check for stuck tapes in the tape drives using
robtest/Linrary console. Eject the stuck tape if any and up the drive. If eject fails, contact
vendor.

Media resource failure

1. Check for the scratch volume pool (vmpool –listscratch)

2. Check the robot number that is defined in the storage unit

3. Check the available tapes in the robot (vmquery –bx –rn <robot number> | grep –I
<scratch volume pool name>

4. If tapes are available, check the maximum mounts set to the tapes using NetBackup
GUI->Media

5. If tapes are not available, then generate a list of offsite (none ) tapes in the scratch
volume pool and inject them (using vmchange –rt tld –rn <robot number> -rh >robot control
host name> -empty_map)

Backup window closed

5. Check the storage unit (bpstulist –label <STU name> -L) and there by tape drive
status (vmoprcmd –d –h <media server>) and verify if actually tape drives are being
used by backup/restore jobs using the same storage unit or tape drives.

6. If no active backup/restore jobs using the tape drives, then check for the hung
allocations in EMM server (nbrbutil –dump | grep <STU name>) and release the
allocations for each tape drive individually (nbrbutil –releaseDrive <tape drive
name>).

7. If active backup jobs occupied all the tape drives, plan for load balancing among the
media servers or increase the capacity (Multiplexing / Tape drive count)

Step 4: Master server contacts the media server and handover the backup job to bpbrm.

Backup might go hung mounting the tape if media server services or tape library
daemons are hung

Trouble shooting steps: check the RCH services for hung or abnormal number of library
daemons (using vmps)
 Check the media server services for hung bptm/bpbrm/tldd daemons (using bpps –x)

Step 5: Now media server tries to connect the client

23/24/25/41/54/57/58/59/71/99 etc

23/24/25/41/54 – Ping < client name> , telnet <client name> bpcd , traceroute <client
name>, bptestbpcd –client <client name> -v , bpgetconfig –s <client name> … all commands
from master and media

57,58,59 – bpgetconfig –s <client name> from media server and master server. Check
the client services and kill any hung processes – better to restart the client services (windows
clients only), check [Link] or NetBackup machines on client for appropriate NBU server
names (use bpcd logs to determine the correct NBU hostnames).

71 – Validate the backup selection list in the client. If ALL_LOCAL_DRIVES is used , then
avoid multistreaming. If only Shadow copy components stream is failing then check the
snapshot configuration of the client. Take symantec technote help to find any missed windows
OS patches.

99 – NDMP generic failure.

Verify the authentication of the filer (using set_ndmp_attr –verify <filer name>)

If authentication is fine, then the backups selections needs to be validated with

the NetApp admins.

Step 6: bpbrm in parallel initiates bptm to place the tape into tape drive.

Bptm invokes ltid to perform the tape mount/unmount request

If ltid is not active job ends with status code is 80. Restart the media server services to fix it.

Ltid invokes tldd and thereby tldcd on the Robot control host to perform the tape
mount/unmount requests, miscommunication between tldd and tldcd causes backup to fail
with 98 error code.

Step 7: Now client starts sending the data to tape.

12/13/14 – Check the bperror log on master (using bperror –jobid <jobid>) and bpbkar log on
client

DB backup failures might occur at this stage, just before sending the data to media server.
 2/6 – SQL / RMAN script haven’t executed successfully. Majorly because of access issue.
The SA who created these scripts doesn’t have access to DBs. Check the access following the
SQL/Oracle configuration steps.

It is worth to check the bphdb and dbclient logs on client to verify why the DB backup
failed.

While backup job is running the backup might fail with the following errors

12/13/14/84/85/86/98/96

12/13/14 – check the bperror logs and bpbkar to determine which filesystem/file is
causing this error. Avoid NFS mounted or shared folders in the backup selections.

84/85/86 – check bptm/OS messages logs has to be verified. Simply freeze the media
and restart/resume the backup (using bpmedia –m <media id> -freeze)

96 – Check for the available media in the robot defined in the stu.

Upon successfully sending the data via child streams, the parent should complete successfully,
but sometimes in the case of DB backup jobs parent stream might fail. It is mostly because of
the script error or script doesn’t finish successfully. Check the script logs (RMAN logs / SQL logs
- bphdb) to find the reason.

Some time backups might go hung ejecting the media out of unresponding tape drives. Worth
to check the robot and tape drive communication along with the tape drives health check.