HP 12000 HP 12200 Gateway Virtual Library System User Guide (BW403-10001, June - Page 33

Automigration/Replication, Understanding Automigration Concepts, Echo Copy Concepts

Page 33 highlights

5 Automigration/Replication Instead of the preferred method of copying virtual media to physical media via the backup application, another option is to perform transparent tape migration via the VLS device using automigration. Automigration describes the feature in which the Virtual Library System acts as a tape copy engine that transfers data from virtual cartridges on disk to a physical tape library connected to the VLS device. The VLS automigration feature supports two different schemes: • Echo copy automatically synchronizes the physical cartridges to matching virtual cartridges (with the same barcodes) based on user-defined policies, and is totally transparent to the backup application. • Using smart copy, the automigration process is under the control of the backup application, managed via the VLS SMI-S interface. This requires the backup application to support the HP smart copy interface. You can also copy virtual media using replication. Replication provides automigration from the source VLS across the LAN/WAN to a remote virtual destination library. See "Replication Concepts" (page 35). This section describes automigration topics from overall automigration concepts to specific operations you can perform on your system. NOTE: Throughout the automigration windows, a SAN library refers to a destination library that is connected to the source library through the SAN and uses the automigration feature. A LAN/WAN library refers to a remote destination library that is connected to the source through the LAN/WAN and uses the replication feature. NOTE: When a list of slots is displayed, the message, "[#] items found, displaying 1 to 20." appears. If there are more than 20 items found, scroll through them using the arrows pointing right and left at the far right-hand side at the top of the list. Also, in some cases, only available slots or only slots containing tapes appear in the list. NOTE: For each procedure described in this chapter, at least one means of access to the relevant screen or menu is specified. However, links are often provided in the main window that can be used as a shortcut to other windows or menus. Understanding Automigration Concepts Before using automigration, review the information in this section. This will allow you to create copy pools and automigration policies appropriate to meet your storage needs. Echo Copy Concepts Echo copy acts as a transparent disk cache to the physical library, so that the backup application writes to virtual cartridges in the virtual library. Automigration then automatically schedules the copies from virtual cartridges to physical cartridges with matching barcodes, based on the automigration policies the user establishes. Echo copy is managed through the automigration software, not the backup application. For that reason: • The destination library is not visible to the backup application, so it does not need licensing. • Copy traffic is no longer routed through the SAN. • All destination tapes created by echo copy are in the native tape format, so they can be restored directly from any tape drive or library that is visible to the backup application. When determining whether to use echo copy pools, remember: Understanding Automigration Concepts 33

  • 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
  • 161
  • 162
  • 163
  • 164
  • 165
  • 166
  • 167
  • 168
  • 169
  • 170
  • 171
  • 172
  • 173
  • 174
  • 175
  • 176
  • 177
  • 178
  • 179
  • 180
  • 181
  • 182
  • 183
  • 184
  • 185
  • 186
  • 187
  • 188
  • 189
  • 190
  • 191
  • 192
  • 193
  • 194
  • 195
  • 196
  • 197
  • 198
  • 199
  • 200
  • 201
  • 202
  • 203
  • 204
  • 205

5 Automigration/Replication
Instead of the preferred method of copying virtual media to physical media via the backup
application, another option is to perform transparent tape migration via the VLS device using
automigration
. Automigration describes the feature in which the Virtual Library System acts as a
tape copy engine that transfers data from virtual cartridges on disk to a physical tape library
connected to the VLS device. The VLS automigration feature supports two different schemes:
Echo copy
automatically synchronizes the physical cartridges to matching virtual cartridges
(with the same barcodes) based on user-defined policies, and is totally transparent to the
backup application.
Using
smart copy
, the automigration process is under the control of the backup application,
managed via the VLS SMI-S interface. This requires the backup application to support the HP
smart copy interface.
You can also copy virtual media using
replication
. Replication provides automigration from the
source VLS across the LAN/WAN to a remote virtual destination library. See
“Replication
Concepts” (page 35)
.
This section describes automigration topics from overall automigration concepts to specific operations
you can perform on your system.
NOTE:
Throughout the automigration windows, a
SAN library
refers to a destination library that
is connected to the source library through the SAN and uses the automigration feature. A
LAN/WAN
library
refers to a remote destination library that is connected to the source through the LAN/WAN
and uses the replication feature.
NOTE:
When a list of slots is displayed, the message, “[#] items found, displaying 1 to 20.”
appears. If there are more than 20 items found, scroll through them using the arrows pointing right
and left at the far right-hand side at the top of the list. Also, in some cases, only available slots or
only slots containing tapes appear in the list.
NOTE:
For each procedure described in this chapter, at least one means of access to the relevant
screen or menu is specified. However, links are often provided in the main window that can be
used as a shortcut to other windows or menus.
Understanding Automigration Concepts
Before using automigration, review the information in this section. This will allow you to create
copy pools and automigration policies appropriate to meet your storage needs.
Echo Copy Concepts
Echo copy acts as a transparent disk cache to the physical library, so that the backup application
writes to virtual cartridges in the virtual library. Automigration then automatically schedules the
copies from virtual cartridges to physical cartridges with matching barcodes, based on the
automigration policies the user establishes.
Echo copy is managed through the automigration software, not the backup application. For that
reason:
The destination library is not visible to the backup application, so it does not need licensing.
Copy traffic is no longer routed through the SAN.
All destination tapes created by echo copy are in the native tape format, so they can be
restored directly from any tape drive or library that is visible to the backup application.
When determining whether to use echo copy pools, remember:
Understanding Automigration Concepts
33