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#

• rflkeepfiles
• logstreamfiles
• rfldirectory

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.

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.

Category#

eDirectory

More Information#

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

• EDirectory Monitor Entry
• FLAIM
• FLAIM checkpoint
• Files In Dib Directory
• Logstreamfiles
• RFL
• Rfldirectory
• Rflkeepfiles
• Roll-Forward Log
• TransitiveVector
• _ndsdb.ini

---

• [#1] - Moving the placement of the eDirectory roll forward logs ( rfls ) - based on information obtained 2016-12-29-