It basically seems like I need a "should remain separate" rule, but that doesn't exist. I can manually migrate it to Server 3 after that, but that defeats the point. Instead, the VM seems to randomly end up on the server included in the relevant "should not" rule, violating it. The thought was that this would put them on Servers 1 and 2 under normal operation, but upon losing one of those servers, push that VM to Server 3. I tried setting two sets of "should" rules, saying VM A *should* run on Server 1 and *should not* run on Server 2, and VM B *should* run on Server 2 and *should not* run on Server 1. Setting a "keep these VMs separate" rule means it cannot be violated if we end up with just one server left in the cluster-the 2nd VM will not migrate or start there. I cannot seem to configure DRS rules to achieve this, no matter what permutation I try. If this pod is in another physical location, create a new site. Enter the FQDN of a Connection Server from the first pod, along with credentials. Choose the option to join the pod federation. I'd like them to always remain separate unless 2 servers in the cluster fail, in which case they should both run on the single remaining server. Connect to the Horizon Administrator console on one of the Connection Servers in the that pod (Site 2). I have a 3-server cluster, with 2 VMs that have their own application-level failover capabilities.
0 kommentar(er)
