Have you already run full backup with this new policy? NetBackup does not inherit backup history accross policies. To incremental backup work as it is, full backup on this policy must be run first.

For scheduling issue, please post output of "bppllist policy_name -U" and "nbpemreq -predict -dateu 2147483647 -policy_filter policy_name".

I could not cleary figure out your last issue. Please tell us more detail?

C:\Program Files\VERITAS\NetBackup\bin\admincmd>bppllist File_Share_APSDYFS01 -U

 

the specified policy does not exist in the configuration database (230)

Have you already run full backup with this new policy? NetBackup does not inherit backup history accross policies. To incremental backup work as it is, full backup on this policy must be run first.

Which version of NetBackup are you using? If you got error with "nbpemreq -predict -dateu 2147483647 -policy_filter policy_name", use "nbpemreq -predict 2147483647" instead.

BTW, I checked policy information in your private message now, and wonder if you understand calendar schedule well.

For example, backup window opens from Friday 19:00:00 to Monday 07:00:00 although you specified only Friday as run day. With this configuration, NetBackup can only start backup from Friday 19:00:00 to Friday 24:00:00.

Schedule: Monthly_Archive
Type: Full Backup
Allowed to retry after run day
Friday, Week 1
EXCLUDE DATE 0 - 11/16/2012
Daily Windows:
Friday 19:00:00 --> Monday 07:00:00

Weekly full is as below. Weekly full backup can start from Friday 19:00:00 to Friday 24:00:00. But you have excluded last Friday. This schedule does not take effect across Friday midnight. If you want, you need to add Saturday and Monday as run day.

Schedule: Weekly_Full
Type: Full Backup
Allowed to retry after run day
Friday, Week 2
Friday, Week 3
Friday, Week 4
Friday, Week 5
EXCLUDE DATE 0 - 11/16/2012
Daily Windows:
Friday 19:00:00 --> Monday 07:00:00

This policy go active on last Friday, but full backup in this policy have never run so far. So daily differential incremental backup run on this Monday worked like full.

hey,

1) what is the correct policy name in this question File_Share_APSDYFS01 or File_Share_APSYDFS01

when you say its not starting as per the schudle , ther is something wrong with the policy schedule or with the nbpem timer.

please porvide the below info

bpplinfo -policy <correct policy name inthe question > -U

bpclient -client <corrent client name inthe question > -U

Run the weekly full backup manually tonight. Kick it off before the Incr is due.

In future, make policy changes just before a full is due to prevent the issue that you are currently experiencing.
This is normal behaviour in NBU but unfortunately not very well documented.

Plese run "nbpemreq -predict 2147483647" in stead of "nbpemreq -predict 2147483647 -policy_filter File_share_APSYDFS01".

NetBackup can start backup while start window is open *AND* the day is specified as run day.
With your current configuration, NetBackup will work as below.

• Monthly full backup can start from 19:00:00 to 24:00:00 on 1st Friday.
• Weekly full backup can start from 19:00:00 to 24:00:00 on Friday except 1st Friday of the month.
• Daily differential incremental backup can start on  following time table.
  - Monday 18:00:00 --> Tuesday 06:10:00
  - Tuesday 19:00:00 --> Wednesday 07:00:00
  - Wednesday 19:00:00 --> Thursday 07:00:00
  - Thursday 19:00:00 --> Thursday 24:00:00

Once jobs go active, jobs keep running although start window become closed.
NetBackup does not kill backup when start window is passed. If you configured your start window based on elapsed backup time, please reconsider.

I think current configuration almost follow your intention: full backup must start Friday night, and NetBackup process backup as so. If you really want to allow full backup to start on Saturday, Sunday, and Monday moring, add them as run day.

Anyway, you have to run full backup first to prevent diff from taking all the files. Run full backup manually.

... today it showed the wrong schedule when i checked the predict list..

Please show us what you see?

hi,

you have excluded the date 11/16/2012

and enabled the retries allowed after runday.

I have personally not experienced any joy with nbpemreq -updatepolicies.

I had to wait for nbpem to automatically refresh (every 10 minutes) or either close the GUI and restart NBU.

I hope you have followed advice to only create new policy or change existing before a Full is due to prevent Incrementals from running as full.

Please show us what you see - post output of following:

bppllist <policy-name> -U

nbpemreq -predict -date <mm/dd/yyyy HH:MM:SS>

yes, now incremental is running as incremental after running manual full backup but issue is the policy not starting as per schedule.. 

tried restarting nbu but it didn't help..  please find the outputs to analyze the issue.. 

nbpemreq -predict -date <mm/dd/yyyy HH:MM:SS> - gives all other policies scheduled but not showing up the policy which is having issue.. 

C:\Program Files\VERITAS\NetBackup\bin\admincmd>bppllist file_share_server -U

Whate value did you use for '-date <mm/dd/yyyy HH:MM:SS>' ?

Did you follow advice to only create or modify policy before Full backup is due (i.e. last Friday)?

When last did a backup run for this policy/client combination? This will affect when next backup can be expected.

'NEW' policy seems to have exactly same settings as previous policy, e.g.
 Effective date:      11/16/2012 19:36:17

Does this mean that you have copied the previous policy? 
If there is some sort of corruption in the previous policy, it will be copied to new policy as well...
 

*16th i created this policy - haven't copied from old policy.. ran a manual full backup on the same day, full backup got completed... since then if i trigger increm backup.. it runs as incr backup and last frid 23rd full backup was triggered since its not starting as per schedule.. even yesterday night the incremental backup ran successfully after triggering it manually.. .. 

Whate value did you use for '-date <mm/dd/yyyy HH:MM:SS>' ? i have tried11/27/2012 21:00:00 and 11/28/2012 21:00:00 or any future dates like 11/29 or 12/03 doesnt show this policy schedule....

Every day the backups are triggered manually, does this affect the policy to start as per schedule.. do you suggest to create a new policy again for this client?

The time that you kick off the manual backup will affect automatic schedule. 

If a backup ran during the day, it will not kick off that night. I do expect it to run the next day as per schedule. I have no explanation of why it does not show in predict list. 
I also have a personal preference for Frequency scheduling over Calendar for daily and weekly schedules. See David Chapa's article about Frequency based scheduling:
https://www-secure.symantec.com/connect/articles/n...

Seems like a good idea to create a new policy on Friday, deactivate this one, and see what happens.

Unfortunately the link https://www-secure.symantec.com/connect/articles/n... not opening for me - The requested page could not be found.

Ok, i will deactivate the existing policy and create a new policy on friday, then i will run a manual full backup on the same day.. Will it start the normal schedule for the new policy from Monday onwards.