Skip to main content
Sign Out

Welcome to Dell

My Account
  • Place orders quickly and easily
  • View orders and track your shipping status
  • Create and access a list of your products
  • Manage your Dell EMC sites, products, and product-level contacts using Company Administration.
Sign In Create an Account Premier Sign In Partner Program Sign In
Contact Us

Dell ObjectScale 1.3 Administration Guide

PDF

Introduction to ObjectScale Replication

ObjectScale Replication allows you to manage and monitor replication policies and replicate bucket data. Replication between object stores complies with the S3 protocol of AWS.

ObjectScale replication enables the copying of objects across buckets within ObjectScale instances. The destination, or target, bucket could be in one of the following object stores:

  • The same local object store

  • An object store in the same ObjectScale instance as the source bucket

  • An object store in another ObjectScale instance in an ObjectScale federation

Up to four unique destinations per replication policy can be configured. At any time, replication can be paused, suspended, or throttled.

One or more accounts can own buckets that are configured for object replication.

ObjectScale replication across object stores is an eventual consistency process. The benefits of eventual consistency replication are:

  • It is good for high-latency connections.
  • It provides eventually consistent object access (asynchronous replication).
  • Data reads and writes are always local for the best performance.
  • The system can perform management operations during network partitions.

To enable replication, add a replication configuration to your source bucket. The minimum configuration includes:

  • The destination bucket or buckets where you want ObjectScale to replicate objects.
  • An Identity and Access Management (IAM) role that ObjectScale can use to replicate objects.

    An IAM Role is an IAM identity that you can create in your account that has specific permissions.

    An IAM Role is similar to an IAM end user. They are both an ObjectScale identity with permission policies that determine what the identity can and cannot do in ObjectScale. However, instead of being uniquely associated with one person, a role is intended to be assumable by anyone who needs it.

Each source bucket can be configured to replicate some or all its data to one or more destination buckets. The data that are replicated from the source bucket can be replicated based on a key prefix, a tag or both to make replication granular. An IAM role must be selected for the source bucket account to replicate the data. On the source bucket, the rule can target specific destination buckets that are based on the key prefix and tag.

In ObjectScale:

  • Replication is bucket-to-bucket.
  • Replication rules can be different for every bucket depending on redundancy or locality needs.
  • Replication objects can be part of a bucket (by prefix or by tag set on objects).
  • Replication can do network throttling between different object stores.
  • Objects uploaded to ObjectScale using multipart upload (MPU) can be managed with replication rules after the upload completes.
  • Replication can support large objects up to 50 TB.
ObjectScale administrators and users with the appropriate permissions can perform ObjectScale Replication management operations, including:
  • Review of the replication metrics on different rules for buckets in an object store.
  • Throttle or unthrottle the amount of data that is replicated in order to control the load on the system due to replication traffic.
  • Pause or resume ObjectScale Replication.
    • You can specify a pause ObjectScale Replication end time. Replication will automatically resume after the pause end time. There is no upper limit for the pause time, but the pause time cannot be indefinite. The default pause time is one hour.
    • You can extend the pause duration while the replication is still under suspension.
    • You can resume ObjectScale Replication when the replication status is either paused or suspended.
  • Suspend the replication of an object store.
    • When you suspend a destination object store, it disables all replication rules to that object store. Newly created objects in that object store do not generate replication status for that object store.
    • When a destination object store is suspended, replication for an existing object is paused. When replication for the object store is resumed, those objects and any updates are replicated then.
    • There are no limitations for a suspend duration. Suspend remains in place until the destination object store replication is resumed.
  • Permanently remove an object store from ObjectScale, because of a planned or unplanned event. Any unreplicated objects in those object stores go to FAILreplication status.

Rate this content

Accurate
Useful
Easy to understand
Was this article helpful?
0/3000 characters
  Please provide ratings (1-5 stars).
  Please provide ratings (1-5 stars).
  Please provide ratings (1-5 stars).
  Please select whether the article was helpful or not.
  Comments cannot contain these special characters: <>()\