Experience seamless platform migration for Data Center using CMT tool
Migrating your Connected Backup Data Center with an advanced Windows OS and/or your upgraded SQL Server database is a time consuming and subtle job as you have to make sure your agent communication is not broken with the migration. Often, it applies to rework the migration process due to any missed out step during manual upgrade. To overcome the hustle of manual migration, you can use the Configuration Migration Tool (CMT tool) and experience smooth and faster migration.
What is CMT tool?
Configuration Migration Tool allows Data Center migration for stand-alone, mirrored, or clustered Data Centers and their respective Web servers. It also facilitates synchronizing your Connected Backup versions (supported from v9.0.* and above). The tool is an independent executable, built for Data Center administrators intending to shorten implementation time with reduced risk and complexity related to the migration process.
How does it work?
System Checks (prior to export):
The CMT tool first checks for the system configuration before it initiates the migrations activities. As part of the system check, it looks for the availability of Data Center and SQL Server Database (for DB migration) and adequate administrative access to Database, Files and Registry.
After the system checks are passed, the tool initiates the Export operation. As part of the operation, the tool backs up all the files and information such as Data center files, Database files, Registry keys, Configuration files, Support Center and SSWSAPI files, license files etc. and keeps it in a newly created folder named with the respective machine name. CMT also captures the hostname, ip address and MAC Address of the source machine.
The tool stocks all the configuration related information of components like DataCenter, SupportCenter, Database, SSWS etc. in an xml called “MigrationConfiguration.xml” and keeps it at the Configurations Export location.
During export operation, CMT generates a log file called DCMigrate_<TimeStamp>_fileList.log in the export location, capturing a list of every file that is successfully copied, as the export progresses.
- Before initiating the Import operation, ensure that the new machine has the same hostname, domain and IP address as the original source machine have.
- License file (“License.ctd”) for the new NIC card(s) for the new server is present.
- Administrative rights in the destination system.
- Windows OS with US English locale.
- Data center is not already installed in the destination system
System Checks (prior to Import):
The CMT tool first checks for the system configuration before it initiates the migrations import activities. As part of the system check, it looks for the OS, Authentication check for services, DB directory, region and language for OS, Disk space, IP and MAC Address.
After CMT locates the MigrationConfiguration.xml from the source system, it imports all the backed up files and information from the source system and enables the required configurations, services and registry settings to ensure all the components of Connected Back and Database are up and running smoothly.
During Import operation, CMT generates a log file called DCMigrate_<TimeStamp>_fileList.log in the import location, capturing a migration progress with any error.
- Stop Data Center Services – Make sure the number of current sessions reaches zero or stays at a consistently low number before stopping all the Connected Backup services.
- Break SQL Replication – You must break the SQL replication on your mirrored or clustered Data Center configurations.
- Redirect Web Services Applications Before Migration – If you are using mirrored or clustered Data Centers, before migrating a Data Center, you can direct your agent communication (web server) to your other Data Center in the pair to avoid any service interruption for your users.
- Verify Data Integrity – Before you initiate DB migration, validate your data integrity (using DBMaint.sql script from the \DataCenter\Scripts folder.) The DB migration is not advised if there is any data integrity error.
Note: For more information and detailed migration steps, please contact our Support engineers