Skip to main content
  • EN

Hello, I thought I would give the new BETA2 version of the Veeam Linux deployment a spin. Booting up to the jeOS, I was surprised to see two new options:

  • Veeam Infrastructure Appliance
  • Veeam Infrastructure Appliance (with iSCSI & NVME)

Detailed in the screenshot below, with the BETA1 version following:

BETA2

 

BETA1

Is this the new name for a Proxy or is this something else? And, the thing I’m probably most excited about….are we finally getting NVMe fabric support on Veeam?

Excited to see the Beta 13 Infrastructure Appliance shaping up! The move to Rocky Linux and PostgreSQL is a solid step forward. 

Yes these are new menu names.  I believe the second one would be mainly for a physical box with storage connected to it via the protocols noted.  The first to me is VM.

VBR Proxy for VMware isn’t new really. When you add a Proxy in the UI, you are prompted for adding that specifically (Proxy for VMware...well, not prompted, but an option/choice for that, or Gen Purpose, or CDP Proxy). I’ve looked at BETA1 pretty extensively, but not BETA2 as much so wasn’t aware Veeam added more functionality in their SA Proxies. If so, nice! 😊 Thanks for sharing ​@DaveR_NZ 

Hi ​@DaveR_NZ, the infrastructure appliance can be used for different roles, for example proxies. It comes with a minimal software configuration which is sufficient for those roles. The second option includes more components and will be necessary if you want to deploy a direct SAN proxy or need iSCSI/NVMe tools. From a security point of view, the first option is the way to go and the second one is only used if you really require it.

 

NVMe fabric support is coming, this could open the door to significant performance gains in high-demand environments.

NVMe fabric support is coming, this could open the door to significant performance gains in high-demand environments.

Yes, I’ve several customers running NVMe/TCP and they’ve been waiting for Veeam so they can move back to SAN-snapshots.

Comment


Terms & Conditions