|
|
|
The following options can be defined in the FairCom DB Server configuration file ctsrvr.cfg and should be taken into consideration for all new and existing FairCom DB customers:
|
|
|
Do not operate with SKIP_MISSING_FILES enabled in the ctsrvr.cfg configuration file by default. This configuration may cause files to be inadvertently skipped during recovery, making it difficult to restore the database back to a consistent state. This keyword should only be utilized when confirmed necessary (by reviewing specific error messages in the CTSTATUS.FCS status log file), and then promptly removing it. (Commenting the keyword in the configuration file is suggested, as it is then readily available if absolutely needed.)
|
|
|
To take fullest advantage of FairCom DB’s recovery options, it is advisable to keep as many transaction logs as practical — up through the last two backups, if possible. The FairCom DB restore process can start with an existing backup and roll forward through remaining logs if available, restoring data to the latest possible time point.
|
|
|
FairCom has a feature that reduces the amount of time it takes for automatic recovery to complete, especially in systems with high transaction rates. By adding the keyword FORCE_LOGIDX ON to your ctsrvr.cfg file, FairCom DB will store a few additional bytes of information per index node within the FairCom DB transaction logs, which will greatly reduce the amount of time automatic recovery will take. There is no performance loss with the production system for enabling this feature and you do not need to rebuild indexes to enable this feature.
FORCE_LOGIDX supports these settings:
Note: LOGIDX is ON by default with FairCom DB V9.2 and later.
