Video Screencast Help

catalog backups are failing with error code 12

Created: 17 Sep 2012 • Updated: 28 Jan 2013 | 9 comments
anishC5's picture
This issue has been solved. See solution.

Hi,

On one of our environments, we have a catalog backup failure with error code 12:

17/09/2012 13:56:55 - Error bprd(pid=2152) Unable to write progress log </F/ProgramÀ Files/Veritas/NetBackup/Logs/user_ops/dbext/logs/vxbsa.1347886614.4472.4924.prog.pcb_std> on client corp-mlw-bk01. Policy=NBU_CAT Sched=NBU_Catalog 
17/09/2012 13:56:56 - Error bprd(pid=2152) CLIENT corp-mlw-bk01  POLICY NBU_CAT  SCHED NBU_Catalog  EXIT STATUS 12 (file open failed)

How do i proceed to troubleshoot and what steps / logs shoudl I refer to?

Master server = Media server = NBU 6.5

Thanks,

Anish

Comments 9 CommentsJump to latest comment

Marianne's picture

Check for Full filesystem.

We see 'Program Files' in error message - so, master is on Windows?

Check Windows Event Viewer System and Application logs.

If logging is enabled in NBU, check bprd and bpdbm logs.
admin and bpbkar logs may also help.

Supporting Storage Foundation and VCS on Unix and Windows as well as NetBackup on Unix and Windows
Handy NBU Links

anishC5's picture

Hi Marianne,

Yes please master server is windows svr 2003 standard Sp2 R2.

Our OS is installed in C drive. F drive has the Veritas installed.

the F drive has 7.92 Gb of free space. No errors seen in the application log or event viewer during that time frame.

NBU logging is 5. checking the logs. Will share the logs here if i can get them out of that system.

Crap this "access denied" is eating my bald head off. :(

Thanks,

Anish

Marianne's picture

Please lower that level 5 logging (unless you have an open call with Symantec for which they require level 5 logs).  This level of logging WILL fill up your filesystem at some point in time.

Level 0 logs are fine for 99% of day-to-day troubleshooting.

Has any permissions changed on the F-drive in recent days?

NBU complains about being unable to write a log file.
Check NBU Client Service - if LocalSystem (default) is used as logon account, ensure that this account has full access to entire Veritas directory tree.

Supporting Storage Foundation and VCS on Unix and Windows as well as NetBackup on Unix and Windows
Handy NBU Links

SOLUTION
anishC5's picture

Hi Marianne,

We have raised the same query with Server team regarding permission change on the server, since we had successful backup till 11-Sep-2012.

Also we gave "Everyone" Full access to the program Files folder, veritas folder etc and checked. But backup failed again.

As advised, logging level has been brought down to 0

Marianne's picture

Have you checked the logs as suggested above?

NBU Problem Report may also give indication of where the problem is.

 

Supporting Storage Foundation and VCS on Unix and Windows as well as NetBackup on Unix and Windows
Handy NBU Links

anishC5's picture

hi marianne,

i was going through the logs. each of 4 MB. any ideas what I should be looking for.

i am searching for anything with "catalog" in it.

bprd log has just this entry:

12:08:02.469 [7616.5036] <2> bprd: Az handle cache read 14

Marianne's picture

NBU needs to be restarted for changed logging level to take effect on bprd and bpdbm.

I too have a problem trying to find anything useful in these massive log files.

This is what I search for:

<8>  Warning
<16> Error
<32> Severe error

We mostly see errors manifest as a <16>. I then scroll up a couple of lines to see the debug info <2> associated with this PID [####.####]

Checks logs roundabout the time of the error seen in Job details.

So, in bprd log for 17 Sept, we expect to see info related to PID 2125 roundabout 13:56: 

17/09/2012 13:56:55 - Error bprd(pid=2152) 

 13:56:55.### [2152.####] < >

Supporting Storage Foundation and VCS on Unix and Windows as well as NetBackup on Unix and Windows
Handy NBU Links

anishC5's picture

unfortuantely the issue is closed without resolution since the server has been decommissioned.
:(