HP Servicecontrol Manager 3.0 User's Guide

Installing HP Servicecontrol Manager
Upgrading from Servicecontrol Manager 2.5 to 3.0
Chapter 2
41
Upgrading from Servicecontrol Manager 2.5 to 3.0
The SCM upgrade will install the 3.0 version of SCM and migrate your SCM data to be
compatible with SCM 3.0. The upgrade installation migrates all custom data including:
•users
• nodes
• node groups
• tools
• roles
• authorizations
Multiple versions of SCM cannot coexist on the same system.
NOTE You must be running SCM 2.5 to upgrade to 3.0. If you are running a version of SCM
earlier than 2.5, you must upgrade to 2.5 before upgrading to 3.0.
NOTE SCM 3.0 agents are only compatible with an SCM 3.0 central management server
(CMS). SCM 2.5 agents must be upgraded to 3.0 before you can manage them with a
CMS running SCM 3.0.
NOTE Linux managed nodes must be installed as new nodes. This procedure includes steps to
remove existing SCM software from Linux managed nodes and install SCM 3.0.
CAUTION The following directories are deleted during the SCM upgrade:
/var/mx/
/etc/opt/mx/
/opt/webadmin/mx/
/opt/mx/
If you have stored files in these directories, you need to relocate those files prior to
upgrading, or the data will be lost.
To upgrade from SCM 2.5 to 3.0:
Step 1. Verify that SCM 2.5 is running on the system.
swlist B8339BA
If SCM 2.5 isn’t running, start it.
/sbin/init.d/ServCtlMgr start
Step 2. Back-up your SCM data by copying the output of the mx commands into a file.
mxnode -ln > /directory/mxnode.scm25
mxngroup -ln > /directory/mxngroup.scm25
mxauth -lf > /directory/mxauth.scm25
mxuser -lf > /directory/mxuser.scm25