File level backup of / excludes mounted local file systems.

[MarktheSpark]

Hello All,

I'm new to Veeam, but have many many years of expience of running backup systems, so forgive me if my observations come from ignorance of the product; I'm just leaning

I'm backing up Linux physical machines uisng a backup job that has a Job Mode = Manged by agent, and Backup Mode = File level backup (backup directly from the live file system).

The agent installed on the machines is the NoSnap agent. This is because these machines were created before we started using Veeam and there is no free space available for LVM to create snapshots of volumes.

The documentation https://helpcenter.veeam.com/docs/backu ... ml?ver=120 suggests that backing up '/' will backup everything but NFS or SMB mounted file systems. However, I'm finding that this isn't the case. It only backs up '/' and not '/home' or '/boot' which are different logical volumes (lv) from the same local volume group (vg). So I have to specify all the mountpoints that I want to back up. That's ok when all the machines in the policy have the same file system layout. When they don't, any mountpoints that don't exist are ignored but cause the backup to complete with a warning. Becoming habituated to thinking that a backup completing with a warning is a recipe for disaster in my book. So there has to be a better way.

Am I missing something here?

Any advice greatfully received.

Thanks

Mark

[rovshan.pashayev]

Hello Mark,

You can archive this goal with enabling following value in the veeam.ini file

Code: Select all

# grep root -B1 /etc/veeam/veeam.ini
[filelevel]
# Enable recursive traversal of root directory and its nested mountpoints (excluding remote FS) for file-level backup.
rootRecursion = true

Thanks,
Rovshan.

[MarktheSpark]

Hi Rovshan,

Thank you for your reply. Your suggested fix works perfectly!

Your help is very much appreciated.

Regards,

Mark

[rovshan.pashayev]

Happy to hear that.

Out of curiosity, can you confirm if you were able to successfully perform a backup and restore using a crash-consistent file-level backup without using a snapshot?