- Community Home
- >
- Storage
- >
- Entry Storage Systems
- >
- Disk Enclosures
- >
- Zone requirements for EVA to EVA migrations
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Forums
Discussions
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Community
Resources
Forums
Blogs
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО05-10-2011 03:11 PM
тАО05-10-2011 03:11 PM
So the question is simply what are the physical connection requirements to get 2 EVAs to talk to each other? Do I run both EVAs into a SAN switch and zone them together? (generally speaking, targets don't talk to each other, so I am guessing no here). Is there a special back end port for mirroring/migrating? More than 1 option to choose from?
Any specific info appreciated, especially relevant documentation.
TIA.
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО05-10-2011 05:21 PM
тАО05-10-2011 05:21 PM
SolutionEven though you made the zoning between EVAs, you can't do a migration as this is a licensed feature and requires EVA Contineous Access License to migrate the data between EVA(EVA Replication)
If license is there, yes we need to made the zone between EVA host ports so that they can talk to each other and you can create a DR Group(Group of Vdisk that can be replicated to target EVA).
You can dedicate Single/2 ports on each controller for replication. For this you need to do the zone between the Host ports as like below
Zone: EVA8100_CON_A_FP3; EVA8400_CON_A_FP3;
Zone: EVA8100_CON_A_FP4; EVA8400_CON_A_FP4;
Zone: EVA8100_CON_B_FP3; EVA8400_CON_B_FP3;
Zone: EVA8100_CON_B_FP4; EVA8400_CON_B_FP4;
So that source and destination EVAs can talk by using these ports.
You can search for "HP StorageWorks Continuous Access EVA Planning guide" which gives a complete picture about the other dependencies
There are some services offered from HP for data migration
http://h20195.www2.hp.com/V2/GetPDF.aspx/5982-4107EN.pdf
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО05-11-2011 07:41 AM
тАО05-11-2011 07:41 AM
Re: Physical connection requirements for EVA to EVA migrations
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО05-11-2011 07:50 AM
тАО05-11-2011 07:50 AM
Re: Physical connection requirements for EVA to EVA migrations
- HP StorageWorks Continuous Access EVA implementation guide
T3680-96389__20100718 - August 2010) [7ed] - c02491009
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО05-11-2011 03:25 PM
тАО05-11-2011 03:25 PM
Re: Physical connection requirements for EVA to EVA migrations
Also, related to the above zoning recommendation, do I have to zone the same ports together, ie: CA/FP1 <-> CA/FP1 or could I do
CA/FP1 <-> CA/FP2
or even
CA/FP1 <-> CB/FP2
Thanks again.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО05-13-2011 02:55 PM
тАО05-13-2011 02:55 PM
Re: Physical connection requirements for EVA to EVA migrations
Operation Failed! The local storage system has no available path to the remote storage system.
There must be some option in command view, or config step, or something, after the zone is setup, to get the 2 arrays to see each other. Any advice?
Thanks again.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО05-13-2011 03:05 PM
тАО05-13-2011 03:05 PM
Re: Physical connection requirements for EVA to EVA migrations
http://h20000.www2.hp.com/bizsupport/TechSupport/Document.jsp?lang=en&cc=ca&taskId=110&prodSeriesId=3664768&prodTypeId=12169&objectID=c02440932
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО09-24-2012 09:17 AM
тАО09-24-2012 09:17 AM
Zone requirements for EVA to EVA migrations
I have a HP 6300 EVA and I am trying to replicate to a EVA4400 using CA.
Both SAN's are licensed with CA. Each SAN has 2 controllers with 2 fibre ports.
I have merged Brocade SAN switches and both SAN's appear together in Command View P6300.
When I try to setup a Data Replication group I get an error telling me that there are no remote connections available
Although, on the Data Replication tab in vdisk properties both SAN's are recognised. I can setup the DR group to the point where I get another error "operation failed the local storage system has no available path to the remote storage system"
In terms of zoning, do I need to dedicate one port on each controller or is there something else I may be missing in the configuration?