Novell EDIRECTORY 8.8 SP3, Руководство администратора, Страница: 438 / 634

438 Novell eDirectory 8.8 Administration Guide
n
ov
do
cx (e
n)
11
Ju
ly 20
08
When you turn on continuous roll-forward logging, the history of changes is saved in a set of
consecutive roll-forward log files. Roll-forward logging does not reduce server performance; it
simply saves the log file entries that eDirectory is already creating.
You must turn on roll-forward logging for servers that participate in a replica ring. If you don't,
when you try to restore from your backup files you will get errors and the database will not open.
The restore by default won't open a database that shares replicas with other servers unless it is
restored back to the state it was in at the moment before it went down. (If you don't have roll-
forward logs, you must follow a separate procedure to try to recover, described in
Section 16.9,
“Recovering the Database If Restore Verification Fails,” on page 477 .)
Roll-forward logging is off by default. You must turn it on if you want to use it on a server. Roll-
forward logging is also turned off and the settings returned to default when you restore a server, so
after a restore you must turn it on again, re-create your configuration, and create a new full backup.
(The new full backup is necessary so that you are prepared for any failures that might occur before
the next unattended full backup is scheduled to take place.)
In a single-server environment, roll-forward logging is not required, but you can use it if you want to
be able to restore eDirectory to the moment before it went down instead of just to the last backup.
Make sure you monitor disk space when roll-forward logging is on. For more information, see
“Backing Up and Removing Roll-Forward Logs” on page 441 .
In this section:
Š
“Issues to Be Aware of When Turning On Roll-Forward Logging” on page 438
Š “Location of the Roll-Forward Logs” on page 439
Š
“Backing Up and Removing Roll-Forward Logs” on page 441
Š “Cautionary Note: Removing eDirectory Also Removes the Roll-Forward Logs” on page 441
You can turn on and configure roll-forward logging using either iManager or the eMBox Client. See
“Configuring Roll-Forward Logs with iManager” on page 448 or “Configuring Roll-Forward Logs
with the eMBox Client” on page 460 .
16.3.1 Issues to Be Aware of When Turning On Roll-Forward
Logging
If you decide to use continuous roll-forward logging, you must be aware of the following issues:
Š Turn on roll-forward logging before a backup is done if you want to be able to use this
feature for restoring the database.
Š
For fault tolerance, make sure that the roll-forward logs are placed on a different storage
device than eDirectory.
For security, you should also restrict user rights to the logs. For more
information, see “Location of the Roll-Forward Logs” on page 439 .
Š
Document the location of the roll-forward logs. For more information, see “Location of the
Roll-Forward Logs” on page 439 .
Š
Monitor the available disk space where the logs are located. For more information, see
“Backing Up and Removing Roll-Forward Logs” on page 441 .