3PAR StoreServ Storage
cancel
Showing results for 
Search instead for 
Did you mean: 

SAN Replication Configuration Help for Oracle Database (11gR2)

roydba
Occasional Contributor

SAN Replication Configuration Help for Oracle Database (11gR2)

Hi Experts, 

 

We are using HP 3PAR storage for Oracle RAC database and HP remote copy for replicating data to DR. Our storage is capacity is full. We have another 3PAR box and presented LUNs from that box to database server.

Question: Can I add all LUNs from Box-1 and Box-2 under same Remote Copy Group. 

Requirement is, If Box-2 link failed, Box-1 should stop replicating and vice versa, otherwise there will be difference between Box-1 and Box-2 LUNs. Oracle requires all LUNs should stop replication at same time.  

Would anyone please advise me a solution. 

Thanks in advance. 

 

2 REPLIES
aberus
Regular Visitor

Re: SAN Replication Configuration Help for Oracle Database (11gR2)

You may be in a pickle my friend because your Oracle LUN's are pulling storage from different physical arrays.  In order for Oracle recovery to work you need to have consistency between all of the LUN's which is what the RC groups provides.  About the only thing that I could think of, and this would require testing, would be to place the DB into hot backup mode kick off both of the RC groups then take the DB out of hot backup mode.  Taking this approach you will at least know that your Oracle headers are in a "frozen" state.

I've created a script that does all of this (3PAR Users Group), but my situation is a little difference because I am running Oracle on Windows so I am not able to use Recover manager.

Sheldon Smith
Honored Contributor

Re: SAN Replication Configuration Help for Oracle Database (11gR2)

A Remote Copy Group (RCG) is tied to a target pair. You have two target pairs: Box-1 <> DR, and Box-2 <> DR, so you would have two RCGs: Box-1_DR and Box-2_DR.

HPE 3PAR Recovery Manager Central for Oracle requires all volumes be on one system. So, what Aberus said.
Here's an idea, not sure if this will do what you need or not, it would require testing;
Using Asynchronous Periodic replication, you set both RCG periods to zero, so they require manual (scripted) resynchronization. Then after you put the database into Hot(?) Backup mode (so you are working with consistent database volumes):

  1. Create consistent group snapshots of both groups of DR (secondary) volumes with "creategroupsv"
  2. Manually synchronize both RCGs with "syncrcopy"
  3. Put database back to Normal mode.
  4. After both RCGs complete synchronization, delete the DR snapshots from step 1.

In case of failure, you stop both groups, fail them over to the DR system, and promote the pre-synchronization snapshots to the now primary volumes.


Note: While I work for Hewlett Packard Enterprise, all of my comments (whether noted or not), are my own and are not any official representation of the company.
----------
If my post was useful, click on my KUDOS! thumb below!