Table of Contents
Advertisement
Quick Links
- 1 Introduction
- 2 How to Identify if a Dp Idb Needs Filenames Purging
- 3 Automated Idb Purging Done by the Daily Maintenance
- 4 Methods to Confirm If, and When, Daily Maintenance Is Being Run
- 5 Idb Purging Done by the Daily Maintenance
- 6 Sessions Purge
- 7 Manual Idb Purge Operations
- Download this manual
HP Data Protector IDB Purge best practices
Commands that purge obsolete data from the HP Data Protector
(DP) software Internal Database (IDB), to maintain the IDB in
good condition
Table of contents
Introduction......................................................................................................................................... 2
Scope............................................................................................................................................. 2
Three step guide to use this white paper ............................................................................................. 2
How to identify if a DP IDB needs filenames purging? .............................................................................. 3
Automated discovery ........................................................................................................................ 3
Manual discovery ............................................................................................................................ 4
Automated IDB purging done by the Daily Maintenance........................................................................... 5
What is the Daily Maintenance? ........................................................................................................ 5
Setting the time Daily Maintenance runs ............................................................................................. 5
Methods to confirm if, and when, Daily Maintenance is being run ......................................................... 5
If Daily Maintenance is not running .................................................................................................... 6
IDB purging done by the Daily Maintenance ........................................................................................... 6
Sessions purge................................................................................................................................. 6
Messages purge .............................................................................................................................. 6
Dcbf purge...................................................................................................................................... 7
Mpos purge .................................................................................................................................... 7
Manual IDB purge operations ............................................................................................................... 8
Filenames purge .............................................................................................................................. 8
The consecutive running of a dcbf Purge followed by a fixmpos............................................................. 9
Appendix A ........................................................................................................................................ 9
What does "Requires exclusive access to the IDB" mean? ..................................................................... 9
Appendix B....................................................................................................................................... 11
Further information about the IDB Daily Maintenance: ........................................................................ 11
Appendix C ...................................................................................................................................... 12
Example update to purge.log after a completed forced filenames purge ............................................... 12
Appendix D ...................................................................................................................................... 13
Failed_copies purge ....................................................................................................................... 13
For more information.......................................................................................................................... 14
Glossary........................................................................................................................................... 14
Advertisement
Table of Contents
Related Manuals for HP Data Protector IDB Purge
Summary of Contents for HP Data Protector IDB Purge
-
Page 1: Table Of Contents
HP Data Protector IDB Purge best practices Commands that purge obsolete data from the HP Data Protector (DP) software Internal Database (IDB), to maintain the IDB in good condition Table of contents Introduction............................2 Scope............................. 2 Three step guide to use this white paper ..................... 2 How to identify if a DP IDB needs filenames purging? ................ -
Page 2: Introduction
This document presents some Data Protector commands that can help keep your Internal Database healthy. This white paper is complementary to the white paper HP Data Protector software cell manager planning and sizing. Please also follow the recommendations therein to facilitate reliable Data Protector operation. -
Page 3: How To Identify If A Dp Idb Needs Filenames Purging
The global file is located on the DP Cell Server under: Windows (default) C:\Program Files\OmniBack\Config\Server\Options\global HP-UX/SUN Solaris/Linux (default) /etc/opt/omni/server/options/global The daily check triggers an “IDB Purge Required” notification if: • The time elapsed since the last IDB filename purge exceeds Days Last Purge [days] (default, 180 days). -
Page 4: Manual Discovery
Manual discovery A filenames purge preview status report can be manually created either using the DP command line interface (CLI) or the GUI. • DP CLI: omnirpt –report db_purge_preview • DP GUI: Reporting context, right click on “Reports” and select “Add Reporting Group.” Choose a name and click on “Finish.”... -
Page 5: Automated Idb Purging Done By The Daily Maintenance
DailyMaintenanceTime=08:30 Method 2 Run the command omnicc -debug 20 CHECK.txt, and look at the output debug file which will: • Be in (default)/tmp on HP-UX • Be in (default) C:\Program Files\OmniBack\tmp on Windows • Have file name ending with CHECK.txt. -
Page 6: If Daily Maintenance Is Not Running
Look through the output file for name=DailyMaintenanceTime and see the value: For example if you see value=12:00 daily maintenance is running at 12:00 hrs value=99:99 daily maintenance is disabled value=None daily maintenance is disabled value=20:30 daily maintenance is running at 20:30 hrs If Daily Maintenance is not running In case Daily Maintenance is disabled consider the following steps: In the global file set a time for the daily maintenance to run. -
Page 7: Dcbf Purge
Mpos purge Note: This purge is available by default on DP 6.1, but for DP 5.5 and 6.0 it requires one of the following patches or their successor. Windows HP-UX PA Risc HP-UX IA 64 Data Protector 5.5 DPWIN_00396 PHSS_38726 PHSS_38727 Data Protector 6.0... -
Page 8: Manual Idb Purge Operations
• Look at the file (default location): on windows C:\Program Files\OmniBack\log\server\purge.log on HP-UX /var/opt/omni/server/log/purge.log See Appendix C for an example of the update to purge.log of a completed filenames purge. If the purge has not finished, but you need to run backups simply stop the purge with omnidbutil -purge_stop and use DP as normal. -
Page 9: The Consecutive Running Of A Dcbf Purge Followed By A Fixmpos
Frequently Asked Questions about filenames purge Question 1: Will the force option cause the filenames purge to remove protected data? Answer 1: No, a force purge will not remove any protected data from the DP IDB. A purge without the force option looks for obsolete records for a hostname and only purges those records if there are more than 1000000 obsolete entries. - Page 10 When doing this, it is good practice after stopping DP (omnisv -stop) to look for any remaining DP processes that may be running and close them before restarting DP (omnisv -start) On HP-UX proceed as follows: • Close all DP GUIs •...
-
Page 11: Appendix B
Windows default location of global file: C:\Program Files\OmniBack\Config\Server\Options HP-UX location of global file: /etc/opt/omni/server/options The value for the number of days used by the daily maintenance omnidbutil -purge - messages <days> command is determined by the setting value of KeepMessages in the global file. -
Page 12: Appendix C
Appendix C Example update to purge.log after a completed forced filenames purge 1/12/2009 2:37:09 PM ASM.5312.4976 ["sm/asm/asm_purge.c /main/dp56/1":470] A.06.00 bDPWIN_00385 Purge session started. 1/12/2009 2:37:09 PM ASM.5312.4976 ["sm/asm/asm_purge.c /main/dp56/1":480] A.06.00 bDPWIN_00385 Filename purge session started. [REPORT_DATA] 1231771029 1231771052 0 0 6 [REPORT_DATA] 1231771053 1231771067 0 0 6 [REPORT_DATA] 1231771067 1231773602 0 1161430 32 1/12/2009 3:20:02 PM ASM.5312.0 ["db/dc/dcpurge/dcpurge.c... -
Page 13: Appendix D
GUIs are closed. When run, this purge updates the RDS.log file. • On Windows the RDS.log file is, by default, C:\Program Files\OmniBack\db40\datafiles\catalog • On HP-UX the debug.log file is: /var/opt/omni/log Example of messages seen at the command line omnidbutil -purge_failed_copies DONE! Example of the update to RDS.log... -
Page 14: For More Information
Help menu, Help Topics. Search tab for searching. Contents tab is the equivalent of an Administrator’s Guide. • Chapter 5 of the HP Data Protector Concepts Guide, which is available from the DP GUI, help menu, Online documentation • The omnidbutil main page: On HP-UX this can be accessed by ”man omnidbutil”... - Page 15 Nothing herein should be construed as constituting an additional warranty. HP shall not be liable for technical or editorial errors or omissions contained herein.