Veeam Quick Migration job snapshot left behind

[massimiliano.rizzi]

Hello experts,

we are successfully performing several B&R 7.0 Patch #3a (build 7.0.0.839) Quick Migration jobs.

Why Veeam Quick Migration temporary source VM snapshots are not automatically removed by the Veeam Quick Migration job upon successful completion ? Is this by design ?

Is it safe to manually delete them upon successful Quick Migration job completion ?

Any help would be greatly appreciated.

Thanks and Regards,

Massimiliano

[veremin]

The helper snapshot should be automatically deleted in the end of migration activity. So, the described behavior looks unexpected.

I would recommend contacting our support team with that.

Thanks.

[massimiliano.rizzi]

Hi Vladimir,

thank you for taking the time to reply to my question.

I will contact the support team so we can take a deeper look into this.

Regards,

Massimiliano

[Vitaliy S.]

Why Veeam Quick Migration temporary source VM snapshots are not automatically removed by the Veeam Quick Migration job upon successful completion ?

Can you please clarify what source VM are you referring to? Do you see these snapshots present on the datastore without other VM files?

[massimiliano.rizzi]

Hi Vitaliy,

thank you for your reply.

I refer to the VM that has just been migrated successfully (I usually prefer to manually delete the original VM on the source host later).

You can see a couple of screen captures below:

==================================================


==================================================

Thanks and Regards,

Massimiliano

[veremin]

As mentioned, the given snapshot should have not been preserved after the quick migration activity was finished. So, please, raise this issue with our support team. Thanks.

[massimiliano.rizzi]

Hello Vladimir,

I have just filed case ID 00534445 with the support team.

Regards,

Massimiliano

[oz42]

Just for your information, for me this is a normal behaviour with B&R 6.5 and 7. Meanwhile I am used to it: delete the snapshot manually after migration. I already wondered when this will be fixed.