jle1
1 Copper

Mirrorview and Replication Manager

This was posted in the Clariion forum, but suggested it might be better responded to here.

Original posting: http://forums.emc.com/forums/thread.jspa?messageID=606713��


Initial post:

We have a project where RM is to be used to create clones of Mirrorview/S Secondary devices in a consistent manner (SAP/SQL DB). The documentation for Clariion, RM and MV all clearly state this is supported, but I can't find a single reference as to how it's done.
I found a great 'Reference Architecture' document that describes exactly what we are trying to accomplish, but has no technical details.
Is anyone doing this, and if so where did you find supporting documentation?


later post:

This is a new implementation of CX4's, MV and RM (5.1) with SAP on SQL. There is currently nothing in place. I'm working on the RM part, and the design calls for cloning the secondary devices, at the DR site.
I've done RM install/configures with SAP/SQL before, and am familiar with all the features, but do not recall seeing anything specific to MV in any config screens. When you create an application set it figures out what the storage devices are for the SQL DB. By default that would be the MV primary devices, as that is all that the SQL DB knows about. Unless RM can dynamically recognize that the devices are MV primary devices and offer the option to use the secondaries, the clones will be of the primaries. When working with the secondary devices you also have to account for the links and the current status of the seconday devices. This all plays into the state of those devices when the clones are taken. We need to have recoverable and/or restorable images. RM docs clearly state that it cannot manage these links, which may not be an issue, but without any clear documentation on how the 2 products are configured together I can't make any assumptions.
I'm still searching technical, config, install, and admin docs, but nothing yet.

Maybe someone here can offer some insight?

Thanks, John
Labels (1)
0 Kudos
6 Replies
jle1
1 Copper

Re: Mirrorview and Replication Manager

Well, it seems the answer was in plain sight all along, I just did not realize what I was seeing.

When you are configure an RM job the replication technology is selected. For Mirrorview/S secondary device clones, you select Snapview Clone (remote). It's that simple.

Sure wish I'd realized this before...

Thanks, John
0 Kudos
kishore4
2 Bronze

Re: Mirrorview and Replication Manager

Hi John, I am doing samething but with Exchange server but I am getting error "000708 ERROR: This is a REMOTE replication, but no remote node exists in the source node for source". Prod Exchange server is connected to Secondary storage with both IP and FC. I tried with only IP connectivity first and tried both connectivity. Did you have to connect your prod SQL via FC?

Cheers
Sanjesh
0 Kudos
Highlighted

Re: Mirrorview and Replication Manager

Hi John,

I am trying to create snapshots of the secondary image of a mirrorview set. The host is obviously zoned to the storage unit hosting the primary LUNs. When i select the mirrorview secondary as a replication source i am not able to select snapview snap (remote), just snapview snap. Any tips?

Danny

0 Kudos
JamesBEMC
3 Argentium

Re: Mirrorview and Replication Manager

Hi There

You can only select snap on a remote secondary volume as a source, because remember that snap will in essence BE remote, as it is being created off the remote MV Target.

James.

0 Kudos
JamesBEMC
3 Argentium

Re: Mirrorview and Replication Manager

The source node will need to be able to connect to the remote CX array in order to some parts of discovery and sanity/

Thanks

James.

0 Kudos

Re: Mirrorview and Replication Manager

Thanks for the quick reply. However when i run the replication i receive the following error:

n 26, 2010 3:20:28 PM server01 000708 ERROR: This is a REMOTE replication, but no remote node exists in the source node for source

Jan 26, 2010 3:20:28 PM server01 101199 ERROR: Could not select storage for activity, server01.
Jan 26, 2010 3:20:28 PM server01 000198 ERROR: Unable to select suitable storage for this replication.

I thought this was due to the snapshot being local instead of the remote site. Any pointers? I must have something configured wrong.

0 Kudos