Moving SOBR to new storage device

[unsichtbarre]

I have a SOBR with 3 older ReFS 64K extents (each contains about 20TB of fully-inflated backups) and one newer extent (80TB) I would like to move the data to new extent(s).

I'd like to use the Evacuate option by placing the older extents into Maintenance Mode one at a time. I realize some of the data may simply be moved to another of the older extent(s), but eventually capacity and data placement should cause everything to go to the newer extent.

Should I change the SOBR to Performance (from data locality) first?
Will the Backup Copy Jobs where the most recent full backup is located on a Maintenance Mode extent continue to run and complete?
Are there any other considerations?

THX,
-JB

[HannesK]

Hello,
to benefit from block cloning: always keep data locality.

Nothing writes to extents in maintenance mode or seal mode (I believe that was the question about the BCJ?).

Depending on the retention you configured, I suggest sealed mode https://helpcenter.veeam.com/docs/backu ... ml?ver=110

Best regards,
Hannes

[unsichtbarre]

So I have sealed an extend and Evacuate is NOT available. The documentation indicates it should be available: https://helpcenter.veeam.com/docs/backu ... ml?ver=110

What's the best practice now, so as not to break the jobs? Copy off of sealed repository and do a re-scan of destination Repository.

The goal of wanting to use Evacuate was to keep jobs running during the copy process - If I start copying data out-of-band, won't I have to disable the Jobs during the copy process?

[veremin]

Can we clarify your goal a bit - are you willing to move all previous restore points to new extent immediately or you want backup server to write new restore points to the new extent while gradually removing previous ones by retention policy? In the former case - use Maintenance Mode + Evacuation, in the latter - Seal Mode. Thanks!

[HannesK]

seal is the opposite of "evacuate". That's why I said "depending on the retention you configured".

use Evacuate was to keep jobs running during the copy process

that doesn't work. It's not like storage-VMotion in VMware.

[unsichtbarre]

Veremin - My goals are to get off older extents of SOBR ASAP. I would like to migrate off of the older SOBR extents without disrupting the Backup Copy Jobs that target the SOBR. Thank you for the clarification! Now that I have sealed one extent, may I un-seal it and use Maintenance Mode + Evacuate?

HannesK - The Veeam documentation clearly shows "Evacuate" as being available during Seal, which is why I was confused: https://helpcenter.veeam.com/docs/backu ... ml?ver=110

Thanks both for the replies,
-JB

[Gostev]

Please note that this documentation is for Capacity Tier and object storage extents, while your original question was about Performance Tier.

[veremin]

Now that I have sealed one extent, may I un-seal it and use Maintenance Mode + Evacuate?

Correct, you can do this. Thanks!

[unsichtbarre]

A quick follow-up question: After an extent is evacuated, how do I remove it from the SOBR?

In https://helpcenter.veeam.com/docs/backu ... ml?ver=110
It indicates that "remove extent" is an option after evacuating - I do not have that option.

THX,
-JB

[foggy]

Hi John, do you open the Edit Repository Wizard (by right-clicking the repo or using the button on the ribbon)? The option to remove an extent is there at the Performance tier step.