Gpt disk not validating in failover cluster dating agent pro

Notice: All of the screenshots and procedures in this post are from 2012 R2.

There is no guarantee that problems resulting from the incorrect use of Registry Editor can be solved. Before you make changes to a registry key or subkey, we recommend that you export, or make a backup copy, of the key or subkey.

You have the option of using the Disk Management MMC console, but this is the 2012 era, and Server Manager is the current tool.

Server Manager can’t control CD/DVD drives or MPIO policies (unless I missed something) but it can do everything else.

This document describes the procedure for re-configuring a Microsoft Windows 2012 R2 cluster environment (that is, either Windows Cluster Service or a Windows Fail-over Cluster) after a Plate Spin Forge or Plate Spin Protect failover/failback occurs.(Conditional) – if the former shared storage drives (that is, the old cluster disks) are online.

In the Windows Disk Manager, change the drive letters of the old cluster disks to some other drive letter to prepare for assigning the original drive letters to the re-attached shared storage can add the disks by using the DISKPART utility to retrieve the Disk ID for each shared disk you add, and you can use the cluster resource command to add the disks, to assign an ID, and to bring the disks online: From a Windows command line, start the DISKPART utility and run the List Disk and Select Disk commands to select a newly attached shared disk, then run the Detail Disk command to retrieve the Disk ID for that disk. From the Windows Power Shell command prompt, run the cluster resource command with the proper option to assign a Disk ID (retrieved and recorded in Step 8.3.1) to each disk created in Step 8.3.3.

Leave a Reply