HP StorageWorks 6000 HP StorageWorks VLS and D2D Solutions Guide (AG306-96028, - Page 44

Benefits of Replication, Considerations of Replication

Get HP StorageWorks 6000 - Virtual Library System PDF manuals and user guides View all HP StorageWorks 6000 manuals
Add to My Manuals
Save this manual to your list of manuals

Page 44 highlights

data instead of the complete data set. This saves time and replication bandwidth, and is one of the most attractive features that deduplication offers. Replication enables better disaster tolerance without the operational costs associated with transporting data off-site on physical tape. See Introduction to Replication. The replication system on both VLS and D2D creates and maintains a cartridge mirror between the source and target devices. Once replication is set up, operations are automatic and seamless to the user. Replication is managed through the firmware on the VLS or D2D, not the backup application. Benefits of Replication • Improves the overall reliability in offsiting data. • Completely automates offsiting data. • Improves the resilience of remote offices and regional data centers while maintaining local data recovery capabilities. • Reduces the overall costs of offsiting data compared to physical tape offsiting when you consider all manual costs. • The replication target library is not visible to the backup application and does not need licensing. • There is no need to license/configure copy jobs in the backup application. Considerations of Replication • The backup application will not be aware of any copy failures. • You cannot have different retention times between the source and target media because cartridges are mirrored. However, with deduplication reducing the amount of disk space required to store tape retention times, you do not generally need different retention times between source and target. • You cannot present both the source and target media to the same backup application at the same time. (See Backup Application Interaction with Replication.) Creating Archive Tapes from the Replication Target Using replication you cannot present both the source and target media to the same backup application at the same time. (See Backup Application Interaction with Replication.) You cannot use automigration (which mirrors whole cartridges) to create the archive tapes because they will have a different barcode, retention time, contents, and potentially a different size from the replication target media. To create archive tapes from the replication target media, you must use a second instance of the backup application to perform this. (See Creating Archive Tapes from the Target.) The backup application must have the ability to "import" tapes created on one backup application domain into another domain (e.g., importing a cartridge from a Data Protector cell server to another cell server). This can be done manually, or it can also be done automatically via a script. On the VLS the script can be driven by an "ISV Email" email report. See Creating Archive Tapes from the Target for details and example scripts. Considerations for Restores There are two restore use models: from tape and from the VLS or D2D. In either case, copies are in native tape format and so can be restored directly. Retention policies drive copy and restore use models. 44 Backup Solution Design Considerations

  • 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
  • 206
  • 207
  • 208
  • 209
  • 210
  • 211
  • 212
  • 213
  • 214
  • 215
  • 216
  • 217
  • 218
data instead of the complete data set. This saves time and replication bandwidth, and is one of the
most attractive features that deduplication offers. Replication enables better disaster tolerance without
the operational costs associated with transporting data off-site on physical tape. See
Introduction to
Replication
.
The replication system on both VLS and D2D creates and maintains a cartridge mirror between the
source and target devices. Once replication is set up, operations are automatic and seamless to the
user. Replication is managed through the firmware on the VLS or D2D, not the backup application.
Benefits of Replication
•
Improves the overall reliability in offsiting data.
•
Completely automates offsiting data.
•
Improves the resilience of remote offices and regional data centers while maintaining local data
recovery capabilities.
•
Reduces the overall costs of offsiting data compared to physical tape offsiting when you consider
all manual costs.
•
The replication target library is not visible to the backup application and does not need licensing.
•
There is no need to license/configure copy jobs in the backup application.
Considerations of Replication
•
The backup application will not be aware of any copy failures.
•
You cannot have different retention times between the source and target media because cartridges
are mirrored. However, with deduplication reducing the amount of disk space required to store
tape retention times, you do not generally need different retention times between source and target.
•
You cannot present both the source and target media to the same backup application at the same
time. (See
Backup Application Interaction with Replication
.)
Creating Archive Tapes from the Replication Target
Using replication you cannot present both the source and target media to the same backup application
at the same time. (See
Backup Application Interaction with Replication
.) You cannot use automigration
(which mirrors whole cartridges) to create the archive tapes because they will have a different barcode,
retention time, contents, and potentially a different size from the replication target media. To create
archive tapes from the replication target media, you must use a second instance of the backup
application to perform this. (See
Creating Archive Tapes from the Target
.)
The backup application must have the ability to
“
import
”
tapes created on one backup application
domain into another domain (e.g., importing a cartridge from a Data Protector cell server to another
cell server). This can be done manually, or it can also be done automatically via a script. On the VLS
the script can be driven by an
“
ISV Email
”
email report. See
Creating Archive Tapes from the Target
for details and example scripts.
Considerations for Restores
There are two restore use models: from tape and from the VLS or D2D. In either case, copies are in
native tape format and so can be restored directly. Retention policies drive copy and restore use
models.
Backup Solution Design Considerations
44