8/14/2019 nbu60 prc flw

1/2

2815 Cleveland Avenue

Roseville, MN 55113Phone: 1.800.327.2232

www.veritas.com

NetBackup 6.0

InstantReference

NetBackupStartup

VERITAS Technical Services Education

nbjm makes a request for resources

to nbrb, the NetBackup resource

broker, on the Enterprise Media

Manager Server. The resource

broker performs the task of

centralizing resource management

and accepts resource requests from

nbemm which can include storage

units, tape drives, and media ids.

The job will remain in a queued state

until all of the resources are

allocated for the job by nbrb. Once

the resources necessary for the job

have been acquired from the

Resource Broker, nbrb, the job can

go active. Once a job is active, nbjm

will start bpbrm and passes the startjob arguments to that process. nbjm

will communicate the job status

information to bpjobd and also

accept job requests from bpjobd

such as; cancel, restart, and resume.

nbjm will accept additional requests

from nbpem in order to cancel a job

if the backup window is closed. This

can occur only if the job is still

queued when the window closedmessage is received. The backupand restore manager, bpbrm starts

the appropriate process, bptm for

tape or optical and bpdm for disk,

and also starts the actual backup by

connecting thru the client daemon,

vnetd, to start the backup and

archive program, bpbkar, on the

Client system. The bpbkar program

sends information about files within

the image to the backup and restore

manager, which directs the file

information to the job manager,

nbjm then communicates with bpdbm

using the nbproxy service in order to

create image records in image

database. bpbkar then transmits the

backup image to bptm or bpdm as

directed. The bptm or bpdm process

forks a second child process for this

non-localized backup, which receives

the image and stores it block by block

into a shared memory segment. The

original process then takes the image

from shared memory and directs it to

the allocated storage media. nbjm

receives and handles job completion

information from bpbrm and reports

any job exit status to nbpem. nbjm

also triggers the release of resourcesfor completed jobs, notifying nbrb by

writing in the job progress log.

8/14/2019 nbu60 prc flw

2/2

When NetBackup 6.0 is started via the appropriate NetBackup startup script, the bprd process starts first on the Master Server. The

bprd process then starts bpdbm, which in turn starts nbjm, one of the new Intelligent Resource Manager services. This is then

followed by nbpem, which is also an IRM service. Upon startup, nbpem obtains all of the Backup Policy information from bpdbm via

the nbproxy process. The currently configured Backup Policy information is used to create the job worklist. The build_worklist

function runs only once when nbpem starts up and not every 10 minutes as in the old bpsched process. This reduces the CPU

requirements. nbpem replaces the bpsched build worklist function that ran in pre-NetBackup 6.0 releases every ten minutes. This

was known as the default wakeup interval when bpsched was started by bprd. The nbpem worklist is now persistent. nbpem

calculates when each job in the worklist is due to run. A timer is set to the due time for each job that needs be run. When the job is

due, the timer expires and nbpem issues a request to nbjm to perform the backup. A job start is submitted by nbpem at the time in

which the job is due to run. nbpem communicates via pbx with nbjm, the job manager, to execute a job using the function job

start. nbpem sets a timer for each job to track when the job is out of window. If the job remains queued and the out of window

timer expires, nbpem notifies nbjm to cancel the job. Normally, nbpem will wait for notification from nbjm that the job has either

completed, or been cancelled. In either case, nbpem sets a timer in order to keep track of when job is due next. So the nbpem

service is really the job scheduler. nbjm initiates a backup job by communicating with bpjobd and the job is added to the job list in

the jobs database. The job will now be visible in the Activity Monitor. The job will initially be in a queued state, waiting for resources

to be allocated. bpjobd receives both data and status for any internal job started by nbjm while external or foreign jobs handle theirown communication with bpjobd. The nbjm service assigns, runs, executes, and starts jobs. Now that the job has been submitted to

the job manager, nbjm, the checks for resources must made. This involves the NetBackup Resource Broker.