[RESOLVED] ABR 11 Virtual Edition...VM's suddenly all failing backups
I recently upgraded from ABR 10 to 11 and everything was actually going quite well up till a few days ago. I was backing workstations and also our 4 VM's all with in OS agents. Since upgrade to ABR 11, I have deployed the Acronis appliance to our host, plugin for vCenter, and was able to get the VM's into the management server as virtual machines. It was all great and I WAS successfully doing the agent-less backups for a few days. A few days ago the datastore I was running the vm's on got full without me realizing at first and I believe it was unable to create vm snapshots in vCenter. the backups started failing right after that.
Now... I have since cleared space on the SAN where these VM datastores are and everything seemed fine. I am able to manually create VM snapshots and delete them without issue. However....My centralized plan which backs up the 4 VM's now fails every single time any backup is started. Each machine get the same list of errors starting with these two:
Error code: 11
Module: 4
LineInfo: 9d05ddc01e814d9d
Fields: $module : smb_supp_glx_pic
Message: The drive is not ready.
Error code: 640
Module: 64
LineInfo: a1d3981537c686fd
Fields: $module : disk_bundle_tape_off_glx_pic
Message: Failed to open the metadata directory.
Not sure what to try next.
Hello Chris,
I have had a similar issue with backing up VMs with ABR 11, and have had an open case with support for quite a while on it. For me the issue started after updating to the 11.0.17437 build. Support is still investigating it, but the last i heard it was an issue with the AcronisESXAppliance (linux) and authentication on the Samba share. (Even weirder is that the NAS i am using allows anonymous access, so no authentication is required.) Your error doesn't appear to be authentication related, but there is definitely an issue with the ESX Appliance and Samba.
My solution to this problem was to set up an internal FTP server (which is the same device that is serving up the samba shares), create a vault to the FTP location, and run backups to it. This has been working well for the last month.
Another comment on the Meta Directory error, support told me that they are no longer using the .meta folders for backups so it is an odd error for sure.
last two errors on all my failed VM backups:
--------------------
Error code: 640
Module: 64
LineInfo: a1d3981537c686fd
Fields: $module : disk_bundle_tape_off_glx_pic
Message: Failed to open the metadata directory.
--------------------
Error code: 20
Module: 4
LineInfo: 72bd8f1a411be0da
Fields: $module : disk_bundle_tape_off_glx_pic
Message: Access to the file is denied.
--------------------
Seems this what it! I connected to the appliance and saw the vaults but I had to reenter the credentials to access them. I changed user to proper domain\user and password and now backups are running. Thanks!