Professional Documents
Culture Documents
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
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
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 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).
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-usableSUSPEND
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
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