Local copy of Veeam update repo

[TimoB]

Hi all,
I've read that it is possible to set up a local clone of https://repository.veeam.com/ and point different Veeam components to that repo (eg. VSA or VIA).
Is there any documentation on which update cases can be supported by having that repository available locally?

I was especially wondering about Veeam Threat Hunter signatures or Veeam Intelligent Diagnostics signatures for Veeam ONE. Maybe they could be distributed that way, as Service Provider Console is unable to do that?

It is a bit unfortunate to enable internet access for almost all Veeam components just to be able to update these signatures.
Or are there any other possibilities to do that in an efficient way without allowing internet access for all components?

Thanks a lot for your suggestions

[david.domask]

Hi TimoB,

Is there any documentation on which update cases can be supported by having that repository available locally?

It's normal DNF mirror, so we don't have official documentation. We have a community post with a walk through.

Long-term we plan to offer a more complete option for configuring a repository mirror, but for now self-managed will be required.

I was especially wondering about Veeam Threat Hunter signatures or Veeam Intelligent Diagnostics signatures for Veeam ONE.

For Threat Hunter, it will not be possible. This will require that the mount server be able to reach the signatures server. You can use an Internet Proxy for such situations.

For Veeam Intelligent Diagnostics, you can manually retrieve and import the signatures.

[TimoB]

Hi David,
I appreciate your prompt response

It's normal DNF mirror, so we don't have official documentation. We have a community post with a walk through.
Long-term we plan to offer a more complete option for configuring a repository mirror, but for now self-managed will be required.

Thanks for that. I was planning to follow that guide. I am looking forward to your long-term repo mirror configuration option.

For Threat Hunter, it will not be possible. This will require that the mount server be able to reach the signatures server. You can use an Internet Proxy for such situations.

Giving proxy access was something that I wanted to avoid. In my simple mind, the signature file is something that could be distributed as a file which could be easily automated. VSPC has some options to distribute patches on Veeam Backup servers. Unfortunately, neither VID nor Threat Hunter files are considered as such.

I will set up the repository and try to find out how good it works with Infrastructure Appliances.
Hopefully, further use cases are available in future as well. Eg. VBR or VeeamONE Updates.
Would be looking forward to it.