Azure#
Installation requirements#
- VHD with Hystax Migration (provided by request).
- Deploy Hystax Migration from this VHD with not less than a Standard D4s v3 (4 vCPUs, 16GB RAM and 200GB disk).
- Create an account for the application with Contributor rights, as described in the doc: https://docs.microsoft.com/en-us/azure/active-directory/develop/howto-create-service-principal-portal
- SMTP server with TLS/SSL encryption.
-
Security Groups allowing the following traffic:
-
Hystax Migration host:
- Ingress -- tcp/443,
- Ingress -- tcp/4443,
- Ingress -- udp/12201.
-
Hystax Cloud Agent (spawned automatically in the Target Project):
- Ingress -- tcp/80,
- Ingress -- tcp/15000.
-
Installation steps#
Cloud configuration#
1. Create a machine from the Hystax Migration VHD with key pair attached.
Note
Adding a key pair is highly recommended to provide you with SSH access to the machine. Although Hystax Engineering team is able to perform maintenance checks and troubleshooting (as long as the network is reachable and your security groups allow the corresponding traffic), it is better to have your own means of accessing the Migration instance. Please refer to Microsoft's official documentation on adding an SSH public-private key pair for Linux VMs in Azure.
2. Associate a Public IP with the created machine.
Pass Migration initial configuration#
Wait 10-20 minutes for the platform to boot up, open a web browser and go to https://<PLATFORM_IP_ADDRESS>/. Please accept the certificate warnings to be redirected to the initial configuration page.
If the platform is inaccessible, refer to this instruction.
Step 1. Admin user creation.
Enter the organization name and new Hystax Admin User credentials into the Setup Wizard. This is the user account for logging in to Hystax Migration Control Panel and managing the system. If there are any errors, the system notifies you.

Step 2. SMTP configuration.
Fill in your Hystax License key that was supposed to be shared with you in advance as well as the settings for accessing your mail server used to send notifications from Migration and generate periodic reports.
Warning
SMTP server with TLS/SSL encryption is required to proceed with deployment.
If you prefer a public SMTP server associated with your email address (gmail, yahoo etc.), please find its settings online. In case of a private SMTP server, contact your network administrator for further details.
A sample notification is sent to the specified "Test email" to verify the functionality when you click "Next".

Step 3. Target cloud configuration.
Fill in all the fields by providing cloud configuration details. Use question mark icons to get hints on the fields. After you click "Next", the Setup Wizard validates the entered data and notifies you in case of an error.

Detailed description of the fields.
Click "Next" to start cloud validation.
Step 4. Log in.
Installation is complete, and you can now log in to the system using credentials entered in the first step.

Congratulations, you are now ready to use Migration! Just enter the administrator username and password specified on the first step of installation in the login page of the platform.