HP StorageWorks P2000 HP StorageWorks P2000 G3 MSA System SMU Reference Guide - Page 101

Using Remote Snap to replicate volumes, About the Remote Snap replication feature - g3 fc iscsi

Page 101 highlights

6 Using Remote Snap to replicate volumes About the Remote Snap replication feature Remote Snap replication is a licensed feature for disaster recovery. This feature performs asynchronous (batch) replication of block-level data from a volume on a local storage system to a volume that can be on the same system or on a second, independent system. This second system can be located at the same site as the first system or at a different site. A typical replication configuration involves these physical and logical components: • A host connected to a local storage system (the replication source), which is networked via FC or iSCSI ports to a remote storage system (the replication destination). The required configurations for replication to be fault tolerant are as follows: • Two FC-only systems each with both ports on each of the four controllers connected to an FC switch. • Two FC/iSCSI systems each with both iSCSI ports on each of the four controllers connected to an iSCSI switch. • Two FC/iSCSI systems each with both FC ports on each of the four controllers connected to an FC switch. • Remote system definition. A management object on the local system that enables the MCs in the local system and in the remote system to communicate and exchange data. • Replication set. A source master volume in the local system that is associated with a destination master volume in the remote system for the purpose of replicating data. A replication set can contain only one pair of master volumes. Master volumes in a replication set are also called replication volumes. • External view. The replication volume in a replication set that can be mapped to hosts for external access. A replication set can have only one external-view volume, which is normally the source master volume. For disaster recovery purposes, if a replication set's external-view volume goes offline, the replication destination volume can be designated as the external view. The following figure illustrates three replication sets in use by two hosts: • The host in New York is mapped to and updates the Finance volume. This volume is replicated to the host in Munich. • The host in Munich is mapped to and updates the Sales and Engineering volumes. The Sales volume is replicated from System 2 to System 3 in the Munich DATA center. The Engineering volume is replicated from System 3 in Munich to System 1 in New York. HP StorageWorks P2000 G3 MSA System SMU Reference Guide 101

  • 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

HP StorageWorks P2000 G3 MSA System SMU Reference Guide
101
6
Using Remote Snap to replicate volumes
About the Remote Snap replication feature
Remote Snap replication is a licensed feature for disaster recovery. This feature performs asynchronous
(batch) replication of block-level data from a volume on a local storage system to a volume that can be on
the same system or on a second, independent system.
This second system can be located at the same site
as the first system or at a different site.
A typical replication configuration involves these physical and logical components:
A host connected to a local storage system (the replication source), which is networked via FC or iSCSI
ports to a remote storage system (the replication destination).
The required configurations for replication to be fault tolerant are as follows:
Two FC-only systems each with both ports on each of the four controllers connected to an FC switch.
Two FC/iSCSI systems each with both iSCSI ports on each of the four controllers connected to an
iSCSI switch.
Two FC/iSCSI systems each with both FC ports on each of the four controllers connected to an FC
switch.
Remote system
definition. A management object on the local system that enables the MCs in the local
system and in the remote system to communicate and exchange data.
Replication set
. A source master volume in the local system that is associated with a destination master
volume in the remote system for the purpose of replicating data. A replication set can contain only one
pair of master volumes. Master volumes in a replication set are also called
replication volumes
.
External view
. The replication volume in a replication set that can be mapped to hosts for external
access. A replication set can have only one external-view volume, which is normally the source master
volume. For disaster recovery purposes, if a replication set’s external-view volume goes offline, the
replication destination volume can be designated as the external view.
The following figure illustrates three replication sets in use by two hosts:
The host in New York is mapped to and updates the Finance volume. This volume is replicated to the
host in Munich.
The host in Munich is mapped to and updates the Sales and Engineering volumes. The Sales volume is
replicated from System 2 to System 3 in the Munich DATA center. The Engineering volume is replicated
from System 3 in Munich to System 1 in New York.