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

Migrating your Existing Backup Data, Configuration and Reporting, Waiting for Next Backup

Page 155 highlights

There are three licenses available, one for each VLS platform - VLS6000-series, VLS9000-series, and VLS12000 Gateway. See Table 24. Table 24 Required Deduplication Licenses by Platform Platform VLS6000-series Deduplication licenses required One license per MSA20 for 250 or 500 GB drives Two licenses per MSA20 for 750 GB drives Two licenses per MSA20 for 1 TB drives VLS9000-series 7.5 and 10 TB systems One license per base unit One license per expansion kit1 VLS9000-series Three licenses for 30 TB capacity Four licenses for 40 TB capacity VLS12000-series Gateway One license per 2 TB EVA LUN 1The VLS9000 7.5 TB system does not require a license for a third expansion kit because the first two expansion kit licenses cover the storage provided by the third kit. Migrating your Existing Backup Data If you are enabling deduplication on an already active VLS, the following process can be used to retain your existing backup data (stored before deduplication was enabled) and gradually overwrite it with new backups that will then be deduplicated. This is because deduplication only works on backups that are stored after deduplication was enabled. After you enable deduplication on your VLS and perform all the preparation steps: 1. Perform your normal backups. 2. Wait one data retention cycle for all the existing virtual cartridges to be expired by the backup application and then rewritten with new backup data. If there are cartridges that would not normally expire, you may need to manually expire them to force them to be reused. At the beginning of the next retention cycle, all of your old backup data should have been overwritten with new backup data that has been deduplicated (freeing up disk space). 3. Once all the existing virtual cartridges have been rewritten and deduplicated, you can extend your retention policy for your backup jobs to take advantage of the deduplication. Configuration and Reporting Accelerated deduplication is aware of the backup contents of tapes. Therefore, you have reporting and policy control options available over the deduplication process. You can: • Enable and disable deduplication by backup job type or individual backup job. • Switch from backup to File-level differencing for file server backup jobs. • View deduplication status and statistics per backup job, by backup job type, or by cartridge. • View a detailed breakdown of the capacity used by reference data, deduplicated data, data awaiting deduplication, and metadata. The deduplication reports show the following states: Waiting for Next Backup - the backup has nothing to difference against and is therefore waiting for a new backup. Incr/diff backups difference against the new full backup, not the old full backup. HP StorageWorks VLS and D2D Solutions Guide 155

  • 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

There are three licenses available, one for each VLS platform
VLS6000
series, VLS9000
series,
and VLS12000 Gateway. See
Table 24
.
Table 24 Required Deduplication Licenses by Platform
Deduplication licenses required
Platform
One license per MSA20 for 250 or 500 GB drives
Two licenses per MSA20 for 750 GB drives
Two licenses per MSA20 for 1 TB drives
VLS6000
series
One license per base unit
One license per expansion kit
1
VLS9000
series 7.5 and 10 TB systems
Three licenses for 30 TB capacity
Four licenses for 40 TB capacity
VLS9000
series
One license per 2 TB EVA LUN
VLS12000
series Gateway
1
The VLS9000 7.5 TB system does not require a license for a third expansion kit because the first two expansion kit licenses
cover the storage provided by the third kit.
Migrating your Existing Backup Data
If you are enabling deduplication on an already active VLS, the following process can be used to
retain your existing backup data (stored before deduplication was enabled) and gradually overwrite
it with new backups that will then be deduplicated. This is because deduplication only works on
backups that are stored after deduplication was enabled.
After you enable deduplication on your VLS and perform all the preparation steps:
1.
Perform your normal backups.
2.
Wait one data retention cycle for all the existing virtual cartridges to be expired by the backup
application and then rewritten with new backup data. If there are cartridges that would not
normally expire, you may need to manually expire them to force them to be reused. At the
beginning of the next retention cycle, all of your old backup data should have been overwritten
with new backup data that has been deduplicated (freeing up disk space).
3.
Once all the existing virtual cartridges have been rewritten and deduplicated, you can extend
your retention policy for your backup jobs to take advantage of the deduplication.
Configuration and Reporting
Accelerated deduplication is aware of the backup contents of tapes. Therefore, you have reporting
and policy control options available over the deduplication process. You can:
Enable and disable deduplication by backup job type or individual backup job.
Switch from backup to File-level differencing for file server backup jobs.
View deduplication status and statistics per backup job, by backup job type, or by cartridge.
View a detailed breakdown of the capacity used by reference data, deduplicated data, data
awaiting deduplication, and metadata.
The deduplication reports show the following states:
Waiting for Next Backup
the backup has nothing to difference against and is therefore waiting
for a new backup. Incr/diff backups difference against the new full backup, not the old full backup.
HP StorageWorks VLS and D2D Solutions Guide
155