controls::set archive log failover retry limit
Overview
Puppet controls are Puppet defined types that ensure a certain security control is implemented. Puppet changes the system in order to make the system compliant.
Description of the control
The numarchretry parameter determines how many times a database will try to archive the log file to the primary or the secondary archive destination before trying the failover directory. It is recommended that this parameter be set to 5.
Rationale
Establishing a failover retry time limit will ensure that the database will always have a means to recover from an abnormal termination. This parameter should not be set to 0.
Skipping
To deliberately skip this control (e.g. meaning don’t use Puppet to enforce this setting), we provide you with two ways:
1) Add db2_secured::controls::set_archive_log_failover_retry_limit: skip to your hiera data. This will skip this control for ALL systems.
3) Add an entry with the content set_archive_log_failover_retry_limit to the array value db2_secured::skip_list in your hiera data.
Benchmarks
This control is used in the following benchmarks:
- db10 CIS V1.1.0 - paragraph 3.1.22
- db11 CIS V1.0.0 - paragraph 4.1.11
Attributes
| Attribute Name | Short Description |
|---|---|
| title | The database identifier to apply the control to. |
title
The database identifier to apply the control to.
All controls need an database identifier to apply the control to. Here is a simple example:
db2_secured::controls::control_name { 'db2inst1/MYDB':}
In this example, the string dbinst1 is the instance, the string MYDB is the database to apply the control to.
Back to overview of controls::set_archive_log_failover_retry_limit
