Dell PowerStore: Metro Volume

• 1

  Overview
• 2

  Audience
• 3

  Revisions
• 4

  We value your feedback

• 1

  Business continuity planning
• 2

  PowerStore overview
• 3

  Terminology

• 1

  Introduction
• 2

  Features
• 3

  Licensing
• 4

  Theory of operation
• 5

  Polarization
• 6

  Host connectivity
• 7

  ESXi path selection policies (PSP)
• 8

  Replication states
• 9

  Replication Metrics
• 10

  Metro Volume operations
• 11

  Create and manage a Metro Volume
• 12

  Failure scenarios
• 13

  Failure scenario table
• 14

  vSphere DRS, HA, and Metro Volume
• 15

  vSphere vMotion and Metro Volume
• 16

  Supported configurations
• 17

  System limits

• 1

  Introduction
• 2

  Requirements and installation
• 3

  Hostnames and certificates
• 4

  Witness registration
• 5

  Upgrading
• 6

  Witness components
• 7

  Communication flow – healthy
• 8

  Metro Volume witness connection states
• 9

  Metro Volume session witness states
• 10

  Communication flow – fracture
• 11

  Failure scenarios with witness

• 1

  Introduction
• 2

  Zero-downtime SAN maintenance and data migration
• 3

  Storage migration for virtual machine migration
• 4

  Disaster avoidance and continuous availability
• 5

  On-demand load distribution

• 1

  Required reading
• 2

  Introduction
• 3

  MPIO
• 4

  Quorum witness
• 5

  SCVMM/SCCM and PRO
• 6

  Cluster Shared Volumes
• 7

  Configuration options and use cases
• 8

  Data path examples
• 9

  Disk Rescans

• 1

  Introduction
• 2

  Requirements for Metro Volume for Linux
• 3

  ALUA optimization
• 4

  Linux MPIO
• 5

  Linux applications with Metro Volume
• 6

  A sample use case for Metro Volume and Red Hat High-Availability Cluster
• 7

  Failure Scenario – Array failure
• 8

  Failure Scenario – Replication link failure
• 9

  Other failure scenarios

• 1

  Summary

• 1

  map-paths.sh script

• 1

  Dell Technologies documentation
• 2

  VMware documentation
• 3

  Red Hat documentation