Feature request - Veeam Managed Servers - Option to skip update check

[petesteven]

When adding a new Veeam Infrastructure Appliance as a managed server in V13, each appliance checks if updates are available for it and if the update server can be reached. This is not possible in dark sites or if FW rules are missing.

The timeout is quite long.

It would be good if there were an option to select “skip update check.” Otherwise, the waiting time when adding many components is very long.

[Dima P.]

Hello Peter,

I'd argue that we must allow to skip it but the time out needs to be fixed for sure. Thank you!

[pma]

Hi Peter,

One possible approach would be to add a key to the VSA configuration and the Windows registry for VBR that allows to bypass the update check.
For VSA, implementing this change would require approval from the security officer before applying the new configuration.

Would this solution be sufficient?

[petesteven]

Hi Maskim,

I'm not a big fan of registry keys (they get carried over during migration, and no one knows what was added, etc.).

It's okay as a workaround, but for the future, it might be a good idea to add a “Skip Updates” button when adding servers. Would that be possible?

[PTide]

Hi Peter

I would like to clarify something about your request.

Do you plan to set up a local repo that is available from your backup infrastructure network later (after adding all VIAs/VHRs) or you are not intending to do that whatsoever?

Even with a local repo on a dark site it is possible to deliver update packages (e.g. by using and ISO file, or by manually uploading packages obtained from elsewhere)

Thanks!

[petesteven]

Hello PTide,

Of course, updates are either downloaded online (though the internet connection may not yet be available because proxy settings aren’t rolled out via your policies until after they’re added, or a firewall rule is still missing) or via a local update server.
(Anything else would completely miss the point of security and updates.)

However, the question from you has nothing to do with the request itself. The request simply asks if the step can be skipped if the connection to the repo (local or online) isn’t available yet. I don't want to skip updates in general, but I just want to be able to skip the check when adding them because of the long timeout values