Is there a SQL Server Best Practice for Veeam Backend ?

[SyNtAxx]

Is there a SQL Server Best Practice for Veeam Backend ? In other words, is it better to keep SQL on a dedicated vm/server as opposed to having Veeam Backup Manager and SQL integrated on the same server? Currently under my v8 build the SQL(2012) and Veeam are running on same Host. The server has 16 cores and 128gb ram of which 64 is dedicated to SQL. I'm asking as I seem to think Veeam and SQL are trampling over each other because of the number of jobs etc to process and update. I plan on building from scratch a new environment for v9 deployment. What is the current concensus or opinions from the user base and of course the official position of Veeam?

Thanks,

Nick

[SyNtAxx]

I just found the solution architect 'best pratice guide".


Nick