Direkt zum Inhalt

Acronis Backup 12 - unable to specify local folder target for VM's

Thread needs solution

Hi,

I've been using Acronis VMProtect for some time and have now migrated to Acronis Backup 12.

If I create a backup for the PC hosting the software/management I can specify a local folder i.e. an attached USB disk as the target.

If I create a backup for one of the VM's hosted on my vCenter, the Local Folders fails to list any local drives. In fact, clicking the Browse button simply drops back to the 'Where to backup' option.

If I force the local drive by simply entering the path in the dialog, i.e. E:\, and then try to run a backup, I get an error:

Backup failed

E:\

Error code 0x01330029+0x01350016+0x01350016+0x01330021+0x009A000D+0x009A000D+0x00040007+0x0004000E

Additional info:

------------------------
Error code: 41
Module: 307
LineInfo: 0xE6792A5EE190DDE7
Fields: {"$module":"agent_protection_addon_glxa64_3500"}
Message: Failed to execute the command.
------------------------
Error code: 22
Module: 309
LineInfo: 0x8D165E86FB819595
Fields: {"$module":"mms_bundle_glxa64_3500","CommandID":"6F33AD8F-B487-4B18-87A3-C5DBD7B77B95"}
Message: TOL: Failed to execute the command. Checking sources and vault in backup plan
------------------------
Error code: 22
Module: 309
LineInfo: 0x8D165E86FB819595
Fields: {"$module":"gtob_ensure_backup_invariants_command_addon_glxa64_3500","CommandID":"6F33AD8F-B487-4B18-87A3-C5DBD7B77B95"}
Message: TOL: Failed to execute the command. Checking sources and vault in backup plan
------------------------
Error code: 33
Module: 307
LineInfo: 0x5D2A9295CC9442E7
Fields: {"$module":"gtob_ensure_backup_invariants_command_addon_glxa64_3500"}
Message: EnsureBackupInvariantsCommand: Failed to prepare the location for the backup archive.
------------------------
Error code: 13
Module: 154
LineInfo: 0x09A79F20828BCAB6
Fields: {"IsReturnCode":"1","$module":"disk_bundle_tape_off_glxa64_3500"}
Message: The vault is unavailable.
------------------------
Error code: 13
Module: 154
LineInfo: 0x90BBCA5EAF5C5C69
Fields: {"$module":"disk_bundle_tape_off_glxa64_3500"}
Message: The vault is unavailable.
------------------------
Error code: 7
Module: 4
LineInfo: 0xBE655347A99BC282
Fields: {"$module":"disk_bundle_tape_off_glxa64_3500"}
Message: Error occurred while opening the file.
------------------------
Error code: 14
Module: 4
LineInfo: 0xBE655347A99BC1D7
Fields: {"$module":"disk_bundle_tape_off_glxa64_3500"}
Message: E:\

 

Error log:

2016-09-06 10:12:30:978 140490839992064 I0135003A: Command 'Backup plan 'Entire machine to E:\'' is running.
2016-09-06 10:12:36:635 140490839992064 W009A0005: Error 0x9a0005: GetFileInfo call of FileManager failed.
| trace level: warning
| channel: tol-activity#3F1FBEFD-1574-408E-AC55-2D25EFA59E19
| line: 0x9a79f20828bcb6f
| file: k:/3500/enterprise/mms/managers/location/impl/manager.cpp:1023
| function: FindLocation
| IsReturnCode: 0x1
| $module: disk_bundle_tape_off_glxa64_3500
|
| error 0x9a0005: GetFileInfo call of FileManager failed.
| line: 0x9a79f20828bccbe
| file: k:/3500/enterprise/mms/managers/location/impl/manager.cpp:1358
| function: FillLocationInfoByFileManager
| $module: disk_bundle_tape_off_glxa64_3500
|
| error 0x920107: Failed to retrieve information about file 'E:\'.
| line: 0x4d7f75fcde07d669
| file: k:/3500/enterprise/file_manager/file_manager_impl.cpp:335
| function: GetFileInfo
| path: E:\
| $module: mms_bundle_glxa64_3500
|
| error 0x40007: Error occurred while opening the file.
| line: 0xbe655347a99bc282
| file: k:/3500/enterprise/file_manager/vfs/impl/vfs_esx_appliance.cpp:507
| function: OpenDir
| $module: disk_bundle_tape_off_glxa64_3500
|
| error 0x4000e: E:\
| line: 0xbe655347a99bc1d7
| file: k:/3500/enterprise/file_manager/vfs/impl/vfs_esx_appliance.cpp:336
| function: GetOSPathImpl
| $module: disk_bundle_tape_off_glxa64_3500
2016-09-06 10:12:36:982 140490839992064 E0135003D: Error 0x135003d: Command 'Backup plan 'Entire machine to E:\'' has failed.
| trace level: error
| channel: tol-activity#3F1FBEFD-1574-408E-AC55-2D25EFA59E19
| line: 0x4a8728dc8a1c9519
| file: k:/3500/enterprise/common/tol/gating_activity.cpp:115
| function: OnCompleted
| $module: mms_bundle_glxa64_3500
|
| error 0x1350016: TOL: Failed to execute the command. Backup plan 'Entire machine to E:\'
| line: 0x8d165e86fb819595
| file: k:/3500/enterprise/common/tol/command/command.cpp:455
| function: MakeFailResult
| CommandID: D332948D-A7A9-4E07-B76C-253DCF6E17FB
| $module: mms_bundle_glxa64_3500
|
| error 0x1350016: TOL: Failed to execute the command. Backup plan 'Entire machine to E:\'
| line: 0x8d165e86fb819595
| file: k:/3500/enterprise/common/tol/command/command.cpp:455
| function: MakeFailResult
| CommandID: D332948D-A7A9-4E07-B76C-253DCF6E17FB
| $module: agent_protection_addon_glxa64_3500
|
| error 0x1330029: Failed to execute the command.
| line: 0xe6792a5ee190dde7
| file: k:/3500/enterprise/managers/gtob/protection/agent_engine/protect_command.cpp:149
| function: SafeExecute
| $module: agent_protection_addon_glxa64_3500
|
| error 0x1350016: TOL: Failed to execute the command. Checking sources and vault in backup plan
| line: 0x8d165e86fb819595
| file: k:/3500/enterprise/common/tol/command/command.cpp:455
| function: MakeFailResult
| CommandID: 6F33AD8F-B487-4B18-87A3-C5DBD7B77B95
| $module: mms_bundle_glxa64_3500
|
| error 0x1350016: TOL: Failed to execute the command. Checking sources and vault in backup plan
| line: 0x8d165e86fb819595
| file: k:/3500/enterprise/common/tol/command/command.cpp:455
| function: MakeFailResult
| CommandID: 6F33AD8F-B487-4B18-87A3-C5DBD7B77B95
| $module: gtob_ensure_backup_invariants_command_addon_glxa64_3500
|
| error 0x1330021: EnsureBackupInvariantsCommand: Failed to prepare the location for the backup archive.
| line: 0x5d2a9295cc9442e7
| file: k:/3500/enterprise/managers/gtob/backupers/ensure_backup_invariants_command/impl/command.cpp:145
| function: SafeExecute
| $module: gtob_ensure_backup_invariants_command_addon_glxa64_3500
|
| error 0x9a000d: The vault is unavailable.
| line: 0x9a79f20828bcab6
| file: k:/3500/enterprise/mms/managers/location/impl/manager.cpp:838
| function: AddLocation
| IsReturnCode: 0x1
| $module: disk_bundle_tape_off_glxa64_3500
|
| error 0x9a000d: The vault is unavailable.
| line: 0x90bbca5eaf5c5c69
| file: k:/3500/enterprise/mms/managers/location/impl/availability_checker.cpp:109
| function: CheckAvailability
| $module: disk_bundle_tape_off_glxa64_3500
|
| error 0x40007: Error occurred while opening the file.
| line: 0xbe655347a99bc282
| file: k:/3500/enterprise/file_manager/vfs/impl/vfs_esx_appliance.cpp:507
| function: OpenDir
| $module: disk_bundle_tape_off_glxa64_3500
|
| error 0x4000e: E:\
| line: 0xbe655347a99bc1d7
| file: k:/3500/enterprise/file_manager/vfs/impl/vfs_esx_appliance.cpp:336
| function: GetOSPathImpl
| $module: disk_bundle_tape_off_glxa64_3500
 

I'm either missing something, or perhaps this is by design and VM backups are not possible to an externally attached disk connected to the machine hosting Acronis. VMProtect didn't work this way, so I presume AB12 would behave the same.

 

Neil

0 Users found this helpful

Additionally, selecting a different target, say a NAS, results in a failure too. Credentials are accepted, but after 18% progress errors with Cannot connect to the host

Error code 0x01350016+0x01350016+0x0072803B+0x0072804E+0x0072804D+0x00728012+0x01490003+0x00010424+0x0095000D+0x00728003+0x00530017+0x0053005E+0x00004650

 

Thankfully, I've still got my VMProtect working. 

Hi Neil,

I assume you are using the Acronis Appliance (seen from your logs).

My understanding from how Acronis Backup works:

- All backup sources and destinations must be reachable from the Acronis Agent
- You have to add additional storage to the Acronis Appliance to store backups "locally" (means to store in the attached storage location)

Have you tried to select the target to search for folders?

Also there is a new release (#3596) having a lot of fixes. You can download it from your online Acronis Account.

Neil wrote:

If I create a backup for one of the VM's hosted on my vCenter, the Local Folders fails to list any local drives. In fact, clicking the Browse button simply drops back to the 'Where to backup' option.

This happens only when you don't have any additional storage attached to the Acronis Appliance.

Neil, you can try to install the "Acronis Agent for VMware" into your AB12 Management Host without using the Appliance (delete in Agent list). It should be possible to store backups to locally attached volumes. (Refresh the WebUI to correctly list local volumes)

 

Thanks. I'll give it a go and let you know how I get on.

I've just installed the 3596 update too.

 

 

frestogaslorastaswastavewroviwroclolacorashibushurutraciwrubrishabenichikucrijorejenufrilomuwrigaslowrikejawrachosleratiswurelaseriprouobrunoviswosuthitribrepakotritopislivadrauibretisetewrapenuwrapi
Beiträge: 250
Kommentare: 7092

Hello Neil,

Thank you for your posting! As correctly pointed out by Raphael you 'll need to attach an additional disk to the virtual appliance so the Agent for VMware can back up to this locally attached storage. This kind of backup is normally faster than a backup via LAN and it does not consume the network bandwidth.

The virtual disk size must be at least 10 GB. Add the disk by editing the settings of the virtual machine and click Refresh. The Create storage link becomes available. Click this link, select the disk, and then specify a label for it.

Be careful when adding an already existing disk. Once the storage is created, all data previously contained on this disk will be lost.

Thank you, 

Hi Ekaterina,

I'm beginning to lose the will to live!

The USB device is attached to the Acronis Appliance (the controller is enabled and the drive is showing as connected), but the Appliance can't see the drive "There is no hard disk where the storage can be created...".

I've now connected the USB drive to the Acronis Backup PC, shared the drive, and successfully backed up the ESXi configuration to the USB 'share'. However, if I try to backup one of the VM's on the same ESXi, I get an error:

Backup failed

Cannot connect to the host

Error code 0x01350016+0x01350016+0x0072803B+0x0072804E+0x0072804D+0x00728012+0x01490003+0x00010424+0x0095000D+0x00728003+0x00530017+0x0053005E+0x00004650

Additional info:

------------------------
Error code: 22
Module: 309
LineInfo: 0x8D165E86FB819595
Fields: {"$module":"service_process_glxa64_3596","CommandID":"8F01AC13-F59E-4851-9204-DE1FD77E36B4"}
Message: TOL: Failed to execute the command. Backing up
------------------------
Error code: 22
Module: 309
LineInfo: 0x8D165E86FB819595
Fields: {"$module":"gtob_backup_command_addon_glxa64_3596","CommandID":"8F01AC13-F59E-4851-9204-DE1FD77E36B4"}
Message: TOL: Failed to execute the command. Backing up
------------------------
Error code: 32827
Module: 114
LineInfo: 0xC35C04057128FEAF
Fields: {"$module":"disk_bundle_tape_off_glxa64_3596"}
Message: Backup of virtual machines has failed.
------------------------
Error code: 32846
Module: 114
LineInfo: 0xC35C04057128FEF2
Fields: {"$module":"disk_bundle_tape_off_glxa64_3596"}
Message: Not all virtual machines have been backed up.
------------------------
Error code: 32845
Module: 114
LineInfo: 0xC35C04057128FF39
Fields: {"$module":"disk_bundle_tape_off_glxa64_3596"}
Message: Failed to back up virtual machine 'W2012.R2.3CX'.
------------------------
Error code: 32786
Module: 114
LineInfo: 0x28314C961DE7D52E
Fields: {"$module":"disk_bundle_tape_off_glxa64_3596"}
Message: Failed to prepare for backup.
------------------------
Error code: 3
Module: 329
LineInfo: 0x1CD98AAE889424F9
Fields: {"$module":"disk_bundle_tape_off_glxa64_3596"}
Message: Backup has failed.
------------------------
Error code: 1060
Module: 1
LineInfo: 0xD1AB7FA1E56EC707
Fields: {"$module":"disk_bundle_tape_off_glxa64_3596"}
Message: 
------------------------
Error code: 13
Module: 149
LineInfo: 0xD1AB7FA1E56EC82B
Fields: {"$module":"disk_bundle_tape_off_glxa64_3596"}
Message: Failed to perform the requested operation.
------------------------
Error code: 32771
Module: 114
LineInfo: 0xF56319586DEDC16E
Fields: {"$module":"disk_bundle_tape_off_glxa64_3596"}
Message: Failed to prepare for backup.
------------------------
Error code: 23
Module: 83
LineInfo: 0xC61573F663F5D92B
Fields: {"$module":"esx_srv_glxa64_3596"}
Message: Failed to get access to hard disk '[datastore1] W2012.R2.3CX/W2012.R2.3CX-000002.vmdk'.
------------------------
Error code: 94
Module: 83
LineInfo: 0xC61573F663F5D880
Fields: {"$module":"esx_srv_glxa64_3596"}
Message: Failed to open virtual disk file '[datastore1] W2012.R2.3CX/W2012.R2.3CX-000002.vmdk'.
------------------------
Error code: 18000
Module: 0
LineInfo: 0xC61573F663F5D761
Fields: {"$module":"esx_srv_glxa64_3596"}
Message: Cannot connect to the host

 

I presume it's a credentials thing, but I can't see where I can specify credentials or even what credentials to specify - vCenter? ESXi root? Something else?

VMProtect is sooooo much easier to work with. Why overcomplicate things?

 

 

You should already have specifyed the credentials when you added the VMware vCenter Server to AB12 in Devices -> Add.

As long as you can see all VMs (in Devices -> Virtual machines) registered to the vCenter your credentials should be correct. You can check the permissions for the credentials in vCenter: http://dl.managed-protection.com/u/backup/help/12/user/en-US/index.html#37160.html

But it seems more like a connection issue. Is the ESXi host pingable from AB12 Management Server and vice versa?

OK. Assuming the credentials are all OK (connected to the vCenter using admin credentials and DataCenter, all ESXi Hosts and all VM's are visible), what else is happening here.

I can connect to the vCenter Appliance web console from the AB12 Management server computer using the same VC admin credentials. I can connect to the vCenter from the vSphere Client using the VC admin credentials. I can connect to each of the ESXi hosts from the vSphere Client using the Root credentials. In fact, the using the Root credentials backing up the ESXi Host Configuration is the only backup I've managed to get to work.

 

 

 

Can you specify wether you use the Acronis ESX Appliance or Agent for VMware in your Management Server?

The Appliance will hot-add the target VM's disk image and backup the desired data.

The Agent for VMware connects to the ESXi host via NFS and performs a network-based backup (902/tcp).

In case of ESXi Config Backup SSH is used to transfer the backup (22/tcp).

So please check your firewall settings at the ESXi host.

Ok. Give me a clue.

Acronis ESX Appliances are installed on each ESXi and the installed agents for each appears to be the same (see attached screenshot).

 

 

 

Anhang Größe
390955-133285.png 87.21 KB

Ok, so the Appliances will use hot-add mode.

The datastore1 is local storage to one host which cannot be accessed by a Appliance on another host, correct?

What I can't answer is how Acronis Appliance determines whether access to the datastore is possible or not, and/or selecting the "nearest" Appliance to the datastore. The ESXi hosts firewall settings should allow access by default.

Maybe it is a good idea to open a support case.

Ok, so yesterday was a long time ago.

I'm about to give up with this software. I've decided that backup to 'local' isn't going to be practical - multiple hosts (oh, and my Acronis Appliance(s) can't see the attached USB disk so can't use it as local (USB controller and USB disk connected in the VM settings).

Back to the drawing board...

I'm now looking at backing up to a NAS and I'm getting stuck again...

Backup failed
Cannot connect to the host
Error code 0x01350016+0x01350016+0x0072803B+0x0072804E+0x0072804D+0x00728012+0x01490003+0x00010424+0x0095000D+0x00728003+0x00530017+0x0053005E+0x00004650

So, I'm running the backup from my Acronis Management computer, selected the network path (\\nas\backup-path) as the "Where to backup", and it still fails. The backup path can be browsed to from both the Acronis Managment computer and the computer being backed-up. An XML file is created on the backup destination so it certainly looks like it can see the destination path.

What can't "connect to the host"? The Acronis Management server? The target machine? The backup destination? 

All I want it to do is work like 11.7 and backup the VM's to a physical drive located on the backup computer! Why has this simple functionality been removed?

 

Neil

 

Does this clue help?

Error code: 23
Module: 83
LineInfo: 0xC61573F663F5D92B
Fields: {"$module":"esx_srv_glxa64_3596"}
Message: Failed to get access to hard disk '[datastore1] W2012.R2.3CX/W2012.R2.3CX-000002.vmdk'.

What can't access the datastore and why? 

I've now tried using the Acronis Cloud as the destination (assuming the free 250GB is active on my account). Same errors.

It looks like it's not an issue with the destination, but with the host credentials "Faile to get access to hard disk '[datastore1]...'

I must be missing something really simple? Is there an Agent missing? The Acronis Appliance is installed to each host. Is that not enough?

 

 

Neil

Neil,

You really should file a support request as it is hard to figure out what is going wrong in your configuration.

Let's go back to the original scenario which is "Backup VMs from multiple ESXi to local harddisk at the Management Server". I have a similar setup and not using the Appliances. The Management Server ist also hosting the Agent for VMware. So your Agent's local disk ist the local disk from the Management Server, could be also an USB drive. The vCenter is connected via the locally installed Agent. If you don't care about network based backups (vs. hot-add backups to local storage attached to the Appliance) it is working well. In my oppinion it is also easier to update components to a newer version.

There is a updated version released (build #3602) btw.

 

Raphael,

Thanks for the info.

Not quite at the point of throwing in the towel and opening a support case.

When you say the vCenter is connected via the locally installed Agent, which locally installed Agent are you referring to? Are you saying your Agent is installed on a Windows machine hosting the vCenter Server?

If I remove the Appliances from each of the hosts, leaving just the local agent running on the AB12 management server computer, I lose all ESXi/vCenter devices. To add the VM's to AB12, it looks like I need to install the Appliances to each host. Unless I'm missing something. My vCenter Server is an Appliance running as a VM Workstation on the AB12 Management computer. I had too many performance issues running vCenter Server for Windows (and it needed another Windows server license!).

Maybe that's what I need to do and install everything (vCenter Server, vCenter Update Server, AB12) on one single Windows Server computer. Perhaps I should rethink my infrastructure.

 

 

 

We have 3 ESXi hosts (in a Cluster), they are connected to a vCenter Server (Windows) which is a VM residing on one of the hosts.

The AB12 Mgmt Server is a technically a Windows Server VM on a standalone ESXi host (also connected to the vCenter but not part of the Cluster). The Agent for VMware is additionally installed to the AB12 Mgmt Server on the same Windows machine.

So in total you install all Acronis components to one single Windows (Server) machine.

Note: The Agent must be installed manually as the deploy wizard don't allow this from the WebUI.

For a separate setup of all components (vCenter [and separate Controller since v6.0], VUM, AB12) you need a lot of Windows licenses, thats true. 

Thanks for the info Raphael,

Just reconfiguring my setup - moving everything to the Windows server running the vCenter Update Server seeing as that had to be installed on a Windows Server. I'll let you know how it all goes.

 

Cheers

 

Neil

All now running on one server computer.

Success!!!! Backups are working! Though, I now have issues with Application-aware configurations, but that's one for a new thread.