0% found this document useful (0 votes)
399 views

NETBACKUP Process Flow

The document summarizes the NetBackup process flow: 1) The master server runs services that manage backups, policies, jobs, and databases. It communicates with clients to run backups and restores. 2) The master server uses services like bpdbm, bprd, nbpem, and nbjm to manage policies, jobs, resources, and communicate with clients. 3) Key components include the policy and job databases that define backup configurations, and daemons that handle tasks, resource acquisition, and communication with clients to perform backups and restores.

Uploaded by

Anirban Sarkar
Copyright
© © All Rights Reserved
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
399 views

NETBACKUP Process Flow

The document summarizes the NetBackup process flow: 1) The master server runs services that manage backups, policies, jobs, and databases. It communicates with clients to run backups and restores. 2) The master server uses services like bpdbm, bprd, nbpem, and nbjm to manage policies, jobs, resources, and communicate with clients. 3) Key components include the policy and job databases that define backup configurations, and daemons that handle tasks, resource acquisition, and communication with clients to perform backups and restores.

Uploaded by

Anirban Sarkar
Copyright
© © All Rights Reserved
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd
You are on page 1/ 11

NETBACKUP Process flow

Created by William Jansen van Nieuwenhuizen


Master Server Backup
Policy Netbackup
Managemen Backup And
t Restore GUI

Config File Database Backup Plus EMM


Netbackup Policy
Job
Resource
Request
Database
Manager
Execution
Broker
Daemon
Manager Manager
Database BPRD On
Onthe
master
master
server
servers,
servers,
that isthe
the
defined
nbpem
NetBackup
nbjm
request
service
asservice
the
daemon
database
EMM
EMMserver,
accepts
uses
responds
server,
nbproxy
manager
jobnbemm
the
requests
toto
nbrb
client
program
getfrom
the
and manages
policy
that
nbpem
service
manages list
and from
fromthe
bpdbm,
media
configuration,
creates
commands the
error,
policy-client
such and
as file
bplabel
databases.
tasks,
and tpreq.
administrative
determines
Started
nbjm
accepts
devices, resource
media,
By: bprd requests
and
requests
(also
storage
by
forfrom
the
unit
following:
nbjm,
configuration,
acquires physical
and performs
BPDBM Restores
when
/usr/openv/netbackup/bin/initbpdbm
acquires
resources
resource
jobs job
selection.
areresources
due toReplaces
run,
fromandnbrb,
vmd
starts
as
and the
due
onruns
UNIX)
device
jobs.
the jobs
allocator.
once
NBPROXY NBPEM Backups
Stopped
resources
from
Started
nbemm,By:
By:
(scheduled
Started
Started
and
/usr/openv/netbackup/bin/bpdbm
manages
when
when
and NetBackup
user-directed)
NetBackup
logical resources.
starts.
starts. -terminate
Archives
command
are
Started
Stopped
available.
By:
By:
on Started
UNIX
/usr/openv/netbackup/bin/nbemmm
/usr/openv/netbackup/bin/nbpem
andwhen
by stopping
NetBackup thestarts.
NetBackup -terminate
Database
List that
Debug
Started
Manager
Stopped
-terminate Log:
By: is Started
On
backed
service
By: the server,
when
up or archived
NetBackup
/usr/openv/logs
files
/usr/openv/netbackup/bin/nbrb
on Windows. starts.(UNIX) or
-terminate
NBPROXY Manual
install_path\logs
Stopped
Debug By:
immediate
Log: /usr/openv/netbackup/bin/nbjm
bpdbm
On (Windows).
backups
the server,
legacy (started
log through
/usr/openv/logs
directory -terminate
on (UNIX)
the the NetBackup
server.
or
NBJM administration
See
DebugUnified
Log:Logging
install_path\logs On interface
the server,
(Windows).manual
/usr/openv/logs
backup option) (UNIX) or
Started
install_path\logs
See Unified
By: logging
Initiate
(Windows).
Request Daemon option on the Special
EMM Database Actions
See Unified logging
NBEMM menu in bpadm (also the
NBRB /usr/openv/netbackup/bin/initbprd command).
Stopped By: Terminate Request Daemon option on the
Special
Actions menu in bpadm.
Debug Log: bprd legacy log directory on the server.

Sha
Mem red
ory

Disk Tape Client


Disk
Created by William Jansen van Nieuwenhuizen
Master Server Backup
Policy Netbackup
Managemen Backup And
t Restore GUI
Backup Plus Remote
Netbackup ClientManager
Backup
Tape
Media Daemon
and
Manager
andDevice
Restore
Process
andManagement
Monitor
Managerservice Startup
Config File Database On master
Process
Remote
UNIXManager
clients,
and mediabpcd
and Monitor
is
servers,
the NetBackup
Service
the Backup/Restore
bptm manages
(nbrmms)
client daemon
bothis the
Manager
disk
and
conduit
and
lets
Database BPRD NetBackup
manages
tape
Media
through and
which
the
device
startclient
EMM
programs
management
and
discovers
bptm on remote
or
andprocesses
bpdm
configures
hosts
process.
are
(canstorage
automatically
Itbealso
UNIX
on
uses
clients and
error
backup
initiated
media duringrestore. It is used when the storage unit type is
or other
status
either
NetBackup
servers. from
In
servers).
addition
startup.
the client
For
to
Toexample,
and
configuration
startfrom
thesethe
bptm
processes
server
management,
or bpdmcan manually,
connect
to determine
nbrmms
run
to UNIX
BPDBM clients
the
disk
bp.start_all
provides
or without
Media
all (UNIX)
access
Manager.
requiring
or
tobpup
media
This
/.rhosts
(Windows).
program
server
entries
resources
manages
ltid
onautomatically
theforthe
remote
monitoring
transfer
host.
starts
of
NBPROXY NBPEM The program
final
images
other
and status
daemons
between
ofisbackup
used
and
theprograms
client
when
or restore
nbjm
andas the
operations.
starts
necessary.
storage
bpbrm device.
Theand daemons
when
bpbrmnotifications.
Started
should
event beBy:running
For each
afterbackup
initial startup.
or restore, bpbrmnbjm startsstartsan an
communicates
instance
In
Started
the case By: with the
ofStarted
robotic whenclient.
daemons,NetBackup
such asstarts,
tl8d andor by tlhd, the
NBPROXY (For
of bpbrm
bptm
a description
associated on onrobot
the
theserver
server
of the
/usr/openv/netbackup/bin/nbrmms
must that
with
NetBackup
also has
the
be the
appropriate
storage
client for
configured daemon
unit.
storage onunit.
the daemon PC to
NBJM clients,
run.
Stopped
ThereBy: Completion
Completion
areStopped
also additional
when of
of operation.
operation.
NetBackup
ways to start stops,
andor stopby daemons.
see BPCDW32.EXE(for
Debug
/usr/openv/netbackup/bin/nbrmms
Log: bptmbpbrmlegacy
legacy
windows)
log
logdirectory
directory
below.)
-terminate
ononthetheserver.
server.
EMM Database StartedLog:
Debug By: On inetd.
the server, /usr/openv/logs (UNIX) or
NBEMM Stopped
install_path\logs
By: Completion
(Windows). of operation.
Backup Plus Client Daemon Service
NBRB Debug
See Unified
Log: logging
bpcd legacy log directory on executable
both client and
On Windows clients, BPCDW32.EXE is the
server.
file that
starts the NetBackup client daemon.
Started By: When Windows starts if the daemon is
in the Startup
group. Otherwise, by double clicking on its icon.
Media Server Stopped By: On Windows, you can stop it through
the Services
NBRMMS application in the Control Panel.
BPCD
Debug Log: BPCD legacy log directory on the client.

BPTM

BPBRM

Sha
Mem red
ory

LTID Client
Disk Tape
Disk
Created by William Jansen van Nieuwenhuizen
Master Server Backup Backup Client
Policy Netbackup
Managemen Backup And
t Restore GUI
Backup Plus Filesystem
INET Daemon
Client
Backup/Archive
Daemon Snapshot
Manager Provider
Config File Database Often
On UNIX
clients,
called
clients,
clients
bpfis
a super-server,
the
creates
bpcdBackup/Archive
is the
andinetd
NetBackup
deletes
listens
Manager
snapshots.
client
on designated
generates
daemon
Note that
and
ports
thelets
Database BPRD used by
NetBackup
backup
bpfis is images.
internet
start programs
services suchon remote
as FTP,hosts
POP3,(canandbetelnet.
UNIXWhen
a TCPofpacket
clients
Started
part theBy:Snapshot
bpbrm
or UDP onpacket
Client
the add-on
server
arriveswith
product.
withthe
a particular
storage unit.
destination
or
Stopped
Started
other servers).
By:
By:port
bpbrm.
Completion
number,
For example,
inetd
of operation.
launches
the serverthe canappropriate
connect to UNIX
BPDBM server program
clients
Debug
Stopped without
Log:
By:bpbkar
Completion
requiring
to handle
legacy/.rhosts
the
oflog
operation.
connection.
directory
entries on on
For
the
the
services
remote
client. that
host.are
NBPROXY NBPEM not expected
The
Debug program
Log: is bpfis
toused
runlegacy
with
when high
log
nbjm
directory
loads,
starts
this
bpbrm
onmethod
the
Backup, Archive and
client
uses
when
or memory
more efficiently, since the specific
bpbrm
alternate or servers
Restore run
from only when
needed. Furthermore,
communicates
client. with the noclient.
network codeGUI is required in the
NBPROXY application-specific
Started By: inetd. daemons, as inetd hooks the sockets
NBJM directly toBy:
Stopped stdin,
Completion
stdout and ofstderr
operation.
of the spawned process.
Debug Log: bpcd legacy log directory on both client and
Backup Plus Client Daemon Service
EMM Database server.
NBEMM On Windows clients, BPCDW32.EXE is the executable
NBRB file that
starts the NetBackup client daemon.
Started By: When Windows starts if the daemon is
in the Startup
group. Otherwise, by double clicking on its icon.
Stopped By: On Windows, you can stop it through
the Services
Media Server application in the Control Panel.
Debug Log: BPCD legacy log directory on the client.
NBRMMS BPCD
BPCD

BPBRM
BPTM BPFIS

BPBRM BPINET
D
Sha BPCD
Mem red
ory

BPBKAR

LTID Client
Disk Tape
Disk
Created by William Jansen van Nieuwenhuizen
Master Server Backup Backup Client
Policy Netbackup
Managemen Backup And
t Restore GUI

Config File Database


Database BPRD

BPDBM
NBPROXY NBPEM
Backup, Archive
or Restore from
GUI
NBPROXY

NBJM
EMM Database
NBEMM
NBRB

Media Server

NBRMMS BPCD
BPCD

BPBRM
BPTM BPFIS

BPBRM BPINET
D
Sha BPCD
Mem red
ory

BPBKAR

LTID Client
Disk Tape
Disk
Created by William Jansen van Nieuwenhuizen
Logging
Log locations
All unified logs are written to the /usr/openv/logs
directory (UNIX) and the install_path\NetBackup\logs
folder (Windows). Unlike legacy logging, you do not
need to create logging subdirectories. Log files for
originator IDs are written to a subdirectory with the
name specified in the log configuration file.
Changing log file locations
The unified logging files can consume a lot of disk
space. You can direct them to a different location, if
needed.
Unified Logging file name format

Unified logging uses a standardized naming format for log files, as


follows:
productID-originatorID-hostID-date-rotation.log
The following shows the meaning of each of the variables in the log file
name:
product ID - Identifies the product.
The NetBackup product ID is 51216.
originatorID - Identifies the log writing entity, such as a process,
service, script, or other software.
hostID - Identifies the host that created the log file.
Unless the file was moved, this ID is the host where the log resides.
date - Shows when the log was written, in YYMMDD format.
rotation - A numbered instance of a log file for a given originator.
This numbering is used for log file rotation.
EXAMPLE
Vxlogview Command
Use this command to view the logs that unified logging creates. These logs
are stored in subdirectories in /usr/openv/logs on UNIX or install_path\logs on
Windows.

Unlike the files that are written in legacy logging, you cannot view unified
logging files with a text editor. The unified logging files are in binary format,
and some of the information is contained in an associated resource file. Only
the vxlogview command can assemble and display the log information
correctly.

You can use vxlogview to view NetBackup log files as well as PBX log files.

To view PBX logs using the vxlogview command, do the following:


Ensure that you are an authorized user. For UNIX and Linux, you must have
root privileges. For Windows, you must have Administrator privileges.
Specify the PBX product ID by entering -p 50936 as a parameter on the
vxlogview command line.
Log View Examples Part I
Log View Examples Part I

You might also like