Veeam Temporary Snapshot not deleted [Case# 02453931]

[tinto1970]

HI folks,

i've noticed in many vSphere installations i manage that snapshots remain active after backup.
I've opened the case 02453931 in this scenario:

Veeam 9.5U3
VCSA 6.5U1d
ESXi 6.5U1

it actually should be a vmware issue, because in task list i see that Veeam sent the command "Remove snapshot" and the Hypervisor replied "completed".
The worst thing is that a long snapshot chain can be created, and the removal process heavyly impacts VM performances during process.

has anyone seen this too?

[veremin]

Correct, we have seen such behaviour previously. Actually, we've even implemented a feature (called Snapshot Hunter) solving this issue. It finds and removes orphaned snapshots. Thanks.

[billcouper]

Snapshot Hunter says it only detects phantom snapshots. Which are snapshots that vCenter is not aware of.
What about all the times Veeam leaves snapshots attached to a backup proxy and they still show in vCenter?
This has become an issue for me since migrating to vCenter 6.5, didn't see this issue on 5.5 at all.

[veremin]

Can you provide us with your support ticket ID for this issues, so that we can investigate the reasons of why snapshots are stuck on a backup proxy machine? Thanks.

[TomU]

I'm having the exact same issue. The snapshot chain will continue to grow to a depth of 20 and then no more can be created. Once that happens the backup fails and I have to go to vCenter and manually delete all of the snapshots. After cleaning them out the backup begins working again. I did not have this problem until switching to the vCenter Server Appliance. For some reason the snapshots aren't being removed during the backup process even though vCenter says that they are.

- Veeam Backup & Replication 9.5.0.1536
- VCSA 6.5.0 (8024368)
- ESXi 6.0U3 (5224934)

[veremin]

Tom, have you reached our support team already? If so, what was the outcome of the investigation? Thanks.

[TomU]

Not yet. I pulled the VCSA out of the backup list for now. I want to create a separate backup just for this VM and see if that makes it behave any differently.

[TomU]

Support case has been opened. I'll let you know how it turns out.

[wesprather]

I'm seeing the same thing - I did not see any follow up to this thread... I'm wondering how to resolve. thanks!

[veremin]

Kindly, create your own support ticket and share its number here. The previous case was closed by the customer without any final conclusion about root cause made. Thanks!

[orb]

I'm seeing the same thing - I did not see any follow up to this thread... I'm wondering how to resolve. thanks!

Hi,

Do you use DirectNFS as transport by any chances?

Oli

[AuGL]

I am having the same problem.

I've seen between three and 17 snapshots on VMs so far.
I've spent days with VMware Support investigating logs etc.

Environment details:
vCenter 6.7 U3.
ESXi hosts a mix of 6.7GA and latest 6.7U3 EP13 patch.
Veeam 9.5 Update 4b.
Using Hot-add mode.

Started happening late last week.
So far on virtual machines that are shut down (not running at the time of backup).
Opened a ticket on the weekend, and had some replies from the Veeam weekend engineer.
Then nothing on Monday from Veeam support, so I had to escalate the ticket via our account manager today to get further action.

Veeam support case: 03865414

[AuGL]

I put the EP13 host into maintenance mode for a week, no issue.
Took it out of maintenance mode last night, and now have a VM with disk consolidation issues.
The affected VM is shutdown, it was not running on the EP13 host at the time of backup.

[foggy]

Hi Glenn, please continue investigating with our engineers, I can see that you're in communication with them.

[AuGL]

Seems to be something with the new 6.7 EP13 and other hosts being on 6.7 GA.

Anyway, I've kept the shutdown VMs and templates on the upgraded hosts as I roll through updating the cluster, and haven't had another issue.

Cheers