Administrator’s Command Line Guide
Table Of Contents
- Introduction
- Accessing Acronis Storage Clusters via iSCSI
- Preparing to Work with Acronis Storage iSCSI Targets
- Creating and Running Acronis Storage iSCSI Targets
- Listing Acronis Storage iSCSI Targets
- Transferring Acronis Storage iSCSI Targets Between Acronis Storage Nodes
- Stopping Acronis Storage iSCSI Targets
- Deleting Acronis Storage iSCSI Targets
- Configuring Multipath I/O for Acronis Storage iSCSI Targets
- Managing CHAP Accounts for Acronis Storage iSCSI Targets
- Managing LUN Snapshots
- Accessing Acronis Storage Clusters via S3 Protocol
- Monitoring Acronis Storage Clusters
- Managing Cluster Security
- Maximizing Cluster Performance
3.2. Deploying Object Storage
To set up object storage services, do the following:
1. Plan the S3 network. Like a Acronis Storage cluster, an object storage cluster needs two networks:
• An internal network in which NS, OS, and GW will interact. These services will generate traffic similar
in amount to the total (incoming and outgoing) S3 user traffic. If this is not going to be much, it is
reasonable to use the same internal network for both object storage and Acronis Storage. If, how-
ever, you expect that object storage traffic will compete with Acronis Storage traffic, it is reasonable
to have S3 traffic go through the user data network (i.e. datacenter network). Once you choose a
network for S3 traffic, you determine which IP addresses can be used while adding cluster nodes.
• An external (public) network through which end users will access the S3 storage. Standard HTTP and
HTTPS ports must be open in this network.
An object storage cluster is almost completely independent on base block storage (like all access points,
including virtual environments and iSCSI). Object and name servers keep their data in the Acronis Storage
25