Lucent Technologies 5ESS-2000, Инструкции по эксплуатации и техническому обслуживанию

Страница: 166 / 1421

The Full, Incremental, and Processor Entity audits use the backup copy of the ODD on the disk and the RC logfiles
to do their processing. This is done to ensure minimum or no impact on the Recent Change throughput. Hence the
data that is audited may not include all the Recent Changes that were done since the last backup of the ODD. The
Entity audit uses the backup copy of the ODD and the log files that were created by Recent Changes since the last
backup. This will enable the Entity audit to audit a current view of the data base.
This feature interfaces with ODD Backup. The Incremental audit starts when the ODD backup completes, therefore
the schedule for the Incremental audit is the same as the schedule for the ODD backup. ODD backup sends a
message to the new Static Data Audit when a backup session completes for starting the Incremental audit. A
message is also sent after each processor is backed up and the log files are copied to the /rclog/SODD/bkuplog
directory. Also, none of the audits can run when the
ODD:BKUP runs. Thus when the ODD backup begins, if any of
these audits are running they will be suspended automatically. The Full audit starts right after the ODD backup
completes if the schedule allows it. Likewise, a suspended Processor Entity audit starts after the ODD backup
completes. If an Entity audit was running before the ODD backup and got stopped by the start of the backup, it is
NOT restarted again after the backup is completed. The ODD backup scenario is as follows:

Full audit is running.

Multiprocessor ODD backup starts.

Backup sets data delivery (DD) bits indicating backup is running, meaning at least one ODD file is changing.

At next attempt at a tuple read, data base manager (DBM) causes SODD to halt because of DD bits.

For each processor completing backup:

Backup copies corc and rc logfiles to /rclog/SODD/bkuplog.

Backup removes corc and rc logfiles from /smlog and /log.

Backup sends a message to SODD control process (RCsoddcp) indicating one processor's backup is
completed.

RCsoddcp starts an instance of DBlogmfs to process the copied logfiles (provided an instance of DBlogmfs
is not already running).

Backup removes /rclog/DBaudsize, indicating the consistent view(s) are no longer valid. (New consistent
view(s) will be established when next SODD audit starts.)

Backup sends final message indicating it's done with the backup.

Backup resets DD keys.

Full audit restarts (as long as there's at least 15 minutes left in the segment.)

RCsoddcp waits for DBlogmfs process to complete.

Incremental audit starts.
5.14.14 LIMITATIONS
The Full audit runs in an infinite loop, starting and suspending itself according to its schedule. If the user supplied a
schedule that severely limits the audit execution time, the audit may never be able to completely validate the ODD.
When the audit restarts at the beginning of the new session, it starts from the relation and processor it left off. In an
235-105-210 October 1999
Copyright © 1999 Page 58