VMware Cloud Community
BHagenSPI
Enthusiast
Enthusiast
Jump to solution

Multiple vsan datastores in a single datacenter?

I currently have 7 esxi 6.0u3 hosts (HCI) running vsan 6.2 in a vspehre 6.7 (with external PSCs) datacenter cluster.

I have built 6 new hosts with esxi 6.7, and plan to migrate all our VMs from the 6.0U3 stack to the 6.7 stack.

Is it possible to add the 6 new hosts to a new cluster under the same datacenter as the 6.0u3 cluster, and create a vsan 6.6.1 datastore in the new cluster?

It would roughly look like this:

DatacenterA

--ClusterA(6.0U3)

----VsanDatastoreA(6.2)

--ClusterB(6.7)

----VsanDatastoreB(6.6.1)

The goal would be to vmotion the VMs from VsanDatastoreA to VsanDatastoreB.

Possible?

Thanks!

0 Kudos
1 Solution

Accepted Solutions
TheBobkin
Champion
Champion
Jump to solution

Hello BHagenSPI​,

Yes of course you can do this (or have them in their own DCs under the same vCenter).

DO consider renaming the vsanDatastores from each cluster though:

https://www.virtuallyghetto.com/2014/02/why-you-should-rename-default-vsan.html

Bob

View solution in original post

0 Kudos
3 Replies
TheBobkin
Champion
Champion
Jump to solution

Hello BHagenSPI​,

Yes of course you can do this (or have them in their own DCs under the same vCenter).

DO consider renaming the vsanDatastores from each cluster though:

https://www.virtuallyghetto.com/2014/02/why-you-should-rename-default-vsan.html

Bob

0 Kudos
IRIX201110141
Champion
Champion
Jump to solution

We running 6.5 and have the exact setup running which are you asking for. Two Cluster with each have one vSAN within one Datacenter.

Renaming the vSAN Datastore is one thing... take a look to the Storage Profiles as well because IIRC there are two vSAN Default Profiles with the same name also.

Regards,
Joerg

BHagenSPI
Enthusiast
Enthusiast
Jump to solution

Thanks! Yes, that was easy...leave it to me to try and make it complicated. 🙂

And yes...I always name my datastores; both my vsan and each local drive. Much easier to sort and understand that way.

I also create new storage policies with appropriate names and add those policies to new vmdk's. Makes it easy to know when somebody's created a new VM; I just check the default policy every once in a while and see if there are any vmdk's attached. 🙂

0 Kudos