"Processing EX2016 Error: Unzulässige Funktion Failed to read data from the file [E:\VM-Disks\EXG2016.vhdx]. Failed to upload disk. Agent failed to process method {DataTransfer.SyncDisk}. Exception from server: Unzulässige Funktion Failed to read data from the file [E:\VM-Disks\EXG2016.vhdx]. Unable to retrieve next block transmission command. Number of already processed blocks: [201098]. Failed to download disk 'EXG2016.vhdx'. Using the following volume for rotated drives: F:"
What does it mean?
Nothing has changed with this WIndows 2016 Exchange server.
Best regards
-
- Lurker
- Posts: 1
- Liked: never
- Joined: Nov 18, 2021 4:03 pm
- Full Name: Manfred Kö
- Contact:
-
- Veeam Software
- Posts: 3626
- Liked: 608 times
- Joined: Aug 28, 2013 8:23 am
- Full Name: Petr Makarov
- Location: Prague, Czech Republic
- Contact:
Re: an error occures backing up 1 of 5 vms #05142999
Hi Manfred and Welcome to Veeam R&D Forums,
It means that the source Data Mover could not read data from the production storage and transfer data to the target Data Mover. Perhaps, it would make sense to check other VMs that are failed, maybe all of them are located on the disk E. Also, it's worth trying to process just a single VM in parallel to minimize the load on source infrastructure during backup.
Unfortunately, there are many different causes that can provoke the error and it is not possible to solve it without examination of debug logs. I see that the case has been closed, support of free products is provided on a best-effort basis. Anyway, I suggest to open another case at least one more time, every single attempt increases chances to get in touch with our engineers.
Thanks!
It means that the source Data Mover could not read data from the production storage and transfer data to the target Data Mover. Perhaps, it would make sense to check other VMs that are failed, maybe all of them are located on the disk E. Also, it's worth trying to process just a single VM in parallel to minimize the load on source infrastructure during backup.
Unfortunately, there are many different causes that can provoke the error and it is not possible to solve it without examination of debug logs. I see that the case has been closed, support of free products is provided on a best-effort basis. Anyway, I suggest to open another case at least one more time, every single attempt increases chances to get in touch with our engineers.
Thanks!
Who is online
Users browsing this forum: AdsBot [Google] and 94 guests