06-05-2013 01:38 PM
hi,
i'm trying to perform an RMAN backup but i'm facing this error :
Solved! Go to Solution.
06-06-2013 04:55 AM
Seems to me that you are having name problems with our master server caused by multihomed network
grcprdmobile1 in the bprd log and mob-archive on the command line shown in the bptestbpcd output files
Does traceroute from the master to the client GRCFX2_ge run through the expected interface on the master ? and vice versa from the client to the master
06-06-2013 06:01 AM
hey please check..
from Master server
bpclntcmd -hn client name
bpclntcmd -ip client ip
from client
bpclntcmd -hn masterservername
bpclntcmd -ip master ip
PBX port from CLient to master is not working.. i am not sure error code 42 also reflect network issue..
06-06-2013 06:12 AM
As Marianne suggested, your client tried to aceess to different IP.
I suppose there are something wrong in backup script or bp.conf file in oracle DBA's home directory(if exist). Please post backup script, bp.conf(in /usr/openv/netbackup and oracle DBA home) and output of "bpclntcmd -ip 10.100.2.46" and "bpclntcmd -ip 10.80.0.77".
06-06-2013 06:35 AM
06-06-2013 06:53 AM
script
06-06-2013 06:57 AM
bp.conf
06-06-2013 07:00 AM
06-06-2013 07:01 AM
Yashuhisha,
What about below error.. is this PBX error from client to master. this seems name or IP resolution issue as you posted.. error 42 generally for Network..
06-06-2013 07:02 AM
06-06-2013 07:03 AM
Your master server for this client is mob-archeve.ce22, but NB_ORA_SERV in backup script is set to mob-archive. Modify this line and try again.
export NB_ORA_SERV=mob-archive.ce22
06-06-2013 07:07 AM
Ankit,
but conntction via vnet is successful. PBX connection failure is just because of firewall.
06-06-2013 07:10 AM
OK - we have a whole mix of hostnames and IP addresses for the client:
06-06-2013 07:16 AM
Do change in script or batter to create new script...
Make sure there would not be client naming issue.
06-06-2013 07:26 AM
the rman backup of the second server is still down.
06-06-2013 07:37 AM
Please start new thread for second sever because it might be caused by other causes.
06-06-2013 08:12 AM
hi all,
it's the same cause.
thank you all of you for your help.
best regards.