cancel
Showing results for 
Search instead for 
Did you mean: 

Status 12 Unable to write progress log

sushilyadav088
Level 4

Hi,

We are trying to configure SAP DB archive backups but backups are failing with below error.

03/30/2017 13:30:01 - Error bprd (pid=14235) Unable to write progress log </sapdb/DDA/backup/logdir/bparchive.log> on client ddxdb. Policy=DV_UNIX_DB_SP_ACH Sched=manual-backup
03/30/2017 13:30:01 - Error bprd (pid=14235) CLIENT ddxdb POLICY DV_UNIX_DB_SP_ACH SCHED manual-backup EXIT STATUS 12 (file open failed)

----------------------

Below is the Archive script on client end

/usr/openv/netbackup/bin/bparchive -p DV_UNIX_DB_SP_ACH -s manual-backup -L ${LOG_DIR}/bparchive.log -S server.company.com -f ${TMP_DIR}/archlist >> $LOG_FILE 2>&1

1 ACCEPTED SOLUTION

Accepted Solutions

quebek
Moderator
Moderator
   VIP    Certified

Hello

Looks like you are running NBU 772 or above...

Here is solution for you http://www.veritas.com/docs/000108221

 

View solution in original post

5 REPLIES 5

quebek
Moderator
Moderator
   VIP    Certified

Hello

Looks like you are running NBU 772 or above...

Here is solution for you http://www.veritas.com/docs/000108221

 

Hi Quebek,

making that change seems to have fixed the issue however now backup is failing due to error 48 "client host name could not be found". Archive backup is getting triggered with first name only not FQDN and i think changing client name to FQDN will fix that issue but i can not find where client name is mentioned in which script on client that i can change to FQDN, could you please suggest script and location where i should search for client name?

OS and DB backups are running good with FQDN name. I can not make changes in master and media server host file.

quebek
Moderator
Moderator
   VIP    Certified

Hi

This is other issue and should have been opened as a new thread and this post marked as solved... right??

But.... I would have checked the /usr/openv/netbackup/bp.conf file to see what is the client name configured there... and then check the forward reverse DNS lookups if all is going hand in hand.... Playing with hosts file is not really welcome... as later on only more troubles are being faced... Please have your network team to properly manage DNS.

Hi quebek,

Yes, this post should have been marked as resolved and i will do it.

bp.conf file has first name but DB and OS backups are running fine with FQDN, my issue is archive backups are triggering from client with only first name. How can i make archive backups triggered with FQDN? that will fix the issue. 

quebek
Moderator
Moderator
   VIP    Certified

you are trying hard way... what name in configured in you policy? short of fqdn? if short add to oracle policy fqdn as client - add not replace, if fqdn add short - add not replace... this should do the trick ...