Process veeamimmureposvc consumes CPU and I/O on startup

[aj_potc]

Support ID: #05444861

Hi there,

I recently rebooted one of my Linux-based repositories and was surprised to see that the process veeamimmureposvc was consuming a fair amount of CPU and I/O resources after the system came back up. This was happening while the system was otherwise idle, with no backup jobs running.

I discovered the reason when I checked the log file VeeamImmutableRepoSvc.log, which showed that veeamimmureposvc was scanning the entire file system, including NFS mounts. Obviously, this is not desirable.

This repository is not immutable, so I'm not sure why this process is even present.

I have a few questions:

• Does anyone know why this service would be present on a non-immutable repository?
• Why does it need to scan the entire file system?
• Is there any way to disable it, or prevent it from doing this full file system scan on startup?

So far support hasn't been unable to uncover much, and I was hoping some product specialists here might know more about what's going on.

Thanks!

[PTide]

Hi,

Right now I have only one answer for you - if the server is not an immutable repo, then the presence of the service looks like a bug.

For other questions please stay tuned, I'll be back soon.

Thanks!

[PTide]

Ok, here is an update:

1. veeamimmureposvc is present regardless of whether or not the host holds the role of an immutable repo

This is by design. It is a child process of another veeam service.

2. It searches for locks imposed by Veeam.

3. What's the problem with it scanning the filesystem after a startup?

Thanks!

[aj_potc]

Thanks for the update!

2. It searches for locks imposed by Veeam.

Out of curiosity, what locks could be imposed by Veeam outside of its repository directory?

3. What's the problem with it scanning the filesystem after a startup?

Well,

1. This scanning needlessly consumes I/O and CPU resources, especially on servers that may have deep non-Veeam directories mounted
2. I feel that a Veeam service related to immutability has no business scanning my server's entire file system outside of the area specifically set up to be the repository

Having said that, this is only an annoyance and not a huge issue. My repository has enough resources to deal with the temporary load while the scanning takes place. I'm just wondering why it's needed.

[PTide]

Got it.

In general, we advise against using Veeam infrastructure servers for something else. That is, a repo server should be only a repo server, and nothing else. It's not that there is some purpose on scanning everything, it's just that the service does not have any knowledge of what directories are related to the repo. I'll discuss with the team when we can introduce some sort of "fencing" to keep the service from scanning directories other than the repository directory.

Thanks!