I have a weird problem with my backups and replicas in Veeam 9.5. Once a week, my replicas do a calculating digests on each VM and It take while. Like 7 hours for 1To... First, it happened just after that my full backups were done. So, I thought it was the reason and I decided to do replica first, then backup of the VM.
05.05.2014 · I have run into this issue a couple times recently where the proxy has gotten itself into trouble and failing the Veeam backup job. Its usually springs up out of no where after the backups have been running smoothy for months. 4/05/2014 9:07:51 PM :: Error: Client error: Failed to open VDDK disk [[DS1_Tier1_********_Controller] [1.10] […]
23.02.2017 · Digest calculating occur everytime an action which can change VM or Disk ID/size is carried out because veeam need to compare the "virtual" new VM and the target replica to keep the integrity of replica chain. Running an active full replication will make it …
28.08.2018 · Digests calculation depends on the data size. I remember previously it took roughly 1 minute to calculate digests for 1GB of data, though this was improved in one of the latest versions. But still, considering the size of your VMs, I'd …
Poor Disk Digest Performance – Veeam Replication. Recently I encountered an issue with dreadful disk digest speeds while running a Veeam replication job. It was taking days to digest a 100GB VMDK. I had over 3TB of data to digest so this simply was not acceptable. Further troubleshooting revealed the Veeam proxy being bottlenecked by a ...
04.08.2016 · Calculating digests for Hard disk 1 (60.0 GB) Error: VDDK error: 14009 (The server refused connection). Value: 0x00000922000036b9 Failed to read from a virtual disk. Failed to process [calcDiskDigestsCli]. In First attemp i can see a Warning which say 4/5/2016 1:02:12 AM :: VM disk size changed since last sync, deleting all restore points