Last night, an incremental backup job of two VMware VMs with AVVI to deduplication storage and linked duplication to tape, which has been running fine for several weeks, reported an error during the tape duplication stage for one of the VMs:
Virtueller Computer MAMMUT V-79-57344-38277 - Öffnen eines Datenträgers des virtuellen Computers nicht möglich. - WARNUNG: "VMVCB::\\10.4.4.130\VCGuestVm\(DC)zagdatactr01(DC)\vm\MAMMUT\MAMMUT\MAMMUT-000002.vmdk" ist beschädigt. Dateiprüfung nicht möglich.
Literal translation:
"Opening of a volume of the virtual computer not possible.
- Warning: "VMVCB::\\10.4.4.130\VCGuestVm\(DC)zagdatactr01(DC)\vm\MAMMUT\MAMMUT\MAMMUT-000002.vmdk" is damaged. File check not possible."
The strange thing is that this error did not appear during the backup to deduplication disk stage where data is actually copied from the VM, but only during the duplication to tape stage which to my untrained eye appears like a purely internal action of the media server for which no access to the VM should be necessary.
Where should I begin to look for possible causes of that error?