Recovery scenarios for GCP VMs with read-only volumes
The following table describes how NetBackup handles the restore/recovery of GCP VMs that have read-only volumes.
Table: Recovery scenarios for read-only GCP VMs
Scenario | Handling |
|---|---|
Restoring a volume from the snapshot of an attached read-only disk, from the tab under Cloud workload. | During restore, the disk is attached in the read/write mode to the original or alternate location. |
Restoring a VM, with a read-only disk, from a crash-consistent snapshot, from the tab under Cloud workloads. | During the restore of such a VM to its original or alternate location, a read-only disk is restored in a read/write mode. |
Restoring a VM with a read-only disk, from an app-consistent snapshot, from the tab under Cloud workload. | You can attach a read-only disk to multiple VMs, but NetBackup discovers it under only one VM. For a Windows VM, the snapshot fails with a VSS error, similar to the following: Failure: flexsnap.GenericError: Failed to take snapshot (error: Failed to create VSS snapshot of the selected volumes.)" For a Linux VM, the snapshot may or may not be successful for the VM under which the disk is discovered, but fails for the rest of the VMs due to the missing dependencies. Error example: linear_flow.Flow: create snapshot (test-win) of host linux-1(len=4)' requires ['snap_google- gcepd-us-west 2-b-7534340043 132122994'] but no other entity produces said requirements\n MissingDependencies In the above case, if a snapshot is successful for a Linux VM, a read-only disk is restored in a read/write mode. |