Question

discuss Configuring Roles for High Availability. Include the cluster aware roles in Windows Server and configuring Continuously Available Shares and Scale-out File Server (SoFS).

list two reference

Answer 1

Configuring Roles for High Availability : Earlier it was possible to add redundancy to most of the roles in Configuration Manager by having multiple instances of these roles in the environment. In version 1806 of the Configuration Manager, the Configuration Manager-based solution was highly available for the site server role to install an additional site server in passive mode. Hierarchy support was added in version 1810, so central administration sites and child primary sites can also have an additional site server in passive mode.

The site server in passive mode can be in following two ways in Azure:

1. On-premises
2. Cloud-based.

A site server in passive mode is the replica of the site server in active mode. It will use the same site database as the site server in active mode. Data will not be written to the site database when it's in passive mode. And it will use the same content library as the site server in active mode.

We need to promote the passive site manually in order to make it active.

Cluster Aware roles in Windows Server: The Cluster-Aware Updating provides multiple functionalities. It provides a UI, the Cluster Aware Updating window and a set of cmdlets that could be used to preview, apply, monitor, and report on the updates. It also provides an end-to-end automation of the cluster-updating operation ,monitored by one or more Update Coordinator machines. It provides a plug, that can be used to apply Microsoft hot-fixes, and that can be customized to apply non-Microsoft updates.

Continuously Available File Shares: The step by step procedure of configuring Continuously Available Shares and Scale-out File Server (SoFS) is as follows:

• Select Fail-over Cluster Manager, in Server Manager, under Tools
• Right-Click Fail-over Cluster Manager and select Create Cluster
• In the Before You Begin, click Next
• In the Select Servers screen enter serverOne, and serverTwo (you can name accordingly) and click Add, and then Next.
• In the Validation Warning screen select No if you are running out of time.
• Provide a Cluster name and IP addresses you want the cluster to have. and click Next
• Click Next to confirm on the next screen and let it complete. then click Finish
• Once the cluster setup is completed. navigate to Failover Cluster Manager, FS-Cluster.contoso.com, Storage, Disks. and select both Cluster Disk 2 and 3, right-click them and select "Add to cluster shared volume”
• Next we will define a cluster role. Navigate to Failover Cluster Manager, FS-Cluster.contoso.com, Right –click Roles and select Configure Roles. Click Next in the “before you Begin” screen and in the Select Role screen select “File Server”.
• Select “Scale-Out File Server for Application data” in the file server type, click Next and give it a name (SMB-FS1 in our case) in the Client Access Point Screen. click Next twice wait for it to complete and click Finish.
• The Final step is to actually create a file share on the cluster.
• Navigate to Failover Cluster Manager, FS-Cluster.contoso.com, Roles. Select the SMB-FS1 Scale-Out File Server (SOFS) and click “Add File Share” in the Action pane.
• Select “SMB Share – Applications”, click Next

• Select the appropriate volume to create your share on, click Next, Give it a name, click Next Three time and Create to complete the wizard.

Thanks!