Hi there,
is it possible to exclude a Disk from KVM-Snapshot?
The Scenario is like this: i have Server A which has two Disks: Disk 1 (Main/Boot - QCOW2) and Disk 2 ("Data Grave" - RAW).
Currently i cannot take a snapshot at all, because not all Disks are in QCOW2-Format.
So the first question is: can i somehow tell Proxmox or KVM to do the snapshot anyway? Only Disk 1 is important, and Disk 2 should not be included in any Snapshot.
Another way would be, to convert the "Data-Grave" to QCOW2, then the Snapshot option would work, but as the title says: is it possible to not include it? I do not want to "record" all the changes done on Disk 2 at all.
My last resort would be a bit blunt: i could remoe the Raw-Disk completely from the server and offer it via iSCSI. That way, the machine could create a snapshot and the Disk 2 would stay in Raw-Format and not be included.
But that option has a big overhead in comparision to adding the disk directly.
Any thoughts?
Best regards,
David
is it possible to exclude a Disk from KVM-Snapshot?
The Scenario is like this: i have Server A which has two Disks: Disk 1 (Main/Boot - QCOW2) and Disk 2 ("Data Grave" - RAW).
Currently i cannot take a snapshot at all, because not all Disks are in QCOW2-Format.
So the first question is: can i somehow tell Proxmox or KVM to do the snapshot anyway? Only Disk 1 is important, and Disk 2 should not be included in any Snapshot.
Another way would be, to convert the "Data-Grave" to QCOW2, then the Snapshot option would work, but as the title says: is it possible to not include it? I do not want to "record" all the changes done on Disk 2 at all.
My last resort would be a bit blunt: i could remoe the Raw-Disk completely from the server and offer it via iSCSI. That way, the machine could create a snapshot and the Disk 2 would stay in Raw-Format and not be included.
But that option has a big overhead in comparision to adding the disk directly.
Any thoughts?
Best regards,
David