Before an upgrade, perform the following tasks to ensure that your data is available after upgrade.
The credentials in the Migrate database for target Cloud containers must be valid at export and import. Ensure that the password does not change or expire after export and until the import completes after upgrade. If your password is pending expiration, modify the password in the Cloud provider environment and update the credentials in Migrate before you begin an export.
WARNING:If credentials are invalid during import, the Cloud container is not imported and its associated workload configurations are corrupted in the imported database. To use the same Migrate server for migrations to the target Cloud container, you must re-install PlateSpin Server, which resets the database. You must re-configure all target containers and workloads.
During the upgrade, the PlateSpin Migrate installation program transparently exports data from your existing database and re-imports it into a new database instance as required. However, as an additional measure of precaution, consider backing up your database files on the PlateSpin Server prior to the upgrade.
Log in to the PlateSpin Migrate Server host machine as the Administrator user.
On your server host, stop MS SQL services:
On the Start menu, click Run, type services.msc, then click OK.
In the Services window, right-click the SQL Server items, then select Stop.
Copy all *.mdf and *.ldf files to a location outside the product installation directory. The default location of these files is:
\Program Files\PlateSpin Migrate Server\Database
Restart MS SQL services that you stopped in Step 2.
Continue with Backing Up Your Custom Linux Blkwatch Drivers Before Upgrade
, or proceed with the upgrade as detailed in Upgrading Migrate.
During the upgrade, the PlateSpin Migrate installation program overwrites the existing Linux blkwatch drivers and copies only the precompiled drivers to the driver library. So, consider saving a copy of the custom Linux blkwatch drivers prior to the upgrade.
Log in to the PlateSpin Migrate Server host machine as the Administrator user.
Navigate to the PlateSpin Migrate installation directory such as <install-folder>\PlateSpin Migrate Server.
Open the \Packages\9D470BFF-E30F-4015-83D8-4D308A8C8B1B\ folder and copy the latest.package (x.package) file out of this folder to a temporary directory.
For example, if the folder contains 1.package, 2.package, and 3.package, copy the 3.package file to a temporary directory.
Rename x.package with the .zip file extension (x.zip) and extract the contents of this zip file to the temporary directory.
Save all the custom drivers (named CustomKernel*) content to another temporary location.
Proceed with the upgrade, as detailed in Upgrading Migrate.
After the upgrade, upload the backed-up custom Linux blkwatch drivers you need for future migrations. See KB Article 7005873.
If you have workload migrations in progress that you want to continue after an upgrade, use the Import/Export utility (ImportExportAll.bat) to export the workload migration data. See Exporting or Importing PlateSpin Migration Data. You can import the data if it is needed after an upgrade.