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

Backup Application Interaction with Replication

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 22 highlights

In this example, it costs less to use active-active because it adds two replication LTUs but saves the hardware/power/footprint cost of a second rack and the cost of a second VLS connectivity kit. However, if your backups required more than half of the maximum device performance (for example, more than two nodes out of a maximum configuration of four nodes), you may have to deploy two devices per site. In this case, it would be cheaper licensing (and better future device scalability) to use 2x active-passive deployment. NOTE: Multi-hop replication (replicating a cartridge from device A to device B, and then replicating the replicated cartridge from device B to device C) is not yet supported. Backup Application Interaction with Replication The replication in both the VLS and D2D systems is mirroring the source cartridge to its matching target cartridge so both cartridges have the same barcode, the same tape contents, etc. Backup applications currently cannot handle seeing two copies of the same cartridge at the same time (because to the backup application, the cartridge is a single entity in the media database). Given this limitation, you must hide the target virtual library from the source device's backup application: • For VLS systems, the replication target is a subset or an entire virtual library that is presented on front-end Fibre Channel ports, so if the source backup application is running media agents on the target site you either need to use SAN zoning or the device's LUN mapping feature to hide this replication target virtual library from the source device's backup application. • For D2D systems, this is currently automatic because the replication target is hidden from all external host access (until it is converted into a non-replicating library in the event of a disaster recovery). Figure 9 Presenting the Replication Target to a Different Backup Application On a VLS (by default) or a D2D (if you enable the read-only mode on the target library), you can still present the replication target to a different backup application instance ( a separate backup application master/cell server on the target site with its own media database), which you can use to "import" replicated cartridges into its media database and then perform restores or copy to physical tape, etc. See "Creating Archive Tapes from the Target" (page 124) for an example on automating this. 22 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
In this example, it costs less to use active-active because it adds two replication LTUs but saves
the hardware/power/footprint cost of a second rack and the cost of a second VLS connectivity
kit. However, if your backups required more than half of the maximum device performance
(for example, more than two nodes out of a maximum configuration of four nodes), you may
have to deploy two devices per site. In this case, it would be cheaper licensing (and better
future device scalability) to use 2x active-passive deployment.
NOTE:
Multi-hop replication (replicating a cartridge from device A to device B, and then
replicating the replicated cartridge from device B to device C) is not yet supported.
Backup Application Interaction with Replication
The replication in both the VLS and D2D systems is mirroring the source cartridge to its matching
target cartridge so both cartridges have the same barcode, the same tape contents, etc. Backup
applications currently cannot handle seeing two copies of the same cartridge at the same time
(because to the backup application, the cartridge is a single entity in the media database). Given
this limitation, you must hide the target virtual library from the source device’s backup application:
•
For VLS systems, the replication target is a subset or an entire virtual library that is presented
on front-end Fibre Channel ports, so if the source backup application is running media agents
on the target site you either need to use SAN zoning or the device’s LUN mapping feature to
hide this replication target virtual library from the source device’s backup application.
•
For D2D systems, this is currently automatic because the replication target is hidden from all
external host access (until it is converted into a non-replicating library in the event of a disaster
recovery).
Figure 9 Presenting the Replication Target to a Different Backup Application
On a VLS (by default) or a D2D (if you enable the read-only mode on the target library), you can
still present the replication target to a different backup application instance ( a separate backup
application master/cell server on the target site with its own media database), which you can use
to “import” replicated cartridges into its media database and then perform restores or copy to
physical tape, etc. See
“Creating Archive Tapes from the Target” (page 124)
for an example on
automating this.
22
Concepts