Netbackup - Scheduled Backups Not Starting

Hi,

It depends. If backup schedule type is frequency based and you have ran manual backup scheduled backup will not run.

If schedule type is calendar based scheduled backup will run even after running manual backup.

If your query is answered please mark as solution

thanks,

Manual backups do have an effect on scheduled backups - but i did think that it was only frequency based ones that were affected rather than calendar based ones

So for frequency based a manual backup counts towards the frequency of the backup.

What does have an effect however is backup failures, so if you did some manual backups as a result of failures then perhaps the failure window had not expired in time for your backups to run.

On the Master server host properties - Global Attributes tab is the Scheduled backup attempts section

So if this is 2 tries in 12 hours and a client has failed twice it will not be valid for any schedules for 12 hours after the last failure

Hope this helps

Solution4all - I am running Calender based as opposed to frequency based and it didn't run as expected - so that theory doesn't stand up.

Mark - failures could be a factor here.  I have not run any manual backups (or scheduled for that matter) on these three policies since yesterday afternoon, so will leave it well alone and see if it runs as expected tonight.  Watch this space.......

AJ

Thanks to you all for the input - especially Marianne for the pointer to the info in the Windows Admin Guide I.

I am assuming (hoping) that the schedules run as planned this evening, and will confirm in the morning and mark up the solution.

AJ.

Easiest way to check is with:
nbpemreq -predict_all -date <mm/dd/yyyy HH:MM:SS> [-policy_filter <policy>]

the directory path to this command is <install_path>\NetBackup\bin\admincmd\

nbpemreq -predict_all -date mm/dd/yyyy HH:MM:SS

This is 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 

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.

For example

nbpemreq -predict -date 09/23/2010 12:00:00
Predicted work assuming no job run between now and Thu Sep 23 12:00:00 2010

to include dates/times

# nbpemreq -due -date 09/23/2010 12:00:00

-due

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 afuture date. Time is indicated bymm/dd/yyyy HH:MM:SS

Then run the following command:

nbpemreq –updatepolicies

please restart the netbackup services

use the command

nbpemreq -predict_all -date <mm/dd/yyyy HH:MM:SS> [-policy_filter <policy>]

as suggested by marine, u can check if job is due or not using above command.

you dont have to wait till teh next schedule, (or staring at NB console to see if jobs come in or not  )

Jobs did start last night so it must have been as identified - the manual backups did affect the scheduling.  Many thanks for the nbpemreq info.

AJ