This line at the bottom of my previous e-mail was redundant...I meant to remove it before sending:
A vendor snapshot can be created of the hypervisor snapshot file, then CS can automatically delete On Wed, Jul 16, 2014 at 8:10 AM, Mike Tutkowski < mike.tutkow...@solidfire.com> wrote: > I believe this is what happens: > > * The VM gets quiesced. > * Hypervisor snapshots are taken of all VM disks (so a new delta file > shows up on each applicable SR). > * The applicable storage plug-in can be invoked to take a vendor-specific > snapshot of a given hypervisor snapshot delta file. > * Once the storage plug-in is done, CS can delete the hypervisor snapshot > delta file(s) that was/were created. > > A couple notes about this: > > * Since you are taking a vendor-side snap of a particular file, this > relates to NFS. > > * I believe all disks of the VM need to be supported by the same storage > vendor (i.e. if the root and data disks are on different SRs, each SR needs > to be supported by the storage of the same backend vendor) > > A vendor snapshot can be created of the hypervisor snapshot file, then CS > can automatically delete > > On Wednesday, July 16, 2014, Punith S <punit...@cloudbyte.com> wrote: > >> hi, >> >> while i was referring the ACS 4.3 doc for VM snapshot, >> i see a feature Quiesce VM supported only by vmware hypervisor if the >> cloudstack default primary storage is used, >> but it also mentions that Quiesce VM can be supported if you are using a >> third party primary storage plugin, the quiesce operation is provided by >> plugin implementation! >> >> is Quiesce VM is a limitation of XEN hypervisor or is it not implemented >> by xen agent in cloudstack ? >> >> how is third party primary storage plugin related to hypervisor feature ? >> >> -- >> regards, >> >> punith s >> cloudbyte.com >> > -- *Mike Tutkowski* *Senior CloudStack Developer, SolidFire Inc.* e: mike.tutkow...@solidfire.com o: 303.746.7302 Advancing the way the world uses the cloud <http://solidfire.com/solution/overview/?video=play>*™*
