Veritas

Netbackup
1. Introduction & Netbackup Architecture.
2. Installation of Master / Media / Clients software,
type of backups and archives
3. Demons and services
4. Backup Hard ware devices (Library and Tapes)
5. Configuration of Policies
6. Configuration of Storage units / Volume pools
7. Netbackup Error Codes and Trouble shooting
8. Important Netbackup commands
9. Restoration / Recovery
10. Health Check & Intializing scheduled backup
& Daily job monitoring
 Information Storage
• Importance of information
• Data, information and storage
• Categories of data
• Storage architectures and their
evolution
What is Data
“Collection of raw facts from which conclusions may be drawn”

• Data is converted into more

convenient form i.e. Digital Video

Data
– Increase in data processing
capabilities 01010101010

– Lower cost of digital storagePhoto 10101011010

– Affordable and faster
00010101011
communication technology
01010101010

Book 10101010101

• Who creates data? 01010101010

– Individuals Letter
Digital Data

– Businesses
 Categories of Data
• Data can be
categorized as
either structured or
E-Mail Attachments PDFs

X-Rays
unstructured data Check Unstructured (80%)

• Over 80% of Manuals Instant Messages

enterprise Images
Documents

information is Forms
Web Pages

unstructured Contracts
Rich Media

Invoices

Audio Video

Structured (20%)
Rows and Columns
 Define
Information
• What do individuals/businesses do Centralized information
storage and processing

with the data they collect? Network Network

– They turn it into

“information” Wired Wireless Wireless Wired

– “Information is the
intelligence and knowledge Uploading
information
Accessing
information

derived from data”

• Businesses analyze raw Creators of

Users of

data in order to identify

Information
information

meaningful trends
– For example:
• Buying habits and patterns of
customers
• Health history of patients
Demand for more
Information

Virtuous cycle of information

 Storage
• Data created by individuals/businesses must be
stored for further processing
• Type of storage used is based on the type of data
and the rate at which it is created and used
• Examples:
– Individuals: Digital camera, Cell phone, DVD’s,
Hard disk
– Businesses: Hard disk, external disk arrays,
tape library
• Storage model: An evolution
– Centralized: mainframe computers
– Decentralized: Client –server model
– Centralized: Storage Networking
 Need for Storage & Growth of
Data
• The Sarbanes-Oxley Act states that all business
records, including electronic records and
electronic messages, must be saved for "not less
than five years." The consequences for non-
compliance are fines, imprisonment, or both. IT
departments are increasingly faced with the
challenge of creating and maintaining a corporate
records archive in a cost-effective fashion that
satisfies the requirements put forth by the
legislation.
 Introduction to Netbackup
• Veritas Product
• Symantec took over veritas
• 70 to 80% of companies world wide
use
• Versions->5.1 to 6.5.3…7,7.01
• GUI and CLI
 4 Tier Architecture of
Netbackup
• 1st tier – Netbackup Client(MLAs)
• 2nd tier – Media Server(Cabinet Ministers)
• 3rd tier – Master Server(CM)
• 4th tier – Global Data Manager(PM)

• Hardware compatibility list:-

• http://seer.entsupport.symantec.com/do
cs/336875.htm
 Netbackup Client
• During the backup or archive,the client
system generates the backup as a data
stream and sends it across the network
to the media server.
• Therefore, our target is the client
whose data needs to be backed up or
restored
• MS SQL Agent comes free with
Netbackup client
 Media Server
• To increase performance by
providing additional processing
ability and better distribution of
workload (Load balancing).
• Note: Tape libraries are always
attached to the media server only
 Master Server
• Master Server is netbackup’s central
brain, providing centralised
operations and management to any
media server and clients
 Global Data Manager

• GDM organises the span geographics

and provides the ability to perform
backup and recovery operations from
various locations.
 ARCHIVE BIT
• The archive bit is a binary bit. As
such, it is either 1 or 0, also
frequently called set (1) and clear or
reset (0). It represents whether the
file has (1) or has not (0) changed
since the last backup.
 Types of Backup
• Full (Archive bit is reset)
• Differential Incremental (Changes since the
latest backup, archive bit is reset)
[Incremental]
• Cumulative Incremental(Changes since the last
full backup)
• Archive Backup (Delete data from source after
backup leaving behind the metadata
,eg:Oracle archive log backup)
• User Initiated Backup (Backup window is 24x7)
 Vault
• Vault job initiates duplicate backup jobs.
• One for onsite and another for offsite
• Ejects the filled tapes from the tape
library
• Automatically sends email to Iron mount
and backup admins stating the scratch
set tape details and tapes which need to
be reloaded
• License is very costly.
 NetBackup Catalog
• NetBackup catalogs are internal databases that
contain information about NetBackup backups and
configuration. Backup information includes
records of the files that have been backed up and
the media on which the files are stored. The
catalogs also contain information about the media
and storage devices.
• NetBackup requires the catalog information in order
to restore backups so it is extremely important to
configure a catalog backup before using NetBackup
for regular client backups, and to schedule the
catalog backups to occur on a regular basis
thereafter. Without regular catalog backups, you
risk losing your regular backups if there is a
problem with the disk that contains the catalogs.
 Parts of the Catalog
• The NetBackup catalog resides on the disk of the
NetBackup master server. The catalog consists of the
following parts:
• Image Database: The image database contains information
about what has been backed up. It is by far the largest part
of the catalog. [c:\prog files\veritas\netbackup\db\]
• NetBackup Relational Database: This includes the media
and volume data describing media usage and volume
information which is used during the backups. [c:\prog
files\veritas\volmgr\database]

• NetBackup configuration files: Policy, schedule and other

flat files used by NetBackup.[ c:\prog
files\veritas\netbackup\var\]
 Netbackup Management
• Host Properties
• Master Server
• Media Server
• Clients ->Double click to check
network connectivity
 Media and Device
Management
• Device Monitor -> Lists Tape drives
and Robots
• Media->Robot Type->TLD (In tape
lib) or none (Offsite)
• Media->Volume Pools->Default 4
Pools
 NOTE

• Media ID:- is a 6 digit alphanumeric

& usually a media has a barcode.
• Media>Robots (RC)>Robot
Inventory>Update Volume config-
>Start
 Frozen,Suspend,Import,Duplicate
• Frozen tape:-Media Manager will auto freeze a
media if the backup can’t use it after 3 attempts.
Incase of media errors 83,84,86,we freeze the
media. Unfreeze later.
• Suspend:-It means that Netbackup won't write
any new data to that tape, until all data on it
expires. It will then be available for re-use.
• Expire:-Data on media will be removed but the
image (index) will remain until the tape is
overwritten
• Duplicate:-Medias sent offsite.Backup done using
either vault/duplicate backup option.
• Import:-catalog db(index/image) from tape when
server crashes and needs restoration
 Volume Pool
• Definition:-Volume Pool is a set of volumes from which netbackup
can draw or take volumes when performing backup
• Group of tapes -Volume/Cartridge/media/tape
• A volume pool identifies a logical set of volumes by type of
usage. Associating volumes with a volume pool protects
them from access by unauthorized users, groups, or
applications.
• With the exception of the volume pools that are automatically
created by NetBackup, you must create a volume pool before you
can add volumes to a volume pool. The following volume pools are
automatically created (see Volume Pools List):
• NetBackup, created by Media Manager, for NetBackup use.
• DataStore, created by NetBackup, for DataStore use.
• CatalogBackup, created by NetBackup, for NetBackup catalog
backups.
• During initial configuration, it is easiest to create all of your volume
pools first. Then as you add volumes, you can assign them to
volume pools.
• It is also possible to configure a scratch pool from which Media
Manager can transfer volumes, when a volume pool has no
volumes available.
• If the volume pool will contain WORM media, see Using WORM
Volume Pools to Manage WORM Media for more information.
 Default Volume Pools
• None -> Cleaning Tapes are present
• Netbackup ->Brand new tapes go to
netbackup volume pool after inventory
• DataStore
• Catalog Backup
Volume Pool which need to be created
• Scratch Pool :-Needs to be created so that
expired tape medias which can be reused
come to the scratch pool.
 Volume Groups
• Volume Groups is a physical location for a media.
• It manages a group of tapes for purpose of admin actions that
allows movement of tapes from slots to drive and vice versa.
• Rules for Assigning Volume Groups
• The following are the rules for assigning volume groups:
• All volumes in a group must be the same media type. However, a
media type and its corresponding cleaning media type are allowed
in the same volume group (for example, DLT and DLT_CLN).
• All volumes in a robotic library must belong to a volume group.
You cannot add volumes to a robotic library without specifying a
group or having Media Manager generate a name for the group.
• The only way to clear a volume group name is to move the
volume to standalone and not specify a volume group.
• More than one volume group can share the same location. For
example, a robotic library can contain volumes from more than
one volume group and you can have more than one standalone
volume group.
• All volumes in a group must be in the same robotic library or be
standalone. That is, Media Manager will not let you add a group
(or part of a group) to a robotic library, if it already exists in
another robotic library.
• Types of Tape Drives
 What is a Tape?
• Tape began as the primary storage medium for computers
in the 1950s. At that time, large mainframe computers
dominated the information systems industry.
• Data storage and backup for these mainframes was on
expensive, reel-to-reel tape systems using half-inch
magnetic tape.
• Data was recorded in parallel tracks using a linear
serpentine recording technology in which the data tracks
were written in alternating bands from the beginning of the
tape to the end and back again.
• Throughout the 60s and 70s these open-reel systems
evolved by increasing the number of tracks, increasing bit
density, and increasing tape speed.
 Types Of Tape Drives
• Digital Linear Tape (DLT)

• Super Digital Linear Tape (SDLT)

• Linear Tape Open (LTO)

 Digital Linear Tape (DLT) –
Quantum
• DLT drives use half-inch wide metal particle tapes - 60% wider
than 8mm tape and the widest tape available - onto which data is
recorded in a serpentine pattern on parallel tracks grouped into
pairs.
• Each data track goes the entire length of the tape. When data is
recorded, the first set of tracks is recorded on the whole length of
the tape. When the end of the tape is reached, the heads are
repositioned to record a new set of tracks, and the tape is again
recorded on its whole length, this time in the opposite direction.
• The process continues, back and forth, until the tape is full.
Current drives record either 128 or 208 tracks.
• The higher density is achieved by angling the data pattern on
adjacent tracks using a technique called Symmetric Phase
Recording (SPR).
• SPR's herringbone pattern eliminates the need for guard bands,
thereby allowing greater track density.
Digital Linear Tape (DLT)
 SDLT
• Super DLT tape technology is the next generation DLT tape
technology platform, the current industry standard for data
storage

• Super DLT tape technology is based on Laser Guided Magnetic

Recording (LGMR) technology, which uses a unique
combination of the best optical and magnetic technologies to
dramatically increase the number of recording tracks on the
data-bearing surface of the media

• The storage capacity of a SDLT-220 drive is 110GB Native

and 220GB Compressed. The storage capacity of a SDLT-320
drive is 160GB Native and 320GB Compressed.
 LTO Tape – HP IBM
SEAGATE
• LTO Technology, or Linear Tape-Open Technology,
combines the advantages of linear multi-channel bi-
directional tape formats in common usage today
with enhancements in the areas of timing based
servo, hardware data compression, optimized track
layouts and high efficiency error correction code to
maximize capacity and performance.
• HP, IBM and Seagate each provided expert
knowledge of customer needs and complementary
technology that provided for delivery of a best-of-
breed technology and promotes a strong foundation
for data interchange. It is their intent that other
companies can participate in this tape industry
opportunity through the open licensing process
 LTO Tape
• Speed and capacity is expected to double with each
generation of the LTO format. The LTO format Generation 1
allows for up to 100GB capacity (uncompressed) in a single
cartridge, while LTO format Generation 2 doubles the capacity
up to 200GB (uncompressed) using Generation 2 data
cartridges. The data transfer peak performance speed doubles
from up to 20MB/second native in the LTO format Generation
1 up to 40MB/second native in Generation 2.
• Users will benefit from a greater than 30 percent increase in
the number of tracks and average tape speed, as well as an
improved recording method. The LTO format Generation 2
provides users with outstanding data and investment
protection because of its capability to read-and-write
Generation 1 cartridges in the LTO Generation 1 format.
• LTO format come in 2 flavours : 1) Single reel catridge
optimized for greater storage capacity called “ULTRIUM” and
2) Dual reel cartridge designed for faster access called “
ACCELIS”
 LTO Tape
• The LTO compatibility is defined with two
concepts demonstrating investment
protection:
1) An LTO drive is expected to read data
from a cartridge in its own generation and
at least the two prior generations.
2) An LTO drive is expected to write data
to a cartridge in its own generation and to
a cartridge from the immediate prior
generation in the prior generation format
 LTO-5
• The current draft has the following
specifications:[14][15]
• Capacity of 1.5 TB (1500 GB)
• Uncompressed data transfer rate of
140 MB/s
• Specifications announced January
19, 2010
• The first LTO-5 drives appeared on
the market in Q2, 2010 [16]
 Other Types of Tape

• Mammoth

• AIT – Advanced Intelligent Tape

 EXABYTE - Mammoth
• Exabyte introduced the 8mm helical scan tape drive in
1985. At that time, the 8mm drive mechanical sub-
assembly was designed and manufactured by Sony.
Exabyte supplied the electronics, firmware, and cosmetics
for the final product. Two generations of full high
• and one generation of half high tape drives were developed
under the Sony/Exabytepartnership. Exabyte chose to
develop and manufacture their own scanner for the
Mammoth product and terminated their relationship with
Sony for any future drivetechnology. Exabyte continues to
rely on Sony for its Mammoth Advanced Metal
• Evaporative (AME) media. Exabyte also uses mechanical
sub-assemblies from Hitachi for its value-line 8mm
products.
 Sony – AIT (Advanced
Intelligent Tape)
• Sony, continuing its role as a leading innovator in
tape technology, began producing the AIT (Advance
Intelligent Tape) drive in 1996. The AIT drive is
designed and
• manufactured entirely by Sony. Although the 8mm
helical scan recording method is used, the AIT
recording format is unique and incompatible with
8mm drives from
• Exabyte. The AIT drive is the first generation of a
technology family positioned to double capacity and
transfer rates every two years.
SDLT vs LTO vs AIT
 Optical Disk
• Electronic data storage medium that
can be written to and read.
• CD – R – 650MB – 700 MB – Write
once Read Many Format
• CD – RW – Rewritable 650MB
-700MB
• Rewritten as many as 1000 times
 DVD - Digital Versatile
Disc
• DVD – 4.8 GB (Regular DVD)
• Dual Layer DVD – (8.84 GB)
• Write once Read Many CD format

• Blue Ray DVD (BD/DVD)

• Using a blue violet laser (450nm) which is
shorter wavelength than a red laser
(600nm)
• This allows data to be packed more tightly
and stored in less space – 25GB/50GB
 Backup Hardware Devices
• Tape Drives and Disk Drives
Tape Drive Technology
• DAT->Digital Audio Tape-Single tape
drive
• DLT->Digital Linear Tape->5MB/s
• SDLT->Super DLT->10MB/s
• LTO ->Linear Tape Open
• VTL ->Virtual Tape Library
 Linear Tape Open
• LTO 1(100/200) [1:1.5 is achievable]
• 100 Gb is the Normal Capacity and
200Gb is the capacity when
compressed.
• LTO2 ->200/400
• LTO3 ->400/800
• LTO4 ->800/1600
• LTO5 ->1.5TB native capacity
Tape Libraries supported by
Netbackup
• Tape Stakers (TS):- 8mm DAT Tapes, Tape Loaders, Tape Libraries, VTL
• Models of Tape Library Eg:-Sun->SL8500

NetBackup Device Support

• VERITAS NetBackup software supports tape drives and libraries from a larger
number of vendors
• The URL for NetBackup Enterprise Server 5.x hardware compatibility matrices for
specific devices on specific OS platforms is:
• http://ftp.support.veritas.com/pub/support/products/NetBackup_Enterprise_Server/
280666.pdf

• The URL for NetBackup Enterprise Server 6.0 hardware compatibility matrices for
specific devices on specific OS platforms is:
• http://ftp.support.veritas.com/pub/support/products/NetBackup_Enterprise_Server/
278692.pdf

• The URL for NetBackup Enterprise Server 6.5 hardware compatibility matrices for
specific devices on specific OS platforms is:
• http://ftp.support.veritas.com/pub/support/products/NetBackup_Enterprise_Server/
284599.pdf/
 Must Watch Videos on
Youtube
• Sun StorageTek SL8500 Product Tour 1 of
2
• Sun StorageTek SL8500 Product Tour 2 of
2
• Tape Library / Autoloader
• Powering Up the SL8500 Tape Library
• Imp links:-
• http://www.quantum.com/Products/Tape
Drives/DLT/Index.aspx
 SCSI
• Small Computer Systems Interface
• Support for many devices
• Single SCSI Channel – 7 Devices
• Bus mastering
• Access to multiple devices
• TCQ
• Intelligent BUS
• MTBF
SCSI
 SCSI interface overview
Interface Bus Clock Max Max Max
Width Speed Through Cable Devices
put Length
SCSI 8-bit 5 MHz 5 MB/s 6m 7
Fast SCSI 8-bit 10 MHz 10 MB/s 1.5-3 m 7
Fast-Wide 16-bit 10 MHz 20 MB/s 1.5-3 m 15
SCSI
Ultra SCSI 8-bit 20 MHz 20 MB/s 1.5-3 m 7
Ultra Wide 16-bit 20 MHz 40 MB/s 1.5-3 m 15
SCSI
Ultra2 SCSI 8-bit 40 MHz 40 MB/s 12 m 7
Ultra2 Wide 16-bit 40 MHz 80 MB/s 12 m 15
SCSI
Ultra3 SCSI 16-bit 40 MHz DDR 160 MB/s 12 m 15
 SCSI
• SCSI Connector – 50pins / 68pins
• 50 pins – 8 bit system

• 68 pins – 16 bit system

 SCSI
• SCSI – I – 5Mb/sec

• SCSI – II – 10mb/ Sec (Fast SCSI / Wide

SCSI)
Single Ended/Differential Versions

• SCSI – III – 40Mb/Sec

Ultra / Ultra 2 / Ultra 3 / Ultra 320

• Termination
 SCSI – Termination/Cabling
• SE – Single Ended

Single-ended SCSI uses half of the cable wires for

carrying
data and control signals and the other half for ground.
Because of this configuration, signals on a single-
ended
bus are more susceptible to corruption due to noise,
especially as bus speed is increased.

Cable Length – Max – 6m , Speed – 5Mhz

SCSI – Termination/Cabling
• HVD
High Voltage Differential (HVD) SCSI uses a set of
two wires for each data or control signal on the bus.
Each signal is determined by the difference in
voltage between the line pair, resulting in higher
noise tolerance. This allows for using longer cables
at faster bus speeds. However, HVD is more costly
to produce and uses more power than single-ended.

Cable Length – Max – 25m – Speed – 5Mhz

SCSI – Termination/Cabling
• LVD (Low Voltage Differential)

Like HVD, Low Voltage Differential (LVD) SCSI also uses two wires for
each signal. This brings the differential bus advantage of reduced signal
corruption due to noise. Another advantage of LVD is that it uses lower
voltages than HVD, reducing cost and power consumption.

Most LVD devices are "multimode", automatically detecting when they

are attached to a single-ended bus, and operating in single-ended
mode. This makes it possible to mix LVD and single-ended devices on
the same bus. However, if only one single-ended device is connected to
a SCSI bus, all devices on that bus will operate in single-ended mode,
and all of the single-ended limitations will apply: shorter cable lengths,
fewer
devices, and slower bus speeds.
 SCSI - Drawbacks
• Additional Hardware
• Lower Volume
• Cost
 Storage Unit
• Definition:- A Storage Unit is a group
of one or more storage devices of
specific type and density that are
attached to a netbackup server.
• It is the logical destination for client
data
• Tapes,Tapedrives,Robots,Library-
>Target Library
 About Disk Staging

• Disk staging provides a method for administrators to create

images on disk initially, then later copy the images to
another media type (as determined in the disk staging
schedule). The media type for the final destination is typically
tape, but could be disk.
• This two-stage process allows the NetBackup administrator
to leverage the advantages of disk-based backups in the near
term, while preserving the advantages of tape-based backups
for long term.
• Disk staging meets the following objectives:
• Allows backups when tape drives are scarce.
• Allows for faster restores from disk.
• Facilitates streaming to tape without image multiplexing.
Disk staging is conducted in
two separate stages
• A backup creates an image on the storage unit acting as the disk
staging storage unit.
• A relocation schedule determines when the image from the disk
staging storage unit should be relocated to the destination storage
unit.
• The image continues to exist on both the disk staging storage unit
and the destination storage unit. File restores are done from the
disk staging storage unit copy, while the destination storage unit
copy can be considered the long term copy.
• The disk copy continues to exist on the disk staging storage unit
until either the copy expires based on the copy's retention period,
or until another Stage I process needs space on the disk storage
unit.
• When a Stage I process detects a full disk staging storage unit, it
pauses the backup, finds the oldest image that has been
successfully copied to the destination storage unit, and expires
this image copy.
 Configuration of Policies
• Policy Definition:- The set of rules that
netbackup follows when backing up its
clients
• In Netbackup Administration Console:-
• How to create a new policy
- Note: Policy name should not have any
spaces
• What does a Policy define?
- Which Client,When/What/Where/How to
Backup
 Veritas Netbackup Client
Software
• It runs on client.
• From Master Server and Media
server,ping the client using the
client’s ipaddress and host name and
vice versa.
• The above 3 way communication
should be there.
 Policy
• Attributes
• Schedules
• Clients
• Backup Selections
• Note:-When seen from the activity
monitor,the parent backup jobs will
have a – under schedule but child
jobs will have the description,for
eg:first backup/daily/weekly/monthly.
• Take checkpoints every
---minutes ->If a backup job is
suspended for some reason and then
resuming the job from the most
recent time can be possible if the
above option is set for example to 15
mins.
• Limit jobs per policy->2
• Job priority ->9999
• Eg: DB archive jobs have highest
priority.,hence set it to 9999.
Allow Multiple Data Streams
• Multiplexing • Multistreaming
• Hardware level • Software Level
• Data streams from option
multiple sources • C:\---ABC(File1)
• ---DEF(File2)
use the same tape
• ---GHI(File3)
drive.
• All the 3 files are
• Usually because backed up in 3
the tape drive’s separate streams on
speed is high to the tape drive.
Perform snapshot backup is
used to backup open files
 Daemons and services
Media Server
Master server Client

Bprd Bpcd
(13720) (13782) bpcd

bpsched
bpbrm
Bpbkar(32)-
Bpdbm
(13721) bptm
bpjobd

Tape Files
Catlog
 List of Daemons
• Bpcd ->Client Daemon
• Bpbrm -> recover manager
• Bptm->Tape manager
• Bprd->request daemon
• Bpshed->schedule daemon
• Bpdbm-> database daemon
• Bpjob ->Netbackup job daemon
• Vmd->Volume Manager Daemon
• Bpbkar(32)
 7 Steps
1.When the Daemon’s wake up interval
occurs,the bprd on master will wake
up and start the bpsched.
• Note: bprd is also activated on media
server but after checking the bp.conf
file(/usr/openv/netbackup/bp.conf)
and determining that it is not running
on master server, bprd becomes
inactive.
2. Bpsched calls bpdbm to check the
policy for auto backup schedules
• Bpsched calls the child process to
handle the backup
• Bpdbm calls bpjobd to communicate
with job catalog

3. Bpsched child contacts the media

server to start the bpcd
 4.On media server the
following occur
• Bpcd invokes bpbrm.
• Bpbrm starts bptm which requests a tape
mount and spans a child process to
communicate with client.
• Vmd(Volume manager daemon)
manages the volume catalog and handles
media requests through out the course of
the backup job.
• Bpbrm contacts the client to start bpcd in
client.
 5.Client’s bpcd starts the bpbkar(32)

6.Bpbkar(32) reads data from client

• Communicates directly with bpbrm to
send catalog meta data which is
ultimately written to images catalog
• Send the backup data stream to the
child bptm process
7. The child bptm process passes the
data to the parent bptm process
which writes data directly to the
destination media.
 Port numbers
• Bpcd - > 13782
• Bprd -> 13720
• Bpdbm -> 13721
• “bp.conf” file is present in all
netbackup master/media/client
(unix)servers.It contains the host
name and ipaddress of all the nodes
involved in netbackup
 verbose flag -Logs
• <Install
path>\netbackup\logs\<create a
folder,eg:bpcd>
• Configuration file entry that causes a
higher level of detail to be written in
the logs.
• 5 stages of logs->5->highest
 7.Netbackup Error Codes and
Trouble shooting

• Activity Monitor->RC->Fliter:-
Status>1=>Shows all failed jobs.
• Common Error Codes:-
• 0->Backup successful
• 1->Backup Incomplete
• 11-> System call failed
Rerun backup job after ensuring that
ping from master to media and client is
fine.Else raise a ticket and assign to
Intel team
• 12,13,14-> File
Open/Read/Write Failed
• 21,24->Socket open/write failed
->Restart Netbackup client services

• 41->Network connectivity timed

out
• 42->Network Read Failed
-> If Client can’t be pinged then
raise a ticket.
• 46->Server not accessible
• 48-> Client host name not found
->Check bp.conf file on master server,media
server and client
• 50-> Client process aborted
• 5-> Restore destination has no space.
• 53->Restore error.Backup restore
manager failed to read the file list.
• 54->Timed out connecting to client.
->Host Properties->Client properties-
>Increase Client Read Timeout value.
• $ more bp.conf
SERVER=nj2nbu1-han
SERVER=nj2nbu1
SERVER=nj2nbu2
CLIENT_NAME=uapkb2db.exnj2.MOMEN026545
9
$ pwd
/usr/openv/netbackup

•
 •71->None of the files in
the file list exist
• 83,84,86->Media open,write,position error
->Freeze media
• 96->Unable to allocate new media
->Scratch pool needs medias
• 98->Error requesting media
• 150->Job terminated by admin
• 156->Snapshot error->Refire after
sometime
• 196->Backup window closed
• 213,219->Storage Unit down/unavailable
 Imp Netbackup Commands
• Important 3 paths from where commands
can be executed:-
[ \usr\openv\veritas\netbackup or c:\prog
files\veritas\->Installation Path]
1.<Install Path>\netbackup\bin\admincmd
2. <Install Path>\ volmgr\bin
3.< Install Path>\netbackup\bin\goodies
usr\openv\veritas\netbacku
p\bin\admincmd
• Bpmedialist –m <Tape id> -h <Media server> {Status
of media}
• Bpmedialist –summary {All medias and related info like-
>expiration date}
• Bpmedia –freeze/unfreeze –m <media id> -h <media
server>
• Bpgetconfig –g <clientname> -L {Client details}
• Bperror –u <err code> {Lists jobs failed with error code..}
• Bpdbjobs –summary {activity monitor}
• Bpdbjobs –report {Number of jobs queued/running/failed}
• Bpimagelist –U <Client Name> -d <Start date> -d <End
Date> {Images of backup for the client}
 usr\openv\veritas\volmgr\bin
• Vmoprcmd {To check if drives are up or down}
• Vmoprcmd –h <media server> -resubmit/reset <0/1 drive num>
• Vmquery –m <Tape id> {Status of the tape/media}
• Vmupdate –rt <TLD/ACS> -rn <0/1>
{To do robot inventory }
• Vmcheckxxx –rt <TLD/ACS> -rn <0/1>
{Lists all slots in the tape lib.
Can check slot availability}
• Robtest -> 1<yes> ->s d/s<show all drives/slots>
• ->m d 1 to s 6 <move media in drive 1 to slot 6>
• ->m s6 to d 1 <move media from slot 6 to drive 1>
• Note:-Robtest is done to check if a media is stuck in a drive
• To check if robot is working fine move tapes from drive to slot or
vice versa
• Vmchange –m <media id> -p <pool num> { To move a new
media from one vol pool to another }
usr\openv\veritas\netbacku
p\bin\goodies
• Available_media {Shows all available
medias in the environment}
• Available_media |grep –I Full |grep –I
TLD
{ To get the details of all the available
medias which are full in the tape library}
• Available_media | grep –I <Tape id>
{Check if media is present in the tape
library.If yes then the result is “TLD”
else the result is “none”}
 Restore
• Info needed:-Source server,Dest
server,source file path,dest file path,date of
backup.
• Source client,Dest client,Policy type,Start
/End date and time,Preview and Restore Tabs
• Preview shows the medias needed.
• Check media robot type{TLD/none} for
availability of tape.
• If destination is not given then the root of
netbackup will get filled.So be careful.
 Health Check
• Regular Admin Job to check the activity
monitor for errors
• Coordinate with other teams and get
issues resolved.
• Have the contact details of other teams
• Raise tickets when required.
• SEV 1/2/3/4->8hrs/16hrs/5days/10days
(varies according to SLA)
 Health Check(Contd)
• If there is a ticket breach then call
for a meeting
• Put ticket on hold when other teams
are handling
• Check for failed jobs.Usually backup
tickets take time to resolve
• On Call Support ->24x7 support
 Imp Questions
• How to duplicate tapes?
• What is a catalog? And wat care should be taken in managing catalogs?
• What is multiplexing and multistreaming with examples?
• What is high and low water mark?
• How to restore backup media’s from one master to other master server?
• If a catalog is corruped? How to restore?
• How to archive catalog or how to reduce catalog if catalog sixe is
increased?
• How to use netbackup scripting for fine tuning?
• Basic parameters to create new policy?
• How is image stored in netbackup?
• If your last catalog backup was two days ago and the master server
crashed what would you have to do to bring your environment back up to
present time?
• There is a Tape library with 10 drives ...Can we able to create 2 Storage
units.....?