Status code 196

Rithesh's picture
Rithesh
November 3rd, 2009

Hi All,

I have NBU 6.5.2A on win 2k3.

I recently noticed some backup jobs fails with 196.
specially yearly backups which had successfully got backed up two weeks back.
Also on daily backup jobs this issue happens for one or two clients even i restart the job..gets successful, then again 196 pops up.

Can anyone know y this happing??

Thanks
Rithesh

Filed under: ,
0 votes
Mouse's picture
Mouse
2 weeks 6 days ago

data tends to grow in time

so your backup window might be not wide enough?

+2 (2 votes)
Deepak W's picture
Deepak W
2 weeks 6 days ago

Ritesh check the Backup

Ritesh check the Backup Window of your job which is getting failed.

Many a tiems it happes due to overlapping of backup windows as well.

For eg - If your yerly backup has a window of 2-4 AM and at the same time your monthly backup is also running. Due to this your yearly backup will remain in que from 2 AM to 4 AM and after 4 AM it will exit with status code 196 - backup window closed.

So for resolving this, increase your backup window for yearly backup schedule.

For more information on status code 196 refer to this link.

Hope this helps.

--
Deepak W

(Kindly close the thread if your query is resolved)

+1 (1 vote)
gavrilov's picture
gavrilov
2 weeks 6 days ago

Try to run bppllist

Try to run bppllist <policy_name> -L to check backup window
and then compair it with logs of your failed jobs:
vxlogview -X jobid=`bpdbjobs -U |grep<policy_name>|head -1 |awk '{print $1}'` -d all > /tmp/job_log
Check start  time.

+1 (1 vote)
Nicolai's picture
Nicolai
2 weeks 6 days ago

ugrade to 6.5.4

There are some major issues with 6.5.2 and backups that span  midnight. Backup to be retained longer than 25years have issues as well.

This TN may assiste you : Tech Alert: A potential for missed backups without notification has been discovered in NetBackup Server/Enterprise Server when calendar based schedules have a configured window spanning midnight and go Active after midnight.

I strongly advise you to upgrade.

0 votes
J.Hinchcliffe's picture
J.Hinchcliffe
2 weeks 5 days ago

RE-spawn issue

If I am reading your post correctly - you are getting good backups - the it re-spawns and fails with a 196.

One thing to check - on your backup selection - do you have it setup to do more then one stream?

C:\
New Stream
D:\

If yes - you need to make sure that there is a New Stream at the top.

New Stream
C:\
New Stream
D:\
(this is fixed in 6.5.4)

----------------
Status 196 "Client backup was not attempted because the backup window closed" received on subsequent retries of backup jobs even though the backup window is open.
seer.entsupport.symantec.com/docs/308278.htm

I don't have to know how to spell....I work on Unix.

+1 (1 vote)
Rithesh's picture
Rithesh
2 days 3 hours ago

Hai, I dnt use New_Stream

Hai,

I dnt use New_Stream directive in any of  policies.

But the issue is eventhough these clients got backed up Yearly.once ..its kicking up again on all my weekends fullbackup & fails with 196.
Due to storage limit i cnt run Yeary backups again..for all these clients...

Please help me to troubleshoot..

Ritz

0 votes