Dell PowerVault MD3260 Administrator's Guide - Page 76

Host-To-Virtual Disk Mapping

Get Dell PowerVault MD3260 PDF manuals and user guides View all Dell PowerVault MD3260 manuals
Add to My Manuals
Save this manual to your list of manuals

Page 76 highlights

RAID Level RAID Level 0 Drawer Loss Protection Requirements Replicated pair 1 = Physical disk located in enclosure 1, drawer 0, slot 0, and physical disk in enclosure 0, drawer 1, slot 0 Replicated pair 2 = Physical disk in enclosure 1, drawer 0, slot 1, and physical disk in enclosure 1, drawer 1, slot 1 Replicated pair 3 = Physical disk in enclosure 1, drawer 0, slot 2, and physical disk in enclosure 2, drawer 1, slot 2 RAID Level 10 requires a minimum of four physical disks. Make sure that each physical disk in a remotely replicated pair is located in a different drawer. You cannot achieve drawer loss protection because the RAID Level 0 disk group does not have redundancy. NOTE: If you create a disk group using the Automatic physical disk selection method, MD Storage Manager attempts to choose physical disks that provide drawer loss protection. If you create a disk group by using the Manual physical disk selection method, you must use the criteria that are specified in the previous table. If a disk group already has a Degraded status due to a failed physical disk when a drawer fails, drawer loss protection does not protect the disk group. The data on the virtual disks becomes inaccessible. Host-To-Virtual Disk Mapping After you create virtual disks, you must map them to the host(s) connected to the array. The following are the guidelines to configure host-to-virtual disk mapping: • Each virtual disk in the storage array can be mapped to only one host or host group. • Host-to-virtual disk mappings are shared between controllers in the storage array. • A unique LUN must be used by a host group or host to access a virtual disk. • Each host has its own LUN address space. MD Storage Manager permits the same LUN to be used by different hosts or host groups to access virtual disks in a storage array. • All operating system do not have the same number of LUNs available. • You can define the mappings on the Host Mappings tab in the AMW. See Using The Host Mappings Tab. Creating Host-To-Virtual Disk Mappings Guidelines to define the mappings: • An access virtual disk mapping is not required for an out-of-band storage array. If your storage array is managed using an out-of-band connection, and an access virtual disk mapping is assigned to the Default Group, an access virtual disk mapping is assigned to every host created from the Default Group. • Most hosts have 256 LUNs mapped per storage partition. The LUN numbering is from 0 through 255. If your operating system restricts LUNs to 127, and you try to map a virtual disk to a LUN that is greater than or equal to 127, the host cannot access it. • An initial mapping of the host group or host must be created using the Storage Partitioning Wizard before defining additional mappings. See Storage Partitioning. To create host to virtual disk mappings: 1. In the AMW, select the Host Mappings tab. 2. In the object tree, select: - Default Group 76

  • 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
RAID Level
Drawer Loss Protection Requirements
Replicated pair 1 = Physical disk located in enclosure 1, drawer 0, slot 0, and physical disk in
enclosure 0, drawer 1, slot 0
Replicated pair 2 = Physical disk in enclosure 1, drawer 0, slot 1, and physical disk in
enclosure 1, drawer 1, slot 1
Replicated pair 3 = Physical disk in enclosure 1, drawer 0, slot 2, and physical disk in
enclosure 2, drawer 1, slot 2
RAID Level 10 requires a minimum of four physical disks. Make sure that each physical disk
in a remotely replicated pair is located in a different drawer.
RAID Level 0
You cannot achieve drawer loss protection because the RAID Level 0 disk group does not
have redundancy.
NOTE:
If you create a disk group using the Automatic physical disk selection method, MD Storage Manager
attempts to choose physical disks that provide drawer loss protection. If you create a disk group by using the
Manual physical disk selection method, you must use the criteria that are specified in the previous table.
If a disk group already has a Degraded status due to a failed physical disk when a drawer fails, drawer loss protection
does not protect the disk group. The data on the virtual disks becomes inaccessible.
Host-To-Virtual Disk Mapping
After you create virtual disks, you must map them to the host(s) connected to the array.
The following are the guidelines to configure host-to-virtual disk mapping:
•
Each virtual disk in the storage array can be mapped to only one host or host group.
•
Host-to-virtual disk mappings are shared between controllers in the storage array.
•
A unique LUN must be used by a host group or host to access a virtual disk.
•
Each host has its own LUN address space. MD Storage Manager permits the same LUN to be used by different
hosts or host groups to access virtual disks in a storage array.
•
All operating system do not have the same number of LUNs available.
•
You can define the mappings on the
Host Mappings
tab in the AMW. See
Using The Host Mappings Tab
.
Creating Host-To-Virtual Disk Mappings
Guidelines to define the mappings:
•
An access virtual disk mapping is not required for an out-of-band storage array. If your storage array is
managed using an out-of-band connection, and an access virtual disk mapping is assigned to the Default Group,
an access virtual disk mapping is assigned to every host created from the Default Group.
•
Most hosts have 256 LUNs mapped per storage partition. The LUN numbering is from 0 through 255. If your
operating system restricts LUNs to 127, and you try to map a virtual disk to a LUN that is greater than or equal to
127, the host cannot access it.
•
An initial mapping of the host group or host must be created using the Storage Partitioning Wizard before
defining additional mappings. See
Storage Partitioning
.
To create host to virtual disk mappings:
1.
In the AMW, select the
Host Mappings
tab.
2.
In the object tree, select:
–
Default Group
76