Migrating OpManager from 32 bit version to 64 bit version
OpManager migration from 32 bit Version to 64 bit Version:
1)Stop OpManager service
2) Take a backup of OpManager database
Backup
---------
To take a backup of the data and configurations in OpManager:
Execute BackupDB.bat from OpManager Home/bin/backup directory.
*Once the backup is over, a directory "backup" is created under OpManager Home directory and the backup file with .zip extension is placed.
The name of the backup file contains the date and time at which backup is taken.
Example:BackUp_March9_2010_03_09_34_8024.zip
(In addition to the above backup, we also recommend you to take the complete OpManager folder backup for any future use, if using MSSQL database make OpManager folder backup + SQL backup)
3.Uninstall 32 bit of OpManager (Remove OpManager directory completely after uninstall)
( Make sure you have copied the OpManager/backup folder on a different location before you uninstall the current one as it contains the backup file which should be used for restoring the database after 64 bit install)
4)Download ManageEngine_OpManager_64bit.exe with the same build number from the link below :
http://archives.manageengine.com/opmanager/
5)Run the above (64 bit) exe file to install OpManager
6)Start OpManager service and make sure OpManager works fine
7)Stop OpManager service
8)Restore the OpManager database
Restore
----------
To restore the backed up data, copy the backup folder from the old install to the new OpManager install under the same directory (OpManager/backup)
(Create a new directory in the name of "backup" if you do not have one and then copy the backup file)
*Execute RestoreDB.bat from OpManager Home /bin/backup> directory with the backup file name as argument.
See example below:
\\OpManager\bin\backup>RestoreDB.bat "C:\Program Files\ManageEngine\OpManager\bin\backup\BackUp_March9_2010_03_09_34_8024.zip"
During restoration, the existing tables are dropped, new tables are created, and the data is restored in all the tables.
(Note: OpManager backup and Restore will work with same OpManager version and same build number)
Applicable for OpManager 8 version and above( build 8030 onwards)
Note: The database backup and Restore commands are different for builds above 9450, refer the link below:
http://support.manageengine.com/sd/AddSolution.sd?solID=104101
1)Stop OpManager service
2) Take a backup of OpManager database
Backup
---------
To take a backup of the data and configurations in OpManager:
Execute BackupDB.bat from OpManager Home/bin/backup directory.
*Once the backup is over, a directory "backup" is created under OpManager Home directory and the backup file with .zip extension is placed.
The name of the backup file contains the date and time at which backup is taken.
Example:BackUp_March9_2010_03_09_34_8024.zip
(In addition to the above backup, we also recommend you to take the complete OpManager folder backup for any future use, if using MSSQL database make OpManager folder backup + SQL backup)
3.Uninstall 32 bit of OpManager (Remove OpManager directory completely after uninstall)
( Make sure you have copied the OpManager/backup folder on a different location before you uninstall the current one as it contains the backup file which should be used for restoring the database after 64 bit install)
4)Download ManageEngine_OpManager_64bit.exe with the same build number from the link below :
http://archives.manageengine.com/opmanager/
5)Run the above (64 bit) exe file to install OpManager
6)Start OpManager service and make sure OpManager works fine
7)Stop OpManager service
8)Restore the OpManager database
Restore
----------
To restore the backed up data, copy the backup folder from the old install to the new OpManager install under the same directory (OpManager/backup)
(Create a new directory in the name of "backup" if you do not have one and then copy the backup file)
*Execute RestoreDB.bat from OpManager Home /bin/backup> directory with the backup file name as argument.
See example below:
\\OpManager\bin\backup>RestoreDB.bat "C:\Program Files\ManageEngine\OpManager\bin\backup\BackUp_March9_2010_03_09_34_8024.zip"
During restoration, the existing tables are dropped, new tables are created, and the data is restored in all the tables.
(Note: OpManager backup and Restore will work with same OpManager version and same build number)
Applicable for OpManager 8 version and above( build 8030 onwards)
Note: The database backup and Restore commands are different for builds above 9450, refer the link below:
http://support.manageengine.com/sd/AddSolution.sd?solID=104101
New to ADSelfService Plus?
Related Articles
Migrating OpManager from one server to another
Here are the steps to go about migrating OpManager to a new server: 1. Please click on Support->About on the OpManager webclient to make a note of the build number of the existing OpManager installation. 2. Take a backup of your existing database by ...OpManager DB migration from PGSQL to MSSQL on the same server in Version 12.3
Please follow the below mentioned steps to migrate DB from PGSQL to MSSQL on the same server. These steps are applicable only on builds 12.3.045 and above. If you are in older versions below 12.3.045, please upgrade to 12.3.045 and follow these ...Migrating OpManager from Linux installation to Windows installation
If OpManager is installed on Linux server and wants to move it to a Windows server for some reason, follow the steps below. 1.On the linux installation of OpManager, click About and check what is the build number of OpManager, download the windows ...OpManager DB migration from PGSQL to MSSQL in Version 125230
For OpManager version 125230: PGSQL to MSSQL Migration Steps : In the PGSQL setup, go to OpManager home → bin, start Command Prompt with administrator privilege from this path and run DBConfiguration.bat. In the popup shown, please chose MSSQL, check ...Vulnerabilities in OpManager 12.0
VULNERABILITY DETAILS(found in build 12000) Vulnerability 1: Unrestricted File Upload: OpManager fails to validate or improperly validates files before uploading to the system. As a result an attacker might be able to upload arbitrary JSP file and ...