Your Browser is Out of Date

Nytro.ai uses technology that works best in other browsers.
For a full experience use one of the browsers below
Oracle RAC and PowerFlex Asynchronous Replication
Executive Summary Introduction Product overview PowerFlex asynchronous replication architecture Basic concepts Solution architecture Oracle RAC configuration Failure scenarios
Failure scenarios
Workload description
Scenario 1: Planned test failover
Scenario 2: Complete failover and reverse replication
Scenario 3: Remote snapshot
Scenario 4: Backup in target
Conclusion Appendix References

Scenario 1: Planned test failover

Home > Storage > PowerFlex > White Papers > Oracle RAC and PowerFlex Asynchronous Replication > Scenario 1: Planned test failover

Scenario 1: Planned test failover

  • This scenario is useful in situations such as to offload from source domain site for use cases such as RMAN backup, reporting, and test/dev setup.

    1. Start the workload.

    1. Log in to the PowerFlex presentation server UI on the source system. From the RCG screen, select the Replication RCG that you want to test and choose the Test Failover menu option.

    DASHBOARD CONFIGURATION Domains Fault Sets Storage Pools Replication: 3 RCGs, 1 selected Show Selected Name Appsy•n c_test oracle_DATARED0 oracle_FRA RCGs Source Sys" bdc•soln•— bdc-soln-_ Target Status Stopped By Search for QCGs Failcwer Test Active secondary (Remote) Aaa RPO Complian« 100% 100% Applied Last Journal Time 2/26/21.12:54 PM MANAGE LAG MODIFY Consistent Consistent Consistent Consistent MORE o A Pools O o QEPUCATION Peer Systems Journal Capacity v Details OVERVIEW Test Last Cycle Next Cycle Time Last Cycle Size VOLUME PAIRS (10) TOPOLOGY Failover Test bdc- soln-gateway (Local) Stopped By user 2/26/21, 12:54 PM 2/26/21.12 55 PM Replication TEST aw 14.48 MB,'s oracle_DATARED0 oracle_DATARED0 RPO COMPLIANCE TOO% Activate Wind Go to Settings to activLag 23Sndows

    1. The workload data is still being generated on the source system. The database running on the source cluster is not affected and continues to be up and running. Journals are still getting transferred from the source system to the target system.
    2. Start the database on the target.
    3. Verify that there is a lag of whatever time the RPO is set between source and target.

    RMAN validate and dbverify

    RMAN validate and dbverify was run and ensured that there was no block corruption in the tablespaces and datafiles in the target setup.