Catalog Backup partially Successful with message WIN32 5: Access is denied

[a_la_carte]

Hello Folks,

Environmen is NBU 7.6.0.1 where Master Server is in Cluster. OS is Windows 2008 R2 x-64.

I am having a strange situation where both Differential and Catalog backup has been getting partially successful since last 2 days with the message "WIN32 5: Access is denied".

We did get these messages before, but upon re-run, the backup gets successful with status code 0, but now since last two days this has repeatedly been getting completed with status code 1.

Any help would be much appreciated.

Below are the logs from the partially completed child stream:-

=======================================================

09/07/2015 12:04:08 - positioned abc001; position time: 0:00:02
09/07/2015 12:04:08 - begin writing
09/07/2015 12:04:18 - Warning bpbrm (pid=19124) from client xxxyyy01P: WRN - can't open file: J:\NetBackup\db\discovery\0.updating (WIN32 5: Access is denied. )
09/07/2015 12:04:18 - Warning bpbrm (pid=19124) from client xxxyyy01P: WRN - can't open file: J:\NetBackup\db\discovery\1.updating (WIN32 5: Access is denied. )
09/07/2015 12:04:18 - Warning bpbrm (pid=19124) from client xxxyyy01P: WRN - can't open file: J:\NetBackup\db\discovery\2.updating (WIN32 5: Access is denied. )
09/07/2015 12:04:19 - Warning bpbrm (pid=19124) from client xxxyyy01P: WRN - can't open file: J:\NetBackup\db\discovery\3.updating (WIN32 5: Access is denied. )
09/07/2015 12:04:19 - Warning bpbrm (pid=19124) from client xxxyyy01P: WRN - can't open file: J:\NetBackup\db\discovery\4.updating (WIN32 5: Access is denied. )
09/07/2015 12:04:19 - Warning bpbrm (pid=19124) from client xxxyyy01P: WRN - can't open file: J:\NetBackup\db\discovery\5.updating (WIN32 5: Access is denied. )
09/07/2015 12:04:19 - Warning bpbrm (pid=19124) from client xxxyyy01P: WRN - can't open file: J:\NetBackup\db\discovery\6.updating (WIN32 5: Access is denied. )
09/07/2015 12:05:42 - Info bpbkar32 (pid=21096) 50000 entries sent to bpdbm
09/07/2015 12:07:11 - Info bpbkar32 (pid=21096) 100000 entries sent to bpdbm
09/07/2015 12:18:45 - Info bpbkar32 (pid=21096) 150000 entries sent to bpdbm
09/07/2015 15:03:48 - Info bpbkar32 (pid=21096) bpbkar waited 10490 times for empty buffer, delayed 10832 times.
09/07/2015 15:03:48 - Info bptm (pid=19808) waited for full buffer 433271 times, delayed 598815 times
09/07/2015 15:04:09 - Info bptm (pid=19808) EXITING with status 0 <----------
09/07/2015 15:04:09 - Info bpbrm (pid=19124) validating image for client xxxyyy01P
09/07/2015 15:04:10 - Error bpbrm (pid=19124) cannot send mail to bp.support@pqr.com
09/07/2015 15:04:10 - Error bpbrm (pid=19124) cannot send mail to root on client xxxyyy01P
09/07/2015 15:04:10 - Info bpbkar32 (pid=21096) done. status: 1: the requested operation was partially successful
09/07/2015 15:04:10 - end writing; write time: 3:00:02
the requested operation was partially successful  (1)

==========================================================================================

Any help would be much appreciated.

Many Thanks All.

[GulzarShaikhAUS]

Can you just reboot each cluster node and try the catalog backup again?

Also try to disable nbdisco service from all clients unless you need the OIP(Oracle Intelligent Policies)

[a_la_carte]

Yes.

We do have Oracle RMAN backup running using the OIP and hence we cannot isable NBDISCO at all.

Rebooting cluster nodes would be big decision and requires approval from the management with concerete reasons as to why a reboot is required to solve this problem.

Any other guidance that can be provided at this time please ?

[Marianne]

If you cannot disable nbdisco, you will just have to live with intermittent status 1 catalog backups or else log a Support call with Symantec/Veritas for a permanent solution or workaround.

[a_la_carte]

Same has already been logged.

Let's see what they have to say on this one.

[a_la_carte · Accepted solution]

Symantec Tech support suggested reboot of Master Backup Server as an unknown application was holding a lock on those files and even when we shut down Netbackup, still we couldn't delete those files.

So finally, after rebooting the Master Server, we have been able to get rid of those files and Catalog backup have been successful.