To migrate from a previous version of a product to the new, current version on the same host, you must:

  1. Install the product and specify an installation directory that is different from the one that is used for the previous installation.

  2. Stop the old services for the previous version, if necessary.

    For RHEL/CentOS, keep the service daemon (the sm_serviced component) running. If sm_serviced is stopped, all VMware Smart Assurance products will stop and will need to be restarted.

    For most cases, the installation program detects and stops all services, scheduled jobs, and processes that use programs or libraries that are running from the existing installation.

    It also stops the service daemon, sm_serviced, if it is running.

  3. Migrate user-customized files from the previous installation to the new installation.

  4. Reuse the customized Polling and Thresholds settings from the old repository.

    Detailed instructions are described in “Migration procedure for the same host” on page 66.

    For a test lab environment, since the two installations are on the same host, you can run both installations in parallel. For parallel installations, both installations connect to the same Broker and Global Manager, as long as the old and new product service and sm_server names are unique. In this case, you will need to rename the service and sm_server for the previous product version. Managers registered with the same Broker must have unique names.

    For a production environment, VMware, Inc. recommends that you decommission the previous version of product.

  5. Start with the top-most SAM server.

  6. An Aggregation SAM server if it is a hierarchical SAM deployment.

  7. IP Manager.

  8. Any order: Server Manager, MPLS Manager, and Network Protocol Manager.