Skip to main content

Storage Node Issues

Thread needs solution

Hi there,

 

We are running a trial of Acronis Backup 11.7 Advanced on Windows Server 2016 and we are having issues trying to add a storage node to the Management Console, when trying to do so it just sits saying adding machine but it never does.

Basically the Server has a tape autoloader attached to it and if we install the agent on that server then we have access to the tape unit.

Once we install a management server on the same server we loose the ability from the management console to see the locally attached tape unit.

We then installed the storage node onto the server and that gets added fine however we cannot register this storage node on the management server as it just appears to hang.

We have turned off all firewalls as well as allowing ports 9876 anyway, but even tried changing the default port to something that doesn't get blocked anyway and we have the same issue.

We are using Acroins Backup 11.7 Advanced Build 50058, is this the issue in that this build doesn't support Server 2016 as a storage node?

0 Users found this helpful
frestogaslorastaswastavewroviwroclolacorashibushurutraciwrubrishabenichikucrijorejenufrilomuwrigaslowrikejawrachosleratiswurelaseriprouobrunoviswosuthitribrepakotritopislivadrauibretisetewrapenuwrapi
Posts: 250
Comments: 7092

Hello Duncan,

thank you for your posting! Windows Server 2016 is definitely supported for installation of Acronis Backup 11.7 components. It's difficult to guess without revieweing the operation logs of Acronis Storage Node. Would you send me Acronis info generated on the machine where Acronis Storage Node is installed and from machine with AMS after reproducing the issue. I'll send you an upload link in a personal message. 

Thank you, 

Many thanks for your comments, we have however resolved the issue, it was a winsock problem.

Once we reset the winsock we could then add the storage node.

frestogaslorastaswastavewroviwroclolacorashibushurutraciwrubrishabenichikucrijorejenufrilomuwrigaslowrikejawrachosleratiswurelaseriprouobrunoviswosuthitribrepakotritopislivadrauibretisetewrapenuwrapi
Posts: 250
Comments: 7092

Thank you for feeding back! Good to know, what was the root cause. 

Not entirely sure as to why the winsock required resetting, but another post on this forum suggested resetting it.

Once it was reset and the server was restarted, we could then add the storage node and all is working as expected.