HOWTO: Configure Protected Database for Transparent Backup Failover to Downstream or DR Recovery Appliance
(Doc ID 2263353.1)
Last updated on MARCH 12, 2021
Applies to:Zero Data Loss Recovery Appliance X6 Hardware - Version All Versions and later
Zero Data Loss Recovery Appliance X5 Hardware - Version All Versions and later
Information in this document applies to any platform.
Zero Data Loss Recovery Appliance Software - Version 126.96.36.199.7 and later
To provide step by step instructions on how to configure your protected databases to transparently fail over or switch over to the downstream Recovery Appliance Replica when the upstream Recovery Appliance is down due to unplanned outage or extended planned maintenance. This initial document focuses on RMAN backup operations. This document will be updated regarding redo transport in the future.
When the steps have been implemented, no client side changes are required to the daily RMAN backup operations as a result of planned or unplanned outages which impact one of the two Recovery Appliances.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document
|Step 1 : Configure the Upstream and Downstream Recovery Appliances for Standard Replication|
|Step 1a : Create DB User Accounts in the Upstream and Downstream Recovery Appliance|
|Step 1b : Create Protection Policies for the Protected Database on the Upstream and Downstream Recovery Appliance|
|Step 1c : Add the Protected Database SIEBEL to the Two Recovery Appliances and Grant the Necessary Permissions|
|Step 2 : Configure the replication server That Will Be Used to Replicate the Database Backups from New York City to San Francisco|
|Step 2a : Make the Auto-Login Wallet|
|Step 2b : Add the Credentials to the Wallet|
|Step 2c : Create the RA Replication Server|
|Step 3 : Add the Protection Policy to the Replication Server that is to be Replication to the Downstream Recovery Appliance|
|Step 4 : Configure the Oracle Network Configuration Files That Will Be Used for Transparent Failover to Downstream Recovery Appliance|
|Step 4a : Configure a TNS Alias in the tnsnames.ora File That Will Be Used by RMAN to Connect to the Correct Recovery Appliance|
|Step 4b : Configure the sqlnet.ora File That Will Be Used by RMAN to Connect to the Correct Recovery Appliance|
|Step 5 : Register the Protected Database with Both the Upstream and Downstream Recovery Appliances|
|Step 5a : Create a Replication Wallet That Will Store Each of the VPC User Credentials, If One Does Not Already Exist|
|Step 5b : Create Credential Aliases for Each of the Three Credentials That Will Be Used by RMAN|
|Step 5c : Verify the Credentials Are Working Correctly by Logging into Each Target Using Only the Credential Alias|
|Step 5d : Register the Protected Database with the Recovery Appliance in New York City|
|Step 5e : Configure the Channel Device Parameters for Use with the DR_NYC_SF Alias|
|Step 6 : Create the Two RMAN Run Blocks that Will Be Used by RMAN Database Backups|
|Step 7 : Schedule the Database Backup|
|Step 8 : Post Transparent Backup Failover Steps|