How to fix Microsoft Failover Cluster Manager on Windows server 2012/2016 Part 2

Step 2: Connecting to iSCI network drives

  1. Start the iSCI leader then hook up with your 2 SAN drives:

  2. Click begin > Windows body Tools > iSCI leader.

    One of the drives is designed for your gathering and therefore the alternative is designed for the virtual machines. 5GB is needed for the gathering and therefore the second drive are going to be accustomed store your Virtual machines. Therefore, make sure you have provided enough disc space on this drive to handle the virtual machine storage.

  3. Ensure the drives area unit set to permit cooccurring connections. this is often designed on your SAN. check that you have got granted access to your 2 cluster servers.
  • Connect to the SAN drives:
  • Open iSCSI leader.

Click the Targets tab.

  • In Target, enter the information processing address for the SAN.
  • Click fast Connect.
  • Your publicized drives area unit displayed.
  • Highlight a drive; then click hook up with hook up with every drive.
  • When a drive is connected, click done.

Click the Volumes and Devices tab.

  • Click car piece.
  • Click OK.
  • When you area unit connected on the primary machine, click begin > Windows body tools > pc Management > Disk Management.
  • Your 2 disks seem as Unknown and Offline. They additionally show the dimensions you designed on the SAN (eg: 5GB and 150GB).
  1. Bring the disks online:

  2. Right-click the disk range.
  3. Select on-line.
  • Repeat the higher than step for the second drive.
  • Initialize the disks:
  • Right-click the disk range next to 1 of the new drives.
  • Select Initialize disk.
  • In the box that seems, make sure that each your new disks have a tick mark next to them.
  • Set as MBR.
  • Click OK.
  • Configure the new drive:

Right-click the primary drive.

  • Select produce New straightforward Volume.
  • Leave the defaults in situ.
  • Choose a drive letter to assign.
  • Label your drives:
    5GB drive—label the drive as gathering
    150GB (larger drive)—label it as ClusterStorage

Repeat the higher than steps for the second drive.

  1. Once this is often in deep trouble your initial node (Server), repeat these steps on your extra nodes (Servers). for instance, from the 2 listed servers higher than (Server1 and Server2), you need to connect the iSCSI drives on each systems before they’re going to be offered for your cluster.

    As the straightforward volume is currently designed, you merely have to be compelled to initialize the disks on the opposite Nodes, not recreate the amount.

Step 3: produce the failover cluster:

From the OS of any of the nodes:

Click begin > Windows body tools > Failover Cluster Manager to launch the Failover Cluster Manager.

Click produce Cluster.

The Before you start window is displayed.

Click Next.

The choose Servers window is displayed.

  1. Enter the server names that you just need to feature to the cluster. or else, you’ll be able to find them via Browse.
  2. Click Add.
  • Click Next.

The Validation Warning window is displayed.

  1. Select affirmative to permit verification of the cluster services.
  2. Click Next.

    The Validate a Configuration Wizard is displayed. This wizard validates the server configuration.

Click Next.

The Testing choices window is displayed.

  1. Select Run all tests (recommended).
  2. Click Next.

    The Confirmation window is displayed. This window lists all of the tests which will be run.

Click Next.

The substantiate window is displayed whereas all of the cluster tests area unit being run. This method could take many minutes reckoning on your network infrastructure and therefore the range of nodes you have got chosen to feature to your cluster.

When the tests have completed, check the report then fix any configuration errors. The cluster setup can fail if any errors exist.

A common error is that the NIC/s used on the 2 nodes. The NIC/s should have constant name on each server for the cluster to use the NIC within the configuration.

The Access purpose for administering the Cluster window within the produce Cluster wizard is displayed.

  2. In Cluster Name, enter a reputation for your cluster.

  3. In the offered network give associate degree information processing address for the cluster.

    This name and information processing address are going to be registered in your DNS

Click Next.

The Confirmation window is displayed. This window lists the settings to be applied to your new cluster.

  1. Select the Add all eligible storage to the cluster check box.
    The system can currently try and assign any storage it will notice.

  2. Click Next.

    The system tries to form the new cluster in your domain. This could take {a whereas short time a minute a momenta jiffy short while} as there are a unit many checks that has got to surface and tests that area unit conducted while the system is designed.

When the method is complete, the outline window is displayed stating that the cluster wizard completed with success.

  1. Click finish.

  2. Check to substantiate that the cluster is designed correctly:

In the Failover Cluster Manager, navigate to Nodes.

  • Check that all nodes within the cluster area unit on-line. If they’re not, head to the server that’s offline and produce the system on-line to affix the cluster.

Navigate to Storage > Disks.

  1. The system detects the interface drives and displays them here. If you were setting this up with solely 2 nodes, then the 5GB gathering cluster would are assigned as Disk Witness in gathering.

    If no disks area unit displayed, confirm you have got properly completed the steps on all nodes careful in Connecting to ISCSI network drives.

    The designed space for storing is assigned to offered Storage.

  2. Configure this storage to be a part of the cluster:

Right-click the disk assigned to offered storage; then choose boost Cluster Shared Volumes.

The cluster is currently assigned to Cluster Shared Volume.

Check the Cluster Events folder for any reportable problems with the cluster. If there aren’t any problems, you’ll be able to piece your virtual machine within the cluster setting.

2 Comments on “How to fix Microsoft Failover Cluster Manager on Windows server 2012/2016 Part 2”

Leave a Reply

Your email address will not be published. Required fields are marked *

Enter Captcha Here :