6th : Next we going to add a shared folder to a highly available File Server…
1 – Switch to SVR4 server and open Failover Cluster Manager…
** Expand Cluster1.Adatum.com, and then click Roles.
** Right-click OSI-FS, and then select Add File Share…
2 – In the Select the profile for this share interface, click SMB Share – Quick, and then click Next…
3 – On the Select the server and the path for this share interface, verify the server & Volume to share and then click Next…
4 – On the Specify share name interface, in the Share name box, type OSI-Docs, and then click Next…
5 – On the Configure share settings interface, do not make any changes, and then click Next…
6 – On the Specify permissions to control access interface, click Next…
7 – On the Confirm selections interface, click Create…
8 – On the View results interface, click Close…
9 – Next we need to configure failover and failback settings, on the Failover Cluster Manager, click Roles, right-click OSI-FS, and then click Properties…
“** Failover transfers the responsibility of providing access to resources in a cluster from one node to another. Failover can occur when an administrator intentionally moves resources to another node for maintenance, or when unplanned downtime of one node happens because of hardware failure or other reasons. In addition, service failure on an active node can initiate failover to another node.”
“** The Cluster service can failback instances that were originally hosted on the offline node after the offline node becomes active again. When the Cluster service fails back an instance, it follows the same procedures that it performs during failover. That is, the Cluster service takes all the resources in the instance offline, moves the instance, and then brings all the resources in the instance back online.”
10 – Click the Failover tab and then click Allow failback…
** Click Failback between, and set values to 3 and 4 hours.
11 – Next, click the General tab, then select SVR3 and SVR4 as preferred owners and make sure you move SVR4 up, then click OK…
7th : Now we have to validate / verify the Deployment of our High Availability File Server
1 – Switch to DC01 server (Domain Server), try access to \\osi-fs\osi-docs…
** Verify that you can access the location and that you can open the osi-docs folder…
2 – To verify you can create a any text document inside this folder…
3 – Next, switch back to SVR3 server and open the Failover Cluster Manager.
** Expand Cluster1.adatum.com, and then click Roles. Note the current owner of OSI-FS (SVR3)
** Right-click OSI-FS, click Move, and then click Select Node…
4 – In the Move Clustered Role box, select the cluster node (it will be either SVR3 or SVR4), and then click OK…
5 – Verify that SVR4 has moved to a new owner…
** I do recommend that you switch back to DC1 server and verify that you can still access the \\osi-fs\osi-docs…
6 – Next, in the Failover Cluster Manager, right-click the node (I choose SVR4) , select More Actions, and then click Stop Cluster Service…
7 – Verify that SVR4 now is down…
8 – Verify also OSI-FS has moved to another node which is SVR3…
** ** I do recommend that you switch back to DC1 server again and verify that you can still access the \\osi-fs\osi-docs…
9 – switch back to SVR3 server and on the Failover Cluster Manager, click Nodes. Right-click the stopped node which the SVR4, select More Actions, and then click Start Cluster Service…
10 – Verify all nodes status now up…
11 – Next, expand Storage, and then click Disks.
In the center pane, right-click the disk that is assigned to Disk Witness in Quorum then click Take Offline…
“** Quorum is the number of elements that must be online for a cluster to continue running. In effect, each element can cast one vote to determine whether the cluster continues to run. Each cluster node is an element that has one vote. In case there is an even number of nodes, then an additional element, which is known as a witness, is
assigned to the cluster. The witness element can be either a disk or a file share. Each voting element contains a copy of the cluster configuration; and the Cluster service works to keep all copies synchronized at all times.”
12 – then click Yes…
13 – Switch to DC1 server and verify that you can still access the \\osi-fs\osi-docs location. By doing this, you
verified that the cluster is still running, even if the witness disk is offline…
14 – Now switch back to SVr3 server, in Failover Cluster Manager, expand Storage, click Disks, right-click the disk that is in Offline status, and then click Bring Online…
15 – Next, right-click Cluster1.Adatum.com, select More Actions, and then click Configure Cluster Quorum Settings…
16 – click Next…
17 – On the Select Quorum Configuration Option interface, click Advanced quorum configuration, and then click Next…
18 – On the Select Voting Configuration interface,Do not make any changes, and then click Next…
19 – On the Select Quorum Witness interface, select Configure a disk witness and then click Next…
20 – On the Configure Storage Witness interface, select Cluster Disk 3, and then click Next…
21 – click Next…
22 – click Finish…
** we have succesfully tested the failover scenarios and next we going to configure CAU
8th : Configure CAU – Cluster-Aware Updating
** Cluster-Aware Updating (CAU) is a technology in Windows Server 2012 that automatically updates cluster nodes with Windows Update hotfix, by keeping the cluster online, and minimizing downtime.
** During an update procedure, CAU transparently takes each cluster node offline, installs the updates and any dependent updates, and then performs a restart if necessary. CAU then brings the node back online, and moves to update the next node in a cluster.
1 – Before we proceed, please make sure that you have install Failover Clustering feature in DC1 Domain Server…
2 – Switch back to SVR3 & SVR4 server, and please verify also that Inbound Rule for Remote Shutdown (RPC-EP-In) & Inbound Rule for Remote Shutdown (TCP-In) rule is enabled…
3 – let’s return to DC1 domain server and open Cluster-Aware Updating console…
4 – In the Cluster-Aware Updating interface, in the Connect to a failover cluster drop-down list box, select OSICLUSTER1, and then click Connect…
5 – In the Cluster Actions pane, click Preview updates for this cluster…
6 – In the OSICluster1-Preview Updates interface, click Generate Update Preview List…
7 – After few minutes, updates will display in the list and then click Close…
8 – still on the DC1 server, now we need to update the failover cluster and configure the self-updating…
** in the Cluster-Aware Updating console, click Apply updates to this cluster…
9 – On the Getting Started interface, click Next…
10 – On the Advanced options interface, review the options for updating, and then click Next…
11 – On the Additional Update Options interface, click Next…
12 – On the Confirmation interface, click Update, and then click Close…
13 – In the Cluster nodes pane, you can review the progress of the updating process…
** Please take note that 1 node of the cluster is in a waiting state, and the other node is restarting after it is updated.
** Wait until the process is finished and both nodes will restarted automatically.
14 – The process is finished when both nodes show Succeeded…
15 – Once the SVR3 restarted, log in as administrator and open Cluster-Aware Updating…
** In the Cluster-Aware Updating box, in the Connect to a failover cluster drop-down list box, select OSICLUSTER1. Click Connect….
16 – Click the Configure cluster self-updating options in the Cluster Actions pane…
17 – On the Getting Started interface, click Next…
18 – On the Add CAU Clustered Role with Self-Updating Enabled interface, click Add the CAU clustered role, with self-updating mode enabled, to this cluster, and then click Next…
19 – On the Specify self-updating schedule page,configure your own schedule and then click Next…
20 – On the Advanced Options interface, click Next…
21 – On the Additional Update Options interface, click Next….
22 – On the Confirmation interface, click Apply…
23 – After the clustered role is added successfully, click Close and we have successfully configured CAU.
Không có nhận xét nào:
Đăng nhận xét