HP 12000 HP VLS Solutions Guide Design Guidelines for Virtual Library Systems - Page 20

Replication Deployment Options, secondary disaster recovery copy of the backup data

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

Page 20 highlights

NOTE: T1/T3 and OC12 are old terms with respect to WAN link terminology. Many link providers use their own names (for example, IP Clear and Etherflow). This document distinguishes them by their speed using 2 Mbits/sec, 50 Mbits/sec, etc. One consideration with replication is that you must "initialize" the Virtual Tape Libraries with data prior to starting the replication. This ensures that the source and target devices are both synchronized with the relevant reference data to allow them to interpret the changed data (deltas) that comes across the WAN link during replication. Replication Deployment Options You can deploy the HP VLS and D2D systems for replication in many ways depending on your requirements. You should understand the terminology associated with deduplication and replication. The key terminology for replication deployment: • Source: A series of slots/cartridges in a virtual library that act as the source data to replicate. This is the original copy of the backup data, written to and managed by the source site's backup application. • Target or LAN/WAN destination: A series of corresponding slots in another virtual library on another site in another location which receives data from the source library. This is the secondary (disaster recovery) copy of the backup data, managed by the replication system. For both HP VLS and D2D systems, the unit of replication is a virtual cartridge and the replication link is TCP/IP (one GbE connection per node on the VLS system, and one to two GbE connections on the D2D system). Figure 8 (page 21) shows how you can configure the system to replicate all of the cartridges or just a subset of cartridges from the source virtual library to the target virtual library. 20 Concepts

  • 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
NOTE:
T1/T3 and OC12 are old terms with respect to WAN link terminology. Many link providers
use their own names (for example, IP Clear and Etherflow). This document distinguishes them by
their speed using 2 Mbits/sec, 50 Mbits/sec, etc.
One consideration with replication is that you must “initialize” the Virtual Tape Libraries with data
prior to starting the replication. This ensures that the source and target devices are both synchronized
with the relevant reference data to allow them to interpret the changed data (deltas) that comes
across the WAN link during replication.
Replication Deployment Options
You can deploy the HP VLS and D2D systems for replication in many ways depending on your
requirements. You should understand the terminology associated with deduplication and replication.
The key terminology for replication deployment:
•
Source: A series of slots/cartridges in a virtual library that act as the source data to replicate.
This is the original copy of the backup data, written to and managed by the source site’s
backup application.
•
Target or LAN/WAN destination: A series of corresponding slots in another virtual library on
another site in another location which receives data from the source library. This is the
secondary (disaster recovery) copy of the backup data, managed by the replication system.
For both HP VLS and D2D systems, the unit of replication is a virtual cartridge and the replication
link is TCP/IP (one GbE connection per node on the VLS system, and one to two GbE connections
on the D2D system).
Figure 8 (page 21)
shows how you can configure the system to replicate all
of the cartridges or just a subset of cartridges from the source virtual library to the target virtual
library.
20
Concepts