Migrating your On-Premise HMP to the Cloud

Version 4.1.1 introduces support for deploying HMP on Microsoft Azure and Amazon AWS. To migrate from an on-premise HMP to a cloud deployment, see the following steps.

Note

Your on-premise HMP must be at the same version as your cloud HMP. For example, upgrade your on-premise HMP to version 4.1.1 to match the version available on Azure and AWS.

On-premise HMP

1. Ensure the on-premise HMP is at the same version as your Cloud instance. If not, upgrade your on-premise HMP first.

2. Create and download a backup of your HMP configuration settings. See Backing Up and Restoring HMP. Store the backup in a location accessible during cloud setup.

Note

The following items are not included in the backup:

• VOD recordings

• VOD poster images

• Log files

Cloud HMP

1. Create a virtual server on Amazon AWS or Microsoft Azure. See the relevant quick start guide for details:

   • Amazon AWS Quick Start Guide

   • Microsoft Azure Quick Start Guide

2. If necessary, expand the size of the /assets partition of your VM to match your on-premise HMP. See the section of the relevant quick start guide for details:

   • AWS: Expanding Disk Sizes

   • Azure: Expanding Disk Sizes

3. Ensure the necessary network security rules are defined for each required port, mirroring the firewall settings of your on-premise HMP. See the section of the relevant quick start guide for details:

   • AWS: Modifying Network Security Rules

   • Azure: Modifying Network Security Rules

4. Install TLS certificates. See Managing Certificates.

5. Restore the on-premise settings onto your cloud HMP. See Backing Up and Restoring HMP.

Copy/Move VOD Recordings

If desired, upload any VOD recordings you wish to keep from your on-premise HMP to your cloud HMP.

If your on-premise HMP uses NFS, when you restore the settings onto the cloud HMP, NFS is enabled and the restored settings are used. Update these settings as required.

Update DNS Record

If you are using the same FQDN, update your DNS CNAME record to point to your new cloud HMP.

Set-Top Boxes and Media Gateways

If you are using the same FQDN as your on-premise HMP and have updated your DNS record in the previous step, your set-top boxes and gateways should automatically connect to your new cloud HMP. However, due to DNS propagation and DNS TTL settings, they may not be immediate.

To mitigate this:

1. A few days prior to migration, reduce the TTL setting with your DNS provider (e.g., from one hour to 5 minutes). This minimizes downtime or connection issues during the migration.

2. Migrate your HMP to the cloud.

3. Update your DNS CNAME record to the cloud HMP’s address.

4. When all systems are working and stable, revert the TTL setting.

Note

Set-Top Boxes will automatically connect to the cloud HMP. However, if they are currently streaming, you must send two channel change commands from the cloud HMP for them to the new streaming topology. Set-top boxes may display a temporary 403 error on the first channel change command. Sending a second command will resolve the issue and connect them to the new streaming topology.

Reach out to Haivision Support if you have any issues.