12-11-2013 02:16 AM
Hello,
Long ago I defined an sql backup for a clustered sql server ( 2 nodes).
Now for some reason I have a problem with the client the sql backup is not working, I get status 239.
here is a sample of the error log :
TIMESTAMP 20131211113740
MASTERSERVER MSTIN
CLIENT PVCSQLR2
INSTANCE PVCSQL2
DATABASE DBA
OPERATION BACKUP
OBJECTTYPE DATABASE
OPTION INCREMENTAL
STATUS 239
INFO Server Status: the specified client does not exist in the specified policy
INFO Error in VxBSACreateObject: 3.
INFO System detected error, operation aborted.
INFO Error in GetCommand: 0x80770004.
INFO An abort request is preventing anything except termination actions.
ENDOPER TRUE
The Virtual Client name is pvcsql2, pvcsqlr2 is one of the nodes, the active one.
Here is the backup script:
OPERATION BACKUP
DATABASE $ALL
SQLHOST "PVCSQL2"
NBSERVER "MSTIN"
MAXTRANSFERSIZE 6
BLOCKSIZE 7
BROWSECLIENT "PVCSQL2"
RESTARTTYPE AUTO
RESTARTWAITSECONDS 60
NUMBUFS 2
NUMRESTARTS 3
SQLCOMPRESSION TRUE
ENDOPER TRUE
Please advice, What do you think the problem is ?
Thanks in advance
12-11-2013 02:59 AM
if I am not wrong you have used pvcsql2 as a client in the Netbackup policy. and in the activity moniter the client name is showing as pvcsqlr2.
when the script is submitted its using the pvcsqlr2 as a client that is where all problem comes..
let me find the parameter that give the client name in the script..
12-11-2013 03:20 AM
add the BROWSECLIENT "PVCSQLR2" in the script and try backup.
12-11-2013 03:28 AM
Hi Nagalla,
Thank you for your response.
The activity monitor shows the correct client - pvcsql2.
there is a technote saying that the browsclient should contain the virtual node name that is pvcsql2.
you advice doing the opposite?
12-11-2013 03:49 AM
You've probably made sure of this but are you configurations consistent across the nodes? same scripts?
12-11-2013 04:03 AM
http://www.symantec.com/business/support/index?page=content&id=TECH42954
status 239 --The name being useded from the cluster does not reflect the name in the SQL policy.
Modify the batch file "BROWSECLIENT" accordingly and try tun the backup
12-11-2013 04:13 AM
see the page number 140 in netbackup SQL admin guide..
12-11-2013 04:22 AM
Try setting the REQUIRED_NETWORK_INTERFACE to the cluster IP.
12-13-2013 10:09 PM
Hello Snir,
Can you please keep us posted on the status...
12-19-2013 01:23 AM
Hi,
Yes the configuration is the same acrross the nodes.
Regads,
12-19-2013 01:25 AM
Hi,
I did but it didnt work either.. got the same results.
Regrds,
12-19-2013 04:15 AM
Hi All,
The sql backup started working today, for no apparent reason, I guess somone fixed something.
Thank you all for your help.