Users Guide

Upgrading an Existing Installation | Installing Single-Server Deployment
40 OMNM 6.5.3 Installation Guide
• Adaptive CLI with Perl scripts must contain valid Perl under the “strict” pragma ( use
strict;
). If you import or migrate from a previous version a Perl script that does not pass
this “strict” criterion, you must rewrite it for “strict” compliance before you can successfully
edit or copy it.
• Any configured color changes to the portal may not persist and must be re-made manually.
Similarly, customized page layouts or page order may not persist and you must typically re-
arrange them manually.
• After upgrade or installing new features or module you may need to reset newly available
permissions. New permissions permit no access by default. To see them, any administrator
user can look in the Permissions in Control panel. If you select the administrator role and see
an enabled
Add button, then upgrading added new permissions. View and change any
permissions not assigned after clicking
Add .
• If you upgrade, some device information may not appear. If this occurs, delete and rediscover
the device after upgrading. This is true of the population of Groups. When upgrading, to get
the correct population of device groups some times, you must delete the Group (for example:
Dell PowerConnect) before doing the upgrade.
• If upgrade, or any installation, has difficulties, troubleshoot by searching for “error” in
[installation root]\install.log .
• Upgrading to a different path than the default may cause path/shortcut errors.
• Upgrade may require resetting Config File portlet permissions.
• Expect first Application server restart after upgrade to be slower than usual.
• When vendors re-brand their devices, previously supported devices may appear with 6027 as
vendor. Essentially, you must delete the 6027 vendor, re-seed the relevant driver, re-start
Application server and re-discover the devices to remedy this.
• Note that some OpenManage Network Manager components may trigger virus detection. You
can either ignore such warnings or turn off your virus checker before installing.
• Make sure that you know how the old dashboard is setup before upgrading. Some upgrades
require you to re-create performance dashboards.
• Note that any time you cancel an installation in progress, remnants of the installation may
remain. Uninstall can leave remnants too.
•Run the
dbpostinstall script on the (primary) Application server too whenever you
upgrade your system and your database is on a separate server.
• Log out and log back in to OpenManage Network Manager for any permission change to take
effect.
Backing Up the Database
To back up your database, open a command shell ( Start > Run cmd , in Windows), and then type
the following at the prompt replacing USERNAME and owbusdb. By default, the database is
owbusdb , user name is root and password is dorado .
mysqldump -a -u USERNAME --password=[name] owbusdb > FILENAME.mysql
If you have Performance monitors or Traffic Flow Analyzer, you must also back up your stored
procedures otherwise they do not get restored when you restore the database. The command line
here adds
--routines . For example:
mysqldump -a -u root --password=dorado --routines owbusdb > owbusdb.mysql
This writes the owbusdb to a plain-text file called FILENAME.mysql ( owbusdb.mysql in our
examples). This file is a full backup with which you can fully restore your database in case of
problems.