Skip to main content

Everyone that is part of the Veeam100 group gained access thanks to @Rin to the VB365 v8 Technical Preview.  I took it for a spin in my lab installing it then doing a bit of exploring to find some new things and dialogues.  You can find the blog below and can explore it on my blog site as well here - https://just-virtualization.tech/2024/04/19/veeam-vbm365-v8-technical-preview-installation/

Being part of the Veeam Vanguard/Legends programs gives you some special privileges and opportunities, like testing out the first Technical Preview of the VBM365 v8 software. Today, I am going to go through the installation, which is identical to the current v7 version, but I will point out some new things for v8 that will come once the product goes GA.

!-->

To begin the installation of the software you need to download the ISO file as well as the license (LIC) file for testing. Once again this was available through the Vanguard/Legends program that I am part of. Once downloaded, mount the ISO file and double-click the setup file to begin.

!-->

  • The first screen is the beginning of the installation process and is similar to v7 installation!-->

!-->

Figure 1 - Installation screen for VB365 v8

!-->

  • Once you click Install you then select the components that you wish to install on the system!-->

!-->

Figure 2 - Selection of components for installation

!-->

  • You will accept the license and then have to select the License file you downloaded as well!-->

!-->

Figure 3 - License file required for installation

!-->

  • A system configuration check will happen to ensure your system meets the specified requirements for installation and if not then you are shown message about potential issues. In my case the system I installed on did not have the recommended CPU or RAM requirements for the new version, which is 8 vCPU and 16GB of RAM minimum as noted here - Veeam VB365 - System Requirements!-->

!-->!-->!-->

!-->

!-->

  • I just clicked Next to proceed, which will install any system requirements then show you the Ready to Install window. Notice that VB365 v8 uses a PostgreSQL database engine now which is new.!-->

!-->

Figure 4 - Ready to Install window with details

!-->

  • Click Install to install the application on your server. Once complete you will get the successful installation window and just click Finish.!-->

!-->

Figure 5 - Successful installation

!-->

This will complete the installation of the VB365 v8 software to your system and you are now ready to explore. Some of the new features within the v8 are noted below with some screenshots.

!-->

  • PostgreSQL - this was noted in one of the install screenshots above.
  • Proxies
    • Windows or Linux servers supported
    • Ability to create service accounts on the Proxy server during setup
    • Proxy Pools are now available and can be used in conjunction with Repositories !-->!-->!-->
    !-->!-->!-->

!-->!-->

!-->

!-->

!-->

!-->

  • Repositories
    • Block or Object Storage options
    • Object Storage - similar to Veeam Backup & Replication now
    • Backup Proxy link to repository - Proxy or Proxy Pool
    • Immutability on Repositories !-->!-->!-->!-->
    !-->!-->

!-->!-->

!-->

!-->

!-->

!-->

  • Auto-Logoff and MFA are now available in the VB365 console as well just like VBR!-->

!-->

Figure 6 - Auto-Logoff and MFA available in Console

!-->

So to summarize this blog covers the installation of VB365 v8 Technical Preview as well as some of the newer options that are going to be available once this goes GA. There are a ton more things to discuss but that will be covered in my next blog on VB365 v8 Technical Preview.

!-->

I hope you enjoyed this blog and you can find other Veeam related blogs on my site here - Veeam Blogs. Until next time happy blogging!

Thanks for this share 🙂 In addition, If u select local disk, u can use ur VM local disk. For this reason, you cannot use a backup appliance like Exagrid. Is not it right? What I mean is that you can only use the storage that you can connect to vCenter.

Yes you can use storage local to vCenter as well. As long as the VM can see it you can use it.

Thank u Chris ..

Not a problem always glad to help.


Thanks for this share 🙂 In addition, If u select local disk, u can use ur VM local disk. For this reason, you cannot use a backup appliance like Exagrid. Is not it right? What I mean is that you can only use the storage that you can connect to vCenter.

Yes you can use storage local to vCenter as well. As long as the VM can see it you can use it.

Thank u Chris ..


Great article as usual, @Chris.Childerhose ! Thanks for sharing with us! 👏🏻👏🏻👏🏻

Thanks Luiz. I try. 😁


Thanks for this share 🙂 In addition, If u select local disk, u can use ur VM local disk. For this reason, you cannot use a backup appliance like Exagrid. Is not it right? What I mean is that you can only use the storage that you can connect to vCenter.

Yes you can use storage local to vCenter as well. As long as the VM can see it you can use it.


Great article as usual, @Chris.Childerhose ! Thanks for sharing with us! 👏🏻👏🏻👏🏻


Thanks for this share 🙂 In addition, If u select local disk, u can use ur VM local disk. For this reason, you cannot use a backup appliance like Exagrid. Is not it right? What I mean is that you can only use the storage that you can connect to vCenter.


Nice overview Chris !

We’re playing with the TP release here. Important point to mention is that on the Linux proxys, the .NET frameswork runtime must be installed. This is a prerequisite before starting installing the proxy role.

You’re correct @kristofpoppe .. this is the official Microsoft link where we can find the installation commands https://learn.microsoft.com/en-us/dotnet/core/install/linux-ubuntu-install?tabs=dotnet8&pivots=os-linux-ubuntu-2004

Thanks for sharing that one Marco.


Nice overview Chris !

We’re playing with the TP release here. Important point to mention is that on the Linux proxys, the .NET frameswork runtime must be installed. This is a prerequisite before starting installing the proxy role.

You’re correct @kristofpoppe .. this is the official Microsoft link where we can find the installation commands https://learn.microsoft.com/en-us/dotnet/core/install/linux-ubuntu-install?tabs=dotnet8&pivots=os-linux-ubuntu-2004


Nice overview Chris !

We’re playing with the TP release here. Important point to mention is that on the Linux proxys, the .NET frameswork runtime must be installed. This is a prerequisite before starting installing the proxy role.

Thanks. I thought .NET was only windows not the Linux proxies?  Have not tested the Linux ones just yet but will.  Did install it ahead of configuration though on Windows.


Nice overview Chris !

We’re playing with the TP release here. Important point to mention is that on the Linux proxys, the .NET frameswork runtime must be installed. This is a prerequisite before starting installing the proxy role.


Comment