NetBackup™ 5.

0
Administration
Fundamentals

Catalog Backup and Recovery

At the conclusion of this lesson the participant will be able to:
• Describe the NetBackupTM catalogs.
• Provide general information concerning catalog backups .
• Describe the process of configuring NetBackupTM Catalog Backups.
• Use the ‘bpsyncinfo’ command to display the catalog backup
configuration.
• Initiate catalog backups.
• Monitor catalog backups and recognize success or failure.
• Demonstrate the ability to determine which media has been assigned
for catalog backups.
• Describe the process of how NetBackup™ writes catalog files to a
piece of media.
• Perform a Restore or Recovery of the NetBackup™ catalogs.
What are the NetBackup™ Catalogs?
• NetBackup™ maintains information critical to its operation in
catalogs (databases). Examples of these are:
 image database
 config database
 media database(s)
• Media Manager also stores critical information in catalogs.
Examples of these are:
 Global devices database
 Volume database
 Local devices databases
• From this point on in this lesson both the NetBackup™ catalogs
and the Media Manager catalogs shall be referred to simply as
NetBackup™ catalogs.
Catalog Backup and Recovery – General Information
• Corruption or the loss of the NetBackup™ catalogs would render
NetBackupTM impaired or in a non-operational state. The customer
must be able to restore the catalog information.
• Catalog backups must be performed on a regular basis to ensure
minimum loss of backup information in the event of a disk failure
on the Master server or a Media server system.
• All NetBackup™ catalogs located on the Master Server and on all
Media Servers must be backed up as a point-in-time catalog set.
• Catalog backups can be accomplished automatically or manually.
• Regular backups are not allowed to execute while catalog backups
are active.
Catalog Backup and Recovery – General Information
• NetBackup™ catalogs can be backed up to optical disk, tape, or
disk.
• Specific ‘Media IDs’ must be selected and defined for catalog
backups.
• It is strongly recommended that the backup administrator keep a
manual record of the catalog backup Media ID(s) used during
catalog backups.
• Media that has been configured for use during catalog backups
must be members of the ‘NetBackup’ pool.
Catalog Backup and Recovery – General Information (continued)
• NetBackup™ catalog backups must fit on a single piece of media
for automated catalog backups to occur.
 By default, NetBackup™ catalog backups will not span tapes.
 The procedure to workaround the situation where a customer’s
catalogs are larger than will fit on a single piece of media is
called ‘Protecting Large NetBackup™ Catalogs' and is
documented in the “NetBackup™ 5.0 System Administrator’s
Guide, Volume I”.
• Procedures and details for backing up and restoring NetBackup™
catalogs are documented in the “NetBackup™ 5.0 System
Administrator’s Guide, Volume I”.
Catalog Backup and Recovery – What catalogs must be backed up?
• On a Master Server:
 NetBackup™ catalogs
 License Keys and Authentication catalogs
 Media Manager catalogs
 Vault session information (if Vault is installed and licensed)
 Access Control catalogs (if Access Control installed and
configured)
• On all Media Servers:
 Media database (one of the NetBackup™ catalogs)
 License Keys and Authentication catalogs
 Media Manager catalogs
Locating the NetBackup™ Catalogs
• <install_path>\VERITAS\NetBackup\db (Windows)
• <install_path>/openv/netbackup/db (UNIX)
• Numerous catalogs
 class - Master Server only
 client - Master Server only
 config - Master Server only
 error - Master Server only
 failure history - Master Server only
 images - Master Server only
 jobs - Master Server only
 media - Master Server and each Media Server
 sched - Master Server only
 vault - Master Server , only if the Vault option is
licensed
NetBackup™ License Keys and Authentication Catalogs
• <install_path>\VERITAS\NetBackup\var (Windows)
• <install_path>/openv/var (UNIX)
• The License Keys database is represented by a single file:
 ‘license.txt’
 This file resides on the Master Server and all Media Servers

Windows

UNIX
Media Manager Catalogs
• <install_path>\VERITAS\volmgr\database (Windows)
• <install_path>/openv/volmgr/database (UNIX)
• Several catalogs
 Volume database - located on the ‘volume database host’
 volDB *
 Pool database - Master Server only
 poolDB
 Barcode Rules database - Master Server only
 ruleDB
 Local Devices database - on each Media Server
 ltidevs
 robotic_def
 Global Devices database - on the ‘global device host’
 globDB *
Vault Session Catalog
• Directory/folder location:
 <install_path>\VERITAS\NetBackup\vault (Windows)
 <install_path>/openv/netbackup/vault (UNIX)
• This directory or folder is only present if the Vault option is licensed
and configured, and Vault sessions have been run.
 The ‘sessions’ directory/folder on the Master Server contains
directories, folders, and files which track the operations that
were performed during the Vault sessions. This information is
required for the generation of Vault reports.
 As the ‘Vault’ directory is only relevant if Vault is licensed and
configured, these directory paths need only be added to the
NetBackup™ catalog backups when Vault is being used by the
customer. (Must be added manually as the paths will not be
added automatically to list of directories to back up).
Access Control Catalog
• This directory information is only present and relevant only if the
Access Control feature of NetBackup™ 5.0 is installed and
configured.
 Authentication catalog information
 Authorization catalog information
 Access Control catalog information
 As the ‘Access Control’ information is only relevant if Access
Control is installed and configured, these directory paths need
only be added to NetBackup™ catalog backups when Access
Control is being used by the customer. (Paths will not be added
automatically to list of directories to back up).
• Path(s) to Access Control catalogs
 <Install_Path>\VERITAS\Security (Windows)
 /var/VRTSat (UNIX)
 /var/VRTSaz (UNIX)
Configuring NetBackup™ Catalog Backups
• There are several methods and interfaces for configuring Catalog
Backups:
 Java-based NetBackup™ Administration Console GUI
• Configuration Wizard
• Manual configuration
 Windows-based NetBackup™ Administration Console GUI
• Configuration Wizard
• Manual configuration
 bpadm the Non-graphical interface (UNIX only)
Configuring NetBackup™ Catalog Backups
• Using Java-based NetBackup™ Administration Console

Two methods:
1.Use ‘Configure the Catalog Backup’ Wizard
2.Configure manually.
Configuring NetBackup™ Catalog Backups
• Using Windows-based NetBackup™ Administration Console

Two methods:
1.Use ‘Configure the Catalog Backup’ Wizard
2.Configure manually.
Configuring NetBackup™ Catalog Backups
• Regardless of the interface that is chosen to perform configuration
of catalog backups:
 The configuration parameters required to control the operation
of catalog backups are the same.
 The resulting configuration file, where catalog backup
parameters are stored, is the same.
Configuring NetBackup™ Catalog Backups
• Configuration parameters - Attributes
 Media Server which
will write the backup
 Media 1 for writing
catalog backup
 Media 2 for writing
catalog backup
Configuring NetBackup™ Catalog Backups
• Configuration parameters – Schedule
 Determines how
catalog backups will
occur.
 via scheduler
 Manually only
Configuring NetBackup™ Catalog Backups
• Configuration parameters - Files
 What is backed up?
 Must list catalog
paths for all
NetBackupTM
Servers.
 Configuring NetBackup™ Catalog Backups
• Configuration parameters – Files (continued)
hosta
If paths listed in ‘files list’ do not
/usr/openv/netbackup/db list the ‘hostname’, they are
Unix
ALWAYS related to the system
Master * /usr/openv/volmgr/database which is named as the ‘Media
Server
/usr/openv/var Server’ in the ‘Attributes’.
Recommend that all entries be
hostx pre-pended with the hostname.

Windows hostx:C:\Program Files\VERITAS\NetBackup\db

Media hostx:C:\Program Files\VERITAS\volmgr\database
Server
hostx:C:\Program Files\VERITAS\NetBackup\var
hosty

Windows hosty:C:\Program Files\VERITAS\NetBackup\db

Media hosty:C:\Program Files\VERITAS\volmgr\database
Server
hosty:C:\Program Files\VERITAS\NetBackup\var
= this is the system where catalogs are written (in this case).
*
 Configuring NetBackup™ Catalog Backups
• Configuration parameters – Files (continued)
hosta

Unix hosta:/usr/openv/netbackup/db
Master * hosta:/usr/openv/volmgr/database
Server
hosta:/usr/openv/var
hostx

Windows hostx:C:\Program Files\VERITAS\NetBackup\db

Media hostx:C:\Program Files\VERITAS\volmgr\database
Server
hostx:C:\Program Files\VERITAS\NetBackup\var
hosty

Windows hosty:C:\Program Files\VERITAS\NetBackup\db

Media hosty:C:\Program Files\VERITAS\volmgr\database
Server
hosty:C:\Program Files\VERITAS\NetBackup\var
= this is the system where catalogs are written (in this case).
*
Configuring NetBackup™ Catalog Backups
• Catalog backup parameters configuration file
 ‘sync’ file – exists only on the Master Server
Using the ‘bpsyncinfo’ command
• Located in ‘netbackup’ ‘bin’  ‘admincmd’ directory
 Shows information about most recent catalog backup
 Shows information about catalog backup configuration
 Shows information about media used for catalog backups
 Reads all information from the ‘sync’ file
Initiating NetBackup™ Catalog Backups
• Multiple methods for initiating catalog backups
 Automatically
• The NetBackup scheduler process ‘bpsched’ will initiate a
catalog backup job at the end of a backup session if this
behavior is specified in the catalog backup configuration
(‘sync’ file).
 Manually, using:
• Java NetBackup™ Administration Console GUI
• Windows NetBackup™ Administration Console GUI
• Non-graphical user interface – ‘bpadm’ (UNIX only)
• Command line – ‘bpbackupdb’ command
Initiating NetBackup™ Catalog Backups
• Automatic catalog backup initiation
 ‘MAIN bpsched’ process is responsible
 After all backups in worklist(s) have been completed:
• Initiates databases cleanup
• Reads ‘sync’ file for instructions for performing catalog
backups.
• If ‘automatic’ catalog backup is configured in ‘sync’ file -
calls ‘bpbackupdb’.
• ‘bpbackupdb’ reads ‘sync’ file to obtain instructions for
performing catalog backup.
• A DBBACKUP job type is displayed in the Activity Monitor
Initiating NetBackup™ Catalog Backups
• Manual catalog backup initiation using:
 Java-based NetBackup™ Administration Console GUI
Initiating NetBackup™ Catalog Backups
• Manual catalog backup initiation using:
 Windows-based NetBackup™ Administration Console GUI
Initiating NetBackup™ Catalog Backups
• Manual catalog backup initiation using:
 Non-graphical user interface – ‘bpadm’ (UNIX only)

x
Initiating NetBackup™ Catalog Backups
• Manual catalog backup initiation using:
 Command line – ‘bpbackupdb’ command

 Command options/arguments can be used to override the

contents of the ‘sync’ file
 When used without options/arguments uses ‘sync’ file
parameters to control catalog backup.
 Catalog backup job is displayed in the Activity Monitor.
Monitoring and Confirming Catalog Backups
• Catalog Backup jobs appear in the Activity Monitor.
• The ‘ALL LOG ENTRIES’ report contains entries for Catalog
Backup jobs that are performed
• ‘bpsyncinfo’ command output shows most recent catalog backup
information.
• NetBackup™ debug logs may contain entries that assist in
troubleshooting Catalog Backup failures. In particular, check the
following debug logs:
 bpsched
 bpbkar
 admin (for ‘bpbackupdb’)
Monitoring and Confirming Catalog Backups
• Via Activity Monitor
Monitoring and Confirming Catalog Backups
• Via ‘All Log Entries’ report
Monitoring and Confirming Catalog Backups
• Using ‘bpsyncinfo’ command
 Last ‘mediaID’ used
 Last date/time ‘Media1’ and ‘Media2’ used for catalog backups
Media Used for Catalog Backups
• When a volume is designated as a destination for a catalog backup,
that volume is immediately ASSIGNED (in volume database).
 Status of the volume in volDB is ‘1’ (Catalog).
Media Used for Catalog Backups
• As shown in output of ‘vmquery’ command
 Status of ‘0x1’ indicates ‘Catalog’ backup
Media Used for Catalog Backups
• As shown in output of ‘available_media’ script
 Media status is ‘DBBACKUP’
 Catalog Backup Process Flow
NetBackup
sync bprd Administration
Configuration After
file Backup Interface
Database
Sessions
bpsched Master Server
-OR-
bpdbm 1
2

Server on bpcd Master

which catalog 3 Server
backup is being and
written. EACH
5 Media
bptm bpbackupdb
bpbackupdb bpcd Server
4

bpbkar*
vmd ltid

Tape or Optical Disk with

Databases
 Catalog Backup Process Flow
NetBackup
sync bprd Administration
Configuration Interface
file Database

bpsched Master Server

bpdbm

Server on Master
which catalog Server
backup is being and
written. EACH
Media
bpbackupdb bpcd Server

6 7
bpbkar*
vmd ltid
bpbackupdb

8
Tape or Optical Disk with
Databases
How NetBackup™ Writes Catalog Files
• It is important for support personnel to understand how
NetBackup™ writes catalog backup images onto the backup
media. Here is some key information:
 A backup header always precedes the actual catalog backup
information
 Each entry in the catalog backup ‘files list’ is written as a
separate ‘tar’ image on the backup media.
 Entries in the catalog backup ‘files list’ are written on the
backup media in the order they are listed in the ‘files list’.
 NetBackup™ must be able to successfully write the ‘tar’
images associated with all entries in the ‘files list’ or the entire
catalog backup will fail.
 NetBackup™ never appends to the end of the catalog backup
media. The next time media is used for a catalog backup it
overwrites the previous catalog backup.
How NetBackup™ Writes Catalog Files – an example
• In the illustration below there are three NetBackup™ Servers.
• The respective catalog files lists and a composite list are shown.
MASTERA HOSTA HOSTB
(Master Server hostname) (Media Server hostname) (Media Server hostname)

/usr/openv/netbackup/db /usr/openv/netbackup/db C:\Program Files\VERITAS\NetBackup\db

/usr/openv/volmgr/database /usr/openv/volmgr/database C:\Program Files\VERITAS\volmgr\database
/usr/openv/var /usr/openv/var C:\Program Files\VERITAS\NetBackup\var
Catalog Backup ‘Files List’ Example
mastera:/usr/openv/netbackup/db
mastera:/usr/openv/volmgr/database MASTERA
mastera:/usr/openv/var
hosta:/usr/openv/netbackup/db
hosta:/usr/openv/volmgr/database HOSTA
hosta:/usr/openv/var
hostb:C:\Program Files\VERITAS\NetBackup\db\
hostb:C:\Program Files\VERITAS\volmgr\database\ HOSTB
hostb:C:\Program Files\VERITAS\NetBackup\var\
 How NetBackup™ Writes Catalog Files – an example
• When catalog backups are written to tape, NetBackup™ first
writes a backup header on the backup media.
• Following the backup header, each of the ‘files list’ entries are
written to the backup media, in the order that they are listed.
Tape/Backup Image Image Image Image Image Image Image Image Image
File Mark

File Mark

File Mark

File Mark

File Mark

File Mark

File Mark

File Mark

File Mark
File Mark

Header 1 2 3 4 5 6 7 8 9

Catalog Backup ‘Files List’ Example

Image 1  mastera:/usr/openv/netbackup/db
Image 2  mastera:/usr/openv/volmgr/database MASTERA
Image 3  mastera:/usr/openv/var
Image 4  hosta:/usr/openv/netbackup/db
Image 5  hosta:/usr/openv/volmgr/database HOSTA
Image 6  hosta:/usr/openv/var
Image 7  hostb:C:\Program Files\VERITAS\NetBackup\db\
Image 8  hostb:C:\Program Files\VERITAS\volmgr\database\ HOSTB
Image 9  hostb:C:\Program Files\VERITAS\NetBackup\var\
Restoring and Recovering NetBackup™ Catalogs
• Accomplished via ‘bprecover’ command
 No GUI provided for performing catalog recovery
• ‘bprecover’ is executed on the NetBackup™ Server system on
which the catalog backups were written.
• All NetBackup™ catalogs should always be recovered together, as
the catalog backup represents a point-in-time snapshot of catalog
contents.
 Failure to recover all catalogs (on all NetBackup™ Servers) will
result in out-of-sync catalogs
• On Unix-based NetBackup™ Server systems, all NetBackup™
daemons must be stopped prior to recovery (bp.kill_all or
‘netbackup stop’) *
• On Windows-based NetBackup™ Server systems, all
NetBackup™ Services except the NetBackup™ Client Service
must be stopped prior to recovery. See notes **.
Restoring and Recovering NetBackup™ Catalogs
• Two methods of using ‘bprecover’:
 Media Manager method
• Requires ‘vmd’ running
• If you are using robotic devices to perform recovery, ‘ltid’,
‘txxd/txxcd’ (robotic device daemons) must be running.
• The above two items require that the Media Manager
catalogs be intact – as ‘vmd’ references the Volume
Database (volDB) to locate media, and ‘ltid’ references the
devices database (‘ltidevs’ and ‘robotic_def’) to determine the
local devices that are configured.
• If catalog corruption or loss is evident, use of the ‘Media
Manager’ method may not be possible.
 ‘raw’ method
• No NetBackup™ or Media Manager daemons are required.
Note the exception covered in the notes below.
Restoring and Recovering NetBackup™ Catalogs
• Using the ‘Media Manager’ method to List catalog backup contents
 ‘bprecover’ –l –m <mediaID> -d <density>
Restoring and Recovering NetBackup™ Catalogs
• Using the ‘Media Manager’ method to Recover catalogs
 ‘bprecover’ –r –m <mediaID> -d <density> (prompts)

 bprecover –r ALL –m <media ID> -d <density> (no prompts)

Restoring and Recovering NetBackup™ Catalogs
• Using the ‘raw’ method to List catalog backup contents – from
removable media
 No running Media Manager processes are required – Media
Manager should be stopped!
 Media must be manually mounted before ‘bprecover’ is issued
• Use ‘robtest’, library front panel controls, or manual insert
 ‘bprecover’ –l –tpath <tape device path>
Restoring and Recovering NetBackup™ Catalogs
• Using the ‘raw’ method to List catalog backup contents – from disk
 No running Media Manager processes are required – Media
Manager should be stopped!
 File system path to catalog backups is specified (disk device
path)
 ‘bprecover’ –l –dpath <disk device path>
Restoring and Recovering NetBackup™ Catalogs
• Using the ‘raw’ method to Recover catalog backup contents – from
removable media (Unix)
 No running Media Manager processes are required – Media
Manager should be stopped!
 Media must be manually mounted before ‘bprecover’ is issued
• Use ‘robtest’, library front panel controls, or manual insert
 ‘bprecover’ –r –tpath <tape device path>
Restoring and Recovering NetBackup™ Catalogs
• Using the ‘raw’ method to Recover catalog backup contents – from
removable media (Windows)
 ‘bprecover’ –r –tpath <tape device path>
bprecover -r -tpath \\.\Tape1
Recover shark:C:\Program Files\VERITAS\NetBackup\db y/n (n)? Y
Recovering shark: C:\Program Files\VERITAS\NetBackup\db
Recover shark: C:\Program Files\VERITAS\NetBackup\var y/n (n)? Y
Recovering shark: C:\Program Files\VERITAS\NetBackup\var
Recover shark: C:\Program Files\VERITAS\Volmgr\database y/n (n)? Y
Recovering shark: C:\Program Files\VERITAS\Volmgr\database
Recover eel: C:\Program Files\VERITAS\NetBackup\db y/n (n)? y
Recovering eel: C:\Program Files\VERITAS\NetBackup\db
Recover eel: C:\Program Files\VERITAS\NetBackup\var y/n (n)? y
Recovering eel: C:\Program Files\VERITAS\NetBackup\var
Recover eel: C:\Program Files\VERITAS\Volmgr\database y/n (n)? y
Recovering eel: C:\Program Files\VERITAS\Volmgr\database
Restoring and Recovering NetBackup™ Catalogs
• Using the ‘raw’ method to Recover catalog backup contents – from
disk
 No running Media Manager processes are required – Media
Manager should be stopped!
 ‘bprecover’ –r –dpath <disk device path> (with prompts)

 ‘bprecover’ –r ALL –dpath <disk device path> (without prompts)