How To Restore VSA Backups on Metallic

Introduction

Welcome to SoftwareONE’s BackupSimple service. This Document describes the procedure to perform the restore for a VSA backups taken for the Virtual Machines on Azure, VMware and Hyper-V applications. Below is the step by step Procedure for executing the restores for each of the platforms.

Procedure

Step 1 – Log into the Metallic Portal at https://login.metallic.io

Step 2 – Once logged in, the dashboard page loads up.

Step 3 - From the Navigation pane , click on Protect -> Virtualization

Restoring Virtual Machine:

Following options are available for the recovery of the Virtual machines:

1. Guest Files: You can restore files and folders from a guest virtual machine.
   Considerations:
   a. The Virtual Server Agent uses block-level live browse to enumerate files and folders in a backup, eliminating the need to capture metadata during backups. When browsing a virtual machine, files and folders are displayed after a short delay.
   b. Virtual machines (VMs) with encrypted blobs can be protected and fully recovered. However, guest file recovery of these VMs is not currently supported.
   

2. Attach Disk to Existing VM :When performing a restore from a backup of an Azure VM, you can choose to restore a VM disk and attach it to a different VM that already exists.

By attaching a disk to an existing VM, you can access or reuse the data on the disk without restoring the full source VM.
Considerations:
a. You can use the Attach Disk restore feature with both Azure managed disks and unmanaged disks.
b. You can use the Attach Disk restore feature from streaming backups or IntelliSnap backup copies, but not when restoring directly from IntelliSnap backups.
c. For Azure Classic: When performing a restore from a backup of an Azure VM, you cannot restore a VM disk and attach it to multiple VMs that are part of the same Cloud Service group.
d. You cannot attach a disk to a VM if the VM specified is configured with the managed storage account for boot diagnostics. Instead of using the managed storage account for boot diagnostics, use a custom storage account, and then attach the disk to the VM.
e. For encrypted VM disks, the Attach Disk restore feature is not supported.

3. Full Virtual Machine Virtual machines can be restored in place or out of place (with a different name, or to a different destination).
Considerations:
a. If you attempt to restore to Premium storage with a VM size that Azure Premium storage does not support, the restore fails.
b. Due to a Microsoft limitation, you cannot change the hostname of a restored virtual machine.
c. If the replication type for the storage account that you select for the restore is not compatible with the storage type of the source VM, the restore fails. For example, if a storage account using Zone Redundant Storage (ZRS) is selected when that storage type was not used by the source VM, the restore fails.

Please make sure to STOP/KILL the VM before initiating the In-Place restore with same name, as this will significantly improve the performance of the restores.

4. Virtual Machine Files: You can restore the virtual machine configuration and disk (VHD) files to the file system of the designated access node (also called the proxy).

Restore virtual machine files in the following situations:

• The virtual machine is running, but one of its disk has errors.

• The storage device that hosts the disks has errors or not available.