Ubuntu Hardened Repository - Path is not XFS

[turbulence]

Hi everyone,

It seems there's an issue with Ubuntu 20.04.4 LTS and Veeam 11 running as a hardened repo. Veeam build is 11.0.1.1261 P20220302, though this issue happened on the previous build as well.

I've configured the server per this guide https://nolabnoparty.com/en/veeam-v11-h ... lity-pt-1/ and when I try to create a new repository in Veeam, I receive the error
"File system behind the provided path is not XFS:"

The volume most certainly is XFS.

There have been a few forum posts about this issue over the past 6m, but there isn't a conclusive fix. I suspect there is a wider issue at play here as this should work.

Veeam support case ID = 05408854. The agent suggested I edit the Veeam user's .bashrc file and include PATH="$PATH:/sbin:/usr/sbin to the top. I've done that to no avail.

Any thoughts on this?

Thanks

[jorgedlcruz]

Hello,
If you do not have any data on that disk, I would recommend you to run this quickly, to the /dev/sdx, or disk you want to format as XFS:

Code: Select all

mkfs.xfs -b size=4096 -m reflink=1,crc=1 /dev/sdb

I am running the same Ubuntu build, and the same VBR, and it is working all fine here.

Give it a try and let us know.

[turbulence]

I ran that exact command already (per the article I linked) but as there's no data on the volume, I formatted it again using the same command. It didn't make any difference.

Did you edit the veeam linux user's bashrc file on your system? And is there anything else that you did over and above what is in the article that I linked?

Thanks

[turbulence]

So I've just tried specifying the administrator credentials for the managed server in Veeam, as opposed to single use credentials, and the issue remains. It doesn't seem like a user permission issue to me.

[veremin]

Then it's better to continue working with the support team and let them know the results of your findings. Thanks!

[chris.childerhose]

We were able to fix this on our XFS server that we encountered today. For some reason, there was a mount for /backups but not one for /backup. We fixed the mount and fstab entry to address the issue which then fixed Veeam itself when going into the properties of the repository - no more message about "File System behind...."

Hope this helps with solving this for others.

[jorgedlcruz]

There is a related topic here, just out of curiosity, I have deployed a new VM, Ubuntu 20.04.4, next/next pretty much, assigned a second disk, followed the steps on the blog you shared blog, or on this one which is similar but official steps.

My only caveat was that using a user that can sudo, not ideal, at the moment of selecting the path asked me for this:


As my user oper is not on any group, just did:

Code: Select all

chown -R oper /backups

And had zero problems, all working as expected.


At this point in time, would recommend keeping working with Support, meanwhile, you double-check everything as Chris mentioned, mounts, paths, privileges, etc.

[turbulence]

Thanks for everyone's replies. I have now resolved this issue.

I noticed from the article that I originally linked, on the new backup repository screen, the backup folder was visible. In my case my folder (/mnt/veeam01) was not visible. I also confirmed this by running the df -Th command on Linux. Apparently it wasn't mounted.

However, Veeam still lets you progress to the next screen where you can then manually browse to the folder, and in my case, Veeam could see /mnt/veeam01 as a folder and allow me to select it. I then configured settings (immutability etc) and pressed Next, to be greeted with the Path is not XFS error.

Once I fixed the mount issue in Linux, Veeam could see it on the Server selection screen, and I could create the repo and proceed as expected.

I think it would be worth updating the official documentation to mention that the folder must visible using the df -Th command from the Linux shell, otherwise Veeam can't use it, despite being able to see it.

Thanks again

[jorgedlcruz]

Great feedback, but even better to see the issue has been resolved.

Will contact the team to update the info.

I have been using myself article I wrote in 2020, and never had issues with the process, I am going to ask to add these steps to the official guide.

Thanks a lot for coming back saying all worked, have a great day.

[chris.childerhose]

Yes your article is great Jorge as I use it too.

[turbulence]

Thanks Jorge, appreciated!