FairCom Server remembers the number of currently-active Restore Points based on the KEEP_RESTORE_POINTS configuration option and it keeps transaction logs needed to roll back to those Restore Points. However, FairCom Server’s automatic recovery only supports rolling back to the most recent Restore Point.
File creates, renames, and deletes that are not transaction-dependent (i.e., for files that are not created using the ctTRANDEPx8mode attribute) cannot be done when rolling forward or undone when rolling back to a Restore Point. File deletes on files that do not use the restorable delete (ctRSTRDEL) x8mode attribute cannot be undone when rolling back to a Restore Point. The exceptions are files with the ctTRANDEPx8mode attribute whose delete is not committed before a system crash. Such files are restorable during the rollback to a Restore Point.
The Deferred LOG SYNC feature does not support mirrored transaction log files.
c-tree’s replication support has no knowledge of Restore Points. If FairCom Server’s automatic recovery rolls back to a Restore Point, the Replication Agent will not know if it should skip the transaction log entries that follow the Restore Point (if it has not yet processed them) or undo the transactions that follow the Restore Point (if it has already processed them). To synchronize the source and target data files when the source server rolls back to a Restore Point, the administrator must copy the replicated source data and index files to the target system and then continue replication at the source server’s current log position.
Incremental roll forward is not supported on superfiles.
