every now and then I have to restore an entire disk due to a failed installation or things like that (but luckily not due to ransomware ). Now veeam provides the great feature 'quick rollback', which suits very well in such a case and always worked perfectly. But the last months I observed that the disk very often would not get rolled back, instead it would delete the whole vmdk to build a new one!
I'm confused! Why's that the case? I mean if you delete a disk, you cannot rollback. Could it be due to the disk type (I'm using thin disks)? I've already checked the helpcenter and haven't found any hint why it wouldn't work (for instance in our case we'd have hotadd and the datastore is a DAS on our server). Please note that even if I'm not using the quick rollback, it still asks me to delete the disk, no matter what.
Yeah you're right, it doesn't matter if you used quick rollback or not. The real question is why it ever would delete the whole disk, what's the reason behind that? Using quick rollback would always be faster if the changed data is very small, but if the disk is deleted in any case, it cannot be applied.
Yeah, I did. But no matter if I tick the box or not, it will delete the disk (the message appears). Why does this message appear? I think it cannot be the general intention to delete a disk and build it from scratch. Or is that Plan A?
meanwhile I've created a ticket and talked to the support team. The explanation was: This message acts as a warning because when you restore a disk to an already existing SCSI-Node, then this disk would get overwritten. I understood this message in the sense of 'I will disk the disk during this restore'.
Obviously some active full's in the past also have reseted CBT, that's why I thought later that the whole disk was deleted because veeam couldn't use quick rollback anymore.
So everything is looking good except the misleading message
Hello,
thanks for confirming that everything works fine.
Yes, we discussed the message internally: it will stay because we want to make clear that data might be deleted because of the restore operation. While "rolled back" would be more correct, "deleted" is clearer.
). Now veeam provides the great feature 'quick rollback', which suits very well in such a case and always worked perfectly. But the last months I observed that the disk very often would not get rolled back, instead it would delete the whole vmdk to build a new one!