Hello all,
We wanted to add an additional blade server to our current cluster configuration, but adding a new blade to this existing configuration seems to cause issues detecting the shared storage.
Our current configuration consists of the following (the new blade not included)
- PowerEdge VRTX
- 2 x M520 blade servers with Windows Server 2012R2 (with Hyper V) installed
- Shared Storage configured with multiple assignment set up
- Shared Storage contains a virtual disk of 1GB (quorum) and 12TB (main data)
- Dual Shared PERC8
On the blade servers the following has been installed:
- Hyper V
- Failover Clustering Manager
- MPIO
Our Failover Cluster configuration contains and manages both virtual disks. Several virtual machines have been hosted on the 12TB disk and this works all OK.
Now I would like to add a third M520 blade server and add it to the cluster configuration. However, what happens now is: when I want to assign the shared storage to the new blade, the storage is detected as local storage (direct attached storage) in an Online state. This pretty much freezes the Virtual Disk Management service and I am unable to do anything. (because the storage is in use by the cluster itself)
At the same time the cluster storage (on the existing Hyper V servers) slows down completely as the new blade server tries to discover and scan the newly discovered storage.
Is there anyway or best practice what to do in order to correctly mount the storage in an existing cluster on this VRTX configuration? Preferrably I would like to discover the new disks in an Offline state.
I hope there are some good ideas on this, maybe I just missed something crucial.