Re: Rman fails to backup files after IP change
Date: Mon, 06 Jul 2009 09:38:00 +1000
That was it! The reverse lookup did not work.. Our DNS system is nowadays managed by the Windows Moghuls, who seem to think that reverse lookup records are something alien from another era... That's progress for you!
I added the new IP address to the windows hosts file on the master NB server, which is read first of course, and it works now. Ahead to the next task: convincing some windows people of the need for a PTR record.. :(
Jared Still wrote:
> On Thu, Jul 2, 2009 at 11:50 PM, Tony van Lingen
> <mailto:tony_vanlingen_at_technologyonecorp.com>> wrote:
> This has me stumped for the last 2 days or so. We had to change
> the IP address of one of our database servers (167.x.x.x to
> 10.x.x.x address). All went well, after I remembered to change
> /etc/inet/ipnodes as well (d'oh!), except that RMAN no longer can
> communicate with the Netbackup sbt.
> There is a log file on the netbackup server that you need to look at.
> Unfortunately I can't recall the name of it right now.
> It may be the bphdb log, I believe it will show the attempts to
> communicate with the server.
> Generally when troubleshooting NBU I do a backup attempt, then sort
> the log files on
> the server by date, and examine the most recent ones.
> Another thing to remember about NetBackup is that it always does a
> reverse name lookup,
> and everything must match. I believe that's correct anyway, I haven't
> had to deal with it
> for a few weeks now.
> ping the db server from the NBU master server to ensure that the
> address it is
> getting is correct.
> Also, does the policy reflect the new db server (if applicable)
> Jared Still
> Certifiable Oracle DBA and Part Time Perl Evangelist