Wondering if that is on purpose (technical issue or design flaw due to which it
is better this way)?
While looking into how volume backup (VB) functions will it be possible to
design a revert this way:
1. On the volume snapshot page a button that allows reverting original
disk to this state
2. When button is pressed
2.1. New volume is created from the VB on the backup NFS storage
2.2. VM existing partition is unmounted
2.3. the newly created volume is attached on its place
2.4. (not sure about this step) unmounted partition is removed
Is this design valid? It does not look that complicated, I will ditch in ACS
development files next week and see if it is suitable task for me.
Best regards,
Jordan
-----Original Message-----
From: Yordan Kostov <yord...@nsogroup.com>
Sent: Tuesday, June 29, 2021 12:29 PM
To: users@cloudstack.apache.org
Subject: Cloudstack backup framework
[X] This message came from outside your organization
Dear all,
I have been playing around ACS backup capabilities (4.15 with
XCP-NG) and noticed the following:
1. Full VM snapshot is short term solution for immediate revert after bad
patch change
2. Volume snapshot is long term backup solution of VM data but metadata is
not stored
Did some tests with Volume snaps as follow:
* Made some root partition schedule snaps
* Converted one snap to volume
* I could not find a way to create a new instance with that volume. Is
there a direct way (GUI and API)? It is possible to create a template but that
seems like a bit too much unnecessary steps to revert a VM.
Is it possible to revert existing VM volume from snapshot directly (from a user
perspective through the GUI.
I read the documentation –
(https://urldefense.com/v3/__http://docs.cloudstack.apache.org/en/latest/adminguide/storage.html?highlight=Snapshot*snapshot-restore__;Iw!!A6UyJA!w7oYtaRN24lFJreApwzhpLbWG_V1LHlsIfqocukmbOCLIRdtOCGGN_vIuBxUe84U$
) which also say that direct volume revert is not possible ☹.
Best regards,
Jordan
<font size="2"><font color="#D8D8D8">11!</font>
