SAP restore fails with " dbc_get_string: Output = EXIT STATUS 135"

[Anth105]

Hi

We have a NetBackup 6.5MP5 environment running on Solaris 10 system. the  SAP restore fails withth " dbc_get_string: Output = EXIT STATUS 135"

Here is an excerpt of the backint  log:

10:29:29.202 [7485] <2> bsa_bplist: end_date = Tue Mar 23 03:07:37 2010

10:29:29.202 [7485] <2> bsa_bplist: Request = root sdba sapcha uxzeusc052z18 uxzeusc052z18 sap_zfs_data 9 sap_sapdb 3 999 126931005
7 1269310057 4 4 1 1 1 0 17 0 1231 4 0 C C C C C 0 2 0 0 0
10:29:29.202 [7485] <4> bsa_bplist: Filepath = /sapdb/CHA/backup/Backdata
10:29:29.398 [7485] <2> dbc_get_string: Output = EXIT STATUS 135
10:29:29.398 [7485] <16> VxBSAQueryObject: ERR - dbc_get_string() failed 135
10:29:29.398 [7485] <4> restore_one_fifo: System detected error, operation aborted.
10:29:29.398 [7485] <4> do_restore: Exit.
10:29:29.398 [7485] <4> /usr/openv/netbackup/bin/backint 6.5: *********************************************************************
***********
10:29:33.768 [7480] <2> sap_Wait: waitpid : process (7485) forkId (7485) status (2)
10:29:33.768 [7480] <16> sap_Wait: ERR - job (7485) failed status (2)
10:29:33.768 [7480] <4> do_restore: Exit.
10:29:33.769 [7480] <4> /usr/openv/netbackup/bin/backint 6.5: *******************************************************************


This is NOT an alternative restore. 


I have attached the full backint log file

Any help will be appreciated

thanks


Antho

[Nathan_Kippen]

I'm just going to throw this out there:

touch the following:

/usr/openv/netbackup/db/altnames/No.Restrictions

[Anth105]

 No.Restrictions  is already  and also  on the  master -> Host Properties - Master Servers --> Client Attributes --->  Browse and restore ability on the General tab is set to Allow both.

[Marianne · Accepted solution]

Are you initiating the restore as the same user that performed the backup?

Also verify in Host Properties -> Master Server -> Client Attributes -> Client_Name
that Browse and Restore is allowed for this specific client name.

If all of the above checks out, you need to have a look at bprd log on the master server to see how the master server interpreted the client request.