When you perform a first-time discovery of an Azure Stack, the discovery might take some considerable time (20-30 mins) because PlateSpin Migrate downloads the PlateSpin Replication Environment(PRE) image from the Azure Marketplace and uploads it to the Azure Stack. If the PlateSpin Replication Environment image is not successfully uploaded to Azure Stack, then the following messages are logged and you must manually upload the PRE image to the Azure Stack before you configure migrations to it.
Create UserImage has failed With Message: {0}
Create a User Image manually in the portal with Name {0} before continuing with the migration
For information about discovery, see Target Discovery in the Web Interface.
To manually upload the PRE image to Azure Stack:
Download the PlateSpin Replication Environment disk from the following location to a temporary folder on your computer:
https://platespinmigration2.blob.core.windows.net/vhds/azure-platespin-replication-environment-image-12.2.2.vhd?st=2018-02-09T23%3A00%3A00Z&se=2021-03-31T22%3A00%3A00Z&sp=rl&sv=2016-05-31&sr=b&sig=yb0xWeriJh7AJHEnm1LQaQQBtIYraGNnK4NL3auldD0%3D
Upload the PlateSpin Replication Environment disk from the temporary folder on your computer to a storage account in Azure Stack. Make a note of the blob storage URI where you upload the image. See Azure documentation.
Create a Linux image named PlateSpinReplicationEnvironment.
Log in to the Azure Stack Portal.
Click Images in the portal menu, then click Add in the working pane.
Specify the name of the image you want to create as PlateSpinReplicationEnvironment.
Select the subscription, resource group and location as applicable.
Set the OS disk as Linux.
In the Storage blob option, click Browse and browse to select the blob storage location where you previously uploaded the PRE image.
Select the account type and host caching policy.
Click Create.
After the PRE image is added to the Azure Stack, refresh the discovered Azure Stack by using the PlateSpin Migrate Web Interface. See Refreshing Target Host Details.
See Azure documentation.