V12.2 - Capacity tier has gone

[roleit]

Hi all,
Veeam 12.2.0.334.

I have made changes in 2x backup copy jobs to split performance tier from 1 to two seperate local repositories. In result i have linkt them to the new capatity tiers.

Right now the old capacity tier has gone from Backups > Capacity tier. I can restore from the files from blob but cannot access it directly within Veeam.
From the Scale-ot repositories > Old Repository (not using atm) i can see Blob with correct Used space.

From support ticket i have been instructed to detach current capacity tier from old Scale-out repository, when i try to do this i'm getting bellow warning:

You're about to disable or change your capacity tier to use a different storage system. All backups offloaded to the currenlty seleted object storage system will become unavaiblable for restore. Proceed?

What i want to achive:
I want to have just for archive and restore purposes availability to access old Capacity tier within Veeam and administer it (e.g delete old backups).

Can i proceed with above arning message and import backup from blob to capcity tier (imported) i suppose? Just for visibility and restore purpose in case when i neeed it ?

[Update] Does dummy repo described in this artcle will do the trick? https://koolaid.info/maintaining-recove ... igrations/

[Mildur]

Hi Role

Clicking on that message removes the references to the offloaded backups from the configuration database, meaning they will no longer appear in the backup tree for a restore.
However, the backups themselves will not be deleted from the bucket. You can reconnect your bucket to a backup server and initiate an import session.

Jim Jones' blog mentions a known situation where you cannot import backups from the removed capacity tier back to the original backup server. Instead, a new backup server must be used to connect to the bucket and import the old offloaded backups.
I'll check internally to see if this is still the case (I believe it is). Please give me some days to gather this information.

Best,
Fabian