HP OpenView Operations Administrator's Reference - filibeto.org

Maintaining the Managed Nodes
Maintaining OVO
Maintaining the Managed Nodes
On the managed nodes, you should periodically back up, and then erase,
local OVO logfiles (and their backups). OVO uses 90% of the specified log
directory size for local message logging, and 10% for error and warning
logging. OVO also uses an automatic backup mechanism for the logfiles
(four on UNIX and Solaris, nine on MPE/iX).
For example, the configured size of a UNIX log directory is 10 MB.
The size of a UNIX log directory is allocated in the following way:
❏ Message Logging
OVO allocates 9 MB for local message logging.
Given that there are four logfiles, if the opcmsglg file size is greater
than 2.25 MB, OVO does the following:
Moves opcmsgl2 to opcmsgl3 (if exists).
Moves opcmsgl1 to opcmsgl2 (if exists).
Moves opcmsglg to opcmsgl1.
❏ Error and Warning Message Logging
OVO allocates 1 MB for local error and warning message logging.
If the opcerror (on DCE-based managed nodes) or System.txt (on
HTTPS-based managed nodes) file size is greater than 0.25 MB, OVO
does the following:
On DCE-based managed nodes:
Moves opcerro to opcerro3 (if exists).
Moves opcerro1 to opcerro2 (if exists).
Moves opcerror to opcerro1
On HTTPS-based managed nodes:
Moves System.txt to System.txt.003 (if exists).
Moves System.txt.001 to System.txt.002 (if exists).
Moves System.txt to System.txt.001
Chapter 13 543