Scheduled backup were not running

[Rockey_jay]

Hi All,

     We are getting problem with our Master server, sometime the scheduled backup is not getting triggered. Eventhough all services including "bpsched" were running as well with all drives online and perfect. After frequent recycling backup will trigger automatically. Anyone got this type of issues in your environment before? Can you pls suggest me how can we fix this issue. ?

Thanks,

Rockey

[Stefaan_M]

Hi,

do you run manual backups of your policies?

S.

[Omar_Villa]

what version of netbackup are u running?

[Status_Code_0]

Are you running 6.5?  I know the policy execution manager (nbpem) was rewritten in 6.5 and thus had some bugs.  Getting to 6.5.2a is recommended....

[Rakesh_Khandelw]

First think to look at is your backup schedule type if it's calendar based or freqency based, these works vrey differently.  Once you have confirmed these setting are correct and jobs are still not running as per the schedule

Run following command to check what all jobs are scheduled to run  in the near future.

/usr/openv/netbackup/bin/admincmd/nbpemreq -predict 

The -date command specifies the time more accurately.

/usr/openv/netbackup/bin/admincmd/nbpemreq -predict -date mm/dd/yyyy HH:MM:SS

If you do not see the jobs in there run

/usr/openv/netbackup/bin/admincmd/nbpemreq -updatepolicies

It tells the NetBackup policy execution manager to read in all pending policy updates. 

[Rockey_jay]

Stefaan,

    Manual/user backup running fine.

[Rockey_jay]

Omar, 

    Our NB version is 5.1

[Andy_Welburn]

Have a look at the following post & see if it sheds a little light on your issue:

https://forums.symantec.com/syment/board/message?board.id=21&message.id=40718&query.id=324#M40718

it deals with backups not running if they are frequency based & you then run them manually for whatever reason. If your frequency is set too long then they may not get an opportunity to run again when the next backup window opens. This is possibly the information that Stefaan & Rakesh were trying to glean from you.

[bakitup]

In a large NetBackup environment where I use work, we had issues with same thing in 5.1.  The basic problem is the worklist gets corrupt and the only way to correct it was to cycle NetBackup.  We mainly saw the issue where a backup failed and then after that no backups would get scheduled automatically for that client and Policy without stopping/starting NetBackup on master.  The answer we got from support was that it would be corrected in 6.0 when bpsched would go away.