Dell PowerStore 9200T EMC PowerStore Protecting Your Data - Page 33

Metro protection use cases, Using metro for high availability, Using metro for load balancing

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

Page 33 highlights

Metro protection use cases Use Metro protection to ensure data high availability, load balancing and migration. Using metro for high availability A Metro volume is exposed using two distinct storage arrays that cooperate to expose a single Metro volume to application hosts by providing the same SCSI image and data. The hosts and applications running on them perceive two physical volumes as a single volume with multiple paths. As a result, hosts can access both sides of the Metro volume. If there is a link loss or failure of one of the systems, host access can still be maintained to the active system. Metro protection provides bi-directional synchronous replication, where both sides of the Metro volume can be used for production. Instead of disaster recovery (by failing over a replication session to a remote system), Metro enables disaster avoidance by providing automatic synchronization between the systems without downtime. Using metro for load balancing With PowerStore metro volume, the data centers can be optimized to fully use PowerStore systems through an active/ active environment that enables workload balancing across PowerStore systems. Moving applications non-disruptively between PowerStore systems is simple and easy and can be done when capacity or performance balancing is required. Using metro for migration You can use metro volumes when there is a need to migrate workloads between PowerStore systems. Using metro volumes for migration is simple and easy to use, and it reduces the risk for data loss. With the metro volume option, the migration is non-disruptive and, when migration is complete, the metro volume can be either removed or kept for allowing an extremely fast recovery in the event of a system failure or even a full site failure. Use cases 33

  • 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
Metro protection use cases
Use Metro protection to ensure data high availability, load balancing and migration.
Using metro for high availability
A Metro volume is exposed using two distinct storage arrays that cooperate to expose a single Metro volume to application
hosts by providing the same SCSI image and data. The hosts and applications running on them perceive two physical volumes as
a single volume with multiple paths. As a result, hosts can access both sides of the Metro volume. If there is a link loss or failure
of one of the systems, host access can still be maintained to the active system.
Metro protection provides bi-directional synchronous replication, where both sides of the Metro volume can be used for
production. Instead of disaster recovery (by failing over a replication session to a remote system), Metro enables disaster
avoidance by providing automatic synchronization between the systems without downtime.
Using metro for load balancing
With PowerStore metro volume, the data centers can be optimized to fully use PowerStore systems through an active/
active environment that enables workload balancing across PowerStore systems. Moving applications non-disruptively between
PowerStore systems is simple and easy and can be done when capacity or performance balancing is required.
Using metro for migration
You can use metro volumes when there is a need to migrate workloads between PowerStore systems. Using metro volumes
for migration is simple and easy to use, and it reduces the risk for data loss. With the metro volume option, the migration is
non-disruptive and, when migration is complete, the metro volume can be either removed or kept for allowing an extremely fast
recovery in the event of a system failure or even a full site failure.
Use cases
33