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

Viewing Automigration Cartridges in the Firesafe, Smart Copy Pool Operations, Editing SMI-S Settings

Page 46 highlights

2. The right hand pane then shows all the automigration virtual cartridges (alphabetically by bar code) in the source libraries and information including the cartridge state, last written date, destination library, and destination slot. Viewing Automigration Cartridges in the Firesafe When a cartridge is ejected from the destination library, its matching virtual cartridge is automatically ejected out of the virtual library and moved into the device's firesafe. The firesafe acts as a virtual offline location for the automigration virtual cartridges. Once they are in the firesafe, the automigration virtual cartridges are retained according to their automigration policies, which define how many days the virtual cartridges remain in the firesafe before being automatically deleted. NOTE: From the Automigration/Replication tab of Command View VLS, the firesafe in the window shows items placed in the firesafe by automigration only; items placed in the firesafe from different functions of the VLS are not shown here. To view cartridges in the firesafe, from the Automigration/Replication tab, select Firesafe from the navigation tree. For mirror copies, the firesafe date is the date of the most recent copy. When the physical tape is moved back into the physical library, the corresponding virtual tape is immediately moved from the firesafe back to the appropriate location (based on the location of the physical tape). The physical tape is not read upon load and is not synchronized to the virtual tape. Therefore, if you have modified the physical tape while it was outside of the library, then it is now out-of-sync with the virtual tape in the firesafe. If you want to keep these modifications to the physical tape, you will need to ensure that the data is copied to the virtual tape. Either manually delete the virtual tape from the firesafe or perform a Load Media for Restore. This forces the system to read the physical tape upon load and causes automigration to create a new virtual copy. See "Restoring from a SAN Physical Cartridge" (page 43). Smart Copy Pool Operations Smart copy allows the backup application to trigger copies from virtual cartridges to destination cartridges, and the VLS then performs that copy inside the device. The backup application can only use this feature if it supports the HP smart copy mechanism (via SMI-S v1.3 or later copy services). Editing SMI-S Settings SMI-S is the communications mechanism between the backup application and smart copy. If your backup application supports smart copy, you will need to link your backup application to the device SMI-S interface. This may require you to modify the device SMI-S security. See "SMI-S Support" (page 117) for SMI-S information. Editing the SMI-S settings is done through the backup application. Creating a Smart Copy Pool Smart copy pools are created from physical library slots after a destination tape library is added to the VLS automigration configuration. Each smart copy pool defines: • The single destination library • The single source virtual library • The slot range • The pool mode - echo copy or smart copy • The number of drives allocated to the pool (for smart copy only) To create a smart copy pool: 46 Automigration/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
  • 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

2.
The right hand pane then shows all the automigration virtual cartridges (alphabetically by bar
code) in the source libraries and information including the cartridge state, last written date,
destination library, and destination slot.
Viewing Automigration Cartridges in the Firesafe
When a cartridge is ejected from the destination library, its matching virtual cartridge is
automatically ejected out of the virtual library and moved into the device's firesafe. The firesafe
acts as a virtual offline location for the automigration virtual cartridges. Once they are in the
firesafe, the automigration virtual cartridges are retained according to their automigration policies,
which define how many days the virtual cartridges remain in the firesafe before being automatically
deleted.
NOTE:
From the
Automigration/Replication
tab of Command View VLS, the firesafe in the window
shows items placed in the firesafe by automigration only; items placed in the firesafe from different
functions of the VLS are not shown here.
To view cartridges in the firesafe, from the
Automigration/Replication
tab, select
Firesafe
from the
navigation tree. For mirror copies, the firesafe date is the date of the most recent copy.
When the physical tape is moved back into the physical library, the corresponding virtual tape is
immediately moved from the firesafe back to the appropriate location (based on the location of
the physical tape). The physical tape is not read upon load and is not synchronized to the virtual
tape. Therefore, if you have modified the physical tape while it was outside of the library, then it
is now out-of-sync with the virtual tape in the firesafe. If you want to keep these modifications to
the physical tape, you will need to ensure that the data is copied to the virtual tape. Either manually
delete the virtual tape from the firesafe or perform a
Load Media for Restore
. This forces the system
to read the physical tape upon load and causes automigration to create a new virtual copy. See
“Restoring from a SAN Physical Cartridge” (page 43)
.
Smart Copy Pool Operations
Smart copy allows the backup application to trigger copies from virtual cartridges to destination
cartridges, and the VLS then performs that copy inside the device. The backup application can
only use this feature if it supports the HP smart copy mechanism (via SMI-S v1.3 or later copy
services).
Editing SMI-S Settings
SMI-S is the communications mechanism between the backup application and smart copy. If your
backup application supports smart copy, you will need to link your backup application to the
device SMI-S interface. This may require you to modify the device SMI-S security. See
“SMI-S
Support” (page 117)
for SMI-S information. Editing the SMI-S settings is done through the backup
application.
Creating a Smart Copy Pool
Smart copy pools are created from physical library slots after a destination tape library is added
to the VLS automigration configuration. Each smart copy pool defines:
The single destination library
The single source virtual library
The slot range
The pool mode – echo copy or smart copy
The number of drives allocated to the pool (for smart copy only)
To create a smart copy pool:
46
Automigration/Replication