- Community Home
- >
- Storage
- >
- Entry Storage Systems
- >
- Disk Enclosures
- >
- Re: EVA4400 - Continuous access and replication wi...
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
тАО08-23-2010 05:21 AM
тАО08-23-2010 05:21 AM
We are going to install 2 x EVA4400 (named EVA1 and EVA2). We have 2 groups of data (VDISK1 and VDISK2) and would like to do the following:
- EVA1 will be the active storage device for VDISK1 and standby device for VDISK2.
- EVA2 will be active for VDISK2 and standby device for VDISK1.
We want to balance the working load of every EVA, that┬┤s why we want to distribute the VDISKs that way. I guess we need continuous access LTU so that in case one EVA fails we have instant access to current updated information of VDISK1 or VDISK2.
Is all that possible?
Thank you.
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО08-23-2010 06:16 AM
тАО08-23-2010 06:16 AM
Re: EVA4400 - Continuous access and replication with every virtual disk
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО08-23-2010 07:02 AM
тАО08-23-2010 07:02 AM
Re: EVA4400 - Continuous access and replication with every virtual disk
Let├В┬┤s leave the "instant" issue aside, about the solution: Can I allocate a different active storage device to every VDISK as explained above?
Thanks.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО08-23-2010 07:14 AM
тАО08-23-2010 07:14 AM
Re: EVA4400 - Continuous access and replication with every virtual disk
The EVA replication works on virtual disks. A 'source virtual disk' that is read / written to by the servers and a 'destination virtual disk' located on a second EVA, that is usually not even visible to any server.
It is important to understand that an EVA virtual disk is not the same as an MSA200/P2000 'virtual disk'
MSA/P2000: virtual disk ~= EVA disk group
MSA/P2000: volume ~= EVA virtual disk
== is presented to one or more servers
And CA source and destination virtual disks can exist in the same disk group and managed by the same or different controllers at the same time.
On the MSA2000/P2000, a virtual disk and all contained volumes are managed by one controller at a time. An EVA disk group is not exclusively owned by a controller.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО08-23-2010 07:32 AM
тАО08-23-2010 07:32 AM
Re: EVA4400 - Continuous access and replication with every virtual disk
I am not familiarized with SAN terms, once I have read your explanation, let me please reformulate the question:
We are going to install 2 x EVA4400 (named EVA1 and EVA2). We have 2 VDISKs (VDISK1 and VDISK2) and would like to do the following:
- Some servers will read/write from/to source virtual disk VDISK1 from EVA1, unless this EVA1 fails, in that case EVA2 would be the Storage Device where those servers can access to, with updated information.
- Other servers will have their source virtual disk VDISK2 from EVA2, accessing directly to EVA1 only if EVA2 fails.
So we have 2 VDISK, in every EVA one of them is source and the other one destination, for the servers associated.
Have I explained myself better now?
Thanks.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО08-23-2010 07:39 AM
тАО08-23-2010 07:39 AM
Solution- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО08-23-2010 07:40 AM
тАО08-23-2010 07:40 AM
Re: EVA4400 - Continuous access and replication with every virtual disk
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО08-23-2010 07:42 AM
тАО08-23-2010 07:42 AM
Re: EVA4400 - Continuous access and replication with every virtual disk
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО11-25-2010 08:44 PM
тАО11-25-2010 08:44 PM
Re: EVA4400 - Continuous access and replication with every virtual disk
There is another option that you may consider depending upon the operating system you are running on your servers. For example if you are using HPUX then you could use MirrorDisk optional software to mirror LUNS from each EVA and set primary paths alternatively. This means if you lost one EVA your servers will continue working as normal. However if your server operating system does not support a software based mirroring then this option is no good to you.
If I could afford 2 EVAs I would put them in different physical locations say ~10km apart for site redundancy.