EVA replication

[roadrunner_1]

Has anybody implemented a "many to one" EVA replicatoin? - 2 EVAs replicating to 1 EVA in a different location
If yes, does it work well? any issues or concerns?

[McCready]

A few things

First, you will have to keep all firmware versions in synch, and plan your upgrades accordingly (within a week of each other)

for allowable versions of firmware that are supported together, see

site:hp.com "HP StorageWorks EVA software compatibility reference"

(those long HP URL's are just so messy).

I would also have some type of performance monitoring set up, just to make sure your network links can handle the load, and would not creating a problem caused by one eva, but seen by the other.

But overall, there should be no issues as long as the general EVA best practices are followed - see both the "san design reference guide" and any eva/os specific documentation as well.

[Peter Mattei]

... and dont forget that 2:1 means EVAs but not LUNs eg 1 EVA can talk to 2 EVAs but a particular LUN can only be replicated to one EVA.
See the attached slide for scenarios.

More info can be found in the SAN Guide
http://www.hp.com/go/sandesign

and also check the EVA replication consolidated release note as well as the SW compatibility guide on
http://h18006.www1.hp.com/products/storage/software/conaccesseva/index.html
>>> Technical documents

Cheers
Peter