...
Stop replication on Test (disable scheduler, manually execute Receive and Import only). Because the Replicator Scheduler stores the settings in the DB, turn off all Replicator Services in the Test environment.
Take full Production DB backups on all sites that are represented on Test. Start taking backups from the Main Site.
Save all needed links (settings) from Global Options of the Test system (URL to Crew Portal in Web Services).
Restore backups on the Test SQL server by either restoring as a new database or using the overwrite option. Pay attention to the destination database name and files.
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.
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.
Login to APM and remove any link or reference to Production services and add saved ones for Test system
Web Service
Crewlink (if applicable)
Global Options
Notification tasks
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, copy them from the Production Main Site corresponding Archive folder. After the complete replication cycle, enable Replicator Schedulers.
...
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.
Take full Production DB backup from the Main Site.
Restore backup over the Test Main Site DB. You can use the overwrite option. Pay attention to the destination database name and files.
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.
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.
Login to APM and remove any link to Production services (Web Service, Crewlink, etc.) Manually restore necessary Test settings (Global Options, Notification tasks, etc.)
Login to APM on the Main Site, and set all vessel sites and corresponding channels to inactive.
Create new sites and channels for the Test vessels keeping the Organization’s assignment.
Clean
On satellite sites. Login to APM, choose root level as a current client, and open the Standard crew list view showing both employed and terminated crew. Tag all crew, call the right-click menu, and choose to delete the selected crew.
To prevent spreading deletion from the Satellite sites, set the last export time to 'now' after deletion.
, uninstall all Adonis applications.
Clean the Adonis application folders from any remaining files.
Rename or delete the old Test vessel Adonis database.Continue by installing all necessary Adonis applications on the Test vessels using the new site numbers. Follow the same procedure as for creating a new vessel installation.
Execute the script below on the Main Site database.
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.
...
Tip |
---|
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. |
- The first method could be used for systems without replication.