The Migration is now possible only in a Windows version of Applications Manager.
You need to be on Version 13210 of Applications Manager or above to do migration, so please check the build number in the Support tab.
- Take backup of the PGSQL/MySQL Database before starting Migration.
- Install the Applications Manager with same build number by selecting MS SQL Backend, start & stop it once.
- The MSSQL Build should not be running during Migration. But MySQL/PGSQL build should be running, so please make sure that it is.
- Open Migration.properties file in AppManagerHome\conf folder in PGSQL/MySQL AppManager and enter details of the Microsoft SQL Server like hostname, port, database name, username & password same as you have provided in step 2.
# Target Database Details for migration
# we don’t need to mention port if the target server is a SQLServer instance
# For Domain authentication should be given as DomainName\\Username
Steps for Migration
1.) In the PGSQL/MySQL AppManager execute the below under AppManagerHome\bin\Migration folder in command window (make sure you run as administrator).
A specific Migration.zip file will be created in AppManagerHome/working/ location.
AppManagerMigration.zip (Professional Edition)
AdminServerMigration.zip (Admin Server)
ManagedServer_X0000000.zip (Managed Server With ServerID X)
2.) Copy your specific zip file & unzip it under the C:\ drive of the Windows server where your MSSQL database is running.
3.) Now in PGSQL AppManager, execute the below under AppManagerHome\bin\Migration folder in cmd window.
This will import your data from PGSQL/MySQL DB and insert into target DB (example: AMDB_MSSQL) in the SQL Server.
4.) Copy the below information the existing PGSQL AppManager to MSSQL AppManager installation
5.) Stop the PGSQL/MySQL AppManager and start the MS SQL AppManager. You will have all your existing monitors/configurations and reports in that with data stored in MS SQL server now.
Currently we have the following options while migrating
a. Can exclude any table without migrating
b. Can specify row limit for tables which have more rows count.
(Event or AM_Disk_MinMaxAvgData or similar tables can have million of rows, so we can set a limit if a need arises). These options can be given in migration.conf under AppManagerHome\working\conf\PGSQL\ for PGSQL build and AppManagerHome\working\conf\MySQL\ for MySQL build.
1. This step is not mandatory and may be required while very large database migration only.
2. After Migration, it is mandatory to copy and paste all the Prerequisites files needed for monitoring from MYSQL\PGSQL to the MSSQL build.
3. Once database migration is completed, please confirm that there are no failed tables. Once this is done, start the migrated build.