VM snapshot. Error: CreateSnapshot failed

[umut cilenti]

What is the solution to this problem? Is there any problem when the snapshot is deleted?

Resetting CBT per job settings for active fulls failed Details: Snapshot hierarchy is too deep.
Failed to create VM snapshot. Error: CreateSnapshot failed, vmRef vm-13706, timeout 1800000, snName VEEAM BACKUP TEMPORARY SNAPSHOT, snDescription Please do not delete this snapshot. It is being used by Veeam Backup., memory False, quiesce False
Error: Snapshot hierarchy is too deep.

[Andreas Neufert]

It looks like that the VM has existing snapshots and the amount of snapshots ran into the vSphere limitation so that you can not create an additional snapshot.
Go into vCenter to the VM and into the snapshot manager. There you can check on what kind of snapshots were present.

Are these all Veeam Snapshots? Is it a VM that you backup or is it a Replication target VM? Does the vCenter user that you have added to Veeam has the right to delete snapshots?

Here are some additional insights:
veeam-backup-replication-f2/replication ... 19768.html

[umut cilenti]

hello,
Approximately 560 GB of downward snapshots are available.
when taking a full backup
I am getting an error in the backup and it does not continue.
Will it damage the vcenter machine when I delete the snapshot?
Because the description of the error snapshots says:Please do not delete this snapshot. It is being used by Veeam Backup.

[Andreas Neufert]

Why the vcenter machine?
Do you try to backup the vcenter?

In general backup temporary snapshots are removed when the backup stops. If they can not be deleted, then something is wrong. Maybe only permission but can be something technical.

It is hard to say based on the little information that are available here. Maybe it would be a good idea to open a support case with Veeam or VMware and let them check on why the snapshots were not deleted before and then remove them together with support.

[umut cilenti]

Hello,

These are my problems, shouldn't the image be automatically deleted?
Is there a problem if I delete it myself?

https://drive.google.com/drive/u/1/my-drive

[Andreas Neufert]

The image link is not working.

[umut cilenti]

https://drive.google.com/drive/folders/ ... drive_link

[umut cilenti]

If I remove the snapshot, will there be a problem?

[Andreas Neufert]

Yes, I think you can delete these snapshots. I would delete one by one as it is heavy overhead.
As well I would do this within a maintenance window as the additional disk IO for the snapshot removal will be high.
Then you need to check as well why the snapshots where not delete in the first place.

[umut cilenti]

Alright. Why is this wrong? Shouldn't it be automatically deleted?

I left my head. My manager is very angry with me about this.

I won't delete it, I hope nothing happens. vcenter is an important machine.

[umut cilenti]

Thank you very much for your help my friend, you are a good person.

[Andreas Neufert]

I am not sure if I can follow your feedback. Let me try to explain a bit.

VMware VM snapshots outside of latest vSAN write all the new changes that happen to VMs in the snapshot files.
Which means with any change on the VM the latest snapshot is growing and growing tot he point that it will fill up the storage completely.

For this reason you should not keep snapshots manual or backup long on the VMs.
Backup Software like Veeam try to remove the snapshot as early as possible.

Now you have a lot of snapshots and can not backup the VM anymore as you ran into a VMware limitation with maximum number of snapshots.

You have to remove the snapshots to free up the consumed space, do not run into a out of storage capacity issue on the datastore and be able to continue with the backup.

Removing the snapshot is an IO intensive process. It depends on the underlaying storage how fast it is and how challenging the removal of the snapshots would be. In most of the cases you likely will not see any side effects from the removal process but if you have a storage system under high load, I would do the deletes one by one in a maintenance window just to be save.

As well you need to check with our support on why Veeam was not able to delete the snapshots automatically. I gave above already an idea what could have caused this issue (Veeam vCenter user did not get the rights to delete the snapshots), but there can be another issue.

[umut cilenti]

hello ,
Snapshot problem is over, current connection problem is present.
Could this problem be caused by the firewall port?

11/4/2024 3:27:23 PM :: Processing vCenter 7.0 Error: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond 10.10.10.204:443