Dell PowerVault MD3260i CLI Guide - Page 122

Create Snapshot Virtual Disk, Syntax User-Defined Number of Physical Disks

Page 122 highlights

Passwords are stored on each storage array in a management domain. If a password was not previously set, a password is not needed. The password can be any combination of alphanumeric characters with a maximum of 30 characters. (A storage array password can be defined by using the set storageArray command.) Synchronization priority defines the amount of system resources that are used to synchronize the data between the primary virtual disk and the secondary virtual disk of a replication relationship. If the highest priority level is selected, the data synchronization uses the most system resources to perform the full synchronization, which decreases performance for host data transfers. The writeOrder parameter applies only to asynchronous replications and makes them become part of a consistency group. Setting the writeOrder parameter to preserved causes the remote replication pair to transmit data from the primary virtual disk to the secondary virtual disk in the same order as the host writes to the primary virtual disk. In the event of a transmission link failure, the data is buffered until a full synchronization can occur. This action can require additional system overhead to maintain the buffered data, which slows operations. Setting the writeOrder parameter to notPreserved frees the system from having to maintain data in a buffer, but it requires forcing a full synchronization to make sure that the secondary virtual disk has the same data as the primary virtual disk. Create Snapshot Virtual Disk This command creates a snapshot virtual disk. When you use this command, you can define the snapshot virtual disk in one of three ways: • User-defined physical disks • User-defined disk group • User-defined number of physical disks for the snapshot virtual disk If you choose to define a number of physical disks, the RAID controller module firmware chooses which physical disks to use for the snapshot virtual disk. Syntax (User-Defined Physical Disks) create snapshotVirtualDisk sourceVirtualDisk="sourceVirtualDiskName" (repositoryRAIDLevel=(0 | 1 | 5 | 6) repositoryPhysicalDisks=(enclosureID1,slotID1 enclosureID2,slotID2... enclosureIDn,slotIDn)) [repositoryDiskGroupUserLabel= "repositoryDiskGroupName" enclosureLossProtect=(TRUE | FALSE) freeCapacityArea=freeCapacityIndexNumber userLabel="snapshotVirtualDiskName" warningThresholdPercent=percentValue repositoryPercentOfSource=percentValue repositoryUserLabel="repositoryName" repositoryFullPolicy=(failSourceWrites | failSnapshot)] |enableSchedule=(TRUE | FALSE)|schedule=(immediate | snapshotSchedule) Syntax (User-Defined Number of Physical Disks) create snapshotVirtualDisk sourceVirtualDisk="sourceVirtualDiskName" repositoryRAIDLevel=(1 | 5 | 6) repositoryDriveCount=numberOfPhysicalDisks [repositoryDiskGroupUserLabel= "repositoryDiskGroupName" driveMediaType=(HDD | SSD | unknown | allMedia)] physicalDiskType=(SAS) enclosureLossProtect=(TRUE | FALSE) 122

  • 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
  • 176
  • 177
  • 178
  • 179
  • 180
  • 181
  • 182
  • 183
  • 184
  • 185
  • 186
  • 187
  • 188
  • 189
  • 190
  • 191
  • 192
  • 193
  • 194
  • 195
  • 196
  • 197
  • 198
  • 199
  • 200
  • 201
  • 202
  • 203
  • 204
  • 205
  • 206
  • 207
  • 208
  • 209
  • 210
  • 211
  • 212
  • 213
  • 214
  • 215
  • 216
  • 217
  • 218
  • 219
  • 220
  • 221
  • 222
  • 223
  • 224
  • 225
  • 226

Passwords are stored on each storage array in a management domain. If a password was not previously set, a
password is not needed. The password can be any combination of alphanumeric characters with a maximum of 30
characters. (A storage array password can be defined by using the
set storageArray
command.)
Synchronization priority defines the amount of system resources that are used to synchronize the data between the
primary virtual disk and the secondary virtual disk of a replication relationship. If the highest priority level is selected, the
data synchronization uses the most system resources to perform the full synchronization, which decreases performance
for host data transfers.
The
writeOrder
parameter applies only to asynchronous replications and makes them become part of a consistency
group. Setting the
writeOrder
parameter to
preserved
causes the remote replication pair to transmit data from
the primary virtual disk to the secondary virtual disk in the same order as the host writes to the primary virtual disk. In
the event of a transmission link failure, the data is buffered until a full synchronization can occur. This action can require
additional system overhead to maintain the buffered data, which slows operations. Setting the
writeOrder
parameter
to
notPreserved
frees the system from having to maintain data in a buffer, but it requires forcing a full
synchronization to make sure that the secondary virtual disk has the same data as the primary virtual disk.
Create Snapshot Virtual Disk
This command creates a snapshot virtual disk. When you use this command, you can define the snapshot virtual disk in
one of three ways:
User-defined physical disks
User-defined disk group
User-defined number of physical disks for the snapshot virtual disk
If you choose to define a number of physical disks, the RAID controller module firmware chooses which physical disks
to use for the snapshot virtual disk.
Syntax (User-Defined Physical Disks)
create snapshotVirtualDisk
sourceVirtualDisk=”
sourceVirtualDiskName
(repositoryRAIDLevel=(0 | 1 | 5 | 6)
repositoryPhysicalDisks=(
enclosureID1,slotID1
enclosureID2,slotID2...
enclosureIDn,slotIDn
))
[repositoryDiskGroupUserLabel=
repositoryDiskGroupName
enclosureLossProtect=(TRUE | FALSE)
freeCapacityArea=
freeCapacityIndexNumber
userLabel=”
snapshotVirtualDiskName
warningThresholdPercent=
percentValue
repositoryPercentOfSource=
percentValue
repositoryUserLabel=”
repositoryName
repositoryFullPolicy=(failSourceWrites |
failSnapshot)]
|enableSchedule=(TRUE | FALSE)|schedule=(immediate
|
snapshotSchedule)
Syntax (User-Defined Number of Physical Disks)
create snapshotVirtualDisk
sourceVirtualDisk=”
sourceVirtualDiskName
repositoryRAIDLevel=(1 | 5 | 6)
repositoryDriveCount=
numberOfPhysicalDisks
[repositoryDiskGroupUserLabel=
repositoryDiskGroupName
driveMediaType=(HDD | SSD | unknown | allMedia)]
physicalDiskType=(SAS)
enclosureLossProtect=(TRUE | FALSE)
122