Please enter search query.
Search <product_name> all support & community content...
Article: 100018741
Last Published: 2020-03-08
Ratings: 1 2
Product(s): NetBackup & Alta Data Protection
Problem
Backup jobs fail to start at scheduled times but can be initiated manually.
Cause
This condition may be seen when the job state in the
pempersist file is not correctly written due to the NetBackup Policy Execution Manager (nbpem) being unexpectedly stopped.
Example: If a job state was written as
active in the
pempersist file, and nbpem was unexpectedly or accidentally stopped and restarted, the job would be listed as
active but will never get a job
complete. This job or jobs (if multiple jobs were
active at the time of the shutdown) will never schedule because nbpem thinks they are already
active as indicated in the
pempersist file.
The above result can occur when NetBackup is incorrectly shut down with active jobs.
Solution
If restarting the NetBackup services does not resolve the issue, renaming the pempersist file is required.1. Stop all NetBackup services on the master server:
Windows:
<install path>\netbackup\bin\bpdown -v -f
Unix:
/usr/openv/netbackup/bin/goodies/netbackup stop
2. Rename the
pempersist file:
****The pempersist file will vary in name based on NetBackup version and OS. The asterisk (*) used below is to indicate the potential variation. Please use care when executing the commands below to rename(move) your specific file to make way for NBPEM to create a new one.
****The pempersist file will vary in name based on NetBackup version and OS. The asterisk (*) used below is to indicate the potential variation. Please use care when executing the commands below to rename(move) your specific file to make way for NBPEM to create a new one.
Windows:
cd <install path>\netbackup\db\jobs\
move pempersist* pempersist*.old
Unix:
cd /usr/openv/netbackup/db/jobs/
mv pempersist* pempersist*.old
3. Restart all NetBackup services on the master server:
Windows:
<install path>\netbackup\bin\bpup -v -f
Unix:
/usr/openv/netbackup/bin/goodies/netbackup start
4. Use
nbpemreq to verify scheduling has been updated:
Windows:
<install path>\netbackup\bin\admincmd\nbpemreq -updatepolicies
Unix:
/usr/openv/netbackup/bin/admincmd/nbpemreq -updatepolicies
5.Use
nbpemreq to predict scheduling:
Windows:
<install path>\netbackup\bin\admincmd\nbpemreq -predict -date MM/DD/YY HH:MM:SS
Unix
/usr/openv/netbackup/bin/admincmd/nbpemreq -predict -date MM/DD/YY HH:MM:SS
Example:
./nbpemreq -predict -date 07/11/08 11:05:00
Note: If you have a policy scheduled to start at 11:00:00 AM, predict for 11:05:00. The output will show whether the policy is in the scheduler or not.