Comments
3 comments
-
Hello,
Since so many SQL Servers employ 'locked-down' configurations, it makes it difficult to document every single user right and file location needed by SQL Backup. We keep a living document on the Knowledge Base listing all of the registry entries, file locations, server roles, and policies that we've come across so far.
I hope this points you to the problem area. -
I completely missed that KB article, thanks. I will report back if I find that it's any different.
Doug -
Please do -- most of the information in there is based on past experience with customers. Thanks!
Add comment
Please sign in to leave a comment.
I tried using one account for both the service and SQL by following the documentation for the SQL Backup security model, but ran into a number of issues. I ended up creating a new domain account with the log on a services option along with a separate SQL Account for the agent service to use following the documentation, but unless the service account has administrative privileges SQL Backup does not run.
If running under a non-administrative account I receive a VDI error 1030, but I did confirm that sqlvdi.dll exists on my server and is registered. So it does appear to be an access issue.
What permissions does the service account need since the documentation does not appear to be sufficient?
Do both the service account and SQL Account need to be a member of the SDQL Server sysadmin fixed server role?
Thanks.
Doug