Dell PowerVault MD3260 Administrator's Guide - Page 25

Disk Roaming, Host Server-To-Virtual Disk Mapping

Page 25 highlights

NOTE: To ensure that the migrating disk groups and virtual disks are correctly recognized when the target storage array has an existing physical disk, use hot virtual disk migration. When attempting virtual disk migration, follow these recommendations: • Moving physical disks to the destination array for migration - When inserting drives into the destination storage array during hot virtual disk migration, wait for the inserted physical disk to be displayed in the MD Storage Manager, or wait for 30 seconds (whichever occurs first), before inserting the next physical disk. WARNING: Without the interval between drive insertions, the storage array may become unstable and manageability may be temporarily lost. • Migrating virtual disks from multiple storage arrays into a single storage array - When migrating virtual disks from multiple or different storage arrays into a single destination storage array, move all of the physical disks from the same storage array as a set into the new destination storage array. Ensure that all of the physical disks from a storage array are migrated to the destination storage array before starting migration from the next storage array. NOTE: If the drive modules are not moved as a set to the destination storage array, the newly relocated disk groups may not be accessible. • Migrating virtual disks to a storage array with no existing physical disks - Turn off the destination storage array, when migrating disk groups or a complete set of physical disks from a storage array to another storage array that has no existing physical disks. After the destination storage array has been turned on and has successfully recognized the newly migrated physical disks, migration operations can continue. NOTE: Disk groups from multiple storage arrays must not be migrated at the same time to a storage array that has no existing physical disks. Use cold virtual disk migration for the disk groups from one storage array. • Enabling premium features before migration - Before migrating disk groups and virtual disks, enable the required premium features on the destination storage array. If a disk group is migrated from a storage array that has a premium feature enabled and the destination array does not have this feature enabled, an Out of Compliance error message can be generated. Disk Roaming You can move physical disks within an array. The RAID controller module automatically recognizes the relocated physical disks and logically places them in the proper virtual disks that are part of the disk group. Disk roaming is permitted when the RAID controller module is either online or powered off. NOTE: The disk group must be exported before moving the physical disks. Host Server-To-Virtual Disk Mapping The host server attached to a storage array accesses various virtual disks on the storage array through its host ports. Specific virtual disk-to-LUN mappings to an individual host server can be defined. In addition, the host server can be part of a host group that shares access to one or more virtual disks. You can manually configure a host server-to-virtual disk mapping. When you configure host server-to-virtual disk mapping, consider these guidelines: • You can define one host server-to-virtual disk mapping for each virtual disk in the storage array. • Host server-to-virtual disk mappings are shared between RAID controller modules in the storage array. • A unique LUN must be used by a host group or host server to access a virtual disk. • Not every operating system has the same number of LUNs available for use. 25

  • 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
  • 147
  • 148
  • 149
  • 150
  • 151
  • 152
  • 153
  • 154
  • 155
  • 156
  • 157
  • 158
  • 159
  • 160
  • 161
  • 162
  • 163
  • 164
  • 165
  • 166
  • 167
  • 168
  • 169
  • 170
  • 171
  • 172
  • 173
  • 174
  • 175

NOTE:
To ensure that the migrating disk groups and virtual disks are correctly recognized when the target storage
array has an existing physical disk, use hot virtual disk migration.
When attempting virtual disk migration, follow these recommendations:
Moving physical disks to the destination array for migration — When inserting drives into the destination
storage array during hot virtual disk migration, wait for the inserted physical disk to be displayed in the MD
Storage Manager, or wait for 30 seconds (whichever occurs first), before inserting the next physical disk.
WARNING: Without the interval between drive insertions, the storage array may become unstable and
manageability may be temporarily lost.
Migrating virtual disks from multiple storage arrays into a single storage array — When migrating virtual disks
from multiple or different storage arrays into a single destination storage array, move all of the physical disks
from the same storage array as a set into the new destination storage array. Ensure that all of the physical disks
from a storage array are migrated to the destination storage array before starting migration from the next
storage array.
NOTE:
If the drive modules are not moved as a set to the destination storage array, the newly relocated
disk groups may not be accessible.
Migrating virtual disks to a storage array with no existing physical disks — Turn off the destination storage
array, when migrating disk groups or a complete set of physical disks from a storage array to another storage
array that has no existing physical disks. After the destination storage array has been turned on and has
successfully recognized the newly migrated physical disks, migration operations can continue.
NOTE:
Disk groups from multiple storage arrays must not be migrated at the same time to a storage array
that has no existing physical disks. Use cold virtual disk migration for the disk groups from one storage
array.
Enabling premium features before migration — Before migrating disk groups and virtual disks, enable the
required premium features on the destination storage array. If a disk group is migrated from a storage array that
has a premium feature enabled and the destination array does not have this feature enabled, an
Out of
Compliance
error message can be generated.
Disk Roaming
You can move physical disks within an array. The RAID controller module automatically recognizes the relocated
physical disks and logically places them in the proper virtual disks that are part of the disk group. Disk roaming is
permitted when the RAID controller module is either online or powered off.
NOTE:
The disk group must be exported before moving the physical disks.
Host Server-To-Virtual Disk Mapping
The host server attached to a storage array accesses various virtual disks on the storage array through its host ports.
Specific virtual disk-to-LUN mappings to an individual host server can be defined. In addition, the host server can be
part of a host group that shares access to one or more virtual disks. You can manually configure a host server-to-virtual
disk mapping. When you configure host server-to-virtual disk mapping, consider these guidelines:
You can define one host server-to-virtual disk mapping for each virtual disk in the storage array.
Host server-to-virtual disk mappings are shared between RAID controller modules in the storage array.
A unique LUN must be used by a host group or host server to access a virtual disk.
Not every operating system has the same number of LUNs available for use.
25