SOBR move extent to new host

[somoa]

Hi

I have an extent/repository named VOL1 in a SOBR connected to HOST1 that I need to move to a new HOST2.
The extent/repository is connected to HOST1 as iSCSI.

Would the following plan work to do this without causing problems. I am not sure how the capacity tier may react here.

Disable all backup jobs
Put SOBR VOL1 extent and capacity tier in maintenance mode
Remove VOL1 extent from SOBR
Remove repository VOL1 on HOST1 from Veeam
Shutdown HOST1
Map iSCSI volume from HOST1 to HOST2
Add repository VOL1 on HOST2 to Veeam and let it scan/import backups
Add repository VOL1 on HOST2 to SOBR
Remove maintenance mode on capacity tier
Enable backup jobs

I would like to make sure the capacity tier doesn't delete everything it currently has in it due to removing the extent, while also not reupload all the backups.

[Andreas Neufert]

I think the better way is the following.
Disable all jobs that write to the repository.
But the extend in maintenance mode.
Shutdown the server with the extent you want to migrate.
Mount the iSCSI volume to the other server. Boot the server.
Add the server with the iSCSI volume as new extent and do a rescan of the repository (the backup data will be detected there as all metadata files are still present).
Start the server with the non existing extent.

Continue with backups.
Remove the extent that is in maintenance mode.

[Andreas Neufert]

Even better, here is a KB that gives you exact guidlines:
https://www.veeam.com/kb3100

[somoa]

Thanks, that worked well. The end process ended up doing if anyone wanted to know.

Disable all backup jobs
Shutdown HOST1
Map iSCSI volume from HOST1 to HOST2
Put SOBR VOL1 extent in maintenance mode
Add repository VOL1 on HOST2 to Veeam and did not let it scan/import backups
Add repository VOL1 on HOST2 to SOBR while at same Remove VOL1 extent from SOBR
Rescan SOBR
Remove repository VOL1 on HOST1 and HOST1 from Veeam
Enable backup jobs

[Andreas Neufert]

Thanks for sharing your experience.