Rohit, appreciate your guidance. If the storage plugin relies on the hypervisor‑side utilities (such as QEMU for KVM), then equivalent mechanisms will be required for every supported hypervisor to ensure consistent behavior. Considering this, we can plan to introduce VM quiescing support in a subsequent release of the storage plugin.
Additionally, we would like clarification on whether it is mandatory to move snapshots to secondary storage. For ONTAP‑managed pools specifically, the plugin currently plans to retain snapshots on the primary storage. Since ONTAP snapshots are inherently read‑only, transferring them over the data path to secondary storage is not feasible. Therefore, retaining snapshots on primary storage may be the only practical approach unless an alternative workflow is required. Thanks Rajiv Jain On Fri, Feb 27, 2026 at 5:12 PM Rohit Yadav <[email protected]> wrote: > Hi Rajiv - it depends, if the managed storage along with the hypervisor > can do the quiesce based snapshot (wherein they generally pause the > instance or flush filesystem to have a consistent snapshot). I've asked my > colleagues to review your questions and get back to you. > > > Regards. > > ________________________________ > From: Rajiv Jain <[email protected]> > Sent: Saturday, February 21, 2026 15:46 > To: [email protected] <[email protected]> > Subject: Clarification on VM Snapshot Behavior with Mixed Volume > Configurations > > Hello Team, > > I am currently developing VM‑level snapshot workflows for the NFSv3 > protocol, specifically for environments that leverage NetApp storage > through the NetApp plugin. In certain scenarios, a virtual machine may > contain a mix of managed and non‑managed volumes. > > In such cases, could you please confirm whether the existing VM snapshot > workflow is expected to fail when the quiesce option is enabled? > > Thank you, > Rajiv Jain >
