PlateSpin Migrate includes a Web Interface that supports large scale migration of physical and virtual source workloads to target VMware containers or Microsoft Azure containers. Use this interface when you want to simultaneously migrate a large number of workloads.
Before you use the PlateSpin Migrate Web Interface to migrate workloads to Azure, you must plan the migration. See Section 4.1, Planning For Migrating Workloads to Azure.
IMPORTANT:
Do not use the PlateSpin Migrate Client and the PlateSpin Migrate Web Interface interchangeably to perform the migration tasks during the migration process of a workload. NetIQ Corporation strongly recommends that you either use the PlateSpin Migrate Client or the PlateSpin Migrate Web Interface throughout the migration cycle of a workload. For information about the migration tasks you can perform using the PlateSpin Migrate Client and the PlateSpin Migrate Web Interface, see Section 1.1.3, Migration Tasks Matrix for PlateSpin Migrate Client and PlateSpin Migrate Web Interface.
You cannot use the PlateSpin Migrate Web Interface to migrate the following:
PlateSpin Images
Workloads to the target non-VMware hypervisor containers
Workloads to target physical machines
Azure workloads to target Azure containers.
The default filename for a VM’s virtual disk uses the workload’s FQDN, such as <fqdn>_VM_N.vmdk, where N is the disk number. The total length limit of the virtual disk filename is 63 characters, including the fixed naming conventions and file extension.
You can alter certain elements of the Web Interface to match your organization branding. For more information, see Rebranding the PlateSpin Migrate Web Interface.
Review the following sections: