VBR v11a: file-restore level issue with RHEL9

[SebCharp]

Hi folks,

As RHEL7 support is ending this year, we are preparing to migrate to RHEL9 (and Rocky9).
Our hypervisor is running ESXi 6.7 (+vSphere).

I successfully created a RHEL9 VM, and Veeam BR (version 11a) also successfully backed up the VM.
The "restore entire VM" procedure works perfectly.

However the "restore guest files" ended up with an "unable to mount the file system" message.
I can browse the boot/EFI partition but not the system partition.
All partitions are XFS format which are supported by VBR.

Code: Select all

/dev/mapper/rl-root     /                       xfs     defaults                   0 0
UUID=xxx                /boot xfs               defaults                           0 0
UUID=F1A6-F65D          /boot/efi               vfat    umask=0077,shortname=winnt 0 2
/dev/mapper/rl-home     /home                   xfs     defaults                   0 0
/dev/mapper/rl-swap     none                    swap    defaults                   0 0

What did I do wrong?
Any support would be greatly appreciated.

BR,
Seb

[Gostev]

Hello Seb,

V11a is out of support for a few months now. Please upgrade to V12.1 and try this again. If it does not work, please open a support case for further troubleshooting by one of our support engineers.

Thanks

[SebCharp]

Hi Gostev,

First of all, thanks for your response!
I wasn't aware that v11 support had ended. We are also planning to migrate VBR to v12.
Currently, we are using our Synology NAS as a Linux repository (SSH + Perl). I read that this configuration is not supported anymore with VBR v12.
So, I postponed the upgrade because we are a small company with a limited budget for IT stuff.
I tried to avoid triggering a domino effect as much as possible.
Based on your experience, is the file restore procedure well supported and does it work fine for RHEL9 VMs with VBR v12?

[SebCharp]

Some update: I upgraded to v12.1
For the record, using a Synology NAS as a Linux repository still works perfectly.

The issue mentioned in my first post is gone with VBR v12.

Thanks for your support.

[karsten123]

… and now, lets get rid of that unsupported vSphere 6.7. Just do it

[SebCharp]

Good point. However, since Broadcom acquired VMware (with the "new" pricing policy), we will probably move to Proxmox. The cost is just too high for a small company.
Hoping a Proxmox-Veeam solution will come out soon, since VBR is definitely one of the best backup solution. Fingers crossed!

[karsten123]

Some update: I upgraded to v12.1
For the record, using a Synology NAS as a Linux repository still works perfectly.

What DSM version do you run on your Synology?

[SebCharp]

What DSM version do you run on your Synology?

DSM 7.1

[SebCharp]

Sorry, I meant 7.2