ACI

You see this alert in WebCP > Monitoring > Alerts:

No internet connection on the node <node>.

The following requirements must be met before installing upgrade to Acronis Cyber Infrastructure 3.0:

Symptoms

The following type of alert is being observed in WebCP > Monitoring > Alerts:

Network interface “<iface_name>” on node “<hostname>” is missing important features (or has them disabled): “<feature_name>”.

Cause

Acronis Cyber Infrastructure periodically checks each network interface for features that are important from performance point of view and shows the corresponding alert warning about missing features.

Symptoms

1. Backup storage was created with Acronis Cyber Infrastructure (ACI) and registered in Acronis Management Server (AMS) with some DNS name specified during configuration, e.g.:

2. Registered Acronis Cyber Infrastructure backup storage is listed in AMS > Settings > Storage Node tab:

ACI node was deployed in Azure VM per documentation "Backup Gateway Quick Start Guide for Microsoft Azure" with version less then 3.5. azure-cli package in version less than 2.0.77-1 is installed.

Attempt to perform cluster update or check updates via WebCP fails without specific error, manual attempt to update azure-cli package separately fails due to dependency issue.

Symptoms

After Acronis Cyber Infrastructure update to version 4.0, disk blink option became not available - greyed out, although this funcion was working well before update, e.g.:

Symptoms

After initiation of storage disk "Release" operation one of the following situations occurred causing disk release interruption:

1. CS located on the releasing disk failed, checked and recovered;

2. The node where releasing disk located was entered into Maintenance mode and exited from Maintenance afterwards.

Symptoms

The following alert is being observed in MONITORING > ALERTS on Acronis Cyber Infrastructure cluster with block storage configured:

Symptoms

WebCP and Grafana monitoring dashboards do not reflect performance information on any of the monitoring charts e.g:

      

Symptoms

The following situation is being observed:

1. ABGW with NFS backend is deployed, node connects to NFS share IP via interface which does not have any ACI networks assigned;

2. After update from ACI 4.5 to 4.6 vstorage-abgw service started to fail with "failed to mount" error in /var/log/vstorage/abgw.log.zst log:

Symptoms

1. On multi-node Acronis Cyber Infrastructure cluster after downloading updates via WebCP > Settings > Updates > Download there is no Install button:

2. Manual check of update status via CLI shows that one of the nodes has status uptodate while another ones are in download_completed status:

Symptoms

The following behavior is observed in Acronis Cyber Infrastructure (ACI) cluster:

1. Alerts "Node is offline" suddenly appear for all nodes in a cluster for a short period of time. During this time, status of the Storage is displayed as 'Unavailable' per WebCP dashboard.

Introduction

Backup Gateway on Microsoft Azure to store backups in the Azure cloud is being deployed per Acronis Cyber Infrastructure Backup Gateway Quick Start Guide for Microsoft Azure.

This troubleshooting guide is applicable in cases when deployment failed on the InitializeStorage step:

Symptoms

After Acronis Cyber Infrastructure (ACI) update to version 4.7 the alert of type A CS service has too big journal appeared in WebCP > Monitoring > Alerts, e.g.:

The journal of the CS#1025 on the host node01.vstoragedomain, disk sdc has size 1168M, recommended size is 282M.

Symptoms

1. Backup storage was registered initially with ACI version 4.5 and below;

2. Attempt to update ABGW certificate via WebCP > Storage Services > Backup Storage > Settings > Certificate or via CLI in ACI 4.6/4.7/5.0 fails with error like the following:

Symptoms

On attempt to perform cluster update the following error message appears as result of eligibility check:

shaman target is disabled on the following nodes:
node-hostname1
node-hostnameN

Manual check of shaman.target shows on the listed node(s) shows that it is disabled indeed:

You get this error message on attempt to check cluster updates or start updates via WebCP -> Settings -> Updates:

Failed to start update check
Yum repository is inaccessible on <node_name>

Yum repository is accessible from the affected node, however, the log /var/log/vstorage-ui-agent/software-updates.log contains the following messages:

error: cannot open Packages database in /var/lib/rpm

Symptoms

On attempt to perform cluster update the following error message appears as result of eligibility check:

There are inactive nodes. Check "shaman stat -j"

Manual check of shaman stat -j shows inactive node(s):

Symptoms

Depending on the version of Acronis Cyber Infrastracture one of the following alerts may be observed in WebCP > Monitoring > Alerts:

1. With ACI version 4.0 and lower:

Disk write cache disabled for disk <disk_name> on node "<node_name>"

2. With ACI version 4.5 and higher:

Symptoms

1. Backup storage was registered initially with ACI version 4.5 and below;

2. Attempt to update ABGW certificate via WebCP > Storage Services > Backup Storage > Settings > Certificate or via CLI in ACI 4.6/4.7.0 fails with error like the following:

Cloud installation setup id '1549158355606fa6e94ef55b33886b73-1637911640' does not match the response of account server '7907a68a-af39-45b2-af96-d0971ec7e544'

In WebCP, some nodes or disks are marked as FAILED and the storage icon is shown in red.

In the output of vstorage -c <clustername> top command some of CSs are in the Failed state.

One or more of the following events are found in the vstorage -c <clustername> get-event output:
MDS WRN: CS#1025 have reported IO error on pushing chunk 1cee of 'data.0', please check disks
MDS ERR CS#1026 detected back storage I/O failure
MDS ERR CS#1026 detected journal I/O failure
MDS WRN: Integrity failed accessing 'data.0' by the client at 192.168.1.11:42356
MDS WRN: CS#1025 is failed permanently and will not be used for new chunks allocation

On July 16, 2019, Acronis released a new version of Acronis Software-Defined Infrastructure and the product was renamed into Acronis Cyber Infrastructure (ACI), starting since 3.0 version.

More information regarding the exact software versions may be found in Acronis Cyber Infrastructure Release Notes.

The documentation to the latest version of the product may be found in the  Product Documentation page.

Symptoms

Update of Acronis Cyber Infrastructure to version 5.1 fails on stage of updating "Management panel and Compute API". Error message is "Failed to do post-update actions".

In logs of Management Node following error message can be observed during period of update:

As a service provider using Acronis Cyber Protect Cloud solution you have a hybrid storage organized for storing backups such as Acronis Cyber Infrastructure. After update of ACI cluster to the version 3.5.4 (24) you started to observe failing backups with Network connection failed due to timeout error.

Symptoms

1. ACI cluster is updated to 3.5.4-24 version:

As a service provider using Acronis Backup Cloud solution you can have a Backups storage based on Acronis Cyber Infrastructure/Acronis Software-Defined Infrastructure/Acronis Storage) registered in Acronis Cyber Protect Cloud. In case if change of backup storage address is required, the approach below may be used.

Notes

1. Prior to change of storage address it is required to configure new appropriate DNS records using a new domain name;

This article contains the information about obtaining of ISO with the required Acronis Cyber Infrastructure (ACI) version for installation of the Primary or additional ACI cluster nodes.

Scenario

You have Acronis Cyber Infrastructure rolled out in VMware environment.

You want to create VMware native snapshots of virtual machines serving as Acronis Cyber Infrastructure (ACI) cluster nodes and be able to restore from these snapshots.

Solution

When setting up snapshots, take the following into consideration:

Acronis Cyber Infrastructure  (ACI) is a storage cluster, a group of servers (nodes) interconnected by the network, thus it is vital to follow the Administrator Guide - Network requirements and recommendations during cluster infrastructure planning.

As overall storage cluster performance always depends on network performance between all cluster nodes, it may be required to measure network throughput to pinpoint the network issues or estimate maximum possible throughput between the nodes. iPerf3 is a command-line tool for performing network throughput measurements which may be used as a part of network troubleshooting.

Pages