Migrate from Standalone APM server to Plugin server
Please note that these steps can be followed only if your OpManager version is 127104 or above.
Migration Steps from Standalone Server To Plug-In Server:
In the standalone server, go to AppManager\bin directory and run BackupConfig.bat\.sh file to take a backup of Config files and then proceed by following the below steps.
Point to remember for Enterprise Edition:
- If you are migrating from standalone to Plugin, OpManager should also be in the Enterprise setup with same number of Central and Probe Servers.
- MySQL database is not supported in OpManager
- Applications Manager version must be compatible to OpManager version.
- Backup taken from Managed server in standalone must be restored in Plugin Managed Server with the same Server ID. (Server ID of Plugin installed can be found in AMServer.properties file (keyName : am.server.startresidrange) in AppManager\conf folder)
PGSQL Database:
1. Install a Applications Manager plugin instance with the same build number as the Standalone Applications Manager server, under the respective OpManager server.
2. Start the OpManager server once and stop it.
3. Take a backup of the database from the standalone server using the script as shown below:
Go to $AppManager_Home\bin directory in command prompt. (Run as Administrator)
Execute the backup script as follows:
In Windows:
- AppManager\bin > BackupPGSQLDB.bat --database
In Linux:
- AppManager/bin# sh BackupPGSQLDB.sh --database
The backup ZIP file will be generated under AppManager\working\backup folder.
4. Move the ZIP file to the OpManager\AppManager\working\backup folder of the new plugin installation.
5. Execute the restore script using above backup zip file as shown below:
In Windows:
- OpManager\AppManager\bin > RestorePGSQLDB.bat <Absolute path of backup ZIP file>
In Linux:
- OpManager/AppManager/bin# sh RestorePGSQLDB.sh <Absolute path of backup ZIP file>
6. Save the below queries in a text files called Queries.txt under OpManager/AppManager/working directory.
- delete from am_globalconfig where name='ADMIN_CONFIG_VERSION';
- delete from AM_UserPasswordTable;
- delete from AM_UserGroupTable;
7. Go to $OpManager_HOME/AppManager/bin directory in command prompt. (Run as Administrator)
In Windows:
- OpManager\AppManager\bin > BackupPGSQLDB.bat --queries
In Linux:
- OpManager/AppManager/bin# sh BackupPGSQLDB.sh --queries
8.. Once you execute the above steps, execute the config file backup and restore using the steps given in the CONFIG files backup and Restore section.
Microsoft SQL Database:
1. Install the plugin build with the same build number as the Standalone Applications Manager server. Both OpManager and AppManager Plugin should pointing to same Microsoft SQL server which is used in Standalone Applications Manager database server.
2. Once installed, navigate to OpManager\AppManager\conf\Plugin.properties file and update the database name to match the existing database in Standalone Applications Manager in the same MSSQL Server.
3. Connect to the database in SQL Server using SQL Management studio and execute the following queries:
- delete from am_globalconfig where name='ADMIN_CONFIG_VERSION';
- delete from AM_UserPasswordTable;
- delete from AM_UserGroupTable;
4. Once you implement the above steps, execute the config file backup and restore using steps given below.
5. Restart the OpManager Server once.
CONFIG files backup and Restore
1. Execute the backup config Script as follows:
In Windows:
- AppManager\bin > BackupConfig.bat
In Linux:
- AppManager/bin# sh BackupConfig.sh
2. The backup ZIP file will be generated under $AppManager\working\backup directory.
3. In the new installation, take the copy of the AMServer.properties file under $OpManager\AppManager\conf directory.
4. Move the ZIP file (from the standalone installation) to the $OpManager\AppManager\working\backup folder of the new standalone installation.
5. Execute the restore Script (in the new plugin installation) as given below:
In Windows:
- OpManager\AppManager\bin > RestoreConfig.bat <Absolute path of backup ZIP file under OpManager\AppManager\working\backup folder>
In Linux:
- OpManager/AppManager/bin# sh RestoreConfig.sh <Absolute path of backup ZIP file OpManager/AppManager/working/backup folder>
6. Once above script has been executed, paste the AMServer.properties file taken as backup copy in previous step.
7. Edit the AMServer.properties file and update value of am.appmanager.hostname, am.db.port, am.webserver.port if required.
NOTE: Backup configuration zip file name starts with the name "backupconfzip.New to ADSelfService Plus?
Related Articles
Troubleshooting Applications Manager Plugin database migration failure after service pack upgrade of OPM and APM plugin
When upgrading OpManager from version 12.6.xxx to 12.7.xxx and updating the APM Plugin to 1651x, particularly when using Postgresql as the backend database, an essential one-time migration occurs. This migration involves moving our backend Postgresql ...Upgrade guide for OpManager v 12.7 and APM Plugin
After downloading the service pack for OpManager and the compatible service pack for Applications Manager Plugin (APM Plugin) to OpManager installed server, start the upgrade process for OpManager and APM Plugin by following the steps below: Note: If ...Self monitor Applications Manager using APM Insight Java Agent
Applications Manager is built with Java, hence we can monitor it using APM Insight Java Agent to measure it's performance continuously, which can be very much useful. Setting up APM Insight Java Agent Follow the below steps to download and set up the ...APM Plugin Migration
How do I migrate Applications Manager plugin installed in one machine to a different machine? 1. First migrate the OpManager from the old server to the new server with same backend database. 2. Install Applications Manager plugin in the new server ...APM Plugin Migration from one server to another
Please follow the steps give below to migrate APM Plugin from one server to another: 1. For migrating APM Plugin setup of Applications Manager from one server to another, you have to migrate OpManager also from one machine to another. 2. Install a ...