Migration overview

Refer the Support matrix guide for software versions that require a manual migration to the latest version.

Two methods are available:

• Install and migrate on the same host

• Install and migrate on a different host

  After the installation, run the sm_migrate utility to backup the user-customized files in the previous version and migrate the files to the new version. Chapter 7, “Migration Utilities,” explains how the sm_migrate utility works.

  Disk space requirement—During a migration, the sm_migrate creates a backup of files in actions, conf, model, repos, rules, script directories. Ensure that you have disk space of four times the size of these directories available on the system. After the migration and verifying the installation, you can archive or remove the backup directories. This requirement is in addition to the minimum disk requirement outlined for each product in the Support Matrix guide.

  Server name requirement for migration—To preserve notification history and the original Source attributes of notifications in the Service Assurance Manager, the server names of underlying Domain Managers should remain the same. This way at the end of the migration of all Domain Managers, the SAM server can correctly associate the pre-existing topology and notifications with the topology and events coming from migrated Domain Managers. For example, if the Server Manager has a server name INCHARGE-ESM, do not change it to a different name for the latest release.

  Make sure that you read Install and migrate on the same host and Install and migrate on a different host in their entirety before proceeding.

  Note:

  Remove all the unused files in the /local directory. The unused files will also include RPS files and custom files created by you. The sm_migrate utility creates a backup of all the files in the local directory and copies them back to local directory. RPS and custom files can be large, and may slow down the process.