7.1 Preparing for Upgrade

Before you begin the upgrade, ensure that you meet the Upgrade Requirements and perform the preparatory tasks in Table 7-1.

Table 7-1 Checklist for Preparing to Upgrade PlateSpin Transformation Manager

Status

Prerequisite Task

Notes

Download the PlateSpin Transformation Manager 2019.2 OVF file.

See Section 2.1, Downloading the PTM Software.

  1. Download the <ptm-ovf-file-name>.zip file to the management workstation where you are running the VMware vSphere Client or using the vSphere Web Client in a web browser.

  2. Extract the ZIP file by using a third-party extractor; do not use the default Windows extractor.

(Automated migrations) Ensure that no PTM-controlled automated migrations or replications are in progress.

For automated migrations controlled by PTM, wait until in-progress migrations are complete, or pause migration schedules by placing the workloads in an On Hold state. Wait for in-progress replications to complete, or abort them.

NOTE:Workload migrations must remain in the On Hold state until after you have completed the upgrades for the PTM Appliance, all Migrate Connector instances, and all PlateSpin Migrate servers.

(Tracked migrations) For PlateSpin Migrate servers, ensure that no PTM-tracked migrations or replications are in progress.

For migrations being tracked by PTM, wait until in-progress migrations are complete, or pause migration schedules by using Pause Schedule for the workloads in Migrate. Wait for in-progress replications to complete, or abort them.

NOTE:Workload migrations must remain in the Paused Schedule state until after you have completed the upgrades for the PTM Appliance, all Migrate Connector instances, and all PlateSpin Migrate servers.

Log out of PTM Web Interface (all users) and close the web browser.

You should not attempt to manage workloads and migrations during the upgrade.

On each remote PlateSpin Migrate Connector host server, stop the Migrate Connector instance from running.

There should be no Connector communications with the replacement PTM Appliance until the Connector software has also been upgraded.

In a console on each Connector host server, enter:

rcps_migrate_connector stop

(Optional) If you ever modified the Jetty settings on the Appliance, establish an SSH session with the Appliance and save your Jetty settings.

See Section 7.2.1, Save Jetty Settings.

(Optional) If you ever modified the default theme settings files without copying them to a custom location, save a copy of the existing default files.

See Section 7.2.2, Save Customized Default Theme Files.

Log in to the PTM Appliance Management Console and shut down the PlateSpin Migrate Connector for PTM service, then shut down the PlateSpin Transformation Manager service.

See Section 12.4.1, Starting, Stopping, or Restarting System Services.

Wait until the services stop before you continue.

Log out of the PTM Appliance Management Console and close the web browser.

Do not log in to the Appliance Management Console again except as directed to complete the upgrade.

Log in to VMware vSphere for the Appliance host, then power down the Appliance VM gracefully.

At shutdown, PTM copies essential configuration files to the /vastorage/conf/ folder, including the configuration for the Migrate Connector instance installed on the Appliance.

See Section 7.2.3, Archive Essential Configuration Files.

In vSphere, create a VM folder where you will create the 2019.2 appliance.

Name the folder something relevant (such as ptm-2019-2-<ip-address>).

In vSphere, copy the Disk 2 .vmdk (/vastorage) from the old VM folder to the new VM folder.

Disk 2 contains all essential PTM and Connector configuration files and the PTM database.

Ensure that the person who deploys the replacement appliance is a trusted user.

The upgrade requires the user to set a password for the vaadmin user and root user on the replacement appliance.

Deploy the replacement PTM appliance.

Continue with Section 7.3, Deploying a Replacement Appliance VM.