Hello. I hope I'm posting this in the correct spot, I wanted to see if someone could check this and make sure that I've got the right hardware and licenses, and that I'm not over provisioning the licenses, as well as answer a couple of questions. I'm looking into setting up a 2 node vSAN. There will be a total of three sites. Two of which will be in the same city, the third will be farther away (250ish miles). My plan is to have one host in each of the two sites in the same city, and then put the witness vm in the third site. For the licensing I'm thinking of Vmware HCI Kit Essentials. If I understand it correctly that should get me everything I need for what I'm wanting to do. I'll put the hardware below that I'm thinking of using, as well as link speeds between sites. In addition to this I would like to have a third host setup for disaster recovery in the same site as the witness vm, I'll put the info for that below as well.
Hardware -
Site A and B (Main sites in same city):
Dell PowerEdge R540 (all storage is internal) -
Cache - 2x 1.92 TB SATA SSD's in RAID 1 (configured on PERC H750P). 1.92 TB RAW, 1.78 TB approximate usable capacity.
Data - 10x 2.4 TB 10k SAS HDD's in RAID 6 (configured on PERC H750P). 19.2 TB RAW, 17.4 TB Usable capacity.
Site C (Witness and DR site in separate city):
Dell PowerEdge R540 (all storage is internal) -
Data - 10x 2.4 TB 10k SAS drives in RAID 6 (configured on PERC H750P). 19.2 TB RAW, 17.4 TB Usable capacity.
Witness VM will be setup on this host, and I plan to use this host for DR, so I would like to replicate VM's to it. The RPO I'm shooting for is around 6 hours, but I can go up to 12 if the requirements get to crazy.
Link Speeds -
Link between site A and site B - Layer 2 link provided by ISP at 500 Mbps (would like to lower this though if possible for cost concerns)
Link between site A and site C - Layer 2 link provided by ISP at 100 Mbps
Link between site B and site C - Layer 2 link provided by ISP at 50 Mbps. This link is here because, as I understand it, at least one host in a 2-node setup has to have connectivity to the witness for it to work. So if site A goes down, then site B will be able to continue to handle the workloads as long as it has connectivity to the witness.
Licenses -
This was mentioned above, but I figure I'll put it here as well just in case. Vmware HCI Essentials kit.
Questions -
My questions, summed up, are this.
1. Will the hardware I specified work for a vSAN setup? The goal is that if site A loses power or internet, site B, and the rest of the remote sites, can continue working from site B.
2. Are the link speeds I mentioned good enough, can they be toned down somewhat? I know the 100 Mbps is overkill for only witness traffic, but I plan to use that link for DR replication traffic as well.
3. There is around 12 TB between all the servers at site A that we would be consolidating into this infrastructure as part of this setup. The initial sync for the vSAN, and the replication for the DR host, I imagine will take quite a while. Is it recommended to transfer all this data to the empty host, or should it be seeded? If seeding is recommended, what is the recommended method for this?
4. Is the link between site B and C necessary?
5. Will I be able to do disaster recovery replication using VMWare's built in replication functionality, using the specified hardware and license package?
6. Will the specified license package allow me to use the vSAN like I've mentioned?
7. If a fail over to the DR site is ever necessary, what would the failback procedure be? If someone has a link to a guide or article I would greatly appreciate it.
If I can provide anymore info just let me know.