The following are the methods for backing up Applications Manager, check them and use the one appropriate to you.
- Via Script File.
Use the BackupMysqlDB.bat /.sh or BackupPGSQLDB.bat/.sh available in <AppManager Home>/bin directory to take a backup copy inclusive of conf files of Applications Manager and the database backup. In this backup we take configuration files of MySQL or PGSQL DB, Applications Manager tool and data stored in DB. To restore these files back into Applications Manager you can use theRestoreMysqlDB.bat / .sh or RestorePGSQLDB.bat/.sh file in the same directory. Kindly refer the help link. Applications Manager can be running while taking backup, but to restore we have to stop it.
- DB backup alone (for MySQL backend only)
Applications Manager stores all information of the resources it monitor's in it's database. Hence you can just copy the database folder. The database folder location is<AppManager Home>/working/mysql/data/AMDB. To restore this backup you just need to replace the backup copy in AppManager_home/working/mysql/data/ folder (rename the existing folder). Applications Manager must be stopped while copying the AMDB directory.
- Complete Backup (for MySQL backend only)
This method takes a complete backup of everything in Applications Manager. Like the DB, Conf files & patches already applied in the build you are using. Here you just need to make a copy of the AppManager_home folder either zip it up or copy and paste it in a different location. To restore just paste the backup copy to the same location (rename the existing folder). Applications Manager must be stopped while copying the <AppManager Home> directory.
Note : These steps are for MySQL / PgSQL backend
database. If you are using MSSQL , take backup of the corresponding database in
your MSSQL server using steps in this after stopping Applications
To take the configuration files alone as backup you can
run BackupConfig.bat (sh) / RestoreConfig.bat (sh) available
in <AppManager Home>/bin directory.