HPE Morpheus VM Essentials Software
1869756 Members
1954 Online
110540 Solutions
New Discussion

Checkpoint Target

 
dya
Trusted Contributor

Checkpoint Target

*Note: Apologies if this is difficult to understand as it is a machine translation.

I believe there is a setting for "Checkpoint Target" in the datastore under [Cluster] - [ Storage ]. I do not understand what the difference is when this setting is enabled or disabled. Does anyone know?

◆ Question
Is there no difference whether the "Checkpoint Target" setting on the datastore is enabled or disabled?
*I personally think it might be the same whether it is enabled or disabled.

◆ Environment
    VME v 9.0.2
    HVM host 3 units
    Datastore GFS2

◆ What I tested is as follows:

  1. I enabled "Checkpoint Target" on the datastore.

  2. When provisioning the instance, I created a test VM with the disk set to "raw".

  3. I attempted a backup using Veeam.

  4. I confirmed the changes.    
    ① # virsh checkpoint-list raw-check-on
         → Nothing displayed
    ② virsh qemu-monitor-command raw-check-on '{"execute": "query-block"}' | jq '.'
         → dirty-bitmaps present
    ③ # ls -ltrA /mnt/9768f179-5719-4e41-8be0-3bc5c44b4dd9/raw-check-on/
        → No file (xml) indicating a checkpoint

◆ Results are as follows:
    No change was observed by enabling "Checkpoint Target". Additionally, I stopped and started the target VM, but at that time, as usual, dirty-bitmaps were no longer present in the result of "4-②" above.

◆ Supplementary Info
    I have an impression that it might not be good to use raw devices for anything other than shared disks. Even when taking a snapshot and restoring after that, the target DISK remained as qcow2 in the VM's xml and did not revert to raw, so startup failed.