Filter
Top Products
Troubleshooting
Check Whether Data Protector Functions Properly
Chapter 12 607
Overview of Items to Be Checked
In order to ensure that Data Protector is functioning properly and to
identify potential problems before they arise, it is recommended that you
perform regular checks as described in the following sections.
Using the User Check Failed notification, it is possible to automate
these checks by developing scripts including these checks. Some of the
checks (for example the omnihealthcheck and omnitrig -run_checks
commands) are already automated by the means of Data Protector
checking and maintenance mechanism.
Check the Data Protector Cell Manager
1. Run the omnihealthcheck command to check the following:
• whether the Data Protector services (rds, crs, mmd, omnitrig, and
OmniInet) are active
• whether the Data Protector Media Management Database is
consistent
• whether at least one backup of the IDB exists
The exit code of the command is 0 (OK) only if all three checks
completed successfully (exit code for every check was 0). Exit values
other than 0 indicate that one or more of the checks failed.
For more information on exit codes, refer to omnihealthcheck man
page.
2. Run the omnidbcheck -core command to check the core parts of the
IDB.
The exit code of the command is 0 (OK) only if the check completed
successfully. Exit values other than 0 indicate that the check failed.
For more information on exit codes, refer to omnihealthcheck man
page.
3. Check the critical parts of IDB using the omnidbcheck -critical
command. For more information on the omnidbcheck command, refer
to omnidbcheck man page.
The exit code of the command is 0 (OK) only if the check completed
successfully. Exit values other than 0 indicate that the check failed.
For more information on exit codes, refer to omnidbcheck man page.