Overview[1]#

Roll-Forward Log is used in FLAIM where FLAIM logs operations for each update transaction in a Roll-Forward Log (RFL) file.

Roll-Forward Log is used to recover transactions from a system failure or when restoring from a backup.

Roll-Forward Log file is by default truncated after every FLAIM checkpoint is completed. unless it is turned on (rflkeepfiles) by using a hot continuous backup. (http://www.novell.com/documentation/edir88/edir88/data/a2n4mb7.html).

Roll-Forward Log _ndsdb.ini Settings#

Although the _ndsdb.ini file may only contain the last statement, however, it is recommended that the all Roll-Forward Log lines be used when moving Roll-Forward Logs to a non-default location. At a minimum, if rfls have been enabled.

Should the Roll-Forward Log file not exist one will be created on the next transaction as long as there are no replayable records in the FLAIM database.

If a Roll-Forward Log is deleted and there are playable events a call to Novell INC may be necessary (error: -6034) to recreate it. A blank file will not be sufficient since it does not have the necessary header info in the first 512 bytes.
Novell INC does not support the use of symlinks to specify the location of the eDirectory database or Roll-Forward Log (RFLs). Please modify the nds.conf file to specify DIB location, if it is not in the default location.

This shows how to manually perform this process. When eDirectory services start back up the _ndsdb.ini file is read and the new location as well as the other parameters will be read and used immediately. These steps can also be performed using the eMBox client as well if the platform is on Linux, Windows or a NetWare version 6.0 or greater. Please refer to the eDirectory documentation for more information.

More Information#

There might be more information for this subject on one of the following:

Add new attachment

Only authorized users are allowed to upload new attachments.
« This page (revision-7) was last changed on 29-Dec-2016 13:38 by jim