Administrator’s Guide
Table Of Contents
- Introduction
- Managing Acronis Storage
- Configuring Node Network Interfaces
- Creating Acronis Storage Clusters
- Releasing Nodes from Cluster
- Removing Nodes from the Unassigned List
- Managing Tier Encryption
- Managing Acronis Storage Users
- Managing Acronis Storage Updates
- Allowing root Access to Cluster Nodes Over SSH
- Backing Up and Restoring Management Node
- Managing Acronis Storage Licenses
- Monitoring Acronis Storage Clusters
- Monitoring Acronis Storage Nodes
- Exporting Acronis Storage Cluster Data
- Exporting Data via iSCSI
- Creating Acronis Storage iSCSI Targets
- Listing, Stopping, and Deleting Acronis Storage iSCSI Targets
- Configuring Acronis Storage iSCSI Targets
- Accessing Acronis Storage iSCSI Targets
- Accessing Acronis Storage iSCSI Targets from CentOS 6
- Accessing Acronis Storage iSCSI Targets from Microsoft Windows Server 2012 R2
- Accessing Acronis Storage iSCSI Targets from VMware ESXi
- Accessing Acronis Storage iSCSI Targets from Citrix XenServer 6.2
- Accessing Acronis Storage iSCSI Targets from Microsoft Hyper-V
- Managing iSCSI Users
- Exporting Data via S3
- Using Acronis Storage with Acronis Backup Cloud
- Exporting Data via iSCSI
Chapter 5. Exporting Acronis Storage Cluster Data
1. Define which nodes of the Acronis Storage cluster will run the S3 storage access point services. It is
recommended to have all nodes available in Acronis Storage run these services.
2. Configure the network so that the following is achieved:
• All components of the S3 cluster communicate with each other via the S3 private network. All nodes
of an S3 cluster must be connected to the S3 private network. Acronis Storage internal network can
be used for this purpose.
• The nodes running S3 gateways must have access to the public network.
• The public network for the S3 gateways must be balanced by an external DNS load balancer.
For more details on network configuration, refer to Planning Network in the Acronis Storage 2.0 Installa-
tion Guide.
3. All components of the S3 cluster should run on multiple nodes for high-availability. Name server and
object server components in the S3 cluster are automatically balanced and migrated between S3 nodes.
S3 gateways are not automatically migrated; their high availability is based on DNS records. You should
maintain the DNS records manually when adding or removing the S3 gateways.
5.2.3 Sample Object Storage
This section shows a sample object storage deployed on top of an Acronis Storage cluster of five nodes that
run various services. The final setup is shown on the figure below.
62