Compute. Run virtual machines (technical preview) on Acronis Software-Defined Infrastructure nodes in the hyper-converged mode (storage and compute on same node) or the traditional way (storage and compute on separate nodes)
The following requirements must be met before installing upgrade to Acronis Cyber Infrastructure 3.0:
System requirements for v.2.5
Storage only nodes (the same as in 2.4) or Storage + Management
The document describes manual update for Acronis Storage v. 2.x and all the additional components to the latest available update of Acronis Storage 2.4 and how to update Acronis Software-Defined Infrastructure 2.5 to later updates.
This article explains how to open Acronis Backup Gateway logs. It is required for the troubleshooting storage-related issues.
In Acronis Storage 2.0, logs were written to a .gz file. Since Acronis Storage 2.1, Acronis Software-Defined Infrastructure and Acronis Cyber Infrastructure, logs are written to a .zst file.
This can be checked in Acronis Backup Gateway configuration file:
Supported Configurations of Acronis Storage
On July 16, 2019, Acronis has released a new version of Acronis Software-Defined Infrastructure. The product has been renamed into Acronis Cyber Infrastructure. Product version to this point was 3.0.
With this release, Acronis introduced several new features, see list here.
You can find release notes here.
User guide is here.
You have installed Acronis Cyber Infrastructure (Acronis Storage) and registered it in Acronis Cyber Cloud.
You try to register Backup Agent in Acronis Cyber Protect Cloud, but registration fails with:
"Outgoing connections are not available for the following ports: hostname:44445"
You are trying to update the Storage certificate via CLI according to the article and the following error occurs:
GET 'https://cloud.acronis.com/api/1/groups/self/storages' failed: can't read a response: gzip: invalid header
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