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

D2D Blueprints, Single Site Cost Effective Backup Device Consolidation

Page 60 highlights

• Overwrite vs. append: Overwriting and appending to cartridges is also where virtual tape has an advantage. With physical media you may want to append multiple backup jobs to a single cartridge in order to reduce media costs; the downside is that cartridges cannot be overwritten until the retention policy for the last backup on that cartridge has expired. With virtual tape, you can configure a large number of cartridges for "free" and you can configure their sizes appropriately to the amount of data stored in a specific backup. Therefore, appended backups provide no benefit. (This does not apply to VLS deduplication where appending is required to fill up tapes and perform space reclamation on them.) Considering the above factors, the following provides an example of a good rotation scheme. This user requires weekly full backups sent offsite and recovery point objectives of every day in the last week, every week in the last month, every month in the last year, and every year in the last five years: • Four daily backup cartridges, Monday to Thursday, incremental backup, overwritten every week. • Four weekly backup cartridges, on Fridays, full backup, overwritten every fifth week. • 12 monthly backup cartridges, last Friday of the month, overwritten every 13th month. • Five yearly backup cartridges, last day of the year, overwritten every five years. In the steady state daily backups will be small, and while they will always overwrite the last week the amount of data overwritten will be small. Weekly full backups will always overwrite, but housekeeping has plenty of time to run over the following day or weekend; the same is true for monthly and yearly backups. The user can also offload a full backup to physical tape every week, month, and year after the full backup runs for offsite storage. D2D Blueprints The following blueprints of D2D virtual tape libraries with deduplication and replication start from specifying company requirements, then defining the HP blueprint for the solution, and finally defining any solution caveats or ISV dependencies associated with the solution. This will help you make informed decisions and allow you to quickly assess areas of concern and possible implementations. Single Site Cost Effective Backup Device Consolidation Company requirements: small site with fewer than 6 servers, fewer than 5 TB, no SAN, wants a single device for backup that can grow with the business. Solution: HP D2D Backup System (iSCSI) with Tape Offload, typically used with HP Data Protector Express or Symantec Backup Exec Caveats: The smaller D2D units shown here are a fixed size and not directly expandable in capacity. The initial sizing is very important. ISVs: HP Data Protector Express or Symantec Backup Exec are typical backup applications in this segment. See http://www.hp.com/go/connect and http://www.hp.com/go/ebs. 60 D2D Systems

  • 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

Overwrite vs. append: Overwriting and appending to cartridges is also where virtual tape has
an advantage. With physical media you may want to append multiple backup jobs to a single
cartridge in order to reduce media costs; the downside is that cartridges cannot be overwritten
until the retention policy for the last backup on that cartridge has expired. With virtual tape, you
can configure a large number of cartridges for
free
and you can configure their sizes appropri-
ately to the amount of data stored in a specific backup. Therefore, appended backups provide
no benefit. (This does not apply to VLS deduplication where appending is required to fill up tapes
and perform space reclamation on them.)
Considering the above factors, the following provides an example of a good rotation scheme. This
user requires weekly full backups sent offsite and recovery point objectives of every day in the last
week, every week in the last month, every month in the last year, and every year in the last five years:
Four daily backup cartridges, Monday to Thursday, incremental backup, overwritten every week.
Four weekly backup cartridges, on Fridays, full backup, overwritten every fifth week.
12 monthly backup cartridges, last Friday of the month, overwritten every 13th month.
Five yearly backup cartridges, last day of the year, overwritten every five years.
In the steady state daily backups will be small, and while they will always overwrite the last week the
amount of data overwritten will be small. Weekly full backups will always overwrite, but housekeeping
has plenty of time to run over the following day or weekend; the same is true for monthly and yearly
backups. The user can also offload a full backup to physical tape every week, month, and year after
the full backup runs for offsite storage.
D2D Blueprints
The following blueprints of D2D virtual tape libraries with deduplication and replication start from
specifying company requirements, then defining the HP blueprint for the solution, and finally defining
any solution caveats or ISV dependencies associated with the solution. This will help you make informed
decisions and allow you to quickly assess areas of concern and possible implementations.
Single Site Cost Effective Backup Device Consolidation
Company requirements
: small site with fewer than 6 servers, fewer than 5 TB, no SAN, wants a single
device for backup that can grow with the business.
Solution
: HP D2D Backup System (iSCSI) with Tape Offload, typically used with HP Data Protector
Express or Symantec Backup Exec
Caveats
: The smaller D2D units shown here are a fixed size and not directly expandable in capacity.
The initial sizing is very important.
ISVs
: HP Data Protector Express or Symantec Backup Exec are typical backup applications in this
segment. See
h
t
tp://w
w
w
.hp
.co
m/go/co
nnec
t
and
h
t
tp://w
w
w
.hp
.co
m/go/eb
s
.
D2D Systems
60