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

Using VLS with Multi-data Center Replication to a Common Disaster Recovery Site

Page 70 highlights

Figure 29 Using VLS with Multi-data Center Replication to a Common Disaster Recovery Site Recovery options: Primary site data can be recovered directly from VLS at the primary site. If there is a total disaster at one of the primary sites and all servers and VLS are lost, data can be recovered from the disaster recovery site in several ways: • At the disaster recovery site using a separate backup application master server, data can be recovered to new servers. • A replacement VLS and servers can be installed at the primary site and data can be reverse replicated from the disaster recovery site over the low bandwidth link, although this is not recommended for high volumes of data (TBs) because of the time to replicate data wholesale over a relatively small link speed. • Data can be copied to physical tape at the disaster recovery site then transported to the primary site and imported to new servers and arrays using physical tape at the primary site. Tape could also be copied to the VLS and then recovered from there. Solution advantages: • Automated disaster recovery over cost effective low bandwidth links • Flexible recovery options • Scalable in terms of capacity and performance • Flexible replication implementations: active-to-passive, active-to-active, and many-to-one (up to four) • Very effective disaster recovery consolidation in many-to-one implementation • Only target nodes need to be licenced for replication Solution trade-offs: • Deduplication has to be certified with backup applications and data types. Data Protector, Netbackup, and TSM currently supported. • A one-time initialization process is required the first time replication runs so the source and target can synchronize. For many-to-one implementations this is typically by WAN link of by using Tape Transport. 70 VLS Devices

  • 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

Figure 29 Using VLS with Multi-data Center Replication to a Common Disaster Recovery Site
Recovery options
: Primary site data can be recovered directly from VLS at the primary site. If there
is a total disaster at one of the primary sites and all servers and VLS are lost, data can be recovered
from the disaster recovery site in several ways:
At the disaster recovery site using a separate backup application master server, data can be
recovered to new servers.
A replacement VLS and servers can be installed at the primary site and data can be reverse
replicated from the disaster recovery site over the low bandwidth link, although this is not
recommended for high volumes of data (TBs) because of the time to replicate data wholesale
over a relatively small link speed.
Data can be copied to physical tape at the disaster recovery site then transported to the
primary site and imported to new servers and arrays using physical tape at the primary site.
Tape could also be copied to the VLS and then recovered from there.
Solution advantages
:
Automated disaster recovery over cost effective low bandwidth links
Flexible recovery options
Scalable in terms of capacity and performance
Flexible replication implementations: active-to-passive, active-to-active, and many-to–one (up
to four)
Very effective disaster recovery consolidation in many-to-one implementation
Only target nodes need to be licenced for replication
Solution trade-offs
:
Deduplication has to be certified with backup applications
and
data types. Data Protector,
Netbackup, and TSM currently supported.
A one-time initialization process is required the first time replication runs so the source and
target can synchronize. For many-to-one implementations this is typically by WAN link of by
using Tape Transport.
70
VLS Devices