JumpMind Replication

Due to regulatory requirements and physical location, these implementation types will likely require multiple database instances, replicated using the JumpMind product SymmetricDS. The database and installation are customized to support the symmetric DS product.

While this is a separate product that requires significant configuration and ongoing maintenance, it offers a major benefit: when cloud server stability is low, a local instance of the cloud database is replicated. This approach allows the system to maintain the connectivity advantages of a local database while retaining the centralized control and administration provided by a cloud-based instance.

Key considerations:

• Both data centers must be secured, and communication between them should be reliable and clearly defined.
• There may be a significantly longer delay between pressing Save on the primary EMC and the data being replicated to the secondary servers.
• Upgrades need to be coordinated and planned simultaneously.
• There are likely to be additional constraints on data maintenance and data access.
• While a central entity can manage configuration, reporting data is not sent back to them.