We have some PowerShell scripts that we start from a Windows service. This produces some unpredictable behaviours. By default the service runs with the "Local System" account. Mostly this works well. Sometimes we get the following message:
Get-VBRServer : Microsoft SQL server hosting the configuration database is
currently unavailable. Possible reasons are heavy load, networking issue,
server reboot, or hot backup.
Please wait, and try again later.
When then changing the account to e.g. a local administrator account. The "Get-VBRServer" runs fine again. The Veeam server is running fine all the time. I suspect the error message is due to some account right problems. Unfortunally I cannot figure out which rights this might be. So if some might give me I hint I would do some further researching.
So, the scripts are executed with the use of Windows Schedule, right? What about adding "RunAs" commands to the script, so that, it's run under account with necessary permissions? Thanks.
I am using PowerShell to start a Veeam backup job in Windows 2008 without any problem with the Administrator account. If other user account was used to run the PowerShell for starting the job, exception was thrown :
Start-VBRJob : Exception has been thrown by the target of an invocation.
However, I would like to start the job by an other users (may be of administrators group but not Administrator) so that the use of Administrator account can be avoided
Grateful if anyone could share valuable experience.
just for your information. The problem was solved by using a user with db_owner rights on the Veeam database.
Here is in more details what we observed. We do *not* use the Windows scheduler. We use a custom service that triggers the Powershell commands. The following applies to the logon acount for the service.
When using the database shipped with Veeam no "special" user customization is needed. Running Powershell commands with the system account works.
When using a standalone MSSQL Database (beginning from SQL 2008) you have to use a user with special rights (db_owner) granted to the database. In case you do not do this you can get the misleading message "Get-VBRServer : Microsoft SQL server hosting the configuration database is currently unavailable. ...".