I disabled nsrauth in client and storage node. I will start backup...lets see
Hopefully you did the same on backup server too (and you must restart daemons after that for change to take effect).
I have seen this on two different occasions:
a) nsrauth
b) client has been ugraded and there was an issue with NMDA/NMO licenses (server was lower version and client was higher using NMDA)
However, in both cases if I remeber correctly (for b) for sure) this error would happen imediatelly. In you case, it looks more as if control session is killed by timeout of some kind (firewall, TCP_KEEPALIVE, similar).
If this doesn't fix it, increase the debug level on the backup and check the debug log for more detail around the error message. You do this by adding NSR_DEBUG_LEVEL and NSR_DEBUG_FILE to the parms.
I think this error produced because of a miscommunication between NMO and NetWorker client, This error is not related to RMAN, it is either the nsrauth , or the username and password you are using for backups has been changed ( Permissions ). I believe by disabling the nsrauth ( As you done already ) this behavior will be changed and fixed, otherwise double check the username and password you are using for backing up.
Previously backup was working fine from networker . No Authentication error. From oracle end, backup is completing. larger database backup is failing, not for small database like "user" tablespace with control file. At the end, backup is failing...............
TCP_keepalive was already set. Now issue has been resolved.
Steps: 1. Delete NSR_Peer information from another oracle physical server paired of effected server (Oracle database in RAC enviroment) because i believe somewhere else second server was interrupting the backup from first oracle client.
2. Again configure oracle client using legacy method.
ble1
6 Operator
•
14354 Posts
•
56186 Points
2549
0
Posted June 14th, 2012 05:00
Hopefully you did the same on backup server too (and you must restart daemons after that for change to take effect).
I have seen this on two different occasions:
a) nsrauth
b) client has been ugraded and there was an issue with NMDA/NMO licenses (server was lower version and client was higher using NMDA)
However, in both cases if I remeber correctly (for b) for sure) this error would happen imediatelly. In you case, it looks more as if control session is killed by timeout of some kind (firewall, TCP_KEEPALIVE, similar).