67734: Acronis Cyber Protect Cloud: LACP Bonding

use Google Translate

Last update: 14-12-2020

This article describes how Acronis Cyber Protect and Acronis Cyber Protect Cloud could be made to work with specific LACP Bonding setups.

Note: Keep in mind this will work only for bonding mode 802.3ad/LACP.

Introduction

In case a physical Linux machine is configured with NIC bonding, Acronis agent needs to be informed about such configuration.

If the configuration of the Acronis Agent is not updated, you may face the following issues when recovering from Cloud:

 - recovery with reboot gets stuck and fails after a 30-45 minute timeout

 - recovery with reboot fails with the following error message:

Below error message is generic and may be caused by other sorts of Network issues.
Error code: 26738695
Fields: \{"$module":"disk_bundle_glxa64_24647"}
Message: Failed to open the archive.
------------------------
Error code: 47316996
Fields: \{"$module":"mms_bundle_glxa64_24647","Domain":"AGENT_CORE","HttpStatus":500,"Reason":"INTERNAL_ERROR","code":3}
Message: \{"domain":"AGENT_CORE","code":"INTERNAL_ERROR","debug":{"msg":"Post https://test.com/bc/idp/token: net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers)"}}
------------------------
Error code: 38207511
Fields: \{"$module":"mms_bundle_glxa64_24647","status":500}
Message: \{"domain":"AGENT_CORE","code":"INTERNAL_ERROR","debug":{"msg":"Post https://test.com/bc/idp/token: net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers)"}}
------------------------

Solution

The solution implies that the agent is already installed on the machine. This machine is expected to be used when configuring a recovery task from the Web Console.

1. Run the following command in the terminal:

#curl http://dl.acronis.com/u/kb/fix_bonding_if.sh > fix_bonding_if.sh

(!) You can also download the bonding detection script here fix_bonding_if.zip

2. Execute the script that will detect the machine's existing bonding configuration and propagate it to the Acronis media:

# bash fix_bonding_if.sh

Usage: fix_bonding_if.sh [-h help] [-i install_cronjob] [-u uninstall_cronjob] [-t time_interval]

As a result, the next time a recovery task kicks off, the adjusted configuration is loaded into the bootable environment and now it will be possible to route the Agent properly through the bonded NICs.

3. In the case of repeated restoration, the script must be run again. To ensure it restarts automatically you can set the script as a cronjob bypassing -i option. The default run interval is one hour.

Example: fix_bonding_if.sh --install_cronjob --time_interval 3

You can find more information and usage example by running the script with option -h. It will print the following:
-h, --help Print help message
-v, --version Print script version
-i, --install_cronjob Install this script as a cronjob
-u, --uninstall_cronjob Remove this script from a cronjob
-t, --time_interval Run cronjob every N hours
-b, --bonding_name Name of the bonding interface

If your interface has another name rather than bond0, you will need to run the script with -b option.

More information

  • If you decide to modify or completely remove the bonding configuration later, please run the script after the change. If the bonding configuration is removed, the script will automatically delete the related bonding settings. 
  • If you set up the script to run periodically but you don’t need it anymore you can remove it from cronjobs by running the script with  -u option.

Tags: