HP 6400/8400 HP StorageWorks 6400/8400 Enterprise Virtual Array User Guide - Page 35

Creating 16 TB or greater virtual disks in Windows 2008, Importing Windows dynamic disk volumes

Get HP 6400/8400 PDF manuals and user guides View all HP 6400/8400 manuals
Add to My Manuals
Save this manual to your list of manuals

Page 35 highlights

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) lists the maximum LUN size supported with each supported operating system. 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-1H1 with Integrity servers Maximum LUN size 1 TB 1 TB Operating tips and information 35

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
  • 90
  • 91
  • 92
  • 93
  • 94
  • 95
  • 96
  • 97
  • 98
  • 99
  • 100
  • 101
  • 102
  • 103
  • 104
  • 105
  • 106
  • 107
  • 108
  • 109
  • 110
  • 111
  • 112
  • 113
  • 114
  • 115
  • 116
  • 117
  • 118
  • 119
  • 120
  • 121
  • 122
  • 123
  • 124
  • 125
  • 126
  • 127
  • 128
  • 129
  • 130
  • 131
  • 132
  • 133
  • 134
  • 135
  • 136
  • 137
  • 138
  • 139
  • 140
  • 141
  • 142
  • 143
  • 144
  • 145
  • 146
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:
h
t
tp://su
ppo
r
t
.mi
c
r
o
s
o
f
t
.co
m/kb/8
1
6
3
0
7
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:
h
t
tp://su
ppo
r
t
.mi
c
r
o
s
o
f
t
.co
m/de
f
a
ult
.a
s
p
x?s
c
i
d=KB;EN
-U
S;8
8
6
8
0
7
•
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)
lists the maximum LUN size supported with each supported operating system.
Table 10 Maximum LUN size
Maximum LUN size
Operating system
1 TB
HP OpenVMS 7.3-2, 8.2, and 8.3 with Alpha servers
1 TB
HP OpenVMS 8.2-1, 8.3, and 8.3-1H1 with Integrity
servers
Operating tips and information
35