VMware Virtual Infrastructure 3 (VI3) - Adding a R.Updating vSphere ESXi from 4.0 to 4.1 with vSphere.hba / vmhba not showing up with ESXi 4.0 / 4.1.Example with NetApp for realistic expectations of.Reminder: vCenter 4.1 uses 64-bit DSN | vCenter 4.
#Download backup exec 2010 how to#
Resource name : \\VCVM\VMVCB::\\VCVM\VCGuestVm\vm\WFPSĮrror : e0009585 - Unable to open a disk of the virtual machine.Ĭlick an error below to locate it in the job log Edit the selection list properties, click the View Selection D If the server or resource no longer exists, remove it from the selection list. Make sure that all selected resources exist and are online, and then try again. Job log : C:\Program Files\Symantec\Backup Exec\Data\BEX_WCITORBTBEXEC_00155.xmlĮrror : e000848c - Unable to attach to a resource. Here are some additional copy and paste of the error logs: 4164 (64-bit)ĭesktop and Laptop Option: Version 3.1 Rev. 4164 (64-bit)Īdministration Console: Version 13.0 Rev. Once we upgraded to the R2 version, the backups began to work: 2896 (64-bit)ĭesktop and Laptop Option: Version 3.1 Rev. 2896 (64-bit)Īdministration Console: Version 13.0 Rev. Here’s the version we were initially using: What ended up being the problem was because we were not using the R2 version. V-79-57344-38277 - Unable to open a disk of the virtual machine.Īfter troubleshooting the problem for an hour and being pressed for time, we ended up calling Symantec since we had a support contract. V-79-57344-38277 – Unable to open a disk of the virtual machine Edit the selection list properties, click the View Selection Details tab, and then remove the resource.įor additional information regarding this error refer to link V-79-57344-33932 While configuring backups for a customer with Backup Exec 2010 to backup a vSphere 4 environment, we ran into multiple errors such as the following:įinal error: 0xe000848c - Unable to attach to a resource.