Migrating backup jobs within SOBR extents

[Gunnersaurus]

I have a SOBR with multiple extents which belong to a repository I that I need to decommission. I have already built a replacement new repository which also has multiple extents for the backup data to be migrated onto. All extents are formatted with REFS and the SOBR is set in data locality mode. The SOBR contains a large amount of data and many associated backup jobs. I have some concerns with migrating the data at the extent level as it could have a performance impact on the underlying infrastructure especially when running new active fulls post move.

I was hoping I could use a staggered approach to migrate the data job by job via a manual move operation from old extents to new. I except the initial storage impact due to re-hydration of the data however I'm not sure if this method is feasible. If I follow https://www.veeam.com/kb3100 for the migration of each job, will it result in the data staying on the new extents due to data locality provided the extents don't become full? Once all data has been migrated I would then remove the old extents from the SOBR.

Will this work or is there a better way to achieve the same result?

[Mildur]

Hi

Yes, I expect them to stay on the same extend, if you are doing synthetic full backups. Active Full Backups on the other hand can use any extend if the placement policy decides, the backup must be placed on another extend.

You could place the old extend into maintenance mode, during the first active full of each job (needed for FastClone working again with copied backup files). Then the Active Full will be written to the new extend and not the old one.

[Gunnersaurus]

My only concern with putting the old extent into maintenance mode during the first active full of each job is it could take a substantial amount of time to complete each active full. During that time, the jobs still in the extent in maintenance mode will not be able to backup or perform restores.

[veremin]

You can switch it into sealed mode so that restores are possible, but no new backup files land on the sealed extent. Thanks!