I can try to provide a direction to look in, but take this with a grain of salt…
I believe that the XenServer best practice for ‘restoring’ a VM volume is creating a NEW volume from the snapshot and then attaching that volume to the VM INSTEAD of reverting the volume back to it’s previous state. This is a workflow that ACS currently supports. However, allowing volume revert would mean that a standard ACS workflow goes against the XenServer best practices, which could be problematic. The reason I made some changes to allow for reverting is that some storage vendors (myself included) will be coming along with alternatives to hypervisor snapshots. With these alternatives, reverting is part of our workflows. Maybe someone more knowledgeable with XenServer and best practices can validate this theory? -Chris -- Chris Suich chris.su...@netapp.com NetApp Software Engineer Data Center Platforms – Cloud Solutions Citrix, Cisco & Red Hat On Jan 13, 2014, at 8:25 AM, Nux! <n...@li.nux.ro> wrote: > On 11.01.2014 22:28, Nux! wrote: >> Hi, >> Is there any reason why we shouldn't be able to revert to a volume's >> snapshot/backup? Seems like it would be an awfully more useful feature >> than what we have now; most of the times I'd imagine people would want >> to backup AND restore occasionally. I'm particularly talking about KVM >> which is the only major HV now that ACS doesn't take VM snapshots for. >> What can I do (except coding) to make this happen? >> Lucian > > Opened https://issues.apache.org/jira/browse/CLOUDSTACK-5863 for this. > > Anyone else has any thoughts or interests in this? > > Lucian > > -- > Sent from the Delta quadrant using Borg technology! > > Nux! > www.nux.ro
