Host Pool Disaster Recovery
This feature is only available in the Nerdio Manager Premium edition.
The disaster recovery feature in Nerdio Manager automatically distributes newly created VMs between a primary and secondary Azure region. When the users connect, they are evenly split between the two regions. In case of an outage in one of the regions, users are automatically connected to the remaining region.
The networking in both regions must be configured to communicate with the Active Directory domain controllers (or for the future Entra ID). Currently, in production scenarios, you need line of sight to the Active Directory domain controllers from networks in both locations.
The active-active DR setup is configured on the host pool level. It distributes the VMs, takes care of the FSLogix configuration, and replication of the profiles. The FSLogix profiles are replicated between storage locations in both regions, leveraging the FSLogix Cloud Cache feature.
Prerequisites: A network with line of sight visibility for domain controllers in both regions and an Azure files storage location for the FSLogix local profile copies.
Note: To enable DR on this host pool, the selected FSLogix profile must use Cloud Cache. Create a new profile, or modify an existing one, with Cloud Cache enabled and select it on the FSLogix properties page.
Both primary and secondary FSLogix storage locations are configured on every new session host with Cloud Cache replication. VMs in the primary Azure region are configured with FSLogix storage in that region as primary and VMs in the secondary Azure region are configured with FSLogix storage in that region as primary.
If there are existing hosts in the host pool, delete and recreate them after enabling DR.
To configure host pool disaster recovery:
- Locate the host pool you wish to work with.
From the action menu, select Properties > Disaster Recovery.
Enter the following information:
Enable Disaster Recovery: Toggle this option on.
Secondary VM Prefix: Type the prefix to be used when creating session hosts in the secondary Azure region.
Note: The Name prefix limit is 10 valid, Windows computer name characters. When using a prefix, the system automatically appends “-xxxx” to the name prefix to make a unique name. Do not add “-“ to your name prefix.
Secondary Network: From the drop-down list, select a secondary network that 50% of the newly created VMs are connected to. The selected network also determines the Azure region of the VM.
Secondary Resource Group: From the drop-down list, select the resource group that contains the VMs in the secondary region.
Desktop Image (Template): From the drop-down list, select the desktop image that is used for newly created VMs in the primary and secondary regions.
Note: The image must be stored in the Azure Compute Gallery and replicated to both regions.
Secondary FSLogix Storage: From the drop-down list, select the FSLogix storage location in the secondary region.
Secondary FSLogix Office Container: From the drop-down list, select the FSLogix office container location in the secondary region.
Once you have entered all the desired information, select Save or Save & close.
You now need to review the host pool's auto-scale configuration.
Locate the host pool.
From the action menu, select Auto-scale > Configure.
Make sure that the Desktop Image (Template) is the same that was configured in disaster recovery.
In the Host Pool Sizing section, enter the Base host pool capacity.
Select Save & close.