Migrating Backups within Scale-Out Backup Repository

The migration option allows you to migrate data between performance or capacity extents of different object storage repositories. This option may be helpful if you want to switch from one object storage repository to another or to migrate from the object storage repository with different immutability settings. To migrate data, you need to set the extent to the sealed mode. If necessary, you can switch an old extent into the Maintenance mode and evacuate all data from it.

Migrating Data Between Different Object Storage Repositories

You can follow this scenario in case you need to migrate data from one type of object storage to another. For example, to migrate data from the Amazon S3 object storage repository to the Azure Blob storage or any other object storage.

To migrate data, do the following:

1. Put an extent from which you want to migrate data into the Sealed mode.
2. Add a new object storage repository to the same tier.
3. Switch an extent from which you want to migrate data into the Maintenance mode.
4. Evacuate data from the old extent.
5. Remove the old object storage repository from the backup infrastructure.

Migrating Data Between Different Buckets or Containers

You can follow this scenario in case you need to migrate data between different buckets or containers of the same object storage repository. These buckets or containers can have different immutability settings.

To migrate data, do the following:

1. Add a new object storage repository to the backup infrastructure and specify a new bucket or container. For more information, see the Adding Object Storage Repositories section.
2. Depending on the immutability settings of the bucket or container, do the following:

• If the old and a new object storage repositories have the same immutability settings (for example, both are immutable), switch an extent from which you want to migrate data into the Maintenance mode.
• If the old and a new object storage repositories have different immutability settings (for example, the old repository is mutable and a new repository is immutable), switch an extent from which you want to migrate data into the Sealed and Maintenance modes.

3. Set this new object storage repository as a performance or capacity extent of the scale-out backup repository which you use.
4. Evacuate data from the old extent.
5. Synchronize your data. For more information, see the Synchronizing Capacity Tier Data section.

Copying Data Between Different Buckets or Containers with 3rd Party Tool

You can follow this scenario in case you want to use a 3rd party tool to migrate data located in an object storage repository between different buckets or containers of the same same object storage repository, do the following:

1. Use any available 3rd party tool to copy ALL data from an old bucket or container to a new bucket or container.
2. Add a new object storage repository to the backup infrastructure. For more information, see the Adding Object Storage Repositories section.
3. Set a new object storage repository as a capacity extent of the scale-out backup repository which you use.

4. Synchronize your data. For more information, see the Synchronizing Capacity Tier Data section.

Migrating Data Within One Capacity Tier

You can migrate your data between different extents of the same tier.

To do this, perform the following steps:

1. Switch the necessary extent into the Maintenance mode.
2. Evacuate backups from the extent.