cancel
Showing results for 
Search instead for 
Did you mean: 

Backup policies don't start as scheduled then end with 196 error?

Phong_Thai
Level 4
I've been having this issue with some of the backup policies that I don't know what else to do at this point. For some reasons some of my backup policies just don't start as scheduled then end with 196 error when the backup window closes. The backup window is like between 8:00pm and 7:00am. The frequency is currently set at 14 hours. Another strange thing happened this morning is that I deactivated those policies, and they still ended with 196 error an hour after the backup window has closed at 9:00am???

I've tried the following steps without any success:
1. Increase the back up window from 7:00am to 9:00am
2. Kick them off manually at the scheduled time to see whether they will start as scheduled the next day.
3. Change the frequency to be higher and lower than the backup window.

I'm currently at 5.1MP3 on Windows 2003 Standard. Is there anything else that I could try?
15 REPLIES 15

Emmanuel_TOUPET
Level 3
Hi,

Did you try teh following command for the prediction of policies?

bpschedreq -predict 12/15/2005 -L

Phong_Thai
Level 4
No, I will try the command. What does it actually do?

Phong_Thai
Level 4
I tried the bpschedreq command, but it didn't return anything. I even redirected the output to a text file, and it's empty. Does that mean I have no backup policies scheduled to run even though they're scheduled to run at 8:00pm tonight?

Allan_Perocho
Level 3
Hi,

We do have the same problem. I created a backup which will run every day at 18:00 but no job is running. Netbackup version is 5.1 and MP3.

Kindly update if you have any workaround on this issue.

Has anyone encountered this error? Is this a bug?

Emmanuel_TOUPET
Level 3
the bpschedreq command displays all policies planned.

Did you check the clock in BIOS?

Emmanuel_TOUPET
Level 3
In bpschedreq command, you can specify the window time

Phong_Thai
Level 4
I ran the bpschedreq command with date and time included, and it came up empty. Things seem to get worsen. I manually ran couple of polcicies at 7:30am this morning, and they wouldn't start, then at 9:00am when the backup window closed, they failed with 196 error.

I will take a look at the bios time. However, the NetBackup Administration console displays the correct time though.

I might just have to open a case with Veritas. I will update this thread when the problem is resolved.

Italo_Calvano_J
Level 4
Please, see if bpsched log exist a code (214).

grep -i "(214)" logfile.

If exist see on Veritas Site a corretion for your problem.

Stumpr2
Level 6
do the jobs queue but never go active?

Phong_Thai
Level 4
No, jobs never queue. The same 5 or 6 policies never start through out the backup window, and then the rest of the backup policies do start but usually 3 or 4 hours later than the 8:00pm scheduled time?

I did notice the 214 error in bpsched log as mentioned by Italo, so I increased wakeup interval from 5 to 15 minutes as indicated in Technote 244143.

Italo_Calvano_J
Level 4
Phong,

Can you see at bpsched log the reference about those policies on the correct time?

This is important. If found the policies on log but not executed...

Can you execute a bppllist -U ?

Stumpr2
Level 6
What is the "Maximum jobs per client" set to in the master server's "Global Attributes"

Phong_Thai
Level 4
Italo,

Here is one of the policies that does not run in the bpsched log:

22:54:16.537 <2> build_worklists_scheduled: POLICY nt-app-ub02-LNUD17...
22:54:16.537 <2> any_window_open: checking policy nt-app-ub02-LNUD17
22:54:16.537 <2> in_backup_window: not in any Disaster-Full backup window
22:54:16.537 <2> in_backup_window: not in any Daily-Cumulative backup window
22:54:16.537 <2> any_window_open: not in ANY window for policy nt-app-ub02-LNUD17

Here is what came out of the bppllist:
Policy Name: nt-app-ub02-LNUD17

Policy Type: MS-Windows-NT
Active: yes
Effective date: 12/19/2005 15:59:02
Backup network drvs: no
Collect TIR info: no
Mult. Data Streams: yes
Client Encrypt: no
Checkpoint: no
Policy Priority: 0
Max Jobs/Policy: Unlimited
Disaster Recovery: 0
Residence: lnub02-alt3
Volume Pool: nt
Keyword: (none specified)

HW/OS/Client: PC WindowsNET lnud17

Include: Shadow Copy Components:\
C:\
E:\
O:\

Schedule: Disaster-Full
Type: Full Backup
Frequency: every 12 hours
Maximum MPX: 14
Synthetic: 0
PFI Recovery: 0
Retention Level: 3 (5 weeks) 3 (5 weeks)
Number Copies: 2
Fail on Error: 0 0
Residence: lnub02-alt3 lnub02-alt3
Volume Pool: nt disaster
Daily Windows:
Monday 23:00:00 --> Tuesday 09:00:00

Schedule: Daily-Cumulative
Type: Cumulative Incremental Backup
Frequency: every 12 hours
Maximum MPX: 14
Synthetic: 0
PFI Recovery: 0
Retention Level: 3 (5 weeks)
Number Copies: 1
Fail on Error: 0
Residence: (specific storage unit not required)
Volume Pool: (same as policy volume pool)
Daily Windows:
Sunday 23:00:00 --> Monday 09:00:00
Tuesday 23:00:00 --> Wednesday 09:00:00
Wednesday 23:00:00 --> Thursday 09:00:00
Thursday 23:00:00 --> Friday 09:00:00
Friday 23:00:00 --> Saturday 09:00:00
Saturday 23:00:00 --> Sunday 09:00:00

Phong_Thai
Level 4
Bob,

The maximum job per client is set at 6.

Phani_Kiran
Level 3
Hi Phong, is this problem sorted? If not, you can try the following:

See the number of drives configured under Storage Unit that is being used. Make sure that it is set to a minimum of 1.

Also, try this link. It has some useful information:
http://seer.support.veritas.com/docs/276940.htm

Cheers,