Creating 16 Tb Or Greater Virtual Disks In Windows 2008; Importing Windows Dynamic Disk Volumes; Losing A Path To A Dynamic Disk; Microsoft Windows 2003 Mscs Cluster Installation - HP 6400/8400 User Manual

Creating 16 TB or greater virtual disks in Windows 2008

When creating a virtual disk that is 16 TB or greater in Windows 2008, ensure that the Allocation
unit size field is set to something other than Default in the Windows New Simple Volume wizard.
The recommended setting is 16K. If this field is set to Default, you will receive the following error
message:
The format operation did not complete because the cluster count is
higher than expected.

Importing Windows dynamic disk volumes

If you create a snapshot, snapclone, or mirrorclone with a Windows 2003 RAID-spanned dynamic
volume on the source virtual disk, and then try to import the copy to a Windows 2003 x64 (64-bit)
system, it will import with Dynamic Foreign status. The following message displays in the DiskPart
utility:
The disk management services could not complete the operation.
This error occurs because the 64-bit version of DiskPart fails to import dynamic RAID sets on a new
server.
To avoid this issue, use the 32-bit version of DiskPart instead of the 64-bit version. Copy DiskPart
from a 32-bit x86 Windows system, located in C:\WINDOWS\system32. Place the DiskPart utility
in a temporary folder on the 64-bit x64 Windows system.

Losing a path to a dynamic disk

If you are using Windows 2003 with dynamic disks and a path to the EVA virtual disk is temporarily
lost, the Logical Disk Manager (LDM) will erroneously show a failed dynamic volume. For more
information, see the following issue on the Microsoft knowledge base website:
http://support.microsoft.com/kb/816307
To resolve the issue, reboot the Windows 2003 server to restore the dynamic volume.

Microsoft Windows 2003 MSCS cluster installation

The MSCS cluster installation wizard on Windows 2003 can fail to find the shared quorum device
and disk resources might not be auto-created by the cluster setup wizard. This is a known Windows
Cluster Setup issue that has existed since Windows 2003 was released.
There are two possible workarounds for this problem:
Follow the workaround recommendation described in the Microsoft support article entitled
Shared disks are missing or are marked as "Failed" when you create a server cluster in
Windows Server 2003 (ID 886807), available for download on the Microsoft website:
http://support.microsoft.com/default.aspx?scid=KB;EN-US;886807
Use the MPIO DSM CLI to set the load balancing policy for each LUN to NLB.
Microsoft is currently working on a resolution to address this issue.

Maximum LUN size

Table 10 (page 35)
Table 10 Maximum LUN size
Operating system
HP OpenVMS 7.3-2, 8.2, and 8.3 with Alpha servers
HP OpenVMS 8.2- 1 , 8.3, and 8.3- 1 H1 with Integrity
servers
lists the maximum LUN size supported with each supported operating system.
Maximum LUN size
1 TB
1 TB
Operating tips and information 35