Database replication - j5 - 28.0 - Installation & Upgrade - Hexagon PPM

j5 Installation and Upgrade

English (United States)
Search by Category
Installation & Upgrade
j5 Version

Various techniques are available to ensure that the standby database remains synchronized with the production database. This document does not prescribe a particular choice of technology or how to set it up, but links to Microsoft SQL Server documentation are provided. These principles can be applied to other platforms and technical information relating to other platforms is available on request.

Two solutions are discussed here briefly:

  • Back Up and Restore of SQL Server Databases

  • SQL Server Replication

Any replication solution has an impact on both performance of the production system and bandwidth between the production and standby systems, so these must be considered and tested. High quality infrastructure and a good database administrator are essential to maintain your data reliably.

Back up and restore is a simple strategy that can be used to restore the standby database to the latest production backup.

More information about Back Up and Restore of SQL Server Databases can be found at:

The backup / restore process must be scheduled automatically, and the frequency must be chosen carefully to balance against the performance impact. Frequent backups are desirable, and some data loss is expected, because any production data changes since the last production backup / restore will not be available on the standby server. However, data read writes can be expensive even if done in small chunks, so running a backup job every 15 minutes may not be viable as it may seriously impede server performance. It may be desirable to take system usage into account, for example by scheduling a full backup twenty minutes after a shift handover.

SQL Server Replication

SQL Server Enterprise Edition provides database replication features which can be used to keep the content of the production and standby databases in sync automatically. Database clustering or transactional replication can ensure fast failover and minimal data loss in the event that a database server goes offline.

More information about SQL Server Replication can be found at: