CaseID: 07719581
Hello,
I was wondering if anyone has seen an issue like this before.
We are trying to replicate vms from one vmware cluster to another every 30 minutes. Our old Veeam server is a physical server and when our replication job runs on that one, it works flawlessly. If we create the replication job on our new veeam server which is a vm on the target vmware cluster, it works initially for a day or so before it eventually starts to fail. We dont have any proxies setup other than the veeam servers themselves. We have CDP proxies but those are used for other jobs. We do once daily backups as well on the same servers as well using our old veeam server.
The error that shows up is: Error: Detected an invalid snapshot configuration. (An error occurred while reverting to a snapshot: A required file was not found.) If we look at the target cluster we see several old storage snapshots and if we try to delete them to consolidate the snapshots it gives us another error. The only way to clear it up at this point once this happens is to delete all of the files on the vmware datastore and remove every reference to that vm in the replication job and run it again. This works for about a day and then the issue comes back again.
Veeam support is saying its a vmware issue, which doesnt make sense to me since our other replication jobs on our old veeam server are replicating with zero errors to the same cluster. But for some reason our new veeam server is having issues. I have tickets open with broadcom as well but we are still troubleshooting with them.
-
- Lurker
- Posts: 1
- Liked: never
- Joined: Jun 09, 2025 2:14 pm
- Contact:
-
- Veeam Software
- Posts: 3857
- Liked: 652 times
- Joined: Aug 28, 2013 8:23 am
- Full Name: Petr Makarov
- Location: Prague, Czech Republic
- Contact:
Re: Veeam Replication Jobs Failing
Hello and Welcome to Veeam R&D Forums!
Since this is a revert snapshot operation fully managed by the hypervisor, with Veeam acting only as the requestor, we do not create, delete, or revert snapshots ourselves: we simply send a request to perform the operation and process the result returned by the hypervisor. In our case, this result is an error.
I would suggest that we wait for the results of the troubleshooting performed by Broadcom support.
Thanks!
Since this is a revert snapshot operation fully managed by the hypervisor, with Veeam acting only as the requestor, we do not create, delete, or revert snapshots ourselves: we simply send a request to perform the operation and process the result returned by the hypervisor. In our case, this result is an error.
I would suggest that we wait for the results of the troubleshooting performed by Broadcom support.
Thanks!
Who is online
Users browsing this forum: Bing [Bot] and 18 guests