Forum Discussion
Are all of the VMs in the policies failing, or just a few (ones with snapshot outside of NBU)? Are the VMs being selected via Intelligent Policy (query-based), or manually added to the policy? If it's query-based, I'd try adding one of the problematic VMs to a standalone policy and attempting the backup that way.
Any special network configuration that needs to be considered? VLANs, multiple interfaces, virtual name mismatch for clusters, etc. Status 13 and status 25 are very vague error codes, but they indicate to me that the problem lies between the media server and the Hyper-V host, as I would expect to see status 156 or other snapshot errors if the problem was occurring during snapshotting.
not all of the vms in the policy are failing, only those vms with a non-NBU snapshot are failing.
manual selection is in use
manually creating other policy and adding a client with non-nbu snapshot still fails the backup.
the snapshot operation gets completed and just after beginning the backup operation the error appears in the job.
Related Content
- 3 years ago
- 4 years ago
- 9 years ago