so I've got a basic test up and running and have the following comments;
1. JeOS seems to require 2x120GB disks even for a virtual server being used as a proxy server.
What is the reason for this where is specifically for the mount process it says;
Disk Space: 750 MB for Microsoft Windows-based proxies; 400 MB for Linux-based proxies.
We are currently running 4x Linux Proxies with 15GB OS disk which has been more than adequate for our use case.
2. I've been able to dial in ZFS repository by adding it as a managed server and get the following warning when adding it:In our case I give it a different path folder on the same zvol (i.e. /VeeamBackup/v13backups instead of /VeeamBackup/v13backup)
Backups work fine - throughput was similar to using Rocky9 Linux repositories on V12 (which is great and expected).
3. "restore guest files" option doesn't give an option to specify the credentials for the source machine giving an error;This is for both windows and Linux single file restores. Is this feature working differently to v12?
I tried both by the webui and the Windows client.
4. When I added the IP of the network appliance, I made a typo on the gateway, and on DNS (I blame the keyboard![:lol:]( "Laughing")
). I fixed that but when I tried to change the DNS settings via the webui, they were blanked afterwards. I was only able to make changes to the DNS configuration post install via the VMware console screen for the appliance. After making the change the appliance was able to update itself as expected.
5. Adding a Linux host
Adding a linux host using certficate-based authentication says "Requires a deployment kit pre-installed to the target machine."
Am I correct that to enable an existing Linux server to use certificate-based auth, I need to follow the process here?
https://helpcenter.veeam.com/docs/vbr/u ... tml?ver=13
6. Anton confirmed in a DM that JeOS is patched to make sure that its safe and secure and high performance, so it makes perfect sense to deploy it in the role of Proxies rather than to use generic Linux as it will help keep the security teams at ease! Currently we are making heavy use of OpenZFS for all our repositories and my expectation is that because this is still not officially supported, then I won't be able to deploy a ZFS repository using JeOS, so I'll need to keep using Rocky Linux for the repository?
Overall, this is looking great and certainly keeps the patch management for the environment simple and secure.
Even better is JeOS (Just Enough OS) reminds me of that old Depeche Mode song "Just Can't Get Enough"!
1. JeOS seems to require 2x120GB disks even for a virtual server being used as a proxy server.
What is the reason for this where is specifically for the mount process it says;
Disk Space: 750 MB for Microsoft Windows-based proxies; 400 MB for Linux-based proxies.
We are currently running 4x Linux Proxies with 15GB OS disk which has been more than adequate for our use case.
2. I've been able to dial in ZFS repository by adding it as a managed server and get the following warning when adding it:
Code:
OpenZFS Fast Clone preview is enabled. this functionality is not supported for production use.Backups work fine - throughput was similar to using Rocky9 Linux repositories on V12 (which is great and expected).
3. "restore guest files" option doesn't give an option to specify the credentials for the source machine giving an error;
Code:
The request does not have valid authentication credentialsI tried both by the webui and the Windows client.
4. When I added the IP of the network appliance, I made a typo on the gateway, and on DNS (I blame the keyboard
). I fixed that but when I tried to change the DNS settings via the webui, they were blanked afterwards. I was only able to make changes to the DNS configuration post install via the VMware console screen for the appliance. After making the change the appliance was able to update itself as expected.5. Adding a Linux host
Adding a linux host using certficate-based authentication says "Requires a deployment kit pre-installed to the target machine."
Am I correct that to enable an existing Linux server to use certificate-based auth, I need to follow the process here?
https://helpcenter.veeam.com/docs/vbr/u ... tml?ver=13
6. Anton confirmed in a DM that JeOS is patched to make sure that its safe and secure and high performance, so it makes perfect sense to deploy it in the role of Proxies rather than to use generic Linux as it will help keep the security teams at ease! Currently we are making heavy use of OpenZFS for all our repositories and my expectation is that because this is still not officially supported, then I won't be able to deploy a ZFS repository using JeOS, so I'll need to keep using Rocky Linux for the repository?
Overall, this is looking great and certainly keeps the patch management for the environment simple and secure.
Even better is JeOS (Just Enough OS) reminds me of that old Depeche Mode song "Just Can't Get Enough"!
Statistics: Posted by ashleyw — Sep 15, 2025 4:42 am
