Task starts and completes successfully right away
Hello All,
I am testing Acronis Backup & Recovery 11.5 on my test home server. I install a trial ware on the server, but I am having a really hard time remotely installing the Agent for Windows on my workstation.
It gives a bunch of errors and unable to connect to my workstation. Anyway, I was able to install the agent manually. I extracted the installer files and installed the Acronis Core and then the Agent.
I am now able to see and connect to the workstation from the test server. I created a backup task to do a simple full backup. When I click Run now, it finishes the task successfully right away, but it does not actually back up the workstation. Any suggestions on what to check?

- Log in to post comments

Thank you for your reply.
It is currently under personal vault. I am unable to change it to centralized, but I'll keep trying to see if it makes a difference. Seems like at some point it was able to make the "catalog" file in the backup location. Here are some screenshots.
Attachment | Size |
---|---|
162555-111232.png | 9.26 KB |
162555-111235.png | 74.75 KB |
162555-111238.png | 69.57 KB |
162555-111241.png | 169.2 KB |
162555-111244.png | 182.64 KB |
162555-111247.png | 83.58 KB |
- Log in to post comments

The error 'not enough privileges to perform operations with disks' reveals the reason of failure. Most likely it happens because you have UAC enabled on a machine with agent that is not in domain and connect to it remotely. If the machine is Windows 8, you need to switch is off - http://www.acronis.com/support/documentation/ABR11.5/index.html#23964.h… . The previous help topic states that remote operation does no have this limitation for built-in administrator (which is disabled by default).
- Log in to post comments

Ok, thank you. Disabling UAC enables the server to run the backup task. I understand that if the system is part of the domain you can manage accounts with UAC disabled. I wonder if there's any way to bypass this on workgroup machines?
- Log in to post comments

It's Windows' limitation and if you connect directly to a machine using 'manage remote machine' from management console, specifying login and password it's impossible to overcome this limitation (other than use built-in administrator account). But if the machine is already added to Management Server it uses other type of connection in certain cases and then there is no such limitation. These include centralized operations initiated by Management Server (e.g. if you create centralized backup plan) and for connection performed by 'Connect Directly' in context menu in the list of Machines on Management Server.
- Log in to post comments