Reloading the OS of a Linux repo

[FrenchBlue]

Hello,

For historical reasons, we have 4 bare metal repositories in Ubuntu 22.04. We would like to migrate them to RHEL (8.x). The Veeam backups disks array/mount point is separated from the OS one so we can easily install RHEL on this partition and then re-attach the Veeam data partition. Same hostname, same ip address, same Veeam data, same mount point, but... what would be the impact on existing jobs? Would a simple repository rescan be sufficient? Certificates will be different for sure and veeam compoenents would have to be reinstalled. Also, users id's would be different. Of course we don't want to break the backup chain here.

Thanks.

[Gostev]

Hi, I can't think of many things that can go wrong here. From VBR perspective it's a regular backup repository migration that our customers do all the time, just the hardware happens to remain the same in this particular case. I don't know if in-place rescan alone will be sufficient, however removing old repository, creating new repository, rescanning backups in it and mapping backups of the newly created repository in the backup job settings should definitely work, as again this makes it most standard repository migration process. Thanks

[FrenchBlue]

Hello, thanks, we are going to try this on a less critical repo first.

[JustinIzzard]

@FrenchBlue - Were you successful with reloading the OS on your repo servers? If so, is there any chance you would share a high level of the steps required following RHEL install until resuming backups?

We're in the same place, running Ubuntu on repository servers and need to move to RHEL. In our case, it is due to the lack of HPE firmware management (SUM/SUT) with Ubuntu that exists in RHEL.