Dell PowerStore 1200T EMC PowerStore Protecting Your Data - Page 30

End a metro volume, Using protection policies with metro

Get Dell PowerStore 1200T PDF manuals and user guides View all Dell PowerStore 1200T manuals
Add to My Manuals
Save this manual to your list of manuals

Page 30 highlights

NOTE: The Metro page lists all the metro resources and makes it easy to evaluate all the impacted volume and prioritize promoting according to your considerations. 2. Click the status of a metro volume to display the Metro Volume page and click Demote. The Demote Metro Volume slide-out panel is displayed. 3. Verify that you understand the implication of demoting the metro volume in case the remote system is servicing I/Os and verify that the remote system is down if possible. 4. Click Demote. The demoted state of the volume is indicated in the Metro Volume Details section of the Metro Volume page. End a metro volume About this task When you end a metro volume, the metro configuration is removed, resulting in two independent volumes. If the remote volume is not deleted, the system removes the protection policy assigned to it, unmaps the hosts and assigns it with a new, different SCSI WWN. You can end a metro volume either from the preferred or the non-preferred system. Steps 1. Select Storage > Volume and select the checkbox of a volume. 2. SelectProtect > End Metro Volume. The End Metro Volume slide-out panel is displayed. 3. Select one of the following options from the slide-out panel: ● End metro and keep the volume on both the local and remote system. NOTE: The remote system unmaps the hosts and assigns a different SCSI WWN to the volume. ● End metro and delete the volume and any associated snapshots on the remote system. 4. Click End. Using protection policies with metro When an existing metro volume is assigned with a protection policy, or a volume with a protection policy is configured for metro, the same protection is applied to the metro volume on the both systems. The protection policy that is created on the remote system is read-only. Changes to the protection policy and snapshot rules can only be made to the policy created by the user (regardless of the storage system it was created on). The read-only policy is synchronized with the changes every 15 minutes. User-initiated snapshots that are created on one storage system are also generated on the other system. NOTE: Asynchronous replication is not supported with metro volumes. A protection policy that contains a replication rule cannot be assigned to a metro volume. Assigning a protection policy can be done on either the local or remote system (either preferred or non-preferred). Unassigning the protection policy should be done on the storage system where it was assigned. After the protection policy is unassigned from the volume in the local system, it is unassigned from the volume on the other system as well. Once the read-only protection policy is no longer being used by any metro volumes, it is automatically deleted from the system. NOTE: When the policy cannot be unassigned from the storage system where it was assigned, due to a metro volume failure, the following is allowed: ● A read-only policy can be unassigned or swapped for a read-write policy from a preferred metro volume when it is fractured. ● A read-only policy can be unassigned or swapped for a read-write policy from a promoted non-preferred metro volume. When the metro volume is fractured, snapshots are generated only on the active system and are synchronized to the other system following recovery. 30 Metro Protection

  • 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
NOTE:
The Metro page lists all the metro resources and makes it easy to evaluate all the impacted volume and prioritize
promoting according to your considerations.
2.
Click the status of a metro volume to display the Metro Volume page and click
Demote
.
The
Demote Metro Volume
slide-out panel is displayed.
3.
Verify that you understand the implication of demoting the metro volume in case the remote system is servicing I/Os and
verify that the remote system is down if possible.
4.
Click
Demote
.
The demoted state of the volume is indicated in the Metro Volume Details section of the Metro Volume page.
End a metro volume
About this task
When you end a metro volume, the metro configuration is removed, resulting in two independent volumes. If the remote volume
is not deleted, the system removes the protection policy assigned to it, unmaps the hosts and assigns it with a new, different
SCSI WWN. You can end a metro volume either from the preferred or the non-preferred system.
Steps
1.
Select
Storage
>
Volume
and select the checkbox of a volume.
2.
Select
Protect
>
End Metro Volume
.
The
End Metro Volume
slide-out panel is displayed.
3.
Select one of the following options from the slide-out panel:
●
End metro and keep the volume on both the local and remote system.
NOTE:
The remote system unmaps the hosts and assigns a different SCSI WWN to the volume.
●
End metro and delete the volume and any associated snapshots on the remote system.
4.
Click
End
.
Using protection policies with metro
When an existing metro volume is assigned with a protection policy, or a volume with a protection policy is configured for metro,
the same protection is applied to the metro volume on the both systems. The protection policy that is created on the remote
system is read-only. Changes to the protection policy and snapshot rules can only be made to the policy created by the user
(regardless of the storage system it was created on). The read-only policy is synchronized with the changes every 15 minutes.
User-initiated snapshots that are created on one storage system are also generated on the other system.
NOTE:
Asynchronous replication is not supported with metro volumes. A protection policy that contains a replication rule
cannot be assigned to a metro volume.
Assigning a protection policy can be done on either the local or remote system (either preferred or non-preferred).
Unassigning the protection policy should be done on the storage system where it was assigned. After the protection policy
is unassigned from the volume in the local system, it is unassigned from the volume on the other system as well. Once the
read-only protection policy is no longer being used by any metro volumes, it is automatically deleted from the system.
NOTE:
When the policy cannot be unassigned from the storage system where it was assigned, due to a metro volume
failure, the following is allowed:
●
A read-only policy can be unassigned or swapped for a read-write policy from a preferred metro volume when it is
fractured.
●
A read-only policy can be unassigned or swapped for a read-write policy from a promoted non-preferred metro volume.
When the metro volume is fractured, snapshots are generated only on the active system and are synchronized to the other
system following recovery.
30
Metro Protection