Dell PowerVault MD3260i CLI Guide - Page 75

Suspending And Resuming A Replication Relationship, Removing A Replication Relationship

Page 75 highlights

This example shows how to use the command in a script file: set remoteReplication localVirtualDisk [Jan_04_Account] syncPriority=medium writeOrder=notpreserved writeMode=asynchronous; Suspending And Resuming A Replication Relationship Use the suspend remoteReplication command to stop data transfer between a primary virtual disk and a secondary virtual disk in a replication relationship without disabling the replication relationship. Suspending a replication relationship lets you control when the data on the primary virtual disk and data on the secondary virtual disk are synchronized. Suspending a replication relationship helps to reduce any performance impact to the host application that might occur while any changed data on the primary virtual disk is copied to the secondary virtual disk. Suspending a replication relationship is particularly useful when you want to run a backup of the data on the secondary virtual disk. When a replication relationship is in a suspended state, the primary virtual disk does not make any attempt to contact the secondary virtual disk. Any writes to the primary virtual disk are persistently logged in the replication repository virtual disks. After the replication relationship resumes, any data that is written to the primary virtual disk is automatically written to the secondary virtual disk. Only the modified data blocks on the primary virtual disk are written to the secondary virtual disk. Full synchronization is not required. NOTE: If you suspend a remote replication that is set up in the Write consistency mode, you suspend all remote replicated pairs within the group. You can then resume replication operations for any of the individual remote replicated pairs that are in the group. This example shows the suspend remoteReplication command: c:\...\smX\client>smcli 123.45.67.88 123.45.67.89 -c "suspend remoteReplication primary Jan_04_Account writeConsistency=false;" The writeConsistency parameter defines whether the virtual disks identified in this command are in a writeconsistency group or are separate. For the virtual disks in a write-consistency group, set this parameter to TRUE. For the virtual disks that are not in a write-consistency group, set this parameter to FALSE. This example shows how to use the command in a script file: suspend remoteReplication virtualDisk Jan_04_Account writeConsistency=false; The replication relationship remains suspended until you use the resume remoteReplication command to restart synchronization activities. This command restarts data transfers between a primary virtual disk and a secondary virtual disk in a replication relationship after the replication has been suspended or unsynchronized. This example shows the resume remoteReplication command: c:\...\smX\client>smcli 123.45.67.88 123.45.67.89 -c "resume remoteReplication virtualDisk Jan_04_Account writeConsistency=false;" The writeConsistency parameter in this command operates the same as in the previous command. This example shows how to use the command in a script file: resume remoteReplication virtualDisk Jan_04_Account writeConsistency=false; Removing A Replication Relationship Use the remove remoteReplication command to remove the link between a primary virtual disk and a secondary virtual disk. (Removing a replication relationship is similar to deleting a replication relationship.) Removing the link 75

  • 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

This example shows how to use the command in a script file:
set remoteReplication localVirtualDisk [Jan_04_Account]
syncPriority=medium
writeOrder=notpreserved
writeMode=asynchronous;
Suspending And Resuming A Replication Relationship
Use the suspend
remoteReplication
command to stop data transfer between a primary virtual disk and a
secondary virtual disk in a replication relationship without disabling the replication relationship. Suspending a
replication relationship lets you control when the data on the primary virtual disk and data on the secondary virtual disk
are synchronized. Suspending a replication relationship helps to reduce any performance impact to the host application
that might occur while any changed data on the primary virtual disk is copied to the secondary virtual disk. Suspending a
replication relationship is particularly useful when you want to run a backup of the data on the secondary virtual disk.
When a replication relationship is in a suspended state, the primary virtual disk does not make any attempt to contact
the secondary virtual disk. Any writes to the primary virtual disk are persistently logged in the replication repository
virtual disks. After the replication relationship resumes, any data that is written to the primary virtual disk is
automatically written to the secondary virtual disk. Only the modified data blocks on the primary virtual disk are written
to the secondary virtual disk. Full synchronization is not required.
NOTE:
If you suspend a remote replication that is set up in the Write consistency mode, you suspend all remote
replicated pairs within the group. You can then resume replication operations for any of the individual remote
replicated pairs that are in the group.
This example shows the suspend
remoteReplication
command:
c:\...\smX\client>smcli 123.45.67.88 123.45.67.89
-c “suspend remoteReplication primary Jan_04_Account
writeConsistency=false;”
The
writeConsistency
parameter defines whether the virtual disks identified in this command are in a write-
consistency group or are separate. For the virtual disks in a write-consistency group, set this parameter to TRUE. For the
virtual disks that are not in a write-consistency group, set this parameter to
FALSE
.
This example shows how to use the command in a script file:
suspend remoteReplication virtualDisk Jan_04_Account
writeConsistency=false;
The replication relationship remains suspended until you use the resume remoteReplication command to restart
synchronization activities. This command restarts data transfers between a primary virtual disk and a secondary virtual
disk in a replication relationship after the replication has been suspended or unsynchronized.
This example shows the
resume remoteReplication
command:
c:\...\smX\client>smcli 123.45.67.88 123.45.67.89
-c “resume remoteReplication virtualDisk Jan_04_Account
writeConsistency=false;”
The
writeConsistency
parameter in this command operates the same as in the previous command.
This example shows how to use the command in a script file:
resume remoteReplication virtualDisk Jan_04_Account
writeConsistency=false;
Removing A Replication Relationship
Use the remove
remoteReplication
command to remove the link between a primary virtual disk and a secondary
virtual disk. (Removing a replication relationship is similar to deleting a replication relationship.) Removing the link
75