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

Metro protection

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

If you want to create a new snapshot or replication rule, ensure that you review the parameters and your business requirements with an administrator before proceeding. This helps achieve and maintain consistent policies across the system. For detailed information on protection policies-related procedures you can perform, refer to the Protection Policies chapter. Metro protection Metro provides bi-directional synchronous replication (active/active) across two PowerStore systems. A metro volume is exposed using two distinct systems, typically located in two different data centers, up to 96 km (or 60 miles) apart, or in two distant locations within the same data center. The two systems cooperate to expose a single metro volume to application hosts by providing the same SCSI image and data, making the hosts and application running on them perceive two physical volumes that are hosted by the two systems as a single volume with multiple paths. Metro protection enables increased availability and disaster avoidance, resource balancing across data centers and storage migration between two PowerStore systems. When you configure a metro volume, the content of a metro volume is replicated to the remote system. Protection policies are used to configure additional protection such as local snapshots. A metro session consists of two PowerStore systems. One system is configured as 'preferred' while the other is configured as 'non-preferred'. These roles guide the system behavior on failure situations. When a failure occurs (either on one of the systems or to the connection between the systems), the metro session becomes 'fractured' and the non-preferred system stops servicing I/Os. The following table summarizes the allowed actions that you can perform on a metro volume depending on the current metro status and the system from which the action is initiated. NOTE: The table addresses common use cases and does not include rare failure scenarios. Table 1. Allowed Metro Actions Location Metro Status Modify Role On preferred system Operating Yes Normally Paused No Fractured No Switching to No Metro Synchroniza tion On non-preferred system Operating Yes Normally Paused No Fractured No Switching to No Metro Synchroniza tion Promote No Demote No No Yes No Yes No No Pause Yes No Yes Yes No No Yes Yes (if other No No system is unreachable ) Yes (if other No Yes system is unreachable ) No No Yes Resume No Yes No No End Metro Yes Yes Yes Yes No Yes Yes Yes No Yes No Yes 8 Introduction

  • 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
If you want to create a new snapshot or replication rule, ensure that you review the parameters and your business requirements
with an administrator before proceeding. This helps achieve and maintain consistent policies across the system.
For detailed information on protection policies-related procedures you can perform, refer to the
Protection Policies
chapter.
Metro protection
Metro provides bi-directional synchronous replication (active/active) across two PowerStore systems. A metro volume is
exposed using two distinct systems, typically located in two different data centers, up to 96 km (or 60 miles) apart, or in two
distant locations within the same data center. The two systems cooperate to expose a single metro volume to application hosts
by providing the same SCSI image and data, making the hosts and application running on them perceive two physical volumes
that are hosted by the two systems as a single volume with multiple paths.
Metro protection enables increased availability and disaster avoidance, resource balancing across data centers and storage
migration between two PowerStore systems.
When you configure a metro volume, the content of a metro volume is replicated to the remote system. Protection policies are
used to configure additional protection such as local snapshots.
A metro session consists of two PowerStore systems. One system is configured as 'preferred' while the other is configured
as 'non-preferred'. These roles guide the system behavior on failure situations. When a failure occurs (either on one of the
systems or to the connection between the systems), the metro session becomes 'fractured' and the non-preferred system
stops servicing I/Os.
The following table summarizes the allowed actions that you can perform on a metro volume depending on the current metro
status and the system from which the action is initiated.
NOTE:
The table addresses common use cases and does not include rare failure scenarios.
Table 1. Allowed Metro Actions
Location
Metro
Status
Modify
Role
Promote
Demote
Pause
Resume
End Metro
On preferred system
Operating
Normally
Yes
No
No
Yes
No
Yes
Paused
No
No
Yes
No
Yes
Yes
Fractured
No
No
Yes
Yes
No
Yes
Switching to
Metro
Synchroniza
tion
No
No
No
Yes
No
Yes
On non-preferred system
Operating
Normally
Yes
No
No
Yes
No
Yes
Paused
No
Yes (if other
system is
unreachable
)
No
No
Yes
Yes
Fractured
No
Yes (if other
system is
unreachable
)
No
Yes
No
Yes
Switching to
Metro
Synchroniza
tion
No
No
No
Yes
No
Yes
8
Introduction