Skip to main content

Mumbai Region Object Storage Migration Guide

You may use the Object Storage Replication Rule feature to migrate data from Mumbai buckets to a bucket in the Delhi or Chennai region.

Please follow the steps below:

Step 1 - Create a New Bucket​

Create a new bucket in either:

  • Delhi Region, or
  • Chennai Region

Step 2 - Enable Object Versioning​

Object Versioning must be enabled on both the source (Mumbai) bucket and the destination bucket before configuring replication.

To enable versioning:

  1. Navigate to the bucket.
  2. Click Action → Object Versioning.
  3. Enable versioning for the bucket.

Step 3 - Configure Replication Rule​

  1. Navigate to your Mumbai bucket.
  2. Click Action → Replication Rule.
  3. Enter the destination bucket details.
  4. Click Save to enable replication.

Documentation reference: Replication Rule

Step 4 - Verify Data Replication​

After the replication rule is configured, allow sufficient time for objects to be replicated and verify that all objects have been successfully replicated to the destination bucket.

You may verify the data using the Object Storage CLI (mc tool) by comparing the source and destination buckets.

Refer to the following documentation for configuring and using the CLI tool: Object Storage CLI

Using the CLI tool will help you validate that the object count and data structure are consistent between the source (Mumbai) bucket and the destination bucket before proceeding with further cleanup steps.

Step 5 - Update Application Endpoints​

If your applications or scripts reference the Mumbai Object Storage endpoint, update them to use the appropriate endpoint for the new region.

Previous Mumbai Endpoint:

mum-objectstore.e2enetworks.net

New Endpoints:

  • Delhi Region: objectstore.e2enetworks.net
  • Chennai Region: in-south1-objectstore.e2enetworks.net

Ensure all services and applications referencing the bucket are updated accordingly.

Step 6 - Remove Replication Rule​

Once the data migration is verified, delete the replication rule from the source (Mumbai) bucket.

Step 7 - Delete Mumbai Bucket​

After verifying that all data has been successfully migrated, you may delete the bucket located in the Mumbai region.

Step 8 - Disable Versioning (Optional)​

If Object Versioning was enabled only for the migration process, you may disable versioning on the destination bucket once migration is complete.