We resolved the issue this morning.
There were two issues here. One was my mistake; the other looks like a gap in the documentation.
1. The SQL Server service account did not have a login on the server.
For SQL Backup to use the account, it has to be sysadmin on the server.
I added the service account DEV\sqlservice as a sysadmin on the server.
The server did actually log the failed logins, but I was looking in the agent log rather than the server log. D'oh!
The UI installer over RDP gave the clearest indication of this issue. It would be helpful if the error messages were more consistent.
2. The command line installer requires a password for the service account.
For SQL Backup to use the service account, it needs to know the password.
In the end, a command like this worked for me:
It produced a result like this:
The SQL Backup UI now shows a yellow "Trial" icon next to the server. Success!
The command line installer does not force you to provide a password, and the documentation suggests that one is unnecessary to use the server's account.
I imagine this would work if the server is running under one the default Windows accounts, but we use dedicated service accounts with passwords.
It would be helpful if the documentation was clearer on this point.
As a security note, I don't recommend using my solution for a production deployment. psexec does not encrypt its connection to the remote server. Don't allow someone to sniff your production password over the network!
There were two issues here. One was my mistake; the other looks like a gap in the documentation.
1. The SQL Server service account did not have a login on the server.
For SQL Backup to use the account, it has to be sysadmin on the server.
I added the service account DEV\sqlservice as a sysadmin on the server.
The server did actually log the failed logins, but I was looking in the agent log rather than the server log. D'oh!
The UI installer over RDP gave the clearest indication of this issue. It would be helpful if the error messages were more consistent.
2. The command line installer requires a password for the service account.
For SQL Backup to use the service account, it needs to know the password.
In the end, a command like this worked for me:
| Code: |
psexec \\$TargetServer G:\media\SQBServerSetup.exe /VERYSILENT /SUPPRESSMSGBOXES /SVCUSER $svcuser /SVCPW $svcpw |
It produced a result like this:
| Code: |
PsExec v1.98 - Execute processes remotely Copyright (C) 2001-2010 Mark Russinovich Sysinternals - www.sysinternals.com Connecting to REMOTESERVER...Starting PsExec service on REMOTESERVER...Connecting with PsExec service on REMOTESERVER...Starting G:\media\SQBServerSetup.exe on REMOTESERVER... G:\media\SQBServerSetup.exe exited on REMOTESERVER with error code 0. |
The SQL Backup UI now shows a yellow "Trial" icon next to the server. Success!
The command line installer does not force you to provide a password, and the documentation suggests that one is unnecessary to use the server's account.
I imagine this would work if the server is running under one the default Windows accounts, but we use dedicated service accounts with passwords.
It would be helpful if the documentation was clearer on this point.
As a security note, I don't recommend using my solution for a production deployment. psexec does not encrypt its connection to the remote server. Don't allow someone to sniff your production password over the network!