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

Optimum Record Sizing, Optimizing File Server Deduplication, Backup sets less than 1 MB in size.

Page 159 highlights

2 X X Y Y 3 X X Y 4 X X X 5 X X 6 X X 7 X 8 X X = node for backup and restore, Y = node for deduplication processing only. Note: the maximum deduplication configuration currently supports four nodes. Optimum Record Sizing You must configure your backup application to use a record size (i.e., tape block size) of 256 KB when using deduplication. Optimizing File Server Deduplication There are many reasons why you may get a low deduplication compression ratio. For example, deduplication does not occur on: • Files less than 32 KB in size for File-level deduplication. • Files less than 8 KB in size for Backup-level deduplication. • File names that keep changing (e.g., some database dumps). • Backup sets less than 1 MB in size. If your file server contains the above items, it will not deduplicate efficiently. In these cases, switch from File-level to Backup-level deduplication for more optimal results. NOTE: Deduplication statistics and reports only include the data that is eligible for deduplication. For example, deduplication does not occur on unsupported formats. Therefore, that data is not included in the reports. NOTE: For database flat file backups that have static file names (such as Oracle file backups), with VLS firmware 3.1.2 or higher you do not need to manually change from File-level differencing to Backup-level differencing because optimum performance and deduplication ratios for database file backups are achieved with the default File-level differencing setting. This does not apply to standard file backups or database file backups with varying names (such as database dump files created with a Back Up Database Task within an SQL Maintenance Plan) where you still need to switch to Backup-level differencing in the cases listed above. HP StorageWorks VLS and D2D Solutions Guide 159

  • 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

Y
Y
X
X
2
Y
X
X
3
X
X
X
4
X
X
5
X
X
6
X
7
X
8
X = node for backup and restore, Y = node for deduplication processing only.
Note: the maximum deduplication configuration currently supports four nodes.
Optimum Record Sizing
You must configure your backup application to use a record size (i.e., tape block size) of 256 KB
when using deduplication.
Optimizing File Server Deduplication
There are many reasons why you may get a low deduplication compression ratio.
For example, deduplication does not occur on:
Files less than 32 KB in size for File-level deduplication.
Files less than 8 KB in size for Backup-level deduplication.
File names that keep changing (e.g., some database dumps).
Backup sets less than 1 MB in size.
If your file server contains the above items, it will not deduplicate efficiently.
In these cases, switch from File-level to Backup-level deduplication for more optimal results.
NOTE:
Deduplication statistics and reports only include the data that is eligible for deduplication. For example,
deduplication does not occur on unsupported formats. Therefore, that data is not included in the
reports.
NOTE:
For database flat file backups that have static file names (such as Oracle file backups), with VLS
firmware 3.1.2 or higher you do not need to manually change from File-level differencing to
Backup-level differencing because optimum performance and deduplication ratios for database file
backups are achieved with the default File-level differencing setting. This does not apply to standard
file backups or database file backups with varying names (such as database dump files created with
a Back Up Database Task within an SQL Maintenance Plan) where you still need to switch to
Backup-level differencing in the cases listed above.
HP StorageWorks VLS and D2D Solutions Guide
159