You are on page 1of 94

NetBackup™ 5.

0
Administration
Fundamentals

NetBackup™ Administration
At the conclusion of this lesson the participant will be able to:
• Start, stop, and monitor the NetBackup™ and Media Manager
daemons and processes.
• Interpret the contents of the NetBackup™ bp.conf file on a UNIX-
based system.
• Interpret the contents of the NetBackup™ Registry entries on a
Windows-based system.
• Describe the NetBackup™ Global Attributes and how they effect
operations for policies and clients.
• Describe the default NetBackup™ Reports available and the
information obtained from those reports.
• Obtain and describe information concerning media via interfaces
provided.
• Describe the process of labeling and erasing volumes.
At the conclusion of this module the participant will be able to:
• Describe the following NetBackup™ Media States:
Unassigned
Active
Full
Suspended
Frozen
Imported
• Describe the methods used to expire volumes, images, and media.
• Describe the use of ‘cat_convert’ for working with the image
database.
At the conclusion of this module the participant will be able to:
• Describe the format of Image header and files file.
• Describe the use of ‘cat_convert’
• Describe duplication, importing, and verifying for NetBackup™
backup images.
• List and describe the use of the NetBackup™ Scripts.
Starting and Stopping NetBackup TM
Starting and Stopping NetBackup™ and Media Manager - UNIX
• From the Graphical User Interface:
 NetBackup™ Administration Console > Activity Monitor
• NetBackup command line interface and scripts:
 netbackup < start | stop >
 initbprd (will start ‘bprd’ which starts ‘bpdbm’)
 initbpdbm (starts only ‘bpdbm’)
 bprdreq –terminate (stops ‘bprd’)
 bpdbm –terminate (stops ‘bpdbm’)
 bp.kill_all (stops all NetBackup™ and Media Manager)
 ‘bpps –a’ lists running NetBackup™/Media Manager processes
• Media Manager command line interface
 ltid (starts ‘ltid’, ‘device daemons’ – and ‘avrd’, ‘vmd’)
 stopltid (stops ‘ltid’, device daemons’ – and ‘avrd’)
 vmctrldbm –t (stops just ‘vmd’)
Starting and Stopping NetBackup™ and Media Manager – Java GUI
• From NetBackup™ Administration Console GUI via Activity Monitor.
Starting and Stopping NetBackup™ and Media Manager - Windows
• From the Graphical User Interfaces:
 NetBackup™ Administration Console via the Activity Monitor
 Windows Control Panel via Services
• From the command line interface and scripts:
 bpup - <install_path>\VERITAS\netbackup\bin\
 bpdown - <install_path>\VERITAS\netbackup\bin\
 Use ‘bpps’ to check for running processes
 <Install_Path>\VERITAS\NetBackup\bin\
Starting and Stopping NetBackup™ and Media Manager - Windows
• From NetBackup™ Administration Console GUI via Activity Monitor.
Starting and Stopping NetBackup™ and Media Manager - Windows
• From Windows Control Panel > Administrative Tools > Services
NetBackup Configuration
TM

‘bp.conf’ and ‘Windows Registry’


‘bp.conf’ file – UNIX-based NetBackup™ Servers and Clients
• Located on the Master Server, Media Server(s) and each Client.
• The bp.conf file entries determine the role of the system:
 Master Server, Media Server, or Client
• The bp.conf file is read by ‘bprd’ upon the startup of NetBackup™:
 If a Master Server, ‘bprd’ starts ‘bpdbm’ and ‘bpjobd’
 If a Media Server, ‘bprd’ dies (bpdbm/bpjobd not started)
• The first SERVER entry in the ‘bp.conf’ file establishes the
hostname of the Master Server referenced by this Server/Client.
 First SERVER entry = name of Master Server
 Additional SERVER entries = names of Media Server(s) or
administrative systems
 One CLIENT_NAME entry = name of local Client
• Numerous optional ‘bp.conf’ entries can be made to modify the
behavior of NetBackup™ as needed.
• For changes to take affect, stop and re-start NetBackup™.
Syntax Rules for the bp.conf File Entries
• Use the “#” symbol to comment out lines.
• Minimum of one ‘space’ required on either side of ‘=‘ . Additional
‘white space’ is allowed before/after ‘=‘.
• Blank lines are allowed.
• Any number of blanks or tabs are allowed at the start of a line.
• If a single UNIX system is running as both a Client and a Server,
the <install_path>/openv/netbackup/bp.conf file will contain both
Server and Client options.
• Each non-root user on a UNIX Client can also have a personal
‘bp.conf file in their home directory’:
 $HOME/bp.conf
Sample <install_path>/openv/netbackup/bp.conf file
Registry Entries – Windows-based NetBackup™ Servers and Clients
• The installation of NetBackup™ (as a Server or Client) results in
entries being added to the Windows Registry.
 Items that would be in ‘bp.conf’ on a UNIX-based systems are
found in Registry on Windows-based systems.
• The ‘SERVER’ Registry value determines the Master Server to be
referenced by this Server or Client.
 The first SERVER value = name of Master Server
 Additional references in the SERVER value represent names of
Media Servers or administrative Servers
 MEDIA SERVER value is used to limit administrative access
from those systems referenced.
 One CLIENT_NAME value = name of local Client
• For changes to take affect, stop and re-start NetBackup™.
Registry Entries – Windows-based NetBackup™ Servers and Clients
‘bpgetconfig’ command
• Lists NetBackup™ configuration settings (Windows)

Partial output only


‘bpgetconfig’ command
• Lists NetBackup™ configuration settings (Unix)

Partial output only


NetBackup Configuration
TM

Host Properties
Host Properties
• NetBackup™ provides the ability to modify the behavior of the
product via configuration options presented via the ‘NetBackup™
Administration Console  Host Properties’
 Master Server Host Properties
 Media Server Host Properties
 Client Host Properties
• Too many configuration options to cover them all in this course
material – you have already seen many throughout previous
lessons.
• Documentation is provided in the ‘NetBackup™ 5.0 System
Administrator’s Guide – Volume I’ (Unix and Windows versions).
• Pages which follow illustrate GUI for Master Server, Media Server,
and Client Host Properties.
Host Properties
• Master Server

Java Windows
Host Properties
• Media Server

Java Windows
Host Properties
• Client

Java Windows
NetBackup Configuration
TM

‘SERVER’ and ‘MEDIA SERVER’


SERVER vs. MEDIA SERVER designation
• NetBackup™ provides the ability to restrict administrative access
from systems specified as a “MEDIA SERVER”.
 A System can be defined as a “MEDIA SERVER” as opposed to
a “SERVER”
 Prevents use, by a “MEDIA_SERVER” system, of most
of the administrative functions found in the NetBackup™
Administration Console GUI.
 Protects the Master Server from access by
administrators from defined “MEDIA_SERVER” system.
 “SERVER” and “MEDIA SERVER” designated via ‘Host
Properties on Master and Media server systems.
 “SERVER” and “MEDIA SERVER” designations result in
‘bp.conf’ file entries on UNIX-based NetBackup™ systems and
in a Windows Registry entry on Windows-based NetBackup™
systems.
SERVER vs. MEDIA SERVER designation
Master Server Media Server Media Server

HOSTA HOSTB HOSTC

SERVER = HOSTA SERVER = HOSTA SERVER = HOSTA


SERVER = HOSTB SERVER = HOSTB SERVER = HOSTB
MEDIA_SERVER = HOSTC MEDIA_SERVER = HOSTC MEDIA_SERVER = HOSTC

• The administrator of HOSTA and HOSTB would be fully capable of


using the administrative GUIs (Java or Windows) to perform
administrative functions on HOSTA, HOSTB, or HOSTC.
• The administrator of HOSTC would be limited to running only the
GUI administrative functions that pertain to the ‘Media and Device
Management’ relative to the HOSTC server.
SERVER vs. MEDIA SERVER designation
• NetBackup™ Master Server Host Properties Servers

Results in ‘bp.conf’
SERVER vs. MEDIA SERVER designation
• NetBackup™ Master Server Host Properties
Results in Windows Registry
NetBackup Configuration
TM

Global Attributes
NetBackup™ Global Attributes
• NetBackup™ Global Attributes affect all NetBackup™ behavior
unless overridden by more specific configuration settings.
• NetBackup™ Global Attributes are stored only on the Master
Server.
• NetBackup™ Global Attributes are set via:
 The NetBackup™ Administration Console GUI > Master Server
‘Host Properties’ on either a UNIX or Windows Master Server
 bpadm, the non-graphical User Interface (UNIX only)
• You must stop and re-start the NetBackup™ Request Manager
Daemon (bprd) for changes to take effect.
• Modifying NetBackup™ Global Attributes changes the entries in the
‘behavior’ file, located in the ‘config’ database.
NetBackup™ Global Attributes – Java GUI
NetBackup™ Global Attributes – Windows GUI
NetBackup™ Global Attributes
• Saved on Master Server in ‘behavior’ file:
 <install_path>/openv/netbackup/db/config/behavior (UNIX)
 <install_path>\VERITAS\NetBackup\db\config\behavior
(Windows)

Unix Windows
NetBackup Reports
TM
NetBackup™ Reports
• Provide valuable information to the backup administrator
 Backup success/failure
 Troubleshooting information
 Media utilization
 Media contents
 Locating backup images
 And others….
• Source of the Reports
• Accessed from
 Java NetBackup™ Administration Console GUI
 Windows NetBackup™ Administration Console GUI
 Non-graphical UI – ‘bpadm’ command (UNIX only)
NetBackup™ Reports
• Reports are derived from various sources.
• Reports can be run from GUIs or command line
Report Derived From CLI to generate Brief Description
Name
Backup ‘error’ logs bperror - backstat Shows status and error information
Status on jobs completed within the
specified time period.
Problems ‘error’ logs bperror -problems Lists problems that the server has
reported during the specified time
period.
All Log ‘error’ logs bperror -all Lists all ‘error’ log entries for the
Entries specified period.

Media Log ‘error’ logs bperror -media Shows media errors or


Entries informational messages recorded in
the ‘error’ database
Client Image database bpimagelist -client Shows detailed information on jobs
Backups completed within the specified time
period.
Media Image database bpimagelist -media Identifies volumes that were used
Written for backups during the specified
time period.
NetBackup™ Reports
• Continued from previous page

Report Derived From CLI to generate Brief Description


Name
Media List Media database(s) bpmedialist -mlist Shows information for volumes that
have been allocated for backups.
Media Backup header bpmedialist - Shows contents of a volumes as read
Contents files on backup mcontents directly from media and backup
headers.
media
Images on Image database bpimmedia Lists contents of media as recorded in
Media the NetBackupTM image database

Media Media database(s) bpmedialist - Summarizes active and non-active


Summary summary volumes for the specified server
according to expiration.
Vault Vault sid vlteject -report Various reports pertaining to the
reports directories and vault option. Covered in ‘Vault
Option’ training course.
volume database
NetBackup™ Reports – viewing via NetBackup™ GUI
• Via NetBackup™ Administration Console – Java
NetBackup™ Reports – viewing via NetBackup™ GUI
• Via NetBackup™ Administration Console –Windows
NetBackup™ Reports – viewing with ‘bpadm’
• Character-based Tool (UNIX only)
NetBackup Configuration
TM

Media Administration
Media Information
• The Media Manager application has no reports, but there are ways
to obtain useful information concerning media, including:
 NetBackup™ Administration Console GUI  Media
 ‘vmquery’ command
 ‘available_media’ script
 Media List Report
 ‘bpmedialist’ command
Media Information - via NetBackup™ Administration Console GUI
• Obtains information by querying ‘vmd’ for information from the
Volume Database (volDB)
• Only a fraction of the column information for ‘media is shown’.
Media Information - via NetBackup™ Administration Console GUI
• Column/fields displayed, and order in which they are displayed is
configurable.
Media Information - via ‘vmquery’ command
• Obtains information by
querying ‘vmd’ for
information from the
Volume Database.
• ‘-m <mediaid>’ command
option lists information
for named volume.
• ‘-a’ command option lists
information for all
volumes in Volume
Database.
• Command options exist
for editing volume record
information.
Media Information - via ‘available_media’ script
• Displays information obtained from Volume Database, pool
database, and media database(s)
• Shows media per pool and status of each media id.
Media Information - via ‘Media List’ report
• Shows media assigned to NetBackup™ and status of each
assigned media id.
• Obtains information from mediaDB of each Media Server.
Media Information - via ‘bpmedialist’ command
• Shows media assigned to NetBackup™ and status of each
assigned media id – same content as ‘Media List’ report.
• Obtains information from mediaDB of each Media Server. If
multiple Media Servers exist, will list media owned by each Media
Server.
Labeling Volumes for use with NetBackupTM
• NetBackup™ writes a ‘Media Header’ (1024 bytes) to any tape
(volume) it uses. Normally, volumes are labeled automatically the
first time NetBackup™ uses the media for a backup operation.
 For media in a robotic library – NetBackup™ will automatically
write a label (HEADER) that is based upon the ‘MediaID’ of the
volume, as indicated in the Volume Database (volDB).
• After a volume has been labeled, the MediaID located in the Media
Header is used to identify the volume whenever it is mounted on a
tape drive.
 In this way, NetBackup™ is able to verify that the volume that
was requested is the volume that was mounted.
• If a volume already has a NetBackup™ label (HEADER) on it,
NetBackup™ will not automatically overwrite the existing label.
Labeling Volumes for use with NetBackup™
• Automatic volume labeling
Robot ‘0’ Volume Database (volDB)
Robot Slot barcode MediaID status
# #
Slot 1 0 1 ux1001
- ux1001
- ASSIGNED
-
0 2 ux1002
- ux1002
- -
Slot 2 0 3 ux1003
- ux1003
- -
0 4 ux1004
- ux1004
- -
Slot 3 0 5 ux1005
- ux1005
- -
Slot 4 0 6 ux1006
- ux1006
- -
0 7 ux1007
- ux1007
- -
Slot 5
0 8 ux1008
- ux1008
- -
Slot 6
1) A ‘robot inventory’ is performed and the Volume
Slot 7 Database is updated with records for each tape in the
Slot 8 tape library which shows slot locations of volumes.
2) NetBackup™ requests ‘ux1001’ from Media Manager.
Drive 1
UX1001 3) Media Manager locates ‘ux1001’ in volume database
(volDB).
Drive 2 4) Un-labeled volume is moved from slot 1 to tape drive.
5) NetBackup™ writes label (ux1001) prior to backup
being written.
Labeling Volumes for use with NetBackup™
• There are a few reasons volumes may need to be manually labeled:
 There is data of a non- NetBackup™ format on the media. This
could occur because a customer is re-using tapes – which may
have been previously used by/for another application/purpose.
 If a volume is being used in a ‘standalone’ device (non-robotic
drive), the tape drive will not have a barcode reader and has no
means of identifying the media. To insure that the ‘mediaID”
recorded in the tape header matches the external label on the
volume it may be necessary to manually label the volume.
 See the notes for more information on this situation.
 The volume has an existing NetBackup™ label written on it (in
the tape HEADER) and the customer wishes to assign a new
Volume/Media ID.
 Customer wishes to write backup images to a volume that was
previously used for NetBackupTM catalog backups.
Labeling Volumes for use with NetBackup™
• There are two manual methods for labeling NetBackup™ media:
 Using the NetBackup™ Administration Console GUI
 Using the ‘bplabel’ command
• Using the ‘NetBackup™ Administration Console’ GUI to label media
Labeling Volumes for use with NetBackup™
• Using the ‘bplabel’ command
 Examples of use of bplabel:
 Write a label to a tape where the ‘MediaID’ will be ‘ux1001’.
The tape is a ‘dlt’ tape. A standalone tape drive with a Media
Manager drive index of ‘0’ will be used to write the label.
The ‘-u x’ is used only for standalone drives.
bplabel –m ux1001 –d dlt –u 0
 When used to label volume in a ‘robotic’ drive, ‘bplabel’ will
cause the Volume ID listed to be mounted on a robotic drive
and labeled using the ‘MediaID’ provided (-m). The tape
drive index is not provided when robotic devices are used.
bplabel –m ux1001 –d dlt
 If the volume being labeled is a member of a Volume Pool
other than the ‘NetBackup’ pool, ‘–p <poolname>’ must be
provided to the ‘bplabel’ command.
Erasing Media using NetBackup™
• Two types of erase supported beginning at NetBackup™ 5.0
 Long Erase
• A long erase completely removes all data from the media.
• Because a long erase causes the entire tape to pass in
front of the tape heads, the long erase will require
substantially more time than the quick erase. (A long erase
of a DLT IV tape took just over 2 hours to complete.)
 Quick Erase
• Only erases (writes over) the media header.
• Substantially faster than the long erase, however, data still
may reside on the tape. (A quick erase of a DLT IV tape
(same tape as above) took about 2 minutes to complete).
• Accomplished via the NetBackup™ Administration Console GUI
• Uses ‘bplabel –erase’ command
Erasing Media using NetBackup™
• Accomplished via NetBackup™ Administration Console GUI
 Will not erase assigned media
 ‘Erase’ job shows up in ‘Activity Monitor’.
• Long Erase
• Quick Erase
NetBackup™ Media States
Media State Description
UNASSIGNE Volume has not been assigned to an application. Volume is
‘known’ to Media Manager (is present in Volume Database –
D volDB).

ACTIVE Volume is ASSIGNED to a NetBackup™ Media server. Entry


for volume exists in Media server’s media database
(mediaDB).

FULL Volume is ASSIGNED to a NetBackup™ Media server. ‘End of


media’ has been detected – volume unavailable for backups
until ALL images expire. Can be used for restores

SUSPENDED Volume is ASSIGNED to a NetBackup™ Media server. Volume


is unavailable for writing new backup images. Can be used for
restores.
When ALL images expire, the volume will become
UNASSIGNED.

FROZEN Volume is ASSIGNED to a NetBackup™ Media server. Volume


is unavailable for writing new backup images. Can be used for
restores. When all images expire the volume remains
ASSIGNED. Allows for importing of images.

IMPORTED Volume is ASSIGNED to a NetBackup™ Media server. The


Volume is marked IMPORTED and is available for restores
only. No backups until ALL images expire, media becomes
UNASSIGNED, and then RE-ASSIGNED.
NetBackup™ Media States
• Generally, ‘Media States’ of volumes change automatically
ACTIVE

UN-ASSIGNED FULL FROZEN

SUSPENDED
• There are instances where manual changing of the Media State of
a volume is desirable.
 Customer does not want to use a volume for any further
backups, but wants the images on the volume to expire
normally, and then media to become re-usableSUSPEND
 Customer does not want to write additional backups to media,
and does not want media to re-cycle  FREEZE
NetBackup™ Media States
• Several methods of viewing Media States
 With ‘Media List’ report
 With ‘Media Summary’ report
 With ‘Available_Media’ script
• ‘Media States’ be changed manually using the ‘bpmedia’ command
NetBackup™ Media States
• By Default, NetBackup™ does not overwrite any of the following
formats: ANSI, AOS/VS, CPIO, TAR,DBR or MTF1
 If one of the above formats listed above is detected on a tape
that is mounted for a backup, the state of the volume will be
changed to FROZEN.
• If the volume is in the ‘mediaDB’ (is already owned by
NetBackup™), has been used for backups, and then is found to
contain one of the above formats, the tape will be SUSPENDED.
• If NetBackup™ encounters repeated write failures (2 in a 12 hour
period), when attempting to write to a volume it will SUSPEND the
volume. NetBackup™ tracks media write failures in the error
database.
NetBackup™ Media States
• Viewing with the Media List Report
NetBackup™ Media States
• Viewing with the Media Summary Report
NetBackup™ Media States
• Changing Media States with ‘bpmedia’ command
 Should be executed on the MEDIA Server where the volume
has been used (which OWNS the volume) OR by using ‘-h’ to
specify the Media Server’s hostname.
 Modifies the MEDIA database (mediaDB) on the Media Server
on which the command is executed – unless ‘-h <hostname>’ is
used.
 examples:
• bpmedia –m ux1001 –freeze
• bpmedia –m ux1001 –suspend
• bpmedia –m ux1001 –unfreeze
• bpmedia –m ux1001 –unsuspend
• bpmedia –m ux1001 –<command> –h <hostname>
NetBackup Configuration
TM

Volume, Image and Media Expiration


Volume, Image, and Media Expiration
• Volume Expiration
 Magnetic tape is a media whose quality degrades with use/age.
 The customer may wish to put a limit on the length of
time/amount a tape will be considered for use by NetBackup™.
In NetBackup™ this can be done by setting VOLUME
EXPIRATION.
 Volume expiration can be based upon two criteria:
• A hard end date. After this date the media cannot be used for
further backups. The expired volume may be used for restores.
• A ‘mount count’. After this number of mounts the media cannot be
used for further backups. The expired volume may be used for
restores.
 The VOLUME EXPIRATION DATE and/or MAXIMUM MOUNT
COUNT values (if set) are kept in the Volume Database (volDB).
 Volume Expiration is not set by default.
Volume, Image, and Media Expiration
• Volume Expiration and the NetBackup™ Administration Console
 Volume Expiration is not set by default
Volume, Image, and Media Expiration
• ‘Max Mounts’ and ‘Expiration Date’ are not set by default
• One or both parameters can be set/used – via ‘Change Volumes’.
Volume, Image, and Media Expiration
• Volume Expiration as seen in ‘volDB’ via ‘vmquery’

‘expiration date’ and


‘max mounts allowed’
currently not set for
this volume
Volume, Image, and Media Expiration
• Image Expiration
 While Volume Expiration is optional (per tape) in Media
Manager, image expiration is a standard characteristic of
NetBackup™ behavior.
 Every backup image that is written has a ‘retention level’
associated with it.
• The ‘retention level’ of a backup image is established in the
schedule that is associated with the backup job that created
the backup image.
• The ‘retention level’ is used to calculate an expiration
date/time for the image, at the time the image is created.
Backup time + expiration value = Expiration date/time
 The expiration date and time associated with the backup image
is recorded in the HEADER file for the backup image in the
image database on the Master Server.
Volume, Image, and Media Expiration
• Image Expiration in the HEADER file of the image database
 EXPIRATION field contains a
timestamp which is CTIME when
image will EXPIRE.
 NetBackup™ regularly checks for
and removes images that have
reached their EXPIRATION.
 When ‘EXPIRATION’ is reached
NetBackup™ deletes the
HEADER file and FILES file (.f)
for the backup image.
 Use ‘bpdbm –ctime <timestamp>’
to decode expiration date/time.
Volume, Image, and Media Expiration
• Viewing Image Expiration via the ‘Client Backups’ report
 Report shows backup images created for Client within a
specified time period – including expiration of backup images.
Volume, Image, and Media Expiration
• Viewing Image Expiration via the ‘Images on Media’ report
 Report shows backup images that exist on specified media –
including expiration of backup images.
Volume, Image, and Media Expiration
• While image expiration in NetBackup™ is typically accomplished
automatically (when the image reaches its EXPIRATION date) – it
is also possible to manually expire images.
• There are two general reasons for performing manual image
expiration:
 Expire all images on a volume (media ID) so that the volume
can be re-used immediately.
 Expire an individual image that is no longer required.
• There are two methods that can be used to manually expire
images (all images on a volume or single images):
 Via the NetBackup™ Administration Console GUI
 Via the ‘bpexpdate’ command
Volume, Image, and Media Expiration
• Via the NetBackup™ Administration Console GUI  Catalogs
• This method can be used to expire one or more individual images
at-a-time.
Volume, Image, and Media Expiration
• Methods to manually expire images
 ‘bpexpdate’ command.
– bpexpdate –backupid <backup id> -d <date/time>
 Example:
• bpexpdate –backupid hosta_1068140597 –d 0
(expire image ‘hosta_1068140597’ NOW)
• Method to expire all images on a volume, then UNASSIGN volume
 ‘bpexpdate’ command
• bpexpdate –m <media ID> -d <date/time>
 Example:
• bpexpdate –m QYU085 –d 0
(expire all images on media ID ‘QYU085’ NOW. This
volume will become UNASSIGNED immediately and
available for re-use).
Volume, Image, and Media Expiration
• Effect of expiring individual images
 HEADER file and FILES file for image are removed/deleted
from image database.
 ‘Valid Images’ counter in ‘mediaDB’ on Media Server which
owns the volume is decremented (see counter below).
 ‘Valid Images’ counter must reach a count of ‘0’ (zero) before
media will be re-cycled (becomes UN-ASSIGNED in ‘volDB’).
NetBackup Configuration
TM

Image Database Administration


NetBackup™ Catalogs – format of Image files
• In NetBackup™ 5.0 the image catalog ‘files’ (‘.f’) files are written, by
default, in BINARY format.
• Benefits of BINARY format over ASCII (previous) format include:
 Improved creation, browsing, and search performance
 Reduction of the catalog (.f) file sizes, when compared against
ASCII formatted ‘files’ (.f) file for the same data.
• It is possible to configure NetBackup™ in such a way as to write new
backup images in the old (ASCII) format files (‘.f’ files).
 If the ‘cat_format.cfg’ exists, with ‘CATALOG_FILE_FORMAT=1’,
will cause ‘files’ (.f) files to be written in ASCII format.
 In ‘cat_format.cfg’, with ‘CATALOG_FILE_FORMAT=2’ or
absence of this file - results in BINARY formatted ‘files’ (.f) files.
<install_path>/openv/netbackup/db/config/cat_format.cfg (Unix)
<install_path>\VERITAS\NetBackup\db\config\cat_format.cfg (Windows)
NetBackup™ Catalogs – format of Image files - converting
• NetBackup™ provides a utility to convert image catalog files (.f)
from BINARY-to-ASCII or ASCII-to-BINARY
 cat_convert
 Located in:
• <install_path>/openv/netbackup/bin/ (Unix)
• <install_path>\VERITAS\NetBackup\bin (Windows)
 Binary-to-ASCII conversion, use ‘-b2a’
 ASCII-to-Binary conversion, use ‘-a2b’
 Without switch to indicate what type of conversion to perform,
the utility will identify which format the ‘files’ (.f) file is in and
convert to the other.
 Converting the ‘files’ (.f) file does not necessarily cause the
original source file to be overwritten.
• Use of ‘overwrite’ option (-o) causes original source file to
be replaced/overwritten.
NetBackup™ Catalogs – format of Image files - converting
• ‘cat_convert’
 Used to convert a single image file, to convert all images for a
specific client, or to convert all images files on Master server.
• Examples of use:
 cat_convert <‘Files’ filename>
• If file was ASCII, creates a new file with ‘binary’ embedded
in the new filename. The original file remains ‘as is’.
• If file was BINARY, creates a new file with ‘ascii’ embedded
in the new filename. The original file remains ‘as is’.
 cat_convert <‘Files’ filename> -o
• Converts original file to ‘other’ format (ASCIIBINARY, or
BINARYASCII). Original file replaced.
 cat_convert –b2a <path>/VERITAS/netbackup/db/images/hosta
• Converts all ‘files’ (.f) files for client from BINARY to ASCII.
• Original files remain as is.
NetBackup™ Catalogs – format of Image files - converting
• ‘cat_convert’
• Examples of use - continued:
 cat_convert –b2a <install_path>/openv/netbackup/db/images/
• Converts all ‘files’ (.f) files for all clients from BINARY to
ASCII. The original files remain ‘as is’.
• In a test case, it took about 75 minutes to convert a 50 GB catalog.
• VERY IMPORTANT – Files with ‘ascii’ or ‘binary’ embedded in
filename are not cleaned up by NetBackup™ during image catalog
cleanup. It is the responsibility of person doing the ‘conversion’ to
insure that these files are cleaned up manually.
 For example, the ‘cat_convert’ creates a file with the name
‘policyA_1068145500_FULL_ascii.f’ (original file was
‘policyA_1068145500_FULL.f).
 Files with ‘ascii’ or ‘binary’ in ‘files’ (.f) filenames are never
used/referenced by NetBackup™
NetBackup™ Catalogs – format of Image files - converting
• ‘cat_convert’ illustrated
‘image’ db for client ‘ros1-vtsesun1’

File types before ‘cat_convert’

Files after ‘cat_convert’


NetBackup Configuration
TM

Duplicating, Importing, and Verifying Images


Duplicating NetBackup™ Backup Images
• What is image duplication?
 The creation of additional copies of NetBackup™ backup images.
• Why?
 Additional protection against data loss.
 One or more copies of images might be sent to offsite storage.
• Details relevant to image duplication
 NetBackup™ allows a maximum of 10 copies of an image to exist
(ten is the maximum that NetBackup™ will track in its catalogs).
 The default value for ‘maximum # of copies’ is ‘2’.
 Duplication can be performed using:
• The NetBackup™ Administration Console GUI
• The ‘bpduplicate’ CLI
 When an image is duplicated – the HEADER file for the image, in
the image database, is updated to include a pointer to the new
copy/copies. No new ‘files’ (.f) file is required.
Duplicating NetBackup™ Backup Images
• Setting the ‘Maximum backup copies’ parameter
 A NetBackup™ Global Attribute
 Default Setting = 2, Maximum = 10
Duplicating NetBackup™ Backup Images
• Using the NetBackup™ Administration Console Catalog
Duplicating NetBackup™ Backup Images
• Duplicate images in the NetBackup™ image database
 The screenshots below show excerpts from the HEADER file of
an image which has been duplicated.
 Key information: # of copies, Primary Copy #, and Fragment
Information
Importing NetBackup™ Backup Images
• What is ‘Importing’?
 Importing is the process of reconstructing HEADER file and
‘FILES’ (.f) files in the NetBackup™ image catalog/database
from the actual backup images contained on removable
backup media.
• Why/when is it necessary to perform an import?
 An import is required when an image has expired (automatic or
manual expiration) from the image catalog/database, and it
becomes necessary to restore data from that image. The
HEADER file and ‘FILES’ (.f) file for the backup no longer exist
in the image catalog/database after expiration of the image.
 An import is only possible if the media on which the image
resided has not been re-assigned and been overwritten.
 An image cannot be imported from a disk-based storage unit.
Importing NetBackup™ Backup Images
• ‘Importing’ details
 Importing is a two-phase process
• PHASE ONE involves the reading of the Backup Header
of each image to be imported from the removable media
and the creation of the HEADER file(s) in the Image
Catalog/Database from the contents of the Backup
Header(s). Phase One takes a relatively short amount of
time.
• PHASE TWO involves the reading for the Backup
Image(s) (tar image(s)) for each image to be imported from
the removable media and the creation of the ‘FILES’ (.f)
file(s) in the Image Catalog/Database from the contents of
the tar image(s). Phase Two takes a relatively long time,
compared to Phase One, and is variable depending on the
size of tar image(s).
Importing NetBackup™ Backup Images
• Initiating Phase One of Import
 Via the NetBackup™ Administration Console GUI  Catalog
Importing NetBackup™ Backup Images
• Initiating Phase Two of Import
 Having completed ‘Phase One’, the Administrator searches for
images to Import (Phase Two), selects images, then ‘Import’.
Verifying NetBackup™ Backup Images
• What is ‘Verifying’?
 ‘Verifying’ or ‘Verification’ is the act of reading a backup
image from the backup media on which it is written and
comparing it against the contents of the ‘FILES’ (.f) file for the
image, found in the NetBackup™ image catalog/database.
 No comparison is made between ‘data’ on the backup media
and data found on the client.
 Successful ‘verify’ gives confidence that backup image is
readable on backup media and that NetBackup™ image
catalog accurately reflects the contents of the backup image.
Verifying NetBackup™ Backup Images
• Methods of ‘Verifying’?
 Via NetBackup™ Administration Console GUI
 Via ‘bpverify’ command
• Via NetBackup™ Administration Console  Catalog
 Steps
1. Search for images
2. Select Images to Verify
3. ActionsVerify
NetBackup Configuration
TM

TM
NetBackup Scripts
NetBackup™ Scripts (Unix) and Batch files (Windows)
• Notify Scripts - Server
 backup_notify
 backup_exit_notify
 dbbackup_notify All these scripts are documented in the
 diskfull_notify “NetBackup™ 5.0 System
 restore_notify Administrator’s Guide – Volume II”, in
Chapter 6. Refer to that document for
 session_notify details and examples of usage.
 session_start_notify
 userreq_notify Valuable for gathering information for
• Notify Scripts – Client problem analysis. Required by VERITAS
 bpstart_notify NetBackup™ Support in many cases.
Re-direct output to file.
 bpend_notify
• Other Scripts Provides a summary of media which
may prove useful to a NetBackup™
 support
administrator.
 available_media

You might also like