For instructions on how to recover to Azure, see Article 1224.
FSR can be performed on the following distros:
- RHEL: 7.2, 7.3, 7.4, 7.5, 7.6, 7.7, 7.8
- Centos: 7.4, 7.5, 7.6, 7.7, 8, 8.1, 8.2
- Ubuntu: 16.04, 18.04, 20.04
The following filesystems are supported for backup:
- ext2, ext3, ext4, xfs, btrfs, vfat, fat, msdos
The following filesystems are supported for FSR:
- ext2, ext3, ext4, xfs, vfat, fat
- Unsupported filesystems will be converted to ext4 when performing FSR.
We highly recommend enabling the root user and setting a password. Logging in as the root will be useful in the event of a restore failure.
- Encrypted disks are not supported.
- Azure SSH port 22 will be left open after a restore.
- The user has the option to disable the backup service after a restore (otherwise it remains enabled by default). To re-enable the backup service if it has been disabled, use
systemctl enable backupproto enable the service and
systemctl start backupproto start it up.
- To prevent recovery issues, non-persistent paths should not be present in
/etc/fstab. See Article 1284.
Cloud-init may cause changes to security settings to be reverted on restore. For example, if a user creates an Azure VM from an image with cloud-init and sets the VM to use SSH password auth, but later changes this to SSH keys auth, then cloud-init may revert to the initial setting of SSH password auth on restore. On booting up the new machine after restoring, the user could therefore encounter the initial setting instead of the changed setting.
Please sign in to leave a comment.