VBR installation using a remote sql server

[jcofin13]

Trying to install a fresh VBR server and have the DB stored on a separate SQL server.
When i get to the database part of the install wizard and have Windows Authentication selected i enter in the name of the server and the db name (which i manually created prior). If i hit next it sits for a while and then errors with "Windows Authentication is not supported for remote SQL server with LOCAL SYSTEM service account. Specify a different service account or use native SQL authentication.

I dont understand what this means. The services are not installed yet so there is no LOCAL SYSTEM service account for it to complain about. The SQL server services are running via is default NT Service\MSSQLSERVER account. I can see the SQL Server Browser service is set to "Local Service" but im not sure its talking about that.

What does this mean and how do i avoid using mixed mode and SQL Auth if i dont have to?

Is it best practice to set the veeam service account from "Local System (recommended) to a domain service account which then is a local administrator of the veeam server itself?

[Mildur]

Hi jcofin13,

You must have chosen LOCAL SYSTEM in this step. That’s why the wizard complains on the next page when you select "Windows authentication credentials of service account." LOCAL SYSTEM is always present (Windows client and server), it's a standard Windows account for your local machine and cannot interact with any network components.

If you want to use "Windows authentication credentials of service account" to access the database, you need to run Veeam services under a domain account that has permission to access the MSSQL database.

Alternatively, why not simply create a SQL user on the MSSQL server for the database connection and let the Veeam services run with the LOCAL SYSTEM account?

Best regards,
Fabian

[jcofin13]

Thank you. I did get this figured out. I appreciate the confirmation/response.

The only thing that im still confused about is if you use a remote SQL server should that SQL server be in the AD domain or not? I know it is best practice to not have your VBR server a windows domain.

I have reviewed https://bp.veeam.com/vbr/2_Design_Struc ... abase.html but it makes no mention of the AD status of the SQL server itself. Is there a recommendation here?