For On-Premise Customers :
Here are Stages for Migration from QMetry 5 to QMetry 6
Stage 1 : Upgrade QMetry 5 Version : QMetry 5 version should be on the latest version 5.9.1.05 (Release Notes) to be able to migrate to QMetry 6. For upgrade guide open a ticket at firstname.lastname@example.org mentioning your current QMetry Version and Server OS details. Support would send a customised guide based on the details.
Stage 2 : Get the QMetry 6 Environment Ready : Refer QMetry 6 Deployment Guide to understand the server architecture and Server hardware requirements.
Stage 3 : Install QMetry 6 Staging Server & QMetry 5 Staging Server : We strongly recommend customers to migrate and test QMetry on staging environments before scheduling the production migration.
- Support Team would provide the installation guides based on the latest available QMetry Version
Stage 4 : Migration Steps and Script : Based on the Installed version of Qmetry 6. Support would send you the migration script and the guide.
Stage 5 : Test the Migration : The migration scripts are well tested at our end, however there are chances that there could some gaps after the migration, since every customer has a unique test assets. We recommend On Premise customer to verify the migration using the QMetry Post Migration Checklist.
Stage 6 : Ready QMetry 6 Production Server : After migration is complete on the staging server. QMetry 6 Staging server could be used as the Production Server. The database migration should be done again if there is any delta between Staging DB and Production DB.
For SaaS Customers :
Customers must follow the below steps to ensure successful migration of their instances
Step 1 : ‘Test’ the Tracker Integration on v5.x instance and ensure connection is successful for all the integrations. Ensure the integration is done only with "Admin" credentials. Ensure the connectivity is successful since the Integration migration scripts would stop immediately if there are issues with the connectivity.
Step 2 : Customers using Installed/On-Premise Editions of Defect Tracking tools must whitelist the following QMetry Server IP's to ensure uninterrupted connections. Customers using Hosted/On Demand Editions of Defect Tracking tools must notify their providers to whitelist the following QMetry Server IP's on their firewall. In case if the IP's are blocked, QMetry will not be able to connect the tools.
Here is the IP lists:
Step 3 : Customers must notify their integration providers for not blocking QMetry IPs since huge API calls will go to their servers during issues migration. Blocking of our IP during migration process will stop issue migration immediately.