|
|
nbpemreq — run NetBackup Policy Execution Manager (PEM) Requisition to schedule the jobs that are due and capture PEM information
<admin_dir_path>nbpemreq -due -date mm/dd/yyyy HH:MM:SS [-client_filter client...][-policy_filter policy...]
<admin_dir_path>nbpemreq -due -dateu unixtime [-unixtime] [-client_filter client...][-policy_filter policy...]
<admin_dir_path>nbpemreq -predict -date mm/dd/yyyy HH:MM:SS [-unixtime] [-client_filter client...] [-policy_filter policy...]
<admin_dir_path>nbpemreq -predict -dateu unixtime [-unixtime] [-client_filter client...][-policy_filter policy...]
<admin_dir_path>nbpemreq -predict_all -date mm/dd/yyyy HH:MM:SS [-client_filter client...][-policy_filter policy...]
The NetBackup Policy Execution Manager Requisition (nbpemreq) determines which jobs are due in the near future. It also reads in all entered policy updates that are in a pending state. Finally, nbpemreq gathers the pertinent nbpem information that is placed in the nbpem log file and optionally displayed to stdout.
This command can also instruct nbpem to process policy updates immediately.
When the nbpemreq command runs, nbpem is affected, which slows down policy processing. Because the nbpemreq output may change from release to release, Symantec does not recommend using nbpemreq in scripts.
Provides data about the clients or policies that are scheduled to run by the time specified. The data that is displayed is based on the current time and a future date. Time is indicated bymm/dd/yyyy HH:MM:SS or by a UNIX timestamp.
Provides nbpem information about the state of current jobs and jobs that have run in the previous 30 minutes. nbpem manages all running jobs and keeps history on each job for 30 minutes after the job completes.
Allows nbpemreq to be executed on one or more master servers. The command is executed on each master sequentially in the order that is listed on the command line. When -M is not specified, the default value is the local host.
Provides internal information about the contents of the nbpem persistence database file, which contains information about the jobs that are currently running. If nbpem is interrupted, NetBackup knows which jobs to run when nbpem restarts.
Provides nbpem internal data about the specified policies that includes static data from the policy definition and dynamic information about job scheduling.
Helps determine when a policy is to be run. The displayed information is based on the current time and a future date. Time is indicated by mm/dd/yyyy HH:MM:SS or by a UNIX timestamp.
This option also helps determine why a policy has not run. The difference between the options is the output format and the amount of data presented. It shows the backups that are eligible to run, but it does not indicate which jobs are to run at a specific time. It checks for an open window for the backup, but does not reflect any exclude dates that might be set for the schedule.
Resumes the nbpemreq the scheduling activity that a -suspend_scheduling option has interrupted.
Provides nbpem internal information about the internal subsystem operations. The amount of information that is presented for each subsystem depends on the specified depth. Each subsystem contains varying layers of information.
Suspends the nbpemreq scheduling activity. You can use this option to suspend scheduled backups.
Instructs nbpem to reread the existing policy configuration. Normally, nbpem checks for changes based on the policy update interval that is part of the Global Attributes host properties. The default is 10 minutes. After you run this command, the prompt is simply returned.
Specifies the level of detail to be produced for the various output options. Depth is an integer value starting at zero (least amount of output) and goes up (more output). The maximum depth value and the specific content of each depth level varies from output option to output option. The information differs from the information that is presented by using the -subsystems option.
Displays all 36 subsystems, or the specified subsystems. Separate the subsystems with spaces, not commas. For example:
# nbpemreq depth 3 8 12
Sends the output to stdout. Command output is always directed to the log files even if the screen option is not used. A maximum of 1 MB of data can be written to stdout.
Specifies the number of seconds elapsed since midnight Coordinated Universal Time (UTC) of January 1, 1970, not counting leap seconds.