After you have performed the tasks in Section 14.0, Preparing for Upgrade, the PTM database has been exported to a /vastorage/ptm/pg_backup.sql file on the old Disk 2, and the existing Appliance VM has been powered down gracefully.
Use the checklist in Table 15-1 to perform the deployment-related preparation for the replacement appliance.
Table 15-1 Checklist for Deploying a Replacement Appliance
|
Prerequisite Task |
Notes |
|---|---|
|
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. |
|
In vSphere, create a VM folder where you will create the appliance VM for PTM 2019.5. |
Name the folder something relevant (such as ptm-2019-5-<ip-address>). |
|
In vSphere, remove all VMware snapshots for the old Disk 2. |
Before you copy the old Disk 2 to the new location, ensure that you remove all VMware snapshots so that the /vastorage disk has the correct disk file and the latest configuration settings. |
|
In vSphere, copy the old Disk 2 .vmdk file (/vastorage) from the old VM folder to a datastore in the new VM folder, and rename it as /vastorage_old. |
The old Disk 2 contains the exported data from the existing PTM database that you will use for the replacement PTM Appliance. You will attach the /vastorage_old .vmdk file as Disk 3 until you perform the data import from the /vastorage_old/ptm/pg_backup.sql file. |
|
Download the PlateSpin Transformation Manager 2019.5 OVF file. |
See Section 2.1, Downloading the PTM Software.
|
|
Deploy the replacement PTM appliance. |
Continue with Section 15.2, Deploying a Replacement Appliance VM. |