Skip to end of banner
Go to start of banner

Refreshing a Test environment with replication

Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Version History

« Previous Version 8 Next »

From time to time, any Test environment has to be refreshed with fresh backup from Production. A Test environment with replication requires additional steps for restoring synchronization between sites.

Method 1 - Backup and Restore all separate sites

Backup the office and the vessel database(s) with shortest time possible between each backup made, and restore these databases in the UAT on the separate installation.

  1. Stop replication on Test (disable scheduler, manually execute Receive and Import only). Because Replicator Scheduler stores the settings in the DB, turn off all Replicator Services in the Test environment.

  2. Take full Production DB backups on all sites that are represented on Test. Start taking backups from the Main Site.

  3. Restore backups over the corresponding Test DBs. Use overwrite option

  4. Once all backups are restored, a superuser should open Adonis Control Center and retype passwords for inbuilt DB users (ADPW, REPL, AD_UPGRADE). You can skip this step if passwords match between the Prod and Test.

  5. The Adonis DB version on Production often differs from Test; run the APM upgrade to the desired version. If APM versions on Production and Test are the same, you can skip this step.

  6. Login to APM and remove any link to Production services

    1. Web Service

    2. Crewlink

    3. Global Options,

    4. Notification tasks

  7. Remove all files from in\Receive, in\ImportStorage, in\archive, out\send, and out\Archive of all Replicator instances on Test. Start Replicator Service. Run the full replication circle manually starting from the Main Site. If some replication files appear missing, take them from the Production Main Site corresponding Archive folder. Enable Replicator Schedulers.

This method requires database backups to be taken as close in time as possible. Otherwise, between steps 6 and 7, superuser would need to synchronize the last import\export file numbers and times between al sites.

Method 2 - Backup and Restore the Office site and replicate to all vessel sites

Backup and Restore the office and reset the replication date.
Restore the office database and set the last replication date back to 01/01/1900, forcing all data to be replicated during the next replication.

Install / backup an empty database on each vessel site and set the last replication cab file nr for each site based on the nr found in the office database. The replicator continues replicating to the vessel, and the first cab file created contains all data for the vessel from 01/01/1900

  1. Stop replication on Test (disable scheduler, manually execute Receive and Import only). Because Replicator Scheduler stores the settings in the DB, turn off all Replicator Services in the Test environment.

  2. Take full Production DB backup from the Main Site.

  3. Restore backup over the Test Main Site DB. Use overwrite option.

  4. Once the backup is restored, a superuser should open Adonis Control Center and retype passwords for inbuilt DB users (ADPW, REPL, AD_UPGRADE). You can skip this step if passwords match between the Prod and Test.

  5. The Adonis DB version on Production often differs from Test; run the APM upgrade to the desired version. If APM versions on Production and Test are the same, you can skip this step.

  6. Login to APM and remove any link to Production services (Web Service, Crewlink, etc.) Manually restore necessary Test settings (Global Options, Notification tasks, etc.)

  7. Login to APM on all sites, and clear the last Export/Import file numbers and times for all channels.

  8. Clean satellite sites. Login to APM, choose root level as a current client, and open Standard crew list view showing both employed and terminated crew. Tag all crew, call right-click menu and choose to delete selected crew.

  9. To prevent spreading deletion from the Satellite sites, set the last export time to 'now' after deletion.

  10. Execute the script below on the Main Site database.

  11. Remove all files from in\Receive, in\ImportStorage, in\archive, out\send, and out\Archive of all Replicator instances on Test. Start Replicator Service. Run the full replication circle manually starting from the Main Site. Enable Replicator Schedulers.

This method can be challenging due to needing to process and resend the whole database. Ensure that you have enough free space on the drive where the Replicator is installed.

  • No labels