Migration from DAIR to Public Cloud 

At present, only VMs can be exported. Other data, applications and/or services must be manually transferred to your private account.  

We recommend you review and make note of the following items from the DAIR Cloud interface: 

  • Static IP Addresses 
  • Domain Names and DNS 
  • Security Groups and Firewall rules 
  • Load Balancers 
  • SSH Keys 
  • Terraform Blueprints
  • Networks/Subnets 
  • Routers 
  • SSL Certificates 
  • Data Buckets 
  • Disk Volumes 
  • Backup Jobs 
  • Monitoring 
  • Environment Variables 

Register Your Personal Cloud Account 

You will need your own account with AWS or Azure. At present you are only able to export your resources to the same provider. So if you are using AWS via DAIR, you will need an AWS account. 

Step 1. Contact DAIR Support 

Contact DAIR support at https://www.canarie.ca/cloud/dair-support/ to begin your export process. You will need to provide the following information: 

  • Your tenant name in DAIR 
  • The name(s) of the instance(s) you wish to export 

If you are exporting to AWS you will also need to provide your personal AWS Account ID. You can find your Account ID on the AWS Management Console by clicking on your username and selecting “My Account”: https://console.aws.amazon.com/billing/home?#/account 

Step 2. Create a new instance from your exported images 

Once DAIR Support has contacted you and let you know that the requested export is ready, you can proceed with the steps below to create your new instance from the exported image. Please note, the process is different for each cloud provider. 

Amazon Web Services 

To create a new AWS instance we use a custom AMI exported by DAIR. Additional documentation on this process available from AWS at: https://aws.amazon.com/premiumsupport/knowledge-center/launch-instance-custom-ami 

The exported DAIR image is available in your AWS Management Console under Private Images. You can find this by: 

  1. Set your region to Canada (Central) ca-central-1 at the top of the AWS Management Console 
  1. Open the EC2 dashboard, and under Image select AMIs 

Change the filter from “Owned by Me” to “Private Images” as seen in the screenshot below:


  1. With the image highlighted open the Actions menu and select “Copy AMI” 
  • Cloning the image is necessary as the original is owned by the DAIR account and will be removed once the migration is complete 
  • Select the Region you want to copy the AMI to. DAIR uses Canada (Central) 
  • Provide the image with an identifying name and description 
  1. After the image is cloned select the new image, and from the Actions menu Launch a new instance. 
  • Pick a size that matches your original instance 
  • The default values should be suitable for most situations, customize as needed 
  • Security Group defaults to allowing SSH from all locations, secure or be aware 
  • Select or create a new AWS key – this will not impact your normal access setup 

Once instance is launched, take note of the new public IP address. You can now log in and confirm access and your applications/services are running as expected.

Microsoft Azure 

  1. Using a web browser, download the .vhd file from the URL provided to you by DAIR Support. Be sure the file ends in .vhd  

Tip: This 30GB image download may take hours depending on time of day and your internet speed. We recommend you let this run overnight and confirm the image file downloaded successfully in the morning. Errors are common and it may take more than one attempt to download your image successfully. 
Uploading the image to Azure is a multi-step process and starts in Step 2. 

  1. Using the Azure Portal, create a new Storage Account if you do not already have one. 
  • When making a new storage account, only the Basic info is required. You may create a new resource group or use an existing one. An example is shown in the screenshot below: 
  1. Create a new Blob container 
  • Open the Storage Explorer from the Azure web portal, or use the standalone application 
  • Drill down into your new storage account, and then open the Blob containers 
  • Right click on the Blob Container menu header, and create a new container 
  • Upload your vhd file to the new container 
  • Make sure the file has a vhd file suffix, and the blob type is set to Page Blob. 

With your storage account open in the storage explorer, right click on the Blob Containers and create a new container. Upload your vhd to this container. 

Tip: This 30GB image upload may take hours depending on time of day and your internet speed. We recommend you let this run overnight and confirm the image file uploaded successfully in the morning. Errors are common and it may take more than one attempt to upload your image successfully. 

  1. Now that the vhd image file is uploaded to Azure, you must create an image so that you can choose it when creating a new VM. 
    In the Azure portal open the Images service and create a new Image and fill in the form as on the right: 

NOTE: The Storage blob field will have a browse button. You can use that to find the vhd file you uploaded, or you can copy/paste the link from the Storage Explorer application. 

  1. Now that you have an image, you can go ahead and create your new Azure VM. 
    From the Azure portal, navigate to the Virtual Machines services, and create a virtual machine. You can also click this link to start creating the VM. 
  • Fill out the Create a virtual machine form as below: 
  • Be sure to pick a size that matches the size of your old instance in DAIR. 
  • For the Administration account, create a new user with a SSH public key.  Your old user on the VM will be preserved, with the new user added.
  • At the bottom of the Basic screen you will be asked about inbound port rules. 
  • Be sure to set these rules to allow the same traffic as your old instance did. 
  1. With above complete, finish the form to create the VM. Take note of the new public IP address after the instance is deployed.  
    You will be able to connect to the new VM with its new IP address and using the same access credentials as before the migration. System services will start up and be running as expected.