
Any ideas why this would have happened? Also note that it is only happening on our Windows 2000 virtual machines, none of the other machines are like this. Strange coincidence?
Thanks!
John Yarborough
Code: Select all
automount disable
automount scrub
exit
The only thing that has changed is that we are now backing up to a UNC path. Do I need to change from Virtual Appliance mode to Network?Removing snapshot RemoveSnapshot failed, snapshotRef "snapshot-2245", timeout "3600000" Unable to access file <unspecified filename> since it is locked Veeam Backup will attempt to remove snapshot during the next job cycle, but you may consider removing snapshot manually. Possible causes for snapshot removal failure: - Network connectivity issue, or vCenter server is too busy to serve the request - ESX host was unable to process snapshot removal request in a timely manner - Snapshot was already removed by another application BackupDisk failed Client error: The specified transports are not available. Available transports: [nbd]. Specified transports: [hotadd]. VMDK path: [[san-vol2] clientsrv1/clientsrv1.vmdk]. Server error: End of file
This is probably most typical scenario, and it definitely works. But there are a few things that can prevent this from working, like IDE disks on backed up VM for instance.jyarborough wrote:So does this mean that hotadd does not work when backing up a virtual machine sitting on a SAN through a virtual Veeam BR server sitting on the SAN to a CIFS share accessed through the Veeam server's guest OS?
Now I have to go and manually do the snapshot dance to clean up the hidden consolidation helpers. It's like it can't access the -flat.vmdk files when it is in Virtual Appliance mode but it works fine in Network Mode. Can I send any logs that would help?RemoveSnapshot failed, snapshotRef "snapshot-2256", timeout "3600000"
Unable to access file <unspecified filename> since it is locked
Veeam Backup will attempt to remove snapshot during the next job cycle, but you may consider removing snapshot manually.
Possible causes for snapshot removal failure:
- Network connectivity issue, or vCenter server is too busy to serve the request
- ESX host was unable to process snapshot removal request in a timely manner
- Snapshot was already removed by another application
BackupDisk failed
Client error: The specified transports are not available. Available transports: [nbd]. Specified transports: [hotadd]. VMDK path: [[san-vol1] TS01/TS01.vmdk].
Server error: End of file
Users browsing this forum: Baidu [Spider], Google [Bot] and 54 guests