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
Chapter 3. Accessing Acronis Storage Clusters via S3 Protocol
cluster in the same way as virtual environments, iSCSI, and other services do. So the OS and NS services
depend on vstorage-mount (client) and can only work when the cluster is mounted. Unlike them, gateway
is a stateless service that has no data. It is thus independent on vstorage-mount and can theoretically
be run even on nodes where the Acronis Storage cluster is not mounted. However, for simplicity, we
recommend creating gateways on nodes with object and name servers.
Object and name servers also utilize the standard high availability means of Acronis Storage (i.e. the
shaman service). Like virtual environments and iSCSI, OS and NS are subscribed to HA cluster events.
However, unlike other services, S3 cluster components cannot be managed (tracked and relocated be-
tween nodes) by shaman. Instead, this is done by the S3 configuration service that is subscribed to HA
cluster events and notified by shaman whether nodes are healthy and can run services. For this reason,
S3 cluster components are not shown in shaman top output.
Gateway services which are stateless are never relocated and their high availability is not managed by
the Acronis Storage cluster. Instead, a new gateway service is created when necessary.
2. Make sure that each node that will run OS and NS services is in the high availability cluster. You can add
nodes to HA cluster with the shaman join command.
3. Install the vstorage-ostor package on each cluster node.
# yum install vstorage-ostor
4. Create a cluster configuration on one of the cluster nodes where object storage services will run. It is
recommended to create 10 NS and 10 OS services per each node. For example, if you are going to use
five nodes, you will need 50 NS and 50 OS. Run this command on the first cluster node.
# ostor-ctl create -n <IP_addr> \
-c ”vstorage://<cluster_name>/<ostor_dir> <NS_num> <OS_num>”
where
• <IP_addr> is the node’s IP address that object storage will go through,
• <cluster_name> is the name of your Acronis Storage cluster,
• <ostor_dir> is the directory in the cluster with object storage service files,
• <NS_num>, <OS_num> are the numbers of NS and OS, respectively.
You will be asked to enter and confirm a password for the new object storage (it can be the same as your
Acronis Storage cluster password). You will need this password to add new nodes.
5. Launch the configuration service.
26