HP Data Protector IDB Purge Best Practices

10
The consecutive running of a dcbf Purge followed by a fixmpos
omnidbutil -purge –dcbf, deletes the dcbf records that are no longer required. However, the
mmdb will still have mpos records referring to these removed dcbf records.
Therefore, from time to time we suggest the consecutive running of a dcbf Purge followed by a
fixmpos.
omnidbutil -fixmpos requires exclusive access to the IDB, therefore the consecutive running of
these commands must be done when no backups are in progress.
Example of messages seen at the command line
omnidbutil -purge –dcbf
DONE!
omnidbutil –fixmpos
DONE!
Note:
See Appendix D for information about another manual purge that may, in
some circumstances, be required.
New DP 6.11 purge functionality introduced by patches
The patches below, or their successors, include a new global file variable DbPurgeExpiresOvers.
Table 3.
Windows HP-UX PA Risc HP-UX IA 64
Data Protector 6.11 DPWIN_00440 PHSS_40470 PHSS_40471
DbPurgeExpiredOvers=0 (default value)
Protection Expired Objects, Object versions and Media Positions are not removed, by the daily
maintenance, from the IDB until the medium is overwritten or exported.
DbPurgeExpiredOvers=1
Protection Expired Objects, Object versions and Media Positions are removed from the IDB when the
protection of all Objects on the medium have expired.
DbPurgeExpiredOvers=2
Protection Expired Objects, Object versions and Media Positions are removed from the IDB as their
protection expires, even though other Objects on the medium are still protected.
The use of DbPurgeExpiredOvers=1 or 2 can help control the IDB size. They may also help reduce the
pauses that can occasionally be seen during backups when the records of data on media that are
about to be overwritten are removed from the IDB, if default value is set.
Note:
DbPurgeExpiredOvers=2 should not be used in conjunction with
QuickMediaFormat=1.