Users Guide

Upgrading an Existing Installation | Installing Single-Server Deployment
OMNM 6.5.3 Installation Guide 39
Upgrading an Existing Installation
For a description of the installation user interface and the different fields and options, see
Installation User Interface on page 83.
•
Upgrading from a Previous Version
• Backing Up the Database
• Restoring Databases
• Upgrading on Windows
• Upgrading on Linux
• Importing the OMNM MySQL Database
Upgrading from a Previous Version
When you upgrade your OpenManage Network Manager installation from a previous version, keep
the following topics in mind, as they apply:
•
User Validation
• Upgrading Your Operating System
• General Upgrade Advice/Information
User Validation
The installer in recent versions prevents installation as root user in Linux.
Upgrading Your Operating System
If the OpenManage Network Manager version you plan to install does not support your operating
system version, upgrade to a supported operating system before the OpenManage Network
Manager upgrade. Upgrade your operating system as follows.
1 Back up the database.
For instructions about backing up all databases, see
Backing Up the Database on page 40.
2 Upgrade the operating system.
3 Install the original OpenManage Network Manager version on the new operating system.
4 Restore the database.
5 Proceed with the OpenManage Network Manager upgrade.
See
Restoring Databases on page 41 for instructions about restoring databases.
General Upgrade Advice/Information
• Make sure that you log out of the operating system between installations.
• Make sure that you have a new license, which is required to activate new features.
• Close and re-open browsers when upgrading.
• The following require manual migration (export, then import) from previous versions: SMTP
settings, some Scheduler items, Custom Adaptive CLIs. Some schedules may require
deletion/re-making. If you open them and they are blank, use this method.
• You must re-create topologies.
• User Names/Passwords, and User Groups (Roles) are not automatically reassigned and must
be created again manually.
• The default password policy has no restrictions on password length.