JADE Environment Development Ideas

The term “refresh” in this context is the process of “refreshing/copying” the production database from PROD to a PRE-PROD database, using Jade backup and restore.

Normally a PRE-PROD database will mirror the configuration of the production database.

So, if the production database has a SDS secondary or a RPS node, the PRE-PROD would have the same configuration.

It could also be true to have the PRE-PROD SDS secondary database located at the DR data center.

For large databases, i.e., over 2TB in size, the logistic of transferring data of this size can be problematic.

The “refresh” process requires the following steps currently:

• Complete a Prod Primary Backup.

• Relocate the Backup from the Prod server to the primary PRE-Prod server.

• Action a PRE-PROD Restore from Prod backup on the PRE-Prod server.

  • At this point a new database ID is created on the restored PRE-PROD database.

• Action a new PRE-PROD backup. Because of the new database ID number.

• Relocate the Backup from PRE-Prod server to PRE-PROD DR server.

  • Normally this is over a “somewhat” limited network connection.

• Action a Jade Restore of the PRE-PROD primary back as the PRE-PROD SDS node.

So, the issue is:

How can we use the PROD SDS secondary database already at the DR data center as the source of the PRE-PROD SDS secondary. Note. Currently this isn’t possible as there will be a mismatch on the database ID number on restore between the newly created database ID on the primary PRE-PROD database.

The suggestion is:

Free up the restrictions around creating a new database ID on restore. Maybe allow the target database id to be reused or the ability to provide the target database ID on the secondary restore, or even introduce a new concept around a backup set ID which is transferrable from PROD to PRE-PROD ETC.

This would be a significant time saver for clients using the refresh process within their configurations, in some cases, time savings in days not just hours.