when VDI.enable_cbt is too slow to answer we may take the snapshot before
cbt is enabled, it fails silently , then take the snapshot , then
on the next backup cbt is enabled , but it fails because cbt started
after the last snapshot, but since cbt was enabled, the data are purged,
leading to a new full backup
from 29965
Description
Short explanation of this PR (feel free to re-use commit message)
when VDI.enable_cbt is too slow to answer we may take the snapshot before cbt is enabled, it fails silently , then take the snapshot , then on the next backup cbt is enabled , but it fails because cbt started after the last snapshot, but since cbt was enabled, the data are purged, leading to a new full backup
from 29965
Description
Short explanation of this PR (feel free to re-use commit message)
Checklist
Fixes #007
,See xoa-support#42
,See https://...
)Introduced by
CHANGELOG.unreleased.md
Review process
Notes: