Difference between revisions of "DSA Configuration Considerations"
| (2 intermediate revisions by the same user not shown) | |||
| Line 6: | Line 6: | ||
[HKEY_LOCAL_MACHINE\SOFTWARE\BigFix\Enterprise Server\FillDB] | [HKEY_LOCAL_MACHINE\SOFTWARE\BigFix\Enterprise Server\FillDB] | ||
UnInterruptableReplicationSeconds (DWORD): Seconds | UnInterruptableReplicationSeconds (DWORD): Seconds | ||
| − | + | Default: 30 | |
| − | Default: 30 | + | '''Note''': You must restart the FillDB service for changes to take effect. |
| − | + | ||
| − | Note: You must restart the FillDB service for changes to take effect. | + | |
By raising the value, the BigFix Server will spend more time performing replication each time it attempts to do so based on the replication interval. The error is caused because the BigFix Server is unable to complete replication using the default value. | By raising the value, the BigFix Server will spend more time performing replication each time it attempts to do so based on the replication interval. The error is caused because the BigFix Server is unable to complete replication using the default value. | ||
| Line 15: | Line 13: | ||
For larger deployments of BigFix, try a value of 60-120 seconds. If you are installing a new TEM Server, you might raise the value to 300-600 seconds during the initial replication period to reduce the amount of time spent initializing the new BigFix Server. | For larger deployments of BigFix, try a value of 60-120 seconds. If you are installing a new TEM Server, you might raise the value to 300-600 seconds during the initial replication period to reduce the amount of time spent initializing the new BigFix Server. | ||
| − | Caution: Increasing the UnInterruptableReplicationSeconds extends the time given to the FillDB process for the purpose of DSA replication. However, it takes time away from the FillDB for inserting client reports in the database. If the UnInterruptableReplicationSeconds setting is set too high for too long it can backup the client reports on the relays and servers and cause a cascading reporting failure in the deployment. If this happens, clients will appear offline and reports from the endpoints will be be delayed. | + | '''Caution''': Increasing the UnInterruptableReplicationSeconds extends the time given to the FillDB process for the purpose of DSA replication. However, it takes time away from the FillDB for inserting client reports in the database. If the UnInterruptableReplicationSeconds setting is set too high for too long it can backup the client reports on the relays and servers and cause a cascading reporting failure in the deployment. If this happens, clients will appear offline and reports from the endpoints will be be delayed. |
| + | |||
| + | [[Category:IBM BigFix]] | ||
| + | [[Category:DSA Configuration]] | ||
| + | [[Category:Work]] | ||
Latest revision as of 17:17, 26 July 2018
The DSA Replication Interval If you are using Distributed Server Architecture (DSA) and replication is failing with the error message 'Replication was interrupted to process server database insertions.' in the IBM Endpoint Manager Administration tool, you'll need to raise the maximum amount of time spent doing replication on the TEM Server that is failing.
To increase the maximum replication time, set the following server setting on the BigFix DSA servers.
[HKEY_LOCAL_MACHINE\SOFTWARE\BigFix\Enterprise Server\FillDB] UnInterruptableReplicationSeconds (DWORD): Seconds Default: 30 Note: You must restart the FillDB service for changes to take effect.
By raising the value, the BigFix Server will spend more time performing replication each time it attempts to do so based on the replication interval. The error is caused because the BigFix Server is unable to complete replication using the default value.
For larger deployments of BigFix, try a value of 60-120 seconds. If you are installing a new TEM Server, you might raise the value to 300-600 seconds during the initial replication period to reduce the amount of time spent initializing the new BigFix Server.
Caution: Increasing the UnInterruptableReplicationSeconds extends the time given to the FillDB process for the purpose of DSA replication. However, it takes time away from the FillDB for inserting client reports in the database. If the UnInterruptableReplicationSeconds setting is set too high for too long it can backup the client reports on the relays and servers and cause a cascading reporting failure in the deployment. If this happens, clients will appear offline and reports from the endpoints will be be delayed.
