Skip to main content

Acronis Backup 11.5

Thread solved
Anonymous
Beginner

Can you give me some advice on what to do with this issue?

We have a client who purchased a license for workstation, server and virtual license. They are using VMware 4.1 with many servers which they need to backup.

The first issue that they were encountering is that they cannot connect to the AMS.

Then I gave them this steps to follow:

I just would like to verify if you were able to install the AMS? Please check the services and see if the Acronis AMS is installed.
If AMS is present or installed, this might be a firewall issue.
Please unblock port 9876 from your firewall or set a rule for it. All Acronis components communicate using this port.
Please send any feedback after.

After performing the steps, they were able to use the console.

They asked how to install using remote installation and I provided them with this link: http://www.acronis.com/en-hk/support/documentation/AcronisBackup_11.5/i…

Then they started to have an issue doing remote installation to the server with this error message: "Failed to add machine to the management server."

I asked them to perform the step 2 (specify machine using IP address.)

But they still have the same error message: "Failed to add machine to the management server."

Please advise on what should be done to fix the issue.

Attachment Size
4.jpg 26.4 KB
5.jpg 83.13 KB
6.jpg 35.02 KB
7.jpg 25.58 KB
1.jpg 35.57 KB
2.jpg 31.77 KB
3.jpg 22.25 KB
0 Users found this helpful

It seems that connect ion to the remote machine failed because of incorrect username/password. Do they use correct credentials for the remote machine (where agents are installed) in the 'add machine' dialog (by IP or by name)? Can they connect to the agent installed on the machine directly ('manage remote machine' button of the console) ?

Running inside VM should not affect it. As I understand, it fails on the last step of the remote installation - during adding the machine to the AMS. As a workaround, can you perform this action from the agent side, i.e. connect directly and change 'machine management' type to 'centralized' in 'machine options' ? Not sure what caused this behavior, though.