HP 12000 HP VLS Solutions Guide Design Guidelines for Virtual Library Systems - Page 137

Data Protector Deduplication Guidelines, DPWIN_00426, SSPNT610_012, InitOnLoosePolicy=1

Page 137 highlights

Data Protector Deduplication Guidelines In addition to the Data Protector general guidelines, the following guidelines apply to a VLS with deduplication enabled: • Patch all Windows clients: HP Data Protector on Windows clients requires a software fix to eliminate 56 KB file fragments that diminish deduplication performance on VLS and D2D products. The fix depends on your version of Data Protector: ◦ DP 6.0: install the patch DPWIN_00426 (or later patches). Download the patch from the HP website on the Data Protector version 6.0 "Download drivers and software" page. ◦ DP 6.1: included in the 6.11 service pack. If this is not yet available, request SSPNT610_012 (which you can automatically deploy to all Windows Disk Agent clients) through the Data Protector support channel. • Patch all clients running the Oracle database backup agent so the VLS will correctly identify incremental backups (instead of treating them as full backups). The latest Oracle patch for Data Protector 6.11 is Patch DPWIN_00486. • Oracle RMAN Scripting: See Oracle RMAN Scripting for details. • Tape Retention Planning: Create media pools based on retention period. Mixing retention periods will prevent cartridge expiration reclamation and leads to poor storage utilization. Space used for the shorter retention backup is not reclaimed until all backups on the tape are expired. That is, the backup application cannot reuse/reformat the tape until all backups have exceeded their protection period. The backup application will not reuse expired cartridges until all spare formatted virtual cartridges are used, so in this case HP recommends either removing unneeded virtual cartridges or creating a script on the cell server to automatically reformat expired cartridges on a regular basis. • Allocate Unformatted Media First: If you have deduplication enabled, you should disable the "Allocate unformatted media first" option in the media pool. You must also set the global variable InitOnLoosePolicy=1 defined in the global file and the Data Protector services must be restarted for the global variable to take effect. In HPUX the file is located in /etc/ opt/omni/server/options/global, and in Windows the file is located in C:\Program Files\OmniBack\Config\Server\Options\global. These settings prevents Data Protector from using all available blank cartridges for backups before it starts overwriting expired/scratch cartridges; creating too many virtual cartridges results in the device disk capacity filling up. • Interactive backups will not deduplicate: If you edit a Data Protector backup specification and then manually run it from the GUI without saving it, the backup session will run with a backup specification name of 'Interactive' and therefore will not deduplicate. This is because deduplication correlates backup versions using the backup specification name. • Different backup job names for the same data: Some Data Protector configurations have different backup job names for backing up the same data due to having different retention times for the different backup types (for example, different job names for full backups vs. incremental backups, or different names for weekly full backups vs. monthly full backups). However, because the backups have different backup job names they will not deduplicated against each other even though they contain exactly the same data. To address this, VLS firmware versions 3.3.0 and higher include a GUI option called "Edit Data Protector Configuration" (in the System Maintenance screen). This option allows you to enter suffixes that will be stripped off the end of the Data Protector backup jobs names when they are deduplicated. For example, if you have a full backup called BACKUP1_F and an incremental backup of the same data called BACKUP1_I, you can enter _F and _I in the Edit Data Protector Configuration and the incremental backups will deduplicate against the full backups. Similarly, having a weekly full backup called BACKUP2 (WEEKLY) and a monthly full backup HP Data Protector 137

  • 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

Data Protector Deduplication Guidelines
In addition to the Data Protector general guidelines, the following guidelines apply to a VLS with
deduplication enabled:
Patch all Windows clients: HP Data Protector on Windows clients requires a software fix to
eliminate 56 KB file fragments that diminish deduplication performance on VLS and D2D
products. The fix depends on your version of Data Protector:
DP 6.0: install the patch
DPWIN_00426
(or later patches). Download the patch from the
HP website on the Data Protector version 6.0 “Download drivers and software” page.
DP 6.1: included in the 6.11 service pack. If this is not yet available, request
SSPNT610_012
(which you can automatically deploy to all Windows Disk Agent clients)
through the Data Protector support channel.
Patch all clients running the Oracle database backup agent so the VLS will correctly identify
incremental backups (instead of treating them as full backups). The latest Oracle patch for
Data Protector 6.11 is Patch DPWIN_00486.
Oracle RMAN Scripting: See
Oracle RMAN Scripting
for details.
Tape Retention Planning: Create media pools based on retention period. Mixing retention
periods will prevent cartridge expiration reclamation and leads to poor storage utilization.
Space used for the shorter retention backup is not reclaimed until all backups on the tape are
expired. That is, the backup application cannot reuse/reformat the tape until all backups have
exceeded their protection period. The backup application will not reuse expired cartridges
until all spare formatted virtual cartridges are used, so in this case HP recommends either
removing unneeded virtual cartridges or creating a script on the cell server to automatically
reformat expired cartridges on a regular basis.
Allocate Unformatted Media First: If you have deduplication enabled, you should disable the
“Allocate unformatted media first” option in the media pool. You must also set the global
variable
InitOnLoosePolicy=1
defined in the global file and the Data Protector services
must be restarted for the global variable to take effect. In HPUX the file is located in
/etc/
opt/omni/server/options/global
, and in Windows the file is located in
C:\Program
Files\OmniBack\Config\Server\Options\global
. These settings prevents Data
Protector from using all available blank cartridges for backups before it starts overwriting
expired/scratch cartridges; creating too many virtual cartridges results in the device disk
capacity filling up.
Interactive backups will not deduplicate: If you edit a Data Protector backup specification and
then manually run it from the GUI without saving it, the backup session will run with a backup
specification name of 'Interactive' and therefore will not deduplicate. This is because
deduplication correlates backup versions using the backup specification name.
Different backup job names for the same data: Some Data Protector configurations have
different backup job names for backing up the same data due to having different retention
times for the different backup types (for example, different job names for full backups vs.
incremental backups, or different names for weekly full backups vs. monthly full backups).
However, because the backups have different backup job names they will not deduplicated
against each other even though they contain exactly the same data. To address this, VLS
firmware versions 3.3.0 and higher include a GUI option called “Edit Data Protector
Configuration” (in the System Maintenance screen). This option allows you to enter suffixes
that will be stripped off the end of the Data Protector backup jobs names when they are
deduplicated. For example, if you have a full backup called
BACKUP1_F
and an incremental
backup of the same data called
BACKUP1_I
, you can enter
_F
and
_I
in the Edit Data
Protector Configuration and the incremental backups will deduplicate against the full backups.
Similarly, having a weekly full backup called
BACKUP2 (WEEKLY)
and a monthly full backup
HP Data Protector
137