Limitations of FSR to Azure

  • FSR to Azure currently only applies to accounts backed up with ESE using Full System Backup. This functionality does not apply to Azure VM Pro.
  • FSR to Azure does not work with local copy.
  • FSR to Azure can be slow due to the read and write speeds of the disks used by Microsoft by default.
  • VM limitations:
    • The boot disk has a maximum size of 2TB. This is because 2TB is the maximum size allowed by Microsoft for the OS VHD on a generation 1 VM. Read more on Microsoft's knowledge base here. 
    • Data disks have maximum size of 32TB.
  • We only support VHD format. This is to ensure backwards compatibility with operating systems like Windows 10 32-bit. Read more on Microsoft's knowledge base here.
  • For limitations specific to FSR to Azure on Linux, see Article 1281.

 

Troubleshooting

If you are experiencing problems with Full System Recovery to Azure, check the requirements and instructions in Article 1224 first.

If a 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 (Microsoft knowledge base).

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.

You can also check the InstantData logs located in C:\Users\(your username)\AppData\Roaming\Redstor Backup Pro\InstantData\Logs.

 

Configuration issues

  • If you get an error "[Client] does not have authorization to perform action", the issue is most likely related to roles. See Article 1291 for steps to resolve.
  • If you get an error "An existing connection was forcibly closed by the remote host", the issue may be IP address allowance. See Article 1275 for steps to resolve.