[SOLVED] dirty/new bitmaps

[fabian]

the "snapshot is empty" part is storage specific though, is exactly what I am saying - it doesn't buy as much except complexity compared to just having a "persist bitmap" option that's hidden somewhere and documented to break all future backups if the disk is touched outside of the VM itself. the reason for having such an option is understood - the tradeoff of offering it and having people with broken backups afterwards is where the final decision hasn't been made yet

 

[kcybulski]

I'm fine with "If you enable bitmap persistence, it's your responsibility to clear dirty bitmap if you make changes to VM storage" policy.

Krzysztof

 

[KciNicK]

indeed, same as creating a storage raid 0, i wanna do it anyway, i know the risk, but no, you have to go and do it by command line, i know im not gonna touch the disk, let me poweroff/on and keep the bitmap, i need to add some cores to the vm, i don't wanna read 40tb of data again just becouse of that

 

[PhantexTech]

indeed, same as creating a storage raid 0, i wanna do it anyway, i know the risk, but no, you have to go and do it by command line, i know im not gonna touch the disk, let me poweroff/on and keep the bitmap, i need to add some cores to the vm, i don't wanna read 40tb of data again just becouse of that

I would almost say that if you are keeping massive amount of data in a virtual drive, it's not recommended. I get your point though. Until persistant bitmaps can be introduced or another alternative such as it depending in snapshots in some fashion, I would say use in-guest backup methods, like the veeam agent running inside the VM.