HP P2000 HP P2000 G3 MSA System SMU Reference Guide - Page 109

Replication actions

Get HP P2000 PDF manuals and user guides View all HP P2000 manuals
Add to My Manuals
Save this manual to your list of manuals

Page 109 highlights

NOTE: Because replication is not synchronous (continuous), data in a secondary volume is only as current as the last replication that completed successfully. Replications can be performed manually or scheduled. Snapshot operations are I/O-intensive. Every write to a unique location in a master volume after a snapshot is taken will cause an internal read and write operation to occur in order to preserve the snapshot data. If you intend to create snapshots of, create volume copies of, or replicate volumes in a vdisk, ensure that the vdisk contains no more than four master volumes, snap pools, or both. For example: 2 master volumes and 2 snap pools; 3 master volumes and 1 snap pool; 4 master volumes and 0 snap pools. Replication actions The following figure illustrates actions that occur during a series of replications from System 1 to System 2. 1 Take initial snapshot and initiate replication. 6 Second snapshot taken on secondary volume. This is 2 Initial replication consists of a full data copy. the second sync point. 3 Take second snapshot and request replication. This 7 Other snapshots can be taken and replication initiated can be taken while the initial replication is in progress. on the primary volume while replication is in progress. 4 Snapshot taken on secondary volume. This is the first replication sync point. These snapshots are queued waiting for prior replications to complete. These replication snapshots will not become sync points until their replications are 5 When the initial replication is complete, the second complete. replication automatically starts. Only the data changed since Snap 1 is replicated. Figure 5 Actions that occur during a series of replications HP P2000 G3 MSA System SMU Reference Guide 109

  • 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
  • 143
  • 144
  • 145
  • 146
  • 147
  • 148
  • 149
  • 150
  • 151
  • 152
  • 153
  • 154
  • 155
  • 156
  • 157
  • 158
  • 159
  • 160
HP P2000 G3 MSA System SMU Reference Guide
109
NOTE:
Because replication is not synchronous (continuous), data in a secondary volume is only as current
as the last replication that completed successfully. Replications can be performed manually or scheduled.
Snapshot operations are I/O-intensive. Every write to a unique location in a master volume after a
snapshot is taken will cause an internal read and write operation to occur in order to preserve the snapshot
data. If you intend to create snapshots of, create volume copies of, or replicate volumes in a vdisk, ensure
that the vdisk contains no more than four master volumes, snap pools, or both. For example: 2 master
volumes and 2 snap pools; 3 master volumes and 1 snap pool; 4 master volumes and 0 snap pools.
Replication actions
The following figure illustrates actions that occur during a series of replications from System 1 to System 2.
Figure 5
Actions that occur during a series of replications
1
Take initial snapshot and initiate replication.
2
Initial replication consists of a full data copy.
3
Take second snapshot and request replication. This
can be taken while the initial replication is in progress.
4
Snapshot taken on secondary volume. This is the first
replication sync point.
5
When the initial replication is complete, the second
replication automatically starts. Only the data
changed since Snap 1 is replicated.
6
Second snapshot taken on secondary volume. This is
the second sync point.
7
Other snapshots can be taken and replication initiated
on the primary volume while replication is in progress.
These snapshots are queued waiting for prior
replications to complete. These replication snapshots
will not become sync points until their replications are
complete.