RMAN job failing but filesystem backup ok

[JasonJ54]

Hi

I have a problem where an RMAN job run on the client is unable to connect (get generic eror 250) but I can connect from master server ie open hist properties and the o/s backup is running fine

any ideas anyone?

Thanks

Jason

[DoctorRob]

Are you sure it is a 250?

This could be many things. Can you share the job details?

[Nicolai]

hi @JasonJ54 

I have seen this before. There are multiple reason as of why this can happen since database backup in general are much more complex than file system backup.

Did the setup work before or is this a new client ?

Examples - not a exhaust list.

• NBU media manager library not correctly configured
• configuration errors in rman script
• name resolution errors.
• bp.conf errors.

Thing to check:

• output from RMAN job
• Enable debug logging for Oracle - See : https://www.veritas.com/support/en_US/article.100016353
• Check what the debug logs says - look for <8> warning and <16> Error messages.

[StoneRam-Simon]

Check the CLIENT_NAME in bp.conf / host properties that is set on that client,  an RMAN backup takes the client name from the client, or is hard coded in the rman script...   If the name used is different to the name in the policy, it may not be able to communicate.  

If this is a unix/linux client, you may also have a bp.conf in the oracle home folder that would OVERRIDE settings in the normal bp.conf so check that too..

If you have many databases that are using different names to connect, you may need to update host mappings in the NetBackup host management section of the Master so connections from a different name are associated with the correct client....