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
# ostor-s3-admin create-user -e user@email.com
Created user: email=user@email.com,user id=81d406fa613ad6c1
Key pair[0]: access key id=81d406fa613ad6c1S8HL,
secret access key=ya8iq3yrEYEhpErCkSmui6ifBghDDLdN2vso3sJn
The access key ID and secret access key pair, along with S3 endpoint, are required to connect to object storage
from a client application.
To check that installation has been successful or just monitor object storage status, use the ostor-ctl get-config
command. For example:
# ostor-ctl get-config
07-08-15 11:58:45.470 Use configuration service ’ostor’
SVC_ID TYPE URI
8000000000000006 S3GW svc://1039c0dc90d64607/?address=127.0.0.1:9000
0800000000000000 NS vstorage://cluster1/ostor/services/0800000000000000
1000000000000001 OS vstorage://cluster1/ostor/services/1000000000000001
1000000000000002 OS vstorage://cluster1/ostor/services/1000000000000002
1000000000000003 OS vstorage://cluster1/ostor/services/1000000000000003
1000000000000004 OS vstorage://cluster1/ostor/services/1000000000000004
8000000000000009 S3GW svc://7a1789d20d9f4490/?address=127.0.0.1:9000
800000000000000c S3GW svc://7a1789d20d9f4490/?address=127.0.0.1:9090
3.2.1 Manually Binding Services to Nodes
You can manually bind services to nodes with the ostor-ctl bind command. You will need to specify the target
node ID and one or more service IDs to bind to it. For example, the command:
# ostor-ctl bind -H 4f0038db65274507 -S 0800000000000001 \
-S 1000000000000003 -S 1000000000000005
binds services with IDs 800000000000001, 1000000000000003, and 1000000000000005 to a host with ID 4f0038db65274507.
A service can only be bound to a host that is connected to the shared storage which stores that service’s data.
That is, the cluster name in service URI must match the cluster name in host URI.
For example, in a configuration with two shared storages stor1 and stor2 (see below) services with URIs start-
ing with vstorage://stor1 can only be bound to hosts host510 and host511 while services with URIs starting with
vstorage://stor2 can only be bound to hosts host512 and host513.
30