Database backup - j5 - 28.0 - Installation & Upgrade - Hexagon

j5 Installation and Upgrade

Language
English
Product
j5
Search by Category
Installation & Upgrade
j5 Version
2019

In addition to database replication to a standby server, we recommend that you maintain regular database backups. This backup can be useful in the event that some data on the production database is lost or corrupted, and the changes are replicated to the standby server, causing it to be corrupted as well. Refer to your database vendor’s documentation for further information on how to schedule a database backup task.

We recommend that the:

  • Backup jobs are logged, and the logs are checked. Automatic alerts must be triggered if the backup does not take place.

  • Integrity of the data is checked to ensure that the archived data is not corrupt. Hash sums of the archive can be used to test this.

  • Backups are transferred to a secure isolated location (for example, cloud storage, Netapp, or tape drives in a separate data center).

  • A full backup is used when migrating databases.

Microsoft SQL BACPAC files do not store some critical information. They should not be used as backup files.