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

NetBackup Deduplication Guidelines, NetBackup Import Example Script

Page 198 highlights

NetBackup Deduplication Guidelines In addition to the NetBackup general guidelines, the following guidelines apply to a VLS with deduplication enabled: • NetBackup raw/image file backups: NetBackup raw file backups will only deduplicate if the differencing algorithm for the corresponding policy is set to Backup-level. If the policy for these files is set to File-level, these files will not be deduplicated. • NetBackup catalog backups: NetBackup catalog backups, which consist of the image record files containing the information about the backups, will not deduplicate. • Volume pools: Use as few as possible to quickly fill up tapes. • Turn Off NetBackup Checkpoint: The NetBackup Checkpoint option creates a duplicate backup set with a duplicate name. This prevents the VLS from deduplicating data with that policy because it cannot process duplicate backup sets. You must turn off the NetBackup Checkpoint option for deduplication to work. • Disable multiplexing in Oracle RMAN backups: In the VLS firmware version 3.3.0 (or higher) the scripting requirements for Oracle data files have been relaxed, so it is no longer mandatory to assign prefix naming conventions to Oracle data files to make sure the data is properly deduplicated. The minimum requirement for RMAN to deduplicate efficiently is to disable multiplexing (where you have multiple RMAN streams concurrently writing to the same drive). You can disable multiplexing by setting FILESPERSET=1 for each database backup in the RMAN scripts (not needed for archive logs or control files). You can define additional channels to increase the number of parallel backup processes running with FILESPERSET=1 to generate the same RMAN performance as before, so that each stream goes to a different virtual tape drive. The following RMAN settings will not deduplicate because they always generate totally unique data every backup: • Incremental backups • RMAN compressed backups • RMAN encryption NOTE: If you had previously configured the prefix naming conventions in your Oracle RMAN scripts, this will continue to deduplicate efficiently with the firmware version 3.3.0 (or higher), but you should ensure that multiplexing is disabled as well. If you wish to remove the prefix naming conventions, you will need to rename the backup job name in NetBackup. (New backup jobs will not deduplicate against the previous jobs with the different job name.) NetBackup Import Example Script The following section details a script to perform the tape import commands for Symantec NetBackup. The input to the script is the ISV Import email report (containing a list of cartridges by /barcode/library/slot that were successfully replicated and thus are ready for import). This example uses a Linux server client which contains the Email Processing Example Script) and has CLI access to the NetBackup CLI. The virtual library on the VLS target device has been presented to NetBackup over Fibre Channel and configured in NetBackup as a tape library with tape drives. To perform the import you must define the target virtual library in NetBackup terms with a robot type and robot number. For example, create a libmap_filecontaining entries with the library serial number, library type, and library number: DEC06150U7~TLD~2 198 Virtual Library 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

NetBackup Deduplication Guidelines
In addition to the NetBackup general guidelines, the following guidelines apply to a VLS with
deduplication enabled:
NetBackup raw/image file backups: NetBackup raw file backups will only deduplicate if the dif-
ferencing algorithm for the corresponding policy is set to Backup-level. If the policy for these files
is set to File-level, these files will not be deduplicated.
NetBackup catalog backups: NetBackup catalog backups, which consist of the image record files
containing the information about the backups, will not deduplicate.
Volume pools: Use as few as possible to quickly fill up tapes.
Turn Off NetBackup Checkpoint: The NetBackup Checkpoint option creates a duplicate backup
set with a duplicate name. This prevents the VLS from deduplicating data with that policy because
it cannot process duplicate backup sets. You must turn off the NetBackup Checkpoint option for
deduplication to work.
Disable multiplexing in Oracle RMAN backups: In the VLS firmware version 3.3.0 (or higher) the
scripting requirements for Oracle data files have been relaxed, so it is no longer mandatory to
assign prefix naming conventions to Oracle data files to make sure the data is properly deduplic-
ated. The minimum requirement for RMAN to deduplicate efficiently is to disable multiplexing
(where you have multiple RMAN streams concurrently writing to the same drive). You can disable
multiplexing by setting
FILESPERSET=1
for each database backup in the RMAN scripts (not
needed for archive logs or control files). You can define additional channels to increase the number
of parallel backup processes running with
FILESPERSET=1
to generate the same RMAN perform-
ance as before, so that each stream goes to a different virtual tape drive.
The following RMAN settings will not deduplicate because they always generate totally unique
data every backup:
Incremental backups
RMAN compressed backups
RMAN encryption
NOTE:
If you had previously configured the prefix naming conventions in your Oracle RMAN scripts, this
will continue to deduplicate efficiently with the firmware version 3.3.0 (or higher), but you should
ensure that multiplexing is disabled as well. If you wish to remove the prefix naming conventions,
you will need to rename the backup job name in NetBackup. (New backup jobs will not deduplicate
against the previous jobs with the different job name.)
NetBackup Import Example Script
The following section details a script to perform the tape import commands for Symantec NetBackup.
The input to the script is the ISV Import email report (containing a list of cartridges by
/barcode/library/slot that were successfully replicated and thus are ready for import). This example
uses a Linux server client which contains the
Email Processing Example Script
) and has CLI access to
the NetBackup CLI. The virtual library on the VLS target device has been presented to NetBackup over
Fibre Channel and configured in NetBackup as a tape library with tape drives. To perform the import
you must define the target virtual library in NetBackup terms with a robot type and robot number. For
example, create a
libmap_file
containing entries with the library serial number, library type, and
library number:
DEC06150U7~TLD~2
Virtual Library Systems
198