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
Acronis Storage can export data via an Amazon S3-compatible API, enabling service providers to:
• run S3-based services in their own Acronis Storage infrastructures,
• sell S3-based storage-as-a-service to customers along with Acronis Storage.
The support for S3 expands the functionality of Acronis Storage and requires a working Acronis Storage cluster.
3.1 About Object Storage
Object storage is a storage architecture that enables managing data as objects (like in key-value storage) as
opposed to files in file systems or blocks in block storage. Except data, each object has name (i.e. full path to
object) that describes it and also a unique identifier that allows finding said object in the storage. Object storage
is optimized for storing billions of objects, in particular for application back-end storage, static web content
hosting, online storage services, big data, and backups. All of these uses are enabled by object storage thanks
to a combination of very high scalability and data availability and consistency.
Compared to other types of storage, the key difference of S3 object storage is that parts of an object cannot be
modified, so if the object changes a new version of it is spawned instead. This approach is extremely important
for maintaining data availability and consistency. First of all, changing an object as a whole eliminates the issue
of conflicts. That is, the object with the latest timestamp is considered to be the current version and that is it.
As a result, objects are always consistent, i.e. their state is relevant and appropriate.
Another feature of object storage is eventual consistency. Eventual consistency does not guarantee that reads
15