VPLEX

/VPLEX
VPLEX 2017-05-19T00:20:14+00:00

VPLEX Metro is a storage virtualization appliance, it implements a distributed “virtualization” layer with and across geographically data centers ”the LUN is presented to the VPLEX and VPLEX will present it to the Server”; VPLEX Metro delivers availability and data mobility platform that enables mission-critical applications to remain up and running during a variety of planned and unplanned downtime scenarios

The VPLEX platform should be used at sites where 99.999% uptime is required. The major solutions that the VPLEX provides are avoid/reduce/eliminate cluster downtime, migration with near zero downtime and reduce latency for geo-clusters.

Additionally, VPLEX works with any kind of block storage on the backend “storage agnostic”. This will give the client the flexibility to choose any kind of storage backend in the future and not being locked onto products from a specific vendor; it also solves the problem of stretching clusters between local and remote sites.

The key to the use of VPLEX is data replication between SAN volumes whereby the data is mirrored on different storage arrays and can be accessed at any time from any of the arrays. This allows for seamless disk access across arrays from an application throughout maintenance or disaster scenarios.

To access the service, a user should create a stretched LUN “distributed device” then add it to a virtual volume group in VPLEX. This group will host all the LUNs that the service will use. The LUNs will be mirrored through specific policy with the other VPLEX on the secondary site.

In an event where the primary site goes down the second VPLEX will pick up the LUNS and keep presenting the LUNs to the stretched cluster. Except for the time required for the internal VPLEX process, failover is transparent to the services accessing the data.

All data communication between the two VPLEX takes place on the back-end.

Data Protection and Failover

At a minimum VPLEX will mirror the LUNs from the primary LUN to the secondary LUN with no latency. In case of a hardware failure or power failure VPLEX will failover the primary LUN to the secondary LUN with no downtime. This is implemented on the VPLEX layer. The user can still create different protection layers or add DR policy to this technology

VPLEX Metro Benefits

  • Seamless failover without service interruption.
  • Seamless migration without service interruption.
  • Can create one cluster in two different geographical sites and fail over without service interruption.

Note: VPLEX is an In-line device, performance is not the goal of VPLEX; Mobility, High Availablity and Data Migration is the goal.

Related Recent Articles

Matching back-end array LUN ID to VPLEX UIDS

December 5th, 2014|0 Comments

Changing VPLEX Local Group to Distributed Group

December 4th, 2014|0 Comments

Presenting new Stretched Cluster LUN in VPLEX to a server

December 3rd, 2014|0 Comments

Registering server initiators in VPLEX

November 29th, 2014|0 Comments

About me

I have more than 15 years hands-on experience in the IT field. The majority of my work is in networking, operating systems and applications and storage. I carry industry certifications in Redhat, Microsoft, EMC, VMWare, VCE and ITIL.

I find it hard to find procedures or documents on how to implement specific technology and this is how the decision to create a place to share my knowledge and ideas for anyone interested in the same subject.

If you have the same vision and you are interested to publish on this website please contact me and I will create an account for you.

Certifications:
RHCSA

Certifications:
MCSE Security
MCSA Massaging

Certifications:
EMCIE- Isilon
EMCTA- Isilon
EMCIE- VNX

Certifications:
VCP-DCV

Certifications:
VCE-CIA

Certifications:
TITL

This site is targeting Solution Architects, Implementation Engineers and Systems Administrators. It is not targeting sales or intending to promote any specific technology or vendor.

The focus is on hands-on work, technical documentations and architecting solutions.

The site reflects my knowledge and opinions, I do recommend that you test what you learn in the lab environment before implementing it in production.

If you have a doubt call technical support, I do not assume any liability for any errors or omissions in those articles, I also make no representations as to the accuracy or completeness of any information on this site or found by following any link on this site

Content published here is tested in my own lab and is not reviewed or approved by any vendor.

If you have any issues with your system I highly recommend you contact the technical support of the vendor.

Disclaimer

Knowledge Ascent (KA) makes information available on its web site to enhance public knowledge and promote a better understanding of the IT environment. KA attempts to provide accurate, complete, and timely information. KA, however, cannot guarantee the quality, content, accuracy, or completeness of the information, text, graphics, links, and other items contained on its web pages because the material comes from a variety of sources, collected and maintained for different purposes. KA also retains the right to change any content on its web site without prior notice.

Information provided on the KA web site should not be used as a substitute for IT or other professional advice. KA assumes no liability for any damages or loss of any kind that might arise from the use of, misuse of, or the inability to use the KA web site and/or the materials contained on the web site. KA also assumes no liability for improper or incorrect use of materials or information contained on its web site. All materials that appear on the KA web site are distributed and transmitted "as is," without warranties of any kind, either express or implied, and subject to the terms and conditions stated in this disclaimer.

Contact Me
FAQ