Administer > Service Manager Service Portal administration > Service Manager Service Portal administration tips and tasks > Migration from one Service Manager Service Portal single node to another

Migration from one Service Manager Service Portal single node to another

Note The instructions provided in this section apply to Service Manager Service Portal 9.52 HF3, 9.60 or later versions.

Service Manager Service Portal provides a migration tool that enables you to migrate a Service Manager Service Portal instance to another Service Manager Service Portal node.

The migration tool is a set of Ansible scripts that migrates data and configurations across different hosts.

Important You must install Service Manager Service Portal instances on both source and target hosts before the migration. Make sure the Service Manager Service Portal instances have the same version.

Migration overview

Tip You can perform the migration again if it fails.

The migration scripts automatically perform the following migration steps:

  1. Stop the Service Manager Service Portal services. The Service Manager Service Portal services on both the source host and the target host are stopped.

  2. Perform the pre-migration steps.

  3. Export the data and configuration from the source Service Manager Service Portal host.

  4. Import the data and configuration to the target Service Manager Service Portal host.

  5. Start the Service Manager Service Portal services on the target Service Manager Service Portal host.

Prerequisites

Ansible 2.2.0.0 must be installed on the source Service Manager Service Portal host before you can begin executing the steps in this section to migrate your single Service Manager Service Portal system.

Note The "propel" user must have the sudo privilege.

The initial steps for Service Manager Service Portal migration

If you are running Service Manager Service Portal, follow these steps.

  1. If you are running version 9.60, go to the migrator directory by running the following command:

    # cd /opt/hp/propel/migrator

    Note This directory already exists in version 9.60. If you are running version 9.52 HF3, you need to manually create the /opt/hp/propel/migrator directory and extract the zip file shipped with this document into this directory.

  2. Use "propel" to log in to the source Service Manager Service Portal host, run commands below to set up SSH keys used to access the source and target hosts.

    # ssh-keygen -t rsa -f ~/.ssh/id_rsa 
    # ssh-copy-id propel@source_propel_hostname 
    # ssh-copy-id propel@target_propel_hostname
    

Set up the Ansible inventory

Note Postgres ‘old_vip‘, ‘new_vip‘ and ports ‘old_vip_port‘, ‘new_vip_port‘ will be omitted as there is no VIP replacement needed, so there is no need to change the values of them.

# cd /opt/hp/propel/migrator
# cp inventory.ini.example inventory.ini
# vi inventory.ini

Example migrator inventory is as follows:

[source]
$source_propel_hostname
[target]
$target_propel_hostname 

[target:vars]
hosts_replacement='[ {"old":"$source_propel_hostname", "new":"$target_propel_hostname"} ]' 

Run migration shell

# ./run-migrate.sh | tee migrate.log