HP MSA 1040 HP MSA 1040 SMU Reference Guide (762784-001, March 2014) - Page 134

Starting a vdisk, Reattaching a secondary volume, To start a vdisk

Get HP MSA 1040 PDF manuals and user guides View all HP MSA 1040 manuals
Add to My Manuals
Save this manual to your list of manuals

Page 134 highlights

3. Click Yes to continue; otherwise, click No. If you clicked Yes, the stop operation begins. A message indicates whether the task succeeded or failed. If the stop operation succeeds, the vdisk's health is shown as Unknown, its status is shown as STOP, and its subcomponents are no longer displayed in the Configuration View panel. 4. If the stop operation succeeded for the secondary volume's vdisk and for its snap pool's vdisk (if applicable), you can move the disks into the remote system. Starting a vdisk Starting a vdisk is part of the process for moving a secondary volume from a primary system into a secondary system. The process to move a secondary volume is: 1. In the system where the secondary volume resides: a. Detach the secondary volume. For details see "Detaching a secondary volume" (page 132). b. If the secondary volume's vdisk contains other secondary volumes, detach those volumes. c. Stop the secondary volume's vdisk. For details see "Stopping a vdisk" (page 133). d. If the secondary volumes' snap pools are in other vdisks, stop those vdisks. e. Move the vdisks into the secondary system. This system must support the link type that the replication set is configured to use. For example, if the replication set's link type is configured to use FC links, the secondary system must have FC ports. 2. In the secondary system: a. Start the snap pools' vdisks. b. Start the secondary volumes' vdisks. c. Reattach the secondary volumes. For details see "Reattaching a secondary volume" (page 134). To start a vdisk 1. In the Configuration View panel, right-click a stopped vdisk and select Provisioning > Start Vdisk. 2. In the main panel, click Start Vdisk. A message indicates whether the task succeeded or failed. NOTE: If the replication set was deleted while the secondary volume's vdisk was stopped, restarting the vdisk will make the set partially reappear. To clean up this remnant, reattach the secondary volume, set it to be the primary volume (by using the Set Replication Primary Volume panel on page 135), and then delete the replication set again. Reattaching a secondary volume Reattaching a secondary volume is the last part of the process for moving a secondary volume from a primary system into a secondary system. The process to move a secondary volume is: 1. In the system where the secondary volume resides: a. Detach the secondary volume. For details see "Detaching a secondary volume" (page 132). b. If the secondary volume's vdisk contains other secondary volumes, detach those volumes. c. Stop the secondary volume's vdisk. For details see "Stopping a vdisk" (page 133). d. If the secondary volumes' snap pools are in other vdisks, stop those vdisks. e. Move the vdisks into the secondary system. This system must support the link type that the replication set is configured to use. For example, if the replication set's link type is configured to use FC links, the secondary system must have FC ports. 2. In the secondary system: a. Start the snap pools' vdisks. For details see "Starting a vdisk" (page 134). b. Start the secondary volumes' vdisks. c. Reattach the secondary volumes. 134 Using Remote Snap to replicate volumes

  • 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
134
Using Remote Snap to replicate volumes
3.
Click
Yes
to continue; otherwise, click
No
. If you clicked
Yes
, the stop operation begins. A message indicates
whether the task succeeded or failed. If the stop operation succeeds, the vdisk’s health is shown as
Unknown
, its
status is shown as
STOP
, and its subcomponents are no longer displayed in the Configuration View panel.
4.
If the stop operation succeeded for the secondary volume’s vdisk and for its snap pool’s vdisk (if applicable), you
can move the disks into the remote system.
Starting a vdisk
Starting a vdisk is part of the process for moving a secondary volume from a primary system into a secondary system.
The process to move a secondary volume is:
1.
In the system where the secondary volume resides:
a.
Detach the secondary volume. For details see
"Detaching a secondary volume" (page 132)
.
b.
If the secondary volume’s vdisk contains other secondary volumes, detach those volumes.
c.
Stop the secondary volume’s vdisk. For details see
"Stopping a vdisk" (page 133)
.
d.
If the secondary volumes’ snap pools are in other vdisks, stop those vdisks.
e.
Move the vdisks into the secondary system. This system must support the link type that the replication set is
configured to use. For example, if the replication set’s link type is configured to use FC links, the secondary
system must have FC ports.
2.
In the secondary system:
a.
Start the snap pools’ vdisks.
b.
Start the secondary volumes’ vdisks.
c.
Reattach the secondary volumes. For details see
"Reattaching a secondary volume" (page 134)
.
To start a vdisk
1.
In the Configuration View panel, right-click a stopped vdisk and select
Provisioning > Start Vdisk
.
2.
In the main panel, click
Start Vdisk
. A message indicates whether the task succeeded or failed.
NOTE:
If the replication set was deleted while the secondary volume’s vdisk was stopped, restarting the vdisk will
make the set partially reappear. To clean up this remnant, reattach the secondary volume, set it to be the primary
volume (by using the Set Replication Primary Volume panel on
page 135
), and then delete the replication set again.
Reattaching a secondary volume
Reattaching a secondary volume is the last part of the process for moving a secondary volume from a primary system
into a secondary system. The process to move a secondary volume is:
1.
In the system where the secondary volume resides:
a.
Detach the secondary volume. For details see
"Detaching a secondary volume" (page 132)
.
b.
If the secondary volume’s vdisk contains other secondary volumes, detach those volumes.
c.
Stop the secondary volume’s vdisk. For details see
"Stopping a vdisk" (page 133)
.
d.
If the secondary volumes’ snap pools are in other vdisks, stop those vdisks.
e.
Move the vdisks into the secondary system. This system must support the link type that the replication set is
configured to use. For example, if the replication set’s link type is configured to use FC links, the secondary
system must have FC ports.
2.
In the secondary system:
a.
Start the snap pools’ vdisks. For details see
"Starting a vdisk" (page 134)
.
b.
Start the secondary volumes’ vdisks.
c.
Reattach the secondary volumes.