Difference between revisions of "Disaster Server Architecture"
(→IBM Endpoint Manager Disaster Server Architecture) |
(→Overview) |
||
| (One intermediate revision by the same user not shown) | |||
| Line 3: | Line 3: | ||
The Disaster Server Architecture in IEM is intended to allow the Environment to remain functional if the Main Server should ever crash, or become overloaded. | The Disaster Server Architecture in IEM is intended to allow the Environment to remain functional if the Main Server should ever crash, or become overloaded. | ||
| − | This is accomplished by standing up a 'Secondary' server that replicates the database with the Main Server on a scheduled basis. Since the Replication is bi-directional | + | This is accomplished by standing up a 'Secondary' server that replicates the database with the Main Server on a scheduled basis. Since the Replication is bi-directional, [[IBM Endpoint Manager Relay|IEM Relays]] can be configured to use the Secondary server. This will result in Client Reports taking a little longer to report to the Console, but this is due to the database Replication rather than client or server performance. The Console should only be pointed to the Primary server, so replication must occur before client reports sent to the Secondary server will be visible. |
| + | |||
=== Configuration === | === Configuration === | ||
=== Replication === | === Replication === | ||
Latest revision as of 16:32, 30 December 2014
Contents
IBM Endpoint Manager Disaster Server Architecture
Overview
The Disaster Server Architecture in IEM is intended to allow the Environment to remain functional if the Main Server should ever crash, or become overloaded.
This is accomplished by standing up a 'Secondary' server that replicates the database with the Main Server on a scheduled basis. Since the Replication is bi-directional, IEM Relays can be configured to use the Secondary server. This will result in Client Reports taking a little longer to report to the Console, but this is due to the database Replication rather than client or server performance. The Console should only be pointed to the Primary server, so replication must occur before client reports sent to the Secondary server will be visible.
Configuration
Replication
Recovery
Documentation
IBM Documentation on DSA is availabe HERE.
