Note: For limitations specific to FSR to Azure on Linux, see Article 1281.
Three connections are important for FSR to Azure:
- Local machine to Storage Platform - used for authentication and to select the backup to be restored to Azure
- Local machine to Azure - used for creating resources, including the VM in Azure
- Azure to Storage Platform - used for restoring the actual data to the target machine in Azure (this connection requires the SP to be publicly available from Azure.)
In order to perform FSR to Azure, the user is required to authenticate with credentials that have permission to create resources in an existing subscription. An existing storage account is also required within that subscription.
If you get an error "An existing connection was forcibly closed by the remote host", the issue may be IP address whitelisting. Click here for steps to resolve.
Note: FSR to Azure does not work with local copy.
Azure has limitations on the size of the disks used by the VM:
- Boot disk has a maximum size of 2TB
- Data disks have maximum size of 32TB
- If the VM does not appear to have booted successfully, a good starting place to find out exactly what state the VM is in is Azure Boot Diagnostics.
- Because the data is being restored directly into an Azure VM, many of the log messages will only be available within that VM. In order to get to them, you can export the "Configuration Disk" (which normally ends with "VHD0") from the VM. On that disk will be the FSR agent used to perform the restore, as well as the log files from the restore.
- Check the InstantData logs at C:\Users\(your username)\AppData\Roaming\Redstor Backup Pro\InstantData\Logs
Windows post-restore connectivity
Because of the number of ways of configuring connectivity to a restored VM, the VM will initially only be assigned a private IP. There are a couple of options if the user would like to RDP to the restored machine:
- Assign a public IP to the VM: https://docs.microsoft.com/en-us/azure/virtual-network/associate-public-ip-address-vm
- Create a VPN into Azure in order to access the VM: https://docs.microsoft.com/en-us/azure/vpn-gateway/create-routebased-vpn-gateway-portal