HP Data Protector IDB Purge User Manual

Manual IDB purge operations
Note:
These commands require Exclusive Access to the IDB, so that no backups
are running or no GUIs are open.
On some very busy Cells it can be difficult to book time when no backups are running. This problem
may be greater if the Cell Manager is part of Manager of Managers (MoM), as all backups have to
be stopped on all Cells in the MoM, in order to run the commands that require exclusive access to the
IDB.
Filenames purge
A filenames purge removes obsolete data from the filenames part of the IDB, but leaves filenames
records referring to protected data intact.
Running a DP IDB filenames purge requires exclusive access to the DP IDB, so no backups can be in
progress and all GUIs must be closed. In a MoM environment, DP must not be busy with backups or
other activities anywhere on the MoM.
Run a filenames purge on a DP Cell Manager as follows:
• Verify that no backups or restores are in progress by checking that “omnistat” returns:
“No currently running session“
• Start the purge:
omnidbutil -purge -filenames -force
Note:
Occasionally it will be necessary to stop (omnisv -stop) and start again
(omnisv -start) DP before the command will run.
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.
You can monitor the filenames purge in two ways:-
• Start one GUI and look in the Monitor context
• 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.
Later, when you have time, start the purge again as previously explained.
Example of messages seen at the command line
omnidbutil -purge -filenames -force
Filename purge session started.
8

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