03-18-2012 02:34 AM
Dear Experts,
i have windows 2008 R2 and netbackup 7.1.0.2 as client, and there oracle DB installed on the server.
when i try backup with RMAN the job failed with this error:
(i get it from RMAN log file)
RMAN-00571: ===========================================================
RMAN-03009: failure of backup command on ch2 channel at 03/17/2012 19:03:30
ORA-19506: failed to create sequential file, name="Database_dCIRC_s411_p1_t778186880", parms=""
ORA-27028: skgfqcre: sbtbackup returned error
ORA-19511: Error received from media manager layer, error text:
VxBSAValidateFeatureId: Failed with error:
Server Status: cannot connect on socket
Recovery Manager complete.
Can you please help me? really this critical problem.
03-18-2012 02:51 AM
"Server Status: cannot connect on socket"
Verify that ports are open between client and master: 1556 and 13724.
Please also verify forward and reverse name lookup between master and client. Add hosts entries on master and client if DNS reverse lookup does not function correctly. If separate media server, add hosts entries there as well.
Client connects to bprd on master to request backup. Master needs to resolve client's incoming IP address to hostname that appears in policy Client name.
For further troubleshooting, ensure that you have the following logs enabled:
On master: bprd (restart NBU after creating the folder)
On client: bpcd and dbclient
On media server: bpbrm and bptm (once the process get past master/client verification)
03-18-2012 06:32 AM
Hi,
I have faced this behaviour so many times for SQL server backup, it show the socket opening error. This is not happening for every time, this behaviour takes place only once or twice in month,
It is just because of huge usage of network channel or Database deadlock condition with responissble backuped file.
03-18-2012 06:32 AM
i was already check the connectivity and logs file, everything normal.
03-18-2012 10:15 AM
"Server Status: cannot connect on socket" is not normal. Logs will contain errors.
Please post logs as attachments:
Master: bprd (ensure the connection attempt from client can be seen).
Client: bpcd and dbclient
Please also post output of following commands:
On master: bptestbpcd -client <client-name> -verbose -debug (this will log in client's bpcd log)
On client: bpclntcmd -pn (this will log in Master's bprd log)
03-19-2012 05:52 AM
i change the RMAN script and the backup run without any problem, but the madness when i run online_daily the child run as weekly_archive.
i am sure now the problem related to RMAN script.
can you please check the rman script to me?
hot_database_backup-dd (run with wrong schedule).
hot_database_backup-dd-new (doesn't run and case the problem).
03-19-2012 06:17 AM
I doubt that changing the script would resolve connection errors, unless NB_ORA_SERV or NB_ORA_CLIENT were incorrectly hard-coded in the script.
Your currect problem does not seem to be related to your opening post, right?
The RMAN scripts are not telling us if you have different policies for daily and weekly or different schedules in the same policy for daily and weekly.
You will need to hard-code the policy to be used, otherwise NBU will find the first policy and schedule for the client that is the correct type.
If you have one policy with multiple schedules of type Application Backup, you need to hard-code the schedule in the script.
See this TN: http://www.symantec.com/docs/TECH31742
and this one (O-L-D but still relevant) : http://www.symantec.com/docs/TECH27133