Dell PowerVault MD3260 Administrator's Guide - Page 111

Virtual Disk Read/Write Permissions, Virtual Disk Copy Restrictions

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 111 highlights

Virtual Disk Read/Write Permissions After the virtual disk copy is complete, the target virtual disk automatically becomes read-only to the hosts. The target virtual disk rejects read and write requests while the virtual disk copy operation has a status of Pending or In Progress or if the operation fails before completing the copy. Keep the target virtual disk Read-only enabled if you want to preserve the data on the target virtual disk for reasons such as the following: • If you are using the target virtual disk for backup purposes. • If you are using the data on the target virtual disk to copy back to the source virtual disk of a disabled or failed snapshot virtual disk. If you decide not to preserve the data on the target virtual disk after the virtual disk copy is complete, change the write protection setting for the target virtual disk to Read/Write. Virtual Disk Copy Restrictions Before you perform any virtual disk copy tasks, understand and adhere to the restrictions listed in this section. The restrictions apply to the source virtual disk, the target virtual disk, and the storage array. • While a virtual disk copy has a status of In Progress, Pending, or Failed, the source virtual disk is available for read I/O activity only. After the virtual disk copy is complete, read and write I/O activity to the source virtual disk are permitted. • A virtual disk can be selected as a target virtual disk for only one virtual disk copy at a time. • A virtual disk copy for any virtual disk cannot be mounted on the same host as the source virtual disk. • Windows does not allow a drive letter to be assigned to a virtual disk copy. • A virtual disk with a Failed status cannot be used as a source virtual disk or target virtual disk. • A virtual disk with a Degraded status cannot be used as a target virtual disk. • A virtual disk participating in a modification operation cannot be selected as a source virtual disk or target virtual disk. Modification operations include the following: - Capacity expansion - RAID-level migration - Segment sizing - Virtual disk expansion - Defragmenting a virtual disk NOTE: The following host preparation sections also apply when using the virtual disk copy feature through the CLI interface. 111

  • 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
Virtual Disk Read/Write Permissions
After the virtual disk copy is complete, the target virtual disk automatically becomes read-only to the hosts. The target
virtual disk rejects read and write requests while the virtual disk copy operation has a status of Pending or In Progress
or if the operation fails before completing the copy. Keep the target virtual disk Read-only enabled if you want to
preserve the data on the target virtual disk for reasons such as the following:
•
If you are using the target virtual disk for backup purposes.
•
If you are using the data on the target virtual disk to copy back to the source virtual disk of a disabled or failed
snapshot virtual disk.
If you decide not to preserve the data on the target virtual disk after the virtual disk copy is complete, change the write
protection setting for the target virtual disk to Read/Write.
Virtual Disk Copy Restrictions
Before you perform any virtual disk copy tasks, understand and adhere to the restrictions listed in this section. The
restrictions apply to the source virtual disk, the target virtual disk, and the storage array.
•
While a virtual disk copy has a status of In Progress, Pending, or Failed, the source virtual disk is available for
read I/O activity only. After the virtual disk copy is complete, read and write I/O activity to the source virtual disk
are permitted.
•
A virtual disk can be selected as a target virtual disk for only one virtual disk copy at a time.
•
A virtual disk copy for any virtual disk cannot be mounted on the same host as the source virtual disk.
•
Windows does not allow a drive letter to be assigned to a virtual disk copy.
•
A virtual disk with a Failed status cannot be used as a source virtual disk or target virtual disk.
•
A virtual disk with a Degraded status cannot be used as a target virtual disk.
•
A virtual disk participating in a modification operation cannot be selected as a source virtual disk or target
virtual disk. Modification operations include the following:
–
Capacity expansion
–
RAID-level migration
–
Segment sizing
–
Virtual disk expansion
–
Defragmenting a virtual disk
NOTE:
The following host preparation sections also apply when using the virtual disk copy feature
through the CLI interface.
111