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

Physical Tape Initialization, VLS Initialization using Physical Tape

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

You must decide whether to use the tape initialization process when initially configuring the VLS replication (when creating the echo copy pool). If tape initialization is not selected, WAN or co-location initialization will be performed over LAN/WAN. Physical Tape Initialization Because in enterprise backup environments the initial backups can be quite large (many TB), in most cases it will be impractical to perform tape transfers using the low bandwidth link (because it would take weeks to replicate the first backup). Tape transfer via co-location at a site might also be impractical because of the size and space requirements of the VLS units and inter-site shipment logistics, or because both devices are always busy (for example, when using active-active or many-to-one deployments). The most popular method for initialization on VLS systems is via physical tape transfer as shown in the following diagram: Figure 48 VLS Initialization using Physical Tape This shows how using the export/import pools function within the VLS replication GUI creates a stack of tapes that can be used to populate the deduplication store at the target (destination library). To implement this way of tape transfer, you must select "Initialize via Tape Transport" when creating the echo copy pools. You must prepare for tape initialization by plugging an HP Fibre Channel-attached tape library (MSL, EML, ESL-E) into the storage ports of the VLS device. (For a VLS9000 this would plug into the internal Fibre Channel switches inside the device, for a VLS12000 this would plug into the same Fibre Channel SAN zones containing the EVA arrays, and for the VLS6200/6600 this would require switching 1-2 of the front-end Fibre Channel ports to be back-end storage ports.) Then add this tape library as a "SAN Destination Library" in the Automigration tab. The tape initialization process can be started when the first full backup performed after replication configuration has successfully run to the source device (backups that existed before the replication configuration are not replicated). You can then trigger the tape initialization using the "Initiate Tape Transport" option as shown in the following Command View VLS management GUI screen 106 Replication

  • 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
You must decide whether to use the tape initialization process when initially configuring the VLS
replication (when creating the echo copy pool). If tape initialization is not selected, WAN or
co-location initialization will be performed over LAN/WAN.
Physical Tape Initialization
Because in enterprise backup environments the initial backups can be quite large (many TB), in
most cases it will be impractical to perform tape transfers using the low bandwidth link (because
it would take weeks to replicate the first backup). Tape transfer via co-location at a site might also
be impractical because of the size and space requirements of the VLS units and inter-site shipment
logistics, or because both devices are always busy (for example, when using active-active or
many-to-one deployments). The most popular method for initialization on VLS systems is via physical
tape transfer as shown in the following diagram:
Figure 48 VLS Initialization using Physical Tape
This shows how using the export/import pools function within the VLS replication GUI creates a
stack of tapes that can be used to populate the deduplication store at the target (destination library).
To implement this way of tape transfer, you must select “Initialize via Tape Transport” when creating
the echo copy pools.
You must prepare for tape initialization by plugging an HP Fibre Channel-attached tape library
(MSL, EML, ESL-E) into the storage ports of the VLS device. (For a VLS9000 this would plug into
the internal Fibre Channel switches inside the device, for a VLS12000 this would plug into the
same Fibre Channel SAN zones containing the EVA arrays, and for the VLS6200/6600 this would
require switching 1-2 of the front-end Fibre Channel ports to be back-end storage ports.) Then add
this tape library as a “SAN Destination Library” in the Automigration tab.
The tape initialization process can be started when the first full backup performed after replication
configuration has successfully run to the source device (backups that existed before the replication
configuration are not replicated). You can then trigger the tape initialization using the “Initiate
Tape Transport” option as shown in the following Command View VLS management GUI screen
106
Replication