When configuring a syncrepl provider slapd, which directives must be present in slapd.conf? (Choose TWO correct Answer)
A. syncprov-sessionlog
B. syncprov-overlay
C. syncprov-checkpoint
D. syncprov-errorlog
Correct Answer: AC
Explanation/Reference:
The provider is implemented as an overlay, so the overlay itself must first be configured in slapd.conf (5) before it can be used. The provider has only two configuration directives, for setting checkpoints on the contextCSN and for configuring the session log. Because the LDAP Sync search is subject to access control, proper access control privileges should be set up for the replicated content.
The contextCSN checkpoint is configured by the syncprov-checkpoint directive. Checkpoints are only tested after successful write operations.If operations or more than time has passed since the last checkpoint, a new checkpoint is performed. The session log is configured by the syncprovsessionlog directive, where is the maximum number of session log entries the session log can record. When a session log is configured, it is automatically used for all LDAP Sync searches within the database. syncprov-checkpoint ops minutes This directive controls maintenance of the contextCSN which is normally a memory only value but is written to the database on normal server termination and loaded from the database during server start-up operations. The directive may be used to force the provider to write the contextCSN to the underlying database after a successful write operation after either ops write operations or more than minutes time have passed since the last contextCSN database update (or checkpoint). syncprov-checkpoint is disabled by default. This directive is designed to minimise the amount of consumer synchronization activity required in the event that the master (provider) DIT server crashes.
syncprov-nopresent TRUE | FALSE
If set to TRUE the Present phase of refreshing should be bypassed. This value should only be set TRUE for a syncprov instance used with a log database such as one managed using the accesslog overlay. The default is FALSE.
syncprov-reloadhint TRUE | FALSE
Indicates the overlay should honor the reloadHint flag in the Sync Control (Note certain version 2.3 clients did not set the reloadhint flag correctly). It must be set TRUE when using the accesslog overlay for delta-synchonization. The default is FALSE. reloadhint may be used by the consumer requesting the replication operation to indicate that it wishes to force a complete transfer of the DIT irrespective of any other settings or values – such as the Sync Cookie.
syncprov-sessionlog ops
Indicates that a session log for recording information about write operations made on the database should be maintained by the provider. Ops specifies the number of operations that are recorded in the log. All write operations (except Adds) are recorded in the log. When using the session log, it is helpful to set an eq index on the entryUUID attribute in the underlying provider database
Explanation/Reference:
The provider is implemented as an overlay, so the overlay itself must first be configured in slapd.conf (5) before it can be used. The provider has only two configuration directives, for setting checkpoints on the contextCSN and for configuring the session log. Because the LDAP Sync search is subject to access control, proper access control privileges should be set up for the replicated content.
The contextCSN checkpoint is configured by the syncprov-checkpoint directive. Checkpoints are only tested after successful write operations.If operations or more than time has passed since the last checkpoint, a new checkpoint is performed. The session log is configured by the syncprovsessionlog directive, where is the maximum number of session log entries the session log can record. When a session log is configured, it is automatically used for all LDAP Sync searches within the database. syncprov-checkpoint ops minutes This directive controls maintenance of the contextCSN which is normally a memory only value but is written to the database on normal server termination and loaded from the database during server start-up operations. The directive may be used to force the provider to write the contextCSN to the underlying database after a successful write operation after either ops write operations or more than minutes time have passed since the last contextCSN database update (or checkpoint). syncprov-checkpoint is disabled by default. This directive is designed to minimise the amount of consumer synchronization activity required in the event that the master (provider) DIT server crashes.
syncprov-nopresent TRUE | FALSE
If set to TRUE the Present phase of refreshing should be bypassed. This value should only be set TRUE for a syncprov instance used with a log database such as one managed using the accesslog overlay. The default is FALSE.
syncprov-reloadhint TRUE | FALSE
Indicates the overlay should honor the reloadHint flag in the Sync Control (Note certain version 2.3 clients did not set the reloadhint flag correctly). It must be set TRUE when using the accesslog overlay for delta-synchonization. The default is FALSE. reloadhint may be used by the consumer requesting the replication operation to indicate that it wishes to force a complete transfer of the DIT irrespective of any other settings or values – such as the Sync Cookie.
syncprov-sessionlog ops
Indicates that a session log for recording information about write operations made on the database should be maintained by the provider. Ops specifies the number of operations that are recorded in the log. All write operations (except Adds) are recorded in the log. When using the session log, it is helpful to set an eq index on the entryUUID attribute in the underlying provider database
|
Download Printable PDF. VALID exam to help you PASS. |
 |