Problem with Oracle Database Recovery via RMAN and NMDA

Question

My Enviroment

Networker Server: Windows 2008R2 / Networker 8.2.1.6 Build 806

Oracle Server: Suse Linux Ent.: 11.3

Networker Client: 8.2.1-1

NMDA: 8.2.0.1-1

Hi together,

I have made a full backup of my Oracle Database with RMAN and I using NMDA.

My general RMAN configuration :

My Backup Script:

The Backup runs fine and, in Networker, I can see the SSID of the Backup.

Now, I try to recover my database (at the first step: the controlfile)

run {

startup force nomout;

ALLOCATE CHANNEL c1 DEVICE TYPE sbt_tape

parms 'ENV=(NSR_SERVR=[FQDN of MyNetworker Server],

NSR_GROUP=RMAN_Backup,

NSR_CLIENT=[FQDN of My Oracle Server])';

restore controlfile;

}

The recovery task starts ...

but on the Networker Server I see only "... browsing ...

... with never ends. What's happend!? Not recovery session will be started?

Please help!

ble1 · Answer

You don't have to use NSR_GROUP for backup nor restore.  I use only NSR_SERVER, NSR_CLIENT and NSR_DATA_VOLUME_POOL. Do you have any pending message on server (like waiting on media or similar)?

BSGunny · Answer

Thank you for your answer!I know, but in my desperation, I tried all possible variants. And, no! I have no messages or alerts!

ble1 · Answer

Are you using ddboost?

BSGunny · Answer

What is that ? No!

ledugarte · Answer

First of all, I recommend you try a filesystem restore. Backup up a file to the same pool where your database backups reside. Then, try do do a restore from client. Use debuggin. This can give you a clue about what is happening.

I think it could be related to drive permission or name resolution. Check resolution from your storage node to client.

varunmehta0484 · Answer

Is it really supported

barry_beckers · Answer

about an issue 5 years ago, you wonder what? if you can restore an Oracle NMDA backup as a simple file restore? No you can't. You would need the NW NMDA module on a NW client for that (*).

What the last poster was simply referring to, was the advice to test out a regular file restore first to see if that works, before digging further into trying to solve a NMDA module restore issue.

(*) For the NW NMSAP (sap on oracle) module however, in the past, we performed regular file recoveries (NW6 and/or 7) if the sap team ran into certain issues (for example not using a correctly linked backint or even various versions they copied over from other systems or dealing with OS permissions interfering as sap admins created database files with different users than the one used to restore the data). As long as the parameter filesperset (if I recall correctly or something similar) was set high enough so that each database file was actually one saveset, one could restore the files as a regular file. If memory server me well, if the amount of db files was larger than the setting, so that more than one file ended up in the saveset, then it didn't work.

We never had to do that (nor had the sap admins use recover (or the graphical GUI that still existed at the time for Unix before it got deprecated after it stopped working with a certain nw7 or 8 update) the last decade or so, as more and more things got better streamlined making sure NMSAP was installed correctly (so no various backint versions on one and teh same system anymore) and db users were setup correctly (even using the exact same user id on all systems, making for easier restore so that OS permissions wouldn't interfere), making sure one and the same user created all db files.

NetWorker

Problem with Oracle Database Recovery via RMAN and NMDA

Was this post helpful?