Start a Conversation

Unsolved

This post is more than 5 years old

753

March 21st, 2013 13:00

VSphere 5.1 on CX3- 40c

The CX3-40c is not on the vSphere 5.1 HCL.

We are replacing this and want to determine if the SAN will be a viable option for disaster recovery.

Will it work?

1 Rookie

 • 

20.4K Posts

March 21st, 2013 13:00

define "disaster recover", what do you want to do with this CX3 ?

33 Posts

March 21st, 2013 16:00

we are currently using the cx3 -40c in the live environment. It will be

replaced in the next six months and we are contemplating using it for for

storage in the case of a total lose of the primary data center. We have

determined that the key systems can be placed onto 9 DL380 G6 and

G7 hosts that will be virtualised onto blades.

If we have a cold site with a CX3-40 c and 9 hosts running vSphere we will

be able to restore to the storage and fire up our VMs ?

But because the CX3-40c is not on the HCL for vsphere 5.1 that will be

running in the live estate I am wondering if it will work. It is not a

permanent solution and will only be required in a Disaster recovery or

business continuity scenario

1 Rookie

 • 

20.4K Posts

March 21st, 2013 17:00

are you going to backup and restore your VMs at DR site ? I am not sure if vSphere 5.1 would work with CX3 because there are many key features that were introduced in CX4/VNX (SPC2, VAAI offload). I guess it would be easy to test, stand up a test vSphere 5.1 cluster and see how it works. The problem with aging hardware like that is that you will not be able to get any help from VMware (not on HCL) and will be hard to get help from EMC because it will be EOSL March 31, 2014.

467 Posts

March 21st, 2013 21:00

It will work,  just need to do something on the esx host side... ran into the problem at my dr site the other month.. I can't recall what we had to do,  i'll try to dig up my notes at the office tomorrow..

1 Message

September 5th, 2013 18:00

Hi. Did you get this working. We're investigating doing the same thing. Did you find out what changes were required on the ESXi host side?

No Events found!

Top