From NBU Process flow:
When NetBackup starts up, nbpem obtains policyinformation from bpdbm using the nbproxy process. The policyinformation is used to create the job worklist.
When the job is scheduled to run, nbpem requests that nbjm initiate the backup.nbjm then asks bpjobd to add the scheduledbackup to the job list. The job is now visible in the Activity Monitor.
The job begins in a queued state while nbjm requests resourcesfrom nbrb. During the process,nbpem sets anout-of-window timer. If the job stays queued, and the out-of window timerexpires, nbpem notifies nbjm to cancel the job.
nbrbsecures physical resources from nbemm.Physical resources include storage units, tape drives, disk drives, andspecific media IDs.
Once resources are allocated, the job changes to anactive state. nbjm passes start jobarguments to bpbrm.
nbjmprovides the job status to bpjobd.
bpbrmstarts bptm, which is used forbackups to tape drives or optical drives. bpbrmalso starts bpbkar to begin the actualbackup. If this backup were directed to a disk, bpbrmwould start bpdm instead of bptm.
If the required media is library available, bptm invokes the ltid, which issues acommand to the drive to mount the media. bptmalso spawns a second child process to receive the backup data from the client.
Metadata, which is information about the backup, is sentby bpbkar to bpbrm. bpbrm passes the metadatato nbjm, which in turnpasses it to bpdbm. bpdbm stores the metadatain the Image database.
bpbkartransmits actual backup data to the child bptmprocess, which buffers the backup data into shared memory.
The parent bptmtakes the buffered data from shared memory and writes it to the tape device.
nbjmreceives job completion information from bpbrmand reports the job exit status to nbpem.
Is this information you were looking for?
