Installation Guide
Table Of Contents
- Introduction
- Planning Acronis Storage Infrastructure
- Understanding Acronis Storage Architecture
- Planning Node Hardware Configurations
- Planning Network
- Understanding Data Redundancy
- Understanding Failure Domains
- Understanding Storage Tiers
- Installing Acronis Storage
2.1. Understanding Acronis Storage Architecture
2.1.3 Network Roles (Storage Access Points)
Storage access points enable you to access data stored in Acronis Storage clusters via the standard iSCSI and
S3 protocols and use the clusters as backend storage for Acronis Backup Cloud.
To benefit from high availability, access points should be set up on multiple node.
The following access points are currently supported:
• iSCSI, allows you to use Acronis Storage as a highly available block storage for virtualization, databases,
office applications, and other needs.
• S3, a combination of scalable and highly available services (collectively named Acronis Object Storage)
that allows you to use Acronis Storage as a modern backend for solutions like OpenXchange AppSuite,
Dovecot, and Acronis Access. In addition, to developers of custom applications Acronis Object Storage
offers an Amazon S3-compatible API and compatibility with the S3 libraries for various programming
languages, S3 browsers, and web browsers.
• Acronis Backup Gateway, allows you to connect Acronis Storage to Acronis Backup Cloud via Acronis
FES API.
NFS, SMB, and other access point types are planned in the future releases of Acronis Storage.
The following remote management roles are supported:
• Web CP, allows you to access the web-based user interface from an external network.
• SSH, allows you to connect to Acronis Storage nodes via SSH.
2.1.4 Supplementary Roles
• Management, provides a web-based management panel that enables administrators to configure, man-
age, and monitor Acronis Storage clusters. Only one management panel is needed to create and manage
multiple clusters (and only one is allowed per cluster).
• SSD cache, boosts chunk read/write performance by creating write caches on selected solid-state drives
(SSDs). It is recommended to also use such SSDs for metadata, see Metadata Role on page 4. The use of
write journals may speed up write operations in the cluster by two and more times.
• System, one disk per node that is reserved for the operating system and unavailable for data storage.
5