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
command on every such node:
# ostor-ctl add-host -H <internal_IP_address> -r <cluster_mount_point>/<ostor_dir>
This command will automatically detect and use the node’s hostname and have the object storage agent
service listen on an internal IP address. You will need to provide the object storage password set on step
3.
9. Create S3 gateway instances on chosen nodes with Internet access and external IP addresses.
Note: For security reasons, make sure that only nginx can access the external network and that S3
gateways only listen on internal IP addresses.
# ostor-ctl add-s3gw -a <internal_IP_address>
where <internal_IP_address> is the internal IP address of the node with the gateway.
Note: Port number is mandatory.
10. Launch object storage agent on each cluster node added to the object storage configuration.
# systemctl start ostor-agentd
# systemctl enable ostor-agentd
11. Make sure NS and OS services are bound to the nodes.
By default agents will try to assign NS and OS services to the nodes automatically in a round-robin man-
ner. However, manual assignment is required if a new host has been added to the configuration, or if
the current configuration is not optimized (for details, see Manually Binding Services to Nodes on page 30.
You can check the current binding configuration with the ostor-ctl agent-status command. For example:
# ostor-ctl agent-status
TYPE SVC_ID STATUS UPTIME HOST_ID ADDRS
S3GW 8000000000000009 ACTIVE 527 fcbf5602197245da 127.0.0.1:9090
S3GW 8000000000000008 ACTIVE 536 4f0038db65274507 127.0.0.1:9090
S3GW 8000000000000007 ACTIVE 572 958e982fcc794e58 127.0.0.1:9090
OS 1000000000000005 ACTIVE 452 4f0038db65274507 10.30.29.124:39746
OS 1000000000000004 ACTIVE 647 fcbf5602197245da 10.30.27.69:56363
28