Hello,
I'm seeing failures each time my domain controller goes to back up :
"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-43, 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."
When I go into the VM in Vsphere, I see a bunch of these Temporary Snapshots that have been sitting there for months. The host died awhile back and the VM was automatically moved to another host but now shows offline, but it isn't, in fact i'm accessing Vsphere from it. This is certainly what started all of this.
Is it safe to delete these Temporary Snapshots to attempt to rectify the issue? and any idea what is going on with the VM showing disconnected?
Thanks for any help
VEEAM Support Case ID : 07416071
-
- Lurker
- Posts: 2
- Liked: never
- Joined: Sep 06, 2024 3:35 pm
- Contact:
-
- Chief Product Officer
- Posts: 32222
- Liked: 7587 times
- Joined: Jan 01, 2006 1:01 am
- Location: Baar, Switzerland
- Contact:
Re: Backup Failure
Hi, yes it's totally safe to delete then using vSphere Client. Thanks
-
- Lurker
- Posts: 2
- Liked: never
- Joined: Sep 06, 2024 3:35 pm
- Contact:
Re: Backup Failure
Good to know, thanks. This isn't Veeam related, but for the VM incorrectly showing offline, I was thinking I would shut down the VM from inside the OS and then start it up from the vSphere client. Do you foresee any problems with that? A bit hesitant since it's a Domain Controller (not a primary).
Who is online
Users browsing this forum: No registered users and 79 guests