Skip to main content
Version: 7.3

Data migration between S3 buckets

Introduction​

Data migration between S3 buckets allows administrators to move archived files from an existing S3 bucket to a new bucket while keeping the archived data accessible in the contentACCESS Portal throughout the process. Because contentACCESS continues to reference the configured bucket during migration, the steps below must be followed in the specified order to prevent temporary file unavailability and ensure that the storage configuration is updated safely.

Prerequisites​

Before moving the files, stop all new archiving activity:

  1. Stop and disable all archiving jobs.
  2. Set all available SMTP servers to read-only mode:
    1. Open Central Administration.
    2. Navigate to SMTP Servers.
    3. Select Edit for the relevant SMTP server.
    4. Set SMTP server mode to Receive only.

Move the files to the new bucket​

Copy all files from the old bucket to the new bucket.

warning

Important: Do not remove the files from the old bucket before the contentACCESS configuration has been updated. During the migration, contentACCESS will continue looking for files in the old bucket, so they may temporarily become unavailable if removed too early.

Update the storage configuration​

After all files have been copied to the new bucket, update the bucket name in contentACCESS:

  1. Open Central Administration.
  2. Navigate to Storages.
  3. Select the relevant storage and click Edit.
  4. Update the Bucket name to the name of the new bucket.
  5. Click Save.

Verify the migration​

Open archived files in the contentACCESS Portal and verify that they can be accessed successfully.

Once you have confirmed that the files are available from the new bucket, you can delete the old bucket. After deleting it, verify file access in the contentACCESS Portal again to make sure that archived files remain accessible.

Resume archiving​

When the migration is complete and file accessibility checks are successful:

  1. Enable the previously disabled archiving jobs.
  2. Return the SMTP servers to their normal operating mode.