Oracle RMAN is a powerful tool with many features for recovering datafiles, tablespaces or even single blocks, as well as cloning databases for non production uses. However restoring a database to an entirely different server (or set of servers) it was backed up from is a somewhat cumbersome process.
In this post we will restore an RMAN backup to a new host, keeping the same database name and datafile names.
When using RMAN to restore a database to a new host, the recover database step fails with:
Crosschecked 43 objects
PSDRPC returns significant error 3113.
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-03002: failure of recover command at 03/18/2017 19:31:23
ORA-03113: end-of-file on communication channel
So your dutiful Infrastructure Team upgrades the Data Domain backup appliance with the latest DD OS code and patches, bringing you up to the latest patch level.
After this, your RMAN backups using DD Boost start failing, and checking the sbtio.log file, which is found in the user dump destination, we see entries like this:
SBT-27970 (211074992) 04/01/16 21:45:01 ERR : [6D42:C94BFB0] ddp_open_file() failed for File: dd0205_boost/XIO11WSB_df_svr1vlas_1_1.bk, Err: 5034-nfs create failed (nfs: Permission denied)
SBT-27970 (211074992) 04/01/16 21:45:01 error 7501: sbtbackup: Could not create file XIO11WSB_df_svr1vlas_1_1.bk on host rstdd0205mgmt.us.oracle.com, error 5034
SBT-27973 (227712944) 04/01/16 21:45:01 ERR : [6D45:D929FB0] ddp_open_file() failed for File: dd0205_boost/XIO11WSB_df_t0r1vlas_1_1.bk, Err: 5034-nfs create failed (nfs: Permission denied)
SBT-27973 (227712944) 04/01/16 21:45:01 error 7501: sbtbackup: Could not create file XIO11WSB_df_t0r1vlas_1_1.bk on host rstdd0205mgmt.us.oracle.com, error 5034
Here’s a scenario I’ve been asked about a few times.
The DBA has backed up the database using RMAN and Data Domain DDBoost and dutifully stored details of the backup in the RMAN catalog.
But then he needs to restore and recover the database to a new server without the RMAN catalog.
This can happen, for example, if an entire data center goes down. Many Data Domain users use the automatic replication option, whereby Data Domain will replicate RMAN backupsets from one device to another, often to a remote data center, but without the original RMAN catalog to inspect, how do we restore and recover our database?
In an earlier post, I looked at using RMAN managed replication to make two copies of an RMAN backupset to two separate Data Domains.
In the post Replicating an RMAN Backupset with Data Domain and DD Boost I then restored the database from the secondary copy to demonstrate that RMAN managed replication could be a useful tool for DBAs to protect against data center failures.
In this example however, I am going to use Data Domain’s native Mtree replication instead of RMAN’s managed replication.