HP Data Protector IDB Purge User Manual

To run any of these commands, DP must not be busy doing backups or other activities.
Close all DP GUIs and confirm that no backups, restores or other DP activities are in progress by
checking that ”omnistat“ returns “No currently running session.”
Note:
Exclusive access does not mean that the DP processes must be stopped. But
occasionally it will be necessary to stop and restart them before the
preceding commands can run.
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
• Make sure DP is not active, omnistat returns ”No currently running sessions”
• Stop DP processes with omnisv -stop
• ps -ef | grep omni
• kill any omni processes
• Start DP with omnisv -start
On Windows proceed as follows:
• Close all DP GUIs
• Make sure DP is not active, omnistat returns ”No currently running sessions”
• Stop DP services with omnisv -stop
• Open Task Manager and go to the Processes tab
• Highlight Data Protector process and “End Process” them
Common DP processes are bsm.exe, bma.exe, Manager.exe, dbsm.exe.
• Start DP with omnisv -start
Note:
If DP is running within Microsoft Cluster Services (MCSC) or
MC/ServiceGuard then “omnisv –stop” and “omnisv –start” may not be the
appropriate way to stop and start DP.
While a command that requires exclusive access to the IDB is running, scheduled DP backups will not start.
If the Cell Manager where you want to run the command requiring exclusive access to the IDB is part
of a Manager of Managers (MoM) you have to stop backups on all Cell Managers that are part of
the MoM.
10

HP Data Protector IDB Purge Specifications

General

Brand	HP
Model	Data Protector IDB Purge
Category	Software
Language	English

Summary

Introduction

Scope

Defines the scope of the document regarding Cell Managers and DP versions.

Three step guide to use this white paper

Outlines the three main steps covered in the white paper for IDB maintenance.

How to identify if a DP IDB needs filenames purging?

Automated discovery

Explains the automated daily health check mechanism for identifying purge needs.

Manual discovery

Details manual methods using CLI or GUI to preview purge status.

Automated IDB purging done by the Daily Maintenance

What is the Daily Maintenance?

Describes the purpose and function of the Daily Maintenance process.

Setting the time Daily Maintenance runs

Explains how to configure the execution time of the Daily Maintenance.

Methods to confirm if, and when, Daily Maintenance is being run

Provides methods to check if the Daily Maintenance is active and its schedule.

If Daily Maintenance is not running

Offers steps to take if the Daily Maintenance is disabled or not functioning.

Manual IDB purge operations

Filenames purge

Details the manual purge of obsolete filenames from the IDB, requiring exclusive access.

The consecutive running of a dcbf Purge followed by a fixmpos

Explains the procedure for running dcbf purge and fixmpos consecutively.

Appendix A

What does "Requires exclusive access to the IDB" mean?

Clarifies the meaning of exclusive access requirement for IDB operations.

Appendix B

Further information about the IDB Daily Maintenance:

Provides additional details on the commands executed during Daily Maintenance.

Appendix C

Example update to purge.log after a completed forced filenames purge

Shows an example log entry for a completed forced filenames purge.

Appendix D

Failed_copies purge

Describes the purge of unrequired copies of objects that may overload the IDB.

For more information

Glossary