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 individual files from the snapshot of
your choice. This will allow you to pull a single file out of a volume
based snapshot
- 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

On Fri, Feb 7, 2025 at 11:34 PM pankajfromcomhard (via GitHub) <
g...@apache.org> wrote:

>
> GitHub user pankajfromcomhard added a comment to the discussion: Best Way
> to Restore a Specific VM from Hourly Snapshots in Apache CloudStack 4.19.1.2
>
> 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 VMs crashes or gets infected by a virus, 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.
>
> Currently, we can see both storage locations in Apache CloudStack and can
> browse the VM’s disk files (qcow2) from an hour ago. However, there is no
> direct option to move large files (100-500GB) between the two NFS mounts
> efficiently within CloudStack.
>
> What would be the best way to restore a specific VM from this snapshot
> without manually copying large disk files? Are there any best practices or
> tools to streamline this process?
>
>
>
> GitHub link:
> https://github.com/apache/cloudstack/discussions/10346#discussioncomment-12100854
>
> ----
> This is an automatically sent email for users@cloudstack.apache.org.
> To unsubscribe, please send an email to:
> users-unsubscr...@cloudstack.apache.org
>
>

-- 
Steve Fuller
steveful...@gmail.com

Reply via email to