Windows Restore for GCP

Windows VM Restore Using Backup and DR service

Environment Setup

1. A Windows VM named backup-test-1-gcpwas created for testing.

2. Dummy workload data was generated on the D:\ drive, and the VM was onboarded to Lucidity with the D drive configured as the managed mount point.

Backup Configuration

1. A Backup Plan called windows-backup-plan was created in Backup and DR Service with the following configuration:

• Backup vault

• Scheduled backup rule

• Retention policy of 1 day

  
  

2. An on-demand backup was also triggered from the Compute Engine console.

Restore Process

Two new VMs were restored from the available backups:

• windows-scheduled-backup-restore

• windows-ondemand-backup-restore

As a pre-requisite before restoring, the required Backup Vault Service Agent IAM permissions were configured. Azure suggest this in the portal while configuring the “Choose the restore destination”

Result

The restored VMs windows-scheduled-backup-restore and windows-ondemand-backup-restore

• Preserved application data

• Retained VM tags and metadata

• Automatically appeared in the Lucidity dashboard

• Continued operating with Lucidity AutoScaler.

  
  

Environment Setup

1. A Windows VM named backup-test-2-gcpwas created and onboarded to Lucidity.

2. Dummy data was generated in the D:\ drive.

3. A machine image named vm-image was created from the instance.

   

4. A new VM was restored from the machine image windows-restored-from-machine-image

   

Result

The restored VM windows-restored-from-machine-image

• Preserved VM configuration

• Retained all attached disks

• Automatically appeared in the Lucidity dashboard

• Continued operating with Lucidity AutoScaler