Way to Restore a Specific VM from Hourly Snapshots in Apache CloudStack 4.19.1.2

[pankajfromcomhard]

We are using NetApp SAN storage as the primary NFS storage in our Apache CloudStack 4.19.1.2 environment. Our SAN has the capability to take hourly snapshots of the NFS volume, ensuring data safety and quick recovery.
In case one of our got some files deleted of missing , we create a clone of the NFS repository in our NetApp SAN and mount it as a different NFS share within Apache CloudStack. This allows us to access the data as it was one hour earlier.
We have found a solution to restore a specific VM from these snapshots:
Clone the snapshot in the SAN box.
Create an NFS mount point.
Mount it on a KVM host.
Copy the volume file from the snapshot NFS to the live NFS (named ABCsnapvolume).
On the existing VM, add a new volume (abcnewvolume).
Detach the new volume.
Copy the ID of the newly created volume (abcnewvolume).
Delete the new volume (abcnewvolume).
Change the ID of ABCsnapvolume to match abcnewvolume.
Attach ABCsnapvolume to the VM.
Now, the files from one hour ago are accessible from the snapshot VM disk.
Does anyone have a shorter or more efficient method to achieve this restoration? Looking forward to insights from the community!

[rajujith]

@pankajfromcomhard Once the volume file is copied from the NFS to the target primary storage, you can use the import data volumes/ import instance from the storage feature to import and then attach the volume to the instance. You will find this under the tools tab in the left pane in the UI.

[zenbiking]

@pankajfromcomhard

What I've done

• Stop the VM from within Cloudstack
• Login to a cloudstack host, and locate/rename the qcow file(s) you want to restore
• From the NetApp CLI, perform a "volume snapshot restore-file" with the appropriate parameters to restore the individual files from the snapshot of your choice. The "restore-file" will allow you to quickly restore a single file out of a volume based snapshot without actually copying it
• Once you have restored the file, power the VM on from within Cloudstack.
• After you are happy that the restore worked, then remove the file(s) you've renamed