Skip to main content

Storage node auth issue

Thread needs solution

Hello,

i have Acronis server and storage node installed to the one server. Storage node was successfully created through the management console, after the creation console asked me to type credentials to it. As there is no enough info on it in Acronis manual i tried to type new login/password pair and found the system doesn't want me create it, system want me to type a valid login/password pair to access the node. Ok, i typed login and pass which are valid and it's ok. Next i need to create a backup plan and i select backup destination, i selected created node and next system ask me to type login and pass, i typed the same login and pass, but system asks me to type it again and again. So finally i can't authorize to the node, i typed even AD admin account - no result, different browsers - no result. Acronis support send me a list of logs i need to provide, but i quite sure i just need a complete manual to configure it in a right way. Does anybody have it or knows how to configure the node?

0 Users found this helpful

ignore it and create the backup plan if CREATE button is available, it'll work

or install U2, they claim to have fixed this issue

frestogaslorastaswastavewroviwroclolacorashibushurutraciwrubrishabenichikucrijorejenufrilomuwrigaslowrikejawrachosleratiswurelaseriprouobrunoviswosuthitribrepakotritopislivadrauibretisetewrapenuwrapi
Posts: 22
Comments: 3800

Evgeny,

Suggestion from Tony is correct - if "Create" button is available on the backup plan then you can ignore the prompt (click Cancel on it) - the prompt might be caused by particular browser cache. Before Update 2 it was possible to use only local administrator accounts to access Acronis Storage Node (ASN) locations. With Update 2 (build 8610+) it should be possible to use domain accounts as well, though these accounts still should have local administrator privilege on ASN machine.

Thank you.

hi,

yes, after installing the last update Backup plan creation is fine with AD account. But backup still fails:

Date and time

Dec 19, 2017, 13:55:23

Code

0x01350016+0x01350016+0x01330029+0x01350035+0x01350016+0x01350016+0x0072803B+0x0072804E+0x0072804D+0x009A0008+0x009A0008+0x00030002

Module

309

Message

Backup failed

Additional info:

------------------------
Error code: 22
Module: 309
LineInfo: 0x8D165E86FB81959B
Fields: {"$module":"mms_bundle_glxa64_7970","CommandID":"D332948D-A7A9-4E07-B76C-253DCF6E17FB"}
Message: TOL: Failed to execute the command. Backup plan 'VM Backup'
------------------------
Error code: 22
Module: 309
LineInfo: 0x8D165E86FB81959B
Fields: {"$module":"agent_protection_addon_glxa64_7970","CommandID":"D332948D-A7A9-4E07-B76C-253DCF6E17FB"}
Message: TOL: Failed to execute the command. Backup plan 'VM Backup'
------------------------
Error code: 41
Module: 307
LineInfo: 0xE6792A5EE190DE2C
Fields: {"$module":"agent_protection_addon_glxa64_7970"}
Message: Failed to execute the command.
------------------------
Error code: 53
Module: 309
LineInfo: 0x2E7E9E174F1FB719
Fields: {"$module":"agent_protection_addon_glxa64_7970","FailCount":"10"}
Message: 10 activities have not succeeded. One of them is displayed.
------------------------
Error code: 22
Module: 309
LineInfo: 0x8D165E86FB81959B
Fields: {"$module":"service_process_glxa64_7970","CommandID":"8F01AC13-F59E-4851-9204-DE1FD77E36B4"}
Message: TOL: Failed to execute the command. Backing up
------------------------
Error code: 22
Module: 309
LineInfo: 0x8D165E86FB81959B
Fields: {"$module":"gtob_backup_command_addon_glxa64_7970","CommandID":"8F01AC13-F59E-4851-9204-DE1FD77E36B4"}
Message: TOL: Failed to execute the command. Backing up
------------------------
Error code: 32827
Module: 114
LineInfo: 0xC35C04057128FEDC
Fields: {"$module":"disk_bundle_tape_off_glxa64_7970"}
Message: Backup of virtual machines has failed.
------------------------
Error code: 32846
Module: 114
LineInfo: 0xC35C04057128FF1F
Fields: {"$module":"disk_bundle_tape_off_glxa64_7970"}
Message: Not all virtual machines have been backed up.
------------------------
Error code: 32845
Module: 114
LineInfo: 0xC35C04057128FF66
Fields: {"$module":"disk_bundle_tape_off_glxa64_7970"}
Message: Failed to back up virtual machine 'APP'.
------------------------
Error code: 8
Module: 154
LineInfo: 0x09A79F20828BCB25
Fields: {"$module":"disk_bundle_tape_off_glxa64_7970","IsReturnCode":"1"}
Message: Failed to connect to the storage node.
------------------------
Error code: 8
Module: 154
LineInfo: 0xF9CB46CC20081F1F
Fields: {"$module":"disk_bundle_tape_off_glxa64_7970"}
Message: Failed to connect to the storage node.
------------------------
Error code: 2
Module: 3
LineInfo: 0xE6F03FBB5004181E
Fields: {"$module":"asyncipc_glxa64_7970"}
Message: TimedOut

 

I have ESXi appliance.

frestogaslorastaswastavewroviwroclolacorashibushurutraciwrubrishabenichikucrijorejenufrilomuwrigaslowrikejawrachosleratiswurelaseriprouobrunoviswosuthitribrepakotritopislivadrauibretisetewrapenuwrapi
Posts: 22
Comments: 3800

Evgeny,

In build #7970 (Update 1) you are using the backup agents which perform backups try to connect to Acronis Storage Node using its hostname rather than IP address, which may result in failure if this hostname cannot be resolved to IP from the appliance side like in your case.

In the recently released build #8690 (Update 2) there was an option added which allows to define how the agents will connect to particular location managed by Acronis Storage Node:

image

Therefore the possible options for you are:

1) Update to build 8690 and configure the location defining the IP address as shown on screen shot above

2) Investigate connection issue from the ESXi appliance to Acronis Storage Node:

- Open the appliance GUI console in vSphere client

- Switch to it and press Ctrl+Shift+F1/F2 key combination to switch to command prompt (Alt+F1/F2 will return back to GUI)

- Try to ping Acronis Storage Node by its hostname (#ping [ASN_hostname])

Also ensure that 9876 TCP port is opened on Acronis Storage Node side - this port is used when sending data from agents to these locations.

If nothing from the above help, please contact our support team for assistance.

Thank you.