Migrating Data To Another Capacity Tier

In this article

    You can migrate your data between object storage repositories. After that, you can add a new object storage repository as a capacity extent instead of the previous one.

    The migration option may be useful if you want, for instance, switch your provider.

    Such a migration can be done under the following scenarios:

    Is used to migrate data from one object storage provider to another. For example, you may have been using an Amazon S3 object storage repository for quite some time and decided to change it to Azure Blob storage or any other storage provider.

    Is used to migrate data between different buckets of the same cloud provider.

    Important

    Migrating data between object storage repositories is available only at the capacity tier. Archive tier does not support such scenarios.

    Migrating Data Between Different Cloud Providers

    To migrate data located in an object storage repository between different cloud providers, do the following:

    1. Download data from an object storage repository back to the performance extents, as described in Downloading Data from Capacity Tier.
    2. Add a new object storage repository to the Veeam Backup & Replication environment, as described in Adding Object Storage Repositories.
    3. Change an object storage repository to a new one that you have created at the previous step, as described in Add Capacity Tier.
    4. Copy or move your data to a new object storage repository, as described in Moving to Capacity Tier.

    Migrating Data Between Different Buckets

    To migrate data located in an object storage repository between different buckets of the same cloud provider, do the following:

    1. Use any available 3rd-party tool to copy cloud data to a different bucket of your cloud storage.
    2. Add a new object storage repository to the Veeam Backup & Replication environment, as described in Adding Object Storage Repositories.
    3. Change the capacity extent to a new one that you have created at the previous step, as described in Add Capacity Tier.
    4. Synchronize your data, as described in Synchronizing Capacity Tier Data.

    Keep in mind that you can copy cloud data only to a bucket without the Versioning feature enabled. If you need to migrate your data from a non-immutable bucket to an immutable one, use one of the following ways:

    • Perform the scenario described in Migrating Data Between Different Cloud Providers.
    • If your source bucket had the Versioning feature enabled, copy your data to a bucket without the Versioning feature, then manually enable the Versioning and the Object Lock features. However, instead of migrating data, you can enable the Versioning and the Object Lock features on the existing bucket, and proceed to use this bucket as an immutable one. This only applies to object storage that support the Versioning and the Immutability features. Before you enable the Object Lock feature on the existing bucket, make sure your vendor allows enabling the Object Lock feature after the bucket is already created.

    Use command line interface (CLI) to copy from an immutable bucket to a non-versioned one.