HPE SimpliVity
1828586 Members
2615 Online
109982 Solutions
New Discussion

Re: Stretched Cluster Where Data Stored Question

 
alg204
Advisor

Stretched Cluster Where Data Stored Question

Hello, 

we have a new stretched cluster with 4 nodes. 2 nodes are at 1 site and 2 nodes are at another. Each site is an availability zone. So: zone 1, site 1, 2 nodes and zone 2, site 2, 2 nodes. 

When looking at HPE SimpliVity Federation > Virtual Machine Replica Details: should that match the zones or is that page even meant for showing where a VM is in terms of zones? 

Here is what I see in Virtual Machine replica Details right now

Here are where the VMs are up and running currently:

VM1: SIte 2 Node 2
VM2: Site 2 Node 1
VM3: Site 2 Node 1
VM4: Site 2 Node 1
VM5: Site 2 Node 2

So, it doesn't seem the replica details page quite matches where the VMs actually are? My concern is with VM4 - both primary and secondary replicas are on site 1 instead of one being site 1 and the other being site 2. 

Overall, I guess I'm just trying to understand what the replica details page is used for, is it updated real time - if not how can I update/refresh, and can I use the page as a means to determine if a VM has a copy in both sites so that if vSphere HA kicks in due to a node being taken down it will spin up on other site....

2 REPLIES 2
gustenar
HPE Pro

Re: Stretched Cluster Where Data Stored Question

Hello @alg204,

 

This page is not design for the zoning in specific. It gives you details of where the VM replicas are living within the federation as you know. With zoning implemented there should be a replica of the VM on each availability zone, so it can provide failover. 



I work at HPE
HPE Support Center offers support for your HPE services and products when and how you need it. Get started with HPE Support Center today.
[Any personal opinions expressed are mine, and not official statements on behalf of Hewlett Packard Enterprise]
Accept or Kudo
alg204
Advisor

Re: Stretched Cluster Where Data Stored Question

This thread can be closed. We noticed the zone names when running svt-federation-show were appearing as "(none) => name" so we thought maybe the svt-zone-realize didn't take when engineer ran. We ran svt-zone-realize and looks like everything is now running as expected. No vms are on the same zone anymore for replicas.