An architect is designing a new vSphere solution. The solution will be used to host workloads that have multiple dependencies. The customer provides the following information regarding the workloads:
Workload 1: Self-Service Portal
Workload 2: Database
Workload 3: Identity Broker
Workload 4: Reporting Tool
Workload 5: Management Tool
Application A is formed of workloads 1 and 2 and has a dependency on workload 3
Application B is formed of workloads 2 and 4 and has a dependency on workload 3
Application C is formed of workload 5 and has a dependency on workload 4
How should the architect document the vSphere HA requirements to ensure that all of the applications can be recovered in the event of a host failure while observing the dependencies?
The goal here is to ensure that, in the event of a host failure, the workloads are restarted in the correct order based on their dependencies:
Workload 3 (Identity Broker) is required by both Application A and Application B as a dependency. It needs to be set to High Restart Priority, ensuring that it is restarted before the other dependent workloads.
Workload 4 (Reporting Tool) is required by Application B and Application C, so it should be set to High Restart Priority to ensure it is available before the other dependent workloads (like Workload 5).
Workload 5 (Management Tool) is required by Application C and should have a Medium Restart Priority, meaning it will be restarted after Workload 4.
Workloads 1 and 2 (Self-Service Portal and Database) have Low Restart Priority because they are dependent on Workload 3 (and Workload 4), but they do not have further critical dependencies after Workload 3, so they should be restarted last in the event of a failure.
This setup ensures that all applications can be recovered properly in the event of a host failure, with each workload restarting in the correct order to maintain the application dependencies.
Graham
7 days agoCandida
10 days agoKaitlyn
12 days ago