Skip to main content
Sign Out

Welcome to Dell

My Account
  • Place orders quickly and easily
  • View orders and track your shipping status
  • Enjoy members-only rewards and discounts
  • 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 Dell Financial Services Premier Sign In Partner Program Sign In
Contact Us

Your Dell.com Carts

Dell EMC ObjectScale 1.2.x Administration Guide

PDF

ObjectScale Replication overview and configuration details

ObjectScale Replication, at it is most basic setting, allows users to replicate objects in a bucket to another bucket, the destination bucket could be:
  • In the same object store
  • Another object store in current same ObjectScale instance
  • Another object store in another ObjectScale instance within the ObjectScale federation

More complex ObjectScale Replication configurations can be defined. These complex configurations can allow for a replication to be single-directional or bi-directional replication between buckets or from a single source bucket to multiple destination buckets.

ObjectScale Replication can be defined using replication rules or by replicating by object versions.
  • Since ObjectScale Replication supports multiple source buckets replicating to the same destination bucket, and since replication occurs asynchronously, it is possible to have object name collisions. To avoid having an object being overwritten in the destination, it is required to enable versioning on both the source and destination bucket.
  • Each object version is replicated separately, when it is replicated to the destination, it keeps the same Create Time and Version ID. You could use the same version ID to access a specific version of that object in the destination bucket. Versions keep the same order in the destination bucket, so after everything is replicated, latest version and version history of an object match the destination bucket.

What does ObjectScale Replication replicate?

ObjectScale Replication replicates:

  • Object versions that are created after a replication rule is added to the source object store.

    Updates to the object's User Metadata, Storage class, Encryption type creates a new version of object. The replication rules determine the replication of this new object version when this version is created.

  • When replicated, the replicated object keeps the same metadata as the source object for:
    1. Object Name
    2. Version ID
    3. Object Create Time
    4. User Metadata
    5. Attributes (ACL, Tag, or Lock)

What does ObjectScale Replication not replicate?

ObjectScale Replication does not replicate:

  • User key encrypted objects
  • Updates to bucket-level subresources, such as the lifecycle configuration of the bucket
  • Actions performed by a lifecycle configuration
  • Object version that were created before the replication rule itself was created or enabled. Further,
    1. There is no replication status for this version of object.
    2. Any attribute (ACL, Tag, or Lock) update on this version of the object does not trigger replication of this new object version.
  • The replicated object does not replicate again.
    1. Even if the replication configuration between two buckets is bi-direction, attribute updates on a replicated object do not replicate back to the source object.
    2. Replication for attribute updates on the source bucket overwrites all ACL, Tag, or Lock on the replicated object.
  • A delete marker that is generated by a lifecycle configuration or by a user delete action is not replicated.

ObjectScale Replication Configuration Overview

  1. Create an object store and bucket.
  2. Configure Bucket Replication on the bucket in the created object store.
    • Specify the replication configuration on each bucket to start object replication.
    • A user must be able to create, read, update, and delete replication rules on an object store, irrespective of the state of other object stores or network connectivity to other object stores.
    • Create and specify an IAM Role ARN, or use an existing role, in their replication configuration. The IAM role must have permission to replicate objects.
    • Specify replication rules to specify a replication destination and the replication behaviors in the replication configuration.
  3. Create the replication configuration.

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: <>()\