Exclude FLR appliance from backup jobs

[DonZoomik]

I noticed this in v9.5 as well but when FLR session is active (forgotten, long duration...), it is considered just another VM from Backup job's perspective if Backup job has very large include - for example whole vCenter for catch-all job (with excludes for stuff included by other jobs). However it would catch FLR as it's created at root (can't for example select folder or tag for exclude).
In my example, an admin started a FLR session at 15:25 and left it open for some time to clarify some details. In the meanwhile, at 16:00 a catch-all job started that would effectively double-backup already backed up data (backup-ception!).

Would it be possible to exclude FLR appliances from backups? After all Veeam should be well aware of any FLR sessions and VMs used by them.

[Egor Yakovlev]

Veeam FLR Appliance settings do have an option to set a custom Resource Pool to deploy to.
Feel free to create a custom pool and exclude it from backup job!
/Cheers!

[DonZoomik]

vSphere Essentials (Plus) and Standard (in my case) doesn't have Resource Pools, as Resource Pools require DRS that requires Enterprise (Plus) license.

[Egor Yakovlev]

Right. Guess breaking a non-DRS cluster into standalone hosts(with local Resource Pools) is not an option too...
Noted your feature request!
/Thanks!

[DonZoomik]

Yeah, breaking cluster apart would disable HA and that would be even worse.
Thanks for feedback.

[bhnelson]

Ugh! How is this a 'feature request'? Why in the world were FLR appliances not blacklisted in Veeam from the beginning?! So stupid. I spent all day trying to figure out why my veeam server went sideways and 'backing up an FLR appliance' was ultimately the cause.

+1

[Egor Yakovlev]

There are some improvements planned for FLR appliance handling logic.
Note that with v11 you don't really need a helper appliance at all, as you can use any suitable Linux host as a mounting point for FLR process.

/Thanks!