You can transition to v13 but the auto updates will not work if air-gapped.  I also believe during the installation it calls out to the Veeam servers as well to download packages.

So more than likely not - contradicted myself.  LOL

Hi ​@Matt Danger Shroyer you mean the VR itself is air-gapped and/or the repositories are air-gapped?

here is a summary you should follow.

1. Plan & verify compatibility
2. Download updates externally
3. Backup Veeam configuration (most important)
4. Transfer update files to air-gapped system
5. Update Veeam Backup Server (Core)
6. Update Veeam Console (if remote consoles exist)
7. Update Infrastructure Components (Proxies, Repos, etc.)
8. Update Agents (if applicable)
9. Test & validate backups/restores

Andre,

The entire rack is air-gapped.

I don't need firewalls kind of air-gapped.

I wish I could set DNS to 8.8.8.8 level of air-gapped.  

I have to transfer files via the world's largest 2TB platter HDD air-gapped.

My servers communicate by signal flags and Morse Code type of air-gapped.

Andre,

I forgot my manners. Thank you very much for the advice!

Chris,

I appreciate the advice! The change to require internet facing connections is interesting, and I completely understand. My C-Suite handlers not so much.

​@Matt Danger Shroyer I see your needs, so, you don’t need internet connection in order to upgrade the VBR or any other component.
you just need to download the ISOs and use as you already use to do :-) 

Hi ​@Matt Danger Shroyer!

You can run Veeam Backup & Replication in an offline or air-gapped environment, which many customer currently do. You won’t be able to receive any update notifications, nor do Threat Hunter or any other ransomware detection features get updated definitions. So in general, you’ll need to make sure tho regularly apply updates manually and keep in mind that the ransomware detection features will be out-dated. 

Talking about the V13 Software Appliance. It can be deployed and run without any internet connection. Similar to the current Windows release, you won’t be able to receive any updates. But you could build a offline repository and point the appliance to it.

For now the V13 Software Appliance is meant for new environments and there’s no migration path available. So if you’re currently running V12, you need to wait for the next release 13.0.1 to update your Windows based installation.

As already told: The “luxury” of auto-upgrade (including OS updates btw) requires internet connections for the solution is also designed to run fully independent.

Should be good to go from my POV.

Nice Andre!

Veeam 13 offers auto update, if you have access to the internet.

There is link to repository.veeam.com in the configuration,

but you can create own repository, where you will set link to your location

and anytime you need to update, you can put there new version of Veeam13,

so you can update Veeam internally.