EasyManua.ls Logo

HP Data Protector IDB Purge User Manual

HP Data Protector IDB Purge
15 pages
To Next Page IconTo Next Page
To Next Page IconTo Next Page
To Previous Page IconTo Previous Page
To Previous Page IconTo Previous Page
Page #6 background imageLoading...
Page #6 background image
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:
1. In the global file set a time for the daily maintenance to run.
2. Manually run the daily maintenance with the command omnidbutil –purge –daily.
3. Manually run individual purges that do similar steps to the daily maintenance.
For example
omnidbutil -purge –sessions 30
omnidbutil -purge –messages 10
omnidbutil -purge –dcbf
omnidbutil -purge –mpos
IDB purging done by the Daily Maintenance
Sessions purge
Expired sessions, older than a certain number of days, are removed from an IDB with the command
omnidbutil -purge –sessions [TimeInDays].
For example omnidbutil -purge –sessions 30 removes all expired protection sessions from
the IDB that are more than 30 days old.
Example of messages seen at the command line
omnidbutil -purge -sessions 30
DONE!
Messages purge
Session messages from expired sessions, older than a certain number of days, are removed with
omnidbutil -purge –messages [TimeInDays]
Example of messages seen at the command line
omnidbutil -purge -messages 10
DONE!
6
Question and Answer IconNeed help?

Do you have a question about the HP Data Protector IDB Purge and is the answer not in the manual?

HP Data Protector IDB Purge Specifications

General IconGeneral
BrandHP
ModelData Protector IDB Purge
CategorySoftware
LanguageEnglish

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

Related product manuals