Prepared By -

Date Page 1

Netbackup 6.X
Training

Presenter Name : Aashutosh & Anay
Presenter Division : Storage
Date : 7
th
March 2011
Prepared By -
Date Page 2
Backup hardware devices
Prepared By -
Date Page 3
Tape Library
Prepared By -
Date Page 4
Tape Library console
Prepared By -
Date Page 5
Tape drive connectivity
Prepared By -
Date Page 6
Tapes
Prepared By -
Date Page 7
Tape Barcodes
Prepared By -
Date Page 8
IM containers
Prepared By -
Date Page 9
Demo of Library
http://www.quantum.com/flash/i500/i500.html
Prepared By -
Date Page 10
5.1 and 6.x Architectural Differences.
6.x Architecture in detail.
Prepared By -
Date Page 11
11
Underlying Database
Management
NBU 5.x
NBU 6.0
Product-private data stored in
scattered, for-purpose flat files,
managed with for-purpose code
volDB poolDB ruleDB
globDB mediaDB ltidevs
robotic_def
.namespace.checksum (NDMP)
Storage Units
Vault Containers (attribute of volume)
Data stored in, and managed
with Sybase ASA, through
VxDBMS, accessed with
standard SQL queries
EMM Database consolidates all media
& device data onto the EMM Server,
the Master Server by default


Prepared By -
Date Page 12
12
Device Configuration and
Communication
NBU 5.x
NBU 6.0
Device configuration & status
data scattered across multiple
systems requiring Media
Server-to-Media Server
communication

High firewall impact
Consolidated and centralized
configuration & status data.
Media Server-to-Media Server
communication eliminated
except for robotic control needs
Reduced firewall impact
Prepared By -
Date Page 13
13
Media and Device Selection
NBU 5.x
NBU 6.0
Media & Device selection logic
split across multiple
components
Media Server & STU by bpsched
Media by bptm
Tape Drive by ltid/robotic
daemon
Selection handled completely
within EMM
Prepared By -
Date Page 14
14
Backup Policies, Images, ACLs,
and Catalogs
NBU 5.x
NBU 6.0
Backup Policy data stored in for-
purpose files
No change
Backup Image data stored in for-
purpose files

No change
NetBackup Access Control data
stored in own Sybase ASA
database
No change
NetBackup Catalog Backup
independent of DB client option
No change
Prepared By -
Date Page 15
NetBackup 6.0 Architecture Multiple
Tiers
NetBackup 6.0 uses a multi-tiered
architecture
1. Master Server
2. Media Server
3. Enterprise Media Manager (EMM) Server
4. Client
EMM Server was introduced by
NetBackup 6.0
Prepared By -
Date Page 16
NetBackup 6.0 Environment Mappings
The Enterprise Media Manager
(EMM) Server
Can service either one NetBackup
6.0 Master
Server or multiple NetBackup 6.0
Master
Servers
Master Server
Media Server
Client

Master Server
Media Server
Client
Master Server
Media Server
Client
EMM Server
Prepared By -
Date Page 17
Environment Mappings: Master /EMM
Server
NetBackup 6.0 Master/
EMM Server
NetBackup 6.0
Media Server
NetBackup 6.0
Media Server
NetBackup 6.0
Clients
NetBackup 6.0
Clients
Prepared By -
Date Page 18
Default installation path
Netbackup:

C:\program files\VERITAS\Netbackup

/usr/openv/netbackup



Prepared By -
Date Page 19

Media manager
c:\Program Files\VERITAS\volmgr

/usr/openv/volmgr
Prepared By -
Date Page 20


EMM

C:\Program Files\VERITAS\NetbackupDB

/usr/openv/var
Prepared By -
Date Page 21


License keys

C:\Program Files\VERITAS\Netbakup\var\

/usr/openv/var
Prepared By -
Date Page 22


JAVA

C:\Program Files\VERITAS\java

/usr/openv/java
Prepared By -
Date Page 23
Netbackup Components & 6.X services
Prepared By -
Date Page 24
Components of netbackup
Introduction to components of netbackup
6.0
Prepared By -
Date Page 25
Lessons included
Master server components
EMM server components
Media server components
Client components
Netbackup admin console
Netbackup communication

Prepared By -
Date Page 26
Master server components
bprd bpjobd--jobs DB
Nbnos bpbdm-M Server
catalog
Nbsl nbjm
Nbsvcmon nbgenjob
Bpcompatd nbproxy
Nbpem VERITAS_PBX

Prepared By -
Date Page 27
Bprd- legacy master server component
Netbackup req manager
- Runs only on master server , once started
runs continually
- Listens on TCP port 13720
Responsibilities:
Starts database manager[ bpdbm]
Builds netbackup server list
Verifies the netbackup licenses

Prepared By -
Date Page 28
Initiates recycling of debug logs, recycles
each day
Initiates cleaning of the job database
Enables/allows the policy execution
manager to resume schedulling of jobs

Prepared By -
Date Page 29
Database manager bpdbm

- Started initially by bprd at netbackup start
up
- Runs only on master server
. Once started runs continually
.listens on the port 13721
--maintains update and queries several
netabckup master server catalogs
including: images,
behaviour,clients,retention levels , sync
and others.
Prepared By -
Date Page 30
Job database manager - bpjobd
Runs only on master server
- Running dependent upon bpbdm
- Listens at port 13723
- Updates to backup job entries in jobs databse are
provided to bpjobd by the process that is responsible for
the operation
- Queries to the jobs database are initiated by the activity
monitor and/or via bpdbjobs command

Prepared By -
Date Page 31
Netbackup notification services- nbnos
It runs as a service/daemon
Notifies policy execution manager, nbpem
, of certain changes as soon as they
occur.
Changes include policy additions, changes
and deletions
Changes also include image expiration
and storage unit additions , changes and
deletions
Prepared By -
Date Page 32
As a result of a backup policy change
notification , nbpem will re-evaluate the
next due jobs worklist
Backup jobs which have already been
submitted by nbpem to nbjm for execution
are not affected by backup policy
changes.
Prepared By -
Date Page 33
Bpcompatd-new master server component
Netbackup compatibility daemon
Daemon/service used to allow new
netbackup 6.0 daemons/services to
communicate with legacy
daemons/processes
-runs as daemon/ service on netbackup 6.0
servers
- May be run as a command
Prepared By -
Date Page 34
Nbpem
Policy execution manager nbpem(1)
- Main tasks are to build and maintain the
next Due jobs worklist and to signal the
job manager , nbjm , when a job is due to
run
- Requests for manual ( immediate )
backups or user initiated backups result
in a run once job being added to the
worklist. Job removed when completed
Prepared By -
Date Page 35


Once the next due jobs worklist has been
created nbpem re-evaluates it on an event
driven basis
- when a backup policy is added, modified
or removed
- when backup images are expired
- when a job becomes due
- when a job tryis completed

Prepared By -
Date Page 36


Nbpem maintains out of window timer for
each job
- worklist entries for which multiple data
streams is indicated are a special case
Initially only a parent job entries exists in the
worklist. More on this later in this lesson
Prepared By -
Date Page 37
Nbpem
Policy execution manager- nbpem (2)
- Nbpem is started initially by bprd
- Once started nbpem runs continually- if bprd goes down
schedulling of backup jobs by nbpem continues
- If bprd is shutdown by request( normally) , it sends a
request to nbpem to suspend schedulling{ In this case
wen bprd is started manually then it sends a message to
nbpem to resume schedulling}
Prepared By -
Date Page 38
Nbjm
Job manager nbjm
- Part of intelligent resource manager(IRM)
- Started by startup scripts
- Runs continuallyon master server system
- Nbjm requires/uses veritas_pbxto communicate with
other IRM/EMM components
- Nbjm handles Job Management for all backup jobs
- Nbjm requests and obtains resources for all jobs
- Nbjm releases these resources when a job is completed
Prepared By -
Date Page 39
Nbgenjob
Generic Job- nbgenjob
- Netbackup generic Job- nbgenjob is an
IRM process in netbackup 6.0
- Nbgenjob is initiated on the master
server system by the job manager,
nbjm


Prepared By -
Date Page 40
Nbjenjob tasks
Streams discovery on client for multi-stream backups
Performs snapshot creation/Snapshot deletion
Runs bmrsavecfg when backup policy is configures to
gather BMR information for a client
Runs job star/end notify scripts for parents of multi-
streaming backups
Initiates Vault run
Initiates synthetic backup
Initiates catalog backups
Initiates Sharepoint Portal server resolver
Prepared By -
Date Page 41
EMM Server Components
Its new to 6.0 release
Simplified description: the EMM Server is a centralized
group of services which perform the management and
allocation of resources required for all netbackup
operations including backups, restores, duplication ,
vaulting, imports , catalog backups and more
Resources include, but are not limited to, media and
drives- both tape drives and optical disks and drives
Prepared By -
Date Page 42
EMM server benefits
- the EMM server replaces functions that
were previously spread across various
components of the master server and
media server system
This results in the following:
a) Centralized resource management and
allocation avoids conflict which occurred
due to multiple managers
Prepared By -
Date Page 43


b) New code which implements EMM is
more efficent than its predecessors ,
removing bottlenecks and therefore
improving performance
c) The EMM database is implemented under
a new database engine providnig the
benefits associated with relational
database mgmt systems
Prepared By -
Date Page 44
EMM server And Master servers
EMM Server and Master servers
-An EMM server may provide service to multiple Netbackup
6.0 Masters servers
- It is anticipated that generally an EMM server will provide
resource mgmt and allocation to a single Netbackup 6.0
Master server enviroment
- Each Netbackup master server enviroment may access
one and only one Emm server.
Prepared By -
Date Page 45
EMM server prerequisites
EMM server relies upon the intsallation of
VERITAS_PBX, which is a VERITAS
shared Infrastructure Group (SIG)
component.
The system on which the EMM server is
installed must have network connectivity to
all media Server systems in the netbackup
enviroment.
In the 6.0 release , it may be installed on:
Prepared By -
Date Page 46


The master server system (default)
A media server system
At some point Not At 6.0 release the
EMM server may be installed ona system
independent from other netbackup
functions.

Prepared By -
Date Page 47
EMM server list components
nbrb resource broker
emmlib programming interface
nbemm enterprise media manager
emmdb(with DB_dbsrv or dbsrv9) EMM
database server
Emmdb(NBDB.db) EMM database
Prepared By -
Date Page 48
nbrb netbackuo resource
broker
A component of intelligent resource manager[IRM]
Runs continouslly on EMM server system
Started by startup script (or by nbsvcmon)
Uses VERITAS_PBX to communicate with other IRM
components and with EMM service(nbemm)
Uses the new unified logging (VxUL) logging method
Performs resource allocation for all netbackup activities
which require resources backups , restores,
duplication, catalog backups, imports , verifies etc.
Prepared By -
Date Page 49
emmlib EMM server
component
emmlib
-- allows for netbackup components written
in C programming language to access
EMM which uses a CORBA interface (
emmlib provides a C wrapper around the
CORBA EMM interface)
-- does not generate a debug log
information is written to logs of processes
which communicate with emmlimb

Prepared By -
Date Page 50
nbemm EMM server
component
Netbackup enterprise media manager
Runs continouslly as a service on EMM Server system
Uses VERITAS_PBX to communicate
Uses new unified logging (VxUL) logging method
Is the EMM database manager
Maintains device (tape and optical drives) and media
configuration and status, as well as data previously
associated with numerous Netbackup and media
manager 5.x (and earlier) databases/catalog.
Prepared By -
Date Page 51
nbemm tasks
Accepts requests for resources form mds and requests
to add/modify/delete/change status of db entries via
GUI/CLIs (via emmlib APIs)
NB_dbsrv provides interface to EMM database to :
Reserve devices and media( resources) to meet requests
Add/modify/delete resource configuration records
Update device and media status

Prepared By -
Date Page 52
mds EMM server component
Media and device selection ( mds)
NOT a running process requests for
resources from nbrb
Communicates with nbemm to
identify/reserve resources
. De allocates resources when oprations
are completed.
Prepared By -
Date Page 53
da device allocator
Not a running process ( not a visible with
bpps)
Monitors drivers via assigned scam
host(s)- via emmlib

Prepared By -
Date Page 54
Enterprise media manager
Centralized , relational database
File is not nbdb.db
Managed by EMM service(nbemm)
based upon VERITAS standard multi-platform relational
database defined in the VxDBMS project ( from the
VERITAS shared infrastructure Group SIG )
Houses data previously located in NETBACKUP and
Media manager 5.x [previous] databases/catalogs .
Prepared By -
Date Page 55
MEDIA SERVER
COMPONENTS
bpbrm backup /restore manager
bptm tape manager
bpdm disk manager
vmd volume management daemon
ltid device manager
txxd robotic drive daemon
txxcd robotic control daemon
avrd auto volume recognition
oprd operator request daemon
vnetd VERITAS n/w daemon
bpcd commnicates daemon
Prepared By -
Date Page 56
bpbrm backup and restore manager
Manages backup and restore operations
Bpbrm does not continually is started on a netbackup media
server system as required to perform backup and restore operations
Nbjm starts bpbrm for single-streamed backup jobs.
Nbjm starts bpbrm for each stream of multi streamed backup jobs
Bprd starts bpbrm for restore jobs
-- bpbrm initiates bptm or bpdm for use in backup/restore
operations[
-- bpbrm initiates netbackup Client processes for file system
backup/restore operations.
-bpbkar for backups and tar for restores
Prepared By -
Date Page 57
Tape manager - bptm
-bptm does not run continually it is started as needed
on a netbackup media server system to perform backup
and restore operations ( and other operations ) that
utilize backup and restore operations ( and other
operations) that utilize removable media-tape or optical
media
Bptm is started by bpbrm for backup/restores
Primary bptm tasks during backups and restores
Prepared By -
Date Page 58
Disk manager - bpdm
Bpdm does not run continually it is started as needed
on a netbackup media server system to perform backup
and restore operations ( and other operations) that utilize
magnetic DISK media
Bpdm is started by bpbrm for backup/restores
During backups and restores bpdm writes/reads backup
data to /from disk utilizing the underlying OS and file
system management software.
Bpdm is reliant upon ability to perform disk operations
via the Operating System/file system
Prepared By -
Date Page 59
ltid media server component
Device management service/daemon ltid
Runs on each media server system on which tape and /or optical
drives are configured for netbackup use
In 6.0 the role of ltid has been reduced due ti introduction of the EMM
server and EMM database
ltid obtains status of devices to EMM so that the centralized EMM DB
contains current device status information
ltid recieves requests for mounting/un-mounting of media from bptm.
-- ltid calls appropriate robotic daemons to perform mounts/unmounts
Prepared By -
Date Page 60
vmd
Vmd runs on each media server system on which tape
and/or optical drives are configured for netbackup use
In 6.0 the role of vmd has been reduced due by
introduction of the EMM server/EMM database which
houses information about all removable media
Starts OPRD and connect to ltid to obatain media
information
Vmd forwards queries/updates for volume information from
5.x Media servers to EMM server.
Prepared By -
Date Page 61
Txxd and txxcd
Robotic daemons processes
Names vary by the tape of robotic device.
current types: tl4d , tlmd,tl8d/tl8cd,tldd/tldcd,tlhd/tlhcd
Robotic daemons run on a Media server on which devices of that type
are configured
Once started robotic daemons run continually on the media server( until
Netbackup shutdown)
-receives requests for mounting/un-mounting of media from ltid
Communicates to/with robotic devices to perform mount and unmount
operations

Prepared By -
Date Page 62
avrd
Automatic volume recognition Daemon
Controls automatic volume assignment and label
scanning allow media manager to rean labeled tape and
optical disk volumes on standalone drives
Starts txxcd process to mount and read media label on
robotic drives
Allows media manager to automatically assign the
associated removable media to requesting processes.
Prepared By -
Date Page 63
Oprd
Oprd is started by vmd on Media Server systems
Oprd services the following kinds of requests:
down/up/reset drives , display drive status
Deny/re-submit mount requests
Start/stop ltid , obtain ltid status
Manage pending actions , assign drives
Format optical platters
Clean drives
Obtain host version and scan shared drives

Prepared By -
Date Page 64
CLIENT COMPONENTS
tar
bmrsavecfg
vnetd
bpcd
bpbkar
Prepared By -
Date Page 65
bpbkar or bpbkar32
Initiated on the Netbackup Client System as needed to
perform file system backups and archives
Started by media server backup and restore manager
(bpbrm) process
Generates backup data stream- sends to media server
(bptm/bpdm) to be recorded to backup media
Generates meta-data for backup sends to media
server . This information is sent to to bpbdm on the
master server which writes it to image database
Bpbkar may optionally perform software compression
and/or encryption of backup data

Prepared By -
Date Page 66
tar
Initiated on the netbackup client system as needed to
perform file system restores
Started by media server backup and restore manager (
bpbrm ) process
Receives data to be restored from media server system
process (bptm/bpdm) and writes data to client disk
Tar may perform un-compression and/or decryption of data
stream , if data was software compressed and/or
encyrpted by the client during the backup operation.
Prepared By -
Date Page 67
BMR
BMR information gathering process bmrsavecfg
- BMR client software is installed with the netbackup client software
on supported platforms
BMR must be licensed and properly configured ina backup policy in
order for BMR to be sucessfully implemented
Called by new nbgenjob process.
Netbackup mount command bpmount
is a Netbackup Client Process that is used in the STREAMS auto-
discovery process to identify configured file systems/mounts points
and drives
Called by new nbgenjob process , not scheduler.
Prepared By -
Date Page 68


NetBackup Communications
Prepared By -
Date Page 69
6.x configuration files
Prepared By -
Date Page 70
bp.conf
Prepared By -
Date Page 71
vm.conf
Prepared By -
Date Page 72
Netbackup GUI details
Prepared By -
Date Page 73
Storage Units
Prepared By -
Date Page 74
Configuring Policies
Prepared By -
Date Page 75
Types of Backup
Prepared By -
Date Page 76
Media & Device configuration
Prepared By -
Date Page 77
Backup and Restore
Prepared By -
Date Page 78
Catalog (off-line & On-line)
Prepared By -
Date Page 79
79
Catalog backup in NBU 5.x
Offline catalog backup
Single tape solution
bpbackupdb
Two steps, multi-tapes solution
Using standard backup to backup all clients
catalog
Using bpbackupdb to backup masters catalog
Prepared By -
Date Page 80
80
Feature Overview
This feature is to re-architect the process of NBU catalog
backup
Why are we doing this feature?
Officially support Hot backups of the catalog
Add ability to span tapes
Allow catalog media management by pool
Full and Incremental Catalog Backups
Enable Scheduled Catalog Backups
Enable to potentially take advantage of standard backup
features for releases beyond 6.0. EX: Synthetics Backup, CPR,
Snap Shots.
Prepared By -
Date Page 81
81
Catalog Backup methods in
NBU6.0
Cold, offline catalog backup
It is bpbackupdb
Simple and easy
Be able to have backup windows to do offline
catalog backup
For customers who have small catalog which
could be fitted in a single tape and happy with
old catalog backup method.
Prepared By -
Date Page 82
82
Catalog Backup methods in
NBU6.0
Hot, online catalog backup
For enterprise customers under 24x7 backup
environment
Rich features
Hot catalog backup
Full/Incremental catalog backup
Scheduled catalog backup
Partial catalog recovery capability through BAR UI
Catalog backup policy
UI guided DR catalog recovery
Prepared By -
Date Page 83
83
Hot Catalog Backup
No need to specify clients for catalog
backup.
Bpdbm automatically figure out all the 5.x
media servers.
Centralized EMM database.
No need to specify catalog path and files.
Bpdbm automatically figure out all the catalog
files which should be backed up.
Bpbkar uses Catalog Backup APIs to
access image database.
Catalog Image locking to achieve hot
backup

Prepared By -
Date Page 84
84
Hot Catalog Backup process
Copy 5.x media catalog to Master server.
Using ASA Sybase agent to backup
catalog (EMM, BMR) stored in ASA
Sybase.
Creating a check point.
Backup image database according to
check point to ensure consistency
between EMM and Image databases.
Run Catalog DR file (image header file)
protection.
Prepared By -
Date Page 85
85
DR file protection methods
Prepared By -
Date Page 86
86
Optional DR file protection -
Email
Prepared By -
Date Page 87
87
DR email
Prepared By -
Date Page 88
88
Catalog Recovery
For hot, online catalog backup images
only
Try to guide user through catalog recovery
Automate some catalog recovery
processes
Provide some flexibility on catalog
recovery through manual recovery method
Prepared By -
Date Page 89
89
Catalog Recovery Process
Loading Catalog DR image file (image
header file)
Restore DR image files body file (image .f
file)
Restore DR image.
Restore rest of image database.
Restore EMM, BMR database.
Manually restore 5.x media database if it is
necessary.

Prepared By -
Date Page 90
90
Catalog Recovery Wizard
Prepared By -
Date Page 91
91
Welcome Screen
Prepared By -
Date Page 92
92
Load DR file
Prepared By -
Date Page 93
93
Recovery method
Prepared By -
Date Page 94
6.x Commands
Prepared By -
Date Page 95
Netbackup Vault configuration
Prepared By -
Date Page 96
General Error codes and Troubleshooting
Prepared By -
Date Page 97
Prepared By -
Date Page 98