Veeam B&R and VeeamOne (version 13) on one server, is it possible?

It is best to separate VBR and VONE on two separate servers.  You tend to run into these issues when you put them both on one and it is not best practice to do so.

“We strongly recommend that no highly-transactional and business-critical software is deployed on the same machine as the Veeam backup server… Only Veeam Backup & Replication should run on the backup server.”

Before You Begin - Veeam Backup & Replication User Guide

Hi ​@TomMat, I could not get enough information from your question. Are you looking at deploying VBR and Veeam One in a test or production environment? For Production, kindly pay keen attention to the above recommendations. In case, you have already deployed both together and wish to migrate VOne to another server, I have got you covered 

Hello again,

Thank you for your feedbacks.

Best practices and reality sometimes differ. “Best practice” often assumes an unlimited IT budget, even for small companies.

“We strongly recommend that no highly transactional and business-critical software is deployed on the same machine as the Veeam backup server.”

I understand this recommendation, but in my view, VONE is neither highly transactional nor business-critical software. It is an advanced monitoring and reporting system. IT staff typically access and analyze VONE outputs during working hours - not at night when VBR backups run. According to VONE white papers, the only restriction mentioned is that installation on a domain controller is not allowed.

Our physical server has sufficient resources for both VBR and VONE. It seems wasteful to dedicate it solely to VBR, which only requires a few hours at night, leaving the server idle for the rest of the day.

In previous versions (at least up to v11), this setup was possible. In version 13, I have not found any documentation explicitly prohibiting it.

I am not happy about installing a new virtual server just for VONE (minimum 4 cores, 16 GB RAM recommended, plus a Microsoft Server license). Furthermore, in case of a malfunction in the virtual environment, I might not be able to access VONE and check events leading up to the issue. Installing VONE on a physical server “outside” gives me that possibility.

Therefore, we purchased a server with a configuration strong enough to host both functions, because BR13 and ONE13 documentations did not deny this scenario.

If I must decide between:

• Moving VONE to a virtual environment to have all functions available, or
• Keeping the current setup and ignoring Backup Log Analysis / Veeam Intelligent Diagnostics (the only unavailable function now),

I prefer to keep the current setup.

It is strange that this installation scenario was neither addressed nor prohibited in VONE documentation, and that this issue was not identified earlier.

Best regards, and I appreciate any opinion you may have,
Tom

> Our physical server has sufficient resources for both VBR and VONE. It seems wasteful to dedicate it solely to VBR, which only requires a few hours at night, leaving the server idle for the rest of the day.

Both can coexist. I run VBR and Veeam ONE together this way in my lab 🙂 What was referenced above is a best-practice recommendation, not a hard requirement. If you have a physical server with sufficient resources, you can decide to run both services on the same system. 

​​​​​​Disclaimer: Speaking from personal experience, not as Veeam Support!

Personal experience is sometimes more valuable than professional support!
This means I need to open a support case because coexistence should be possible and should work as intended.

Many thanks!
Tom

Since installing them on one server works with the resources you have and it is one of the services that seems shared by both apps I might suggest you get on with Support now so they can help troubleshoot the issue.  I don’t think anyone here is going to be able to give any further suggestions on how to get the service running other than checking the logs, event viewer, etc. (normal troubleshooting things).

Support will be able to check the logs and probably find the issue much faster.  Logs are under C:\ProgramData\Veeam if you are looking for them based on components, jobs, etc.

When you have resolved your issue, please come back and share your experience with the wider community. Also feel free to mark any replies that helped as the best answer so others can benefit from them.