Backend process for backup and restore operations (AWS)

During the backup operation, Cloud Snapshot Manager backs up the AMI ID of the VM and restores the VM using the same AMI ID.

If that VM AMI ID is not available at restore time, then you can provide another AMI that matches the earlier AMI and has the following profile:

  • Hypervisor. For example, xen.
  • VirtualizationType. For example, hvm.
  • RootDeviceType. For example, ebs.
  • Platform details. For example, Windows or Linux.

At restore time, Cloud Snapshot Manager verifies the AMI ID provided and matches it with the original VM's AMI profile. If it matches, then the restore process happens.

For example, if the original machine was Linux SUSE, and the AMI used at restore time had Ubuntu OS, even then the machine gets restored. Here, Cloud Snapshot Manager deletes the root volume of the AMI and replaces it with the OS disk that was backed up.

NOTE: Cloud Snapshot Manager backs up details like AMI ID, network configuration, security configuration, snapshot OS disk and data disks.

The following is the restore process:

  1. Bring up the VM by using the AMI ID.
  2. Restore all the disks from the snapshots.
  3. Attach all the disks to the VM and shut down the machine.
  4. Delete the root disk (which comes from the AMI) and let the OS disk restored in Step 2 be the root disk.
  5. Reboot the machine from the new OS disk.
  6. Restore network and security configurations.