-
Title
Why doesn't the db_backupoperator role have permissions to execute the LiteSpe -
Description
When using SQL native 'Backup' the user only need to be a member of db_backupoperators database role. Why doesn't the db_backupoperator role have permissions to execute the LiteSpeed xp_backup_database stored procedure?
-
Cause
Microsoft’s VDI (Virtual Backup Device Interface Specification) limitation.
-
Resolution
In order to execute stored procedures it would require sa level permissions. There is no way around this when executing LiteSpeed backups or restores via its extended stored procedures. The LiteSpeed Engine for SQL Server (LSE) does not require the sa permissions because a native ‘Backup Database’ command is being fired off and the engine is capturing the data in transit. If you only want to grant backup operator permissions to users then you should consider LSE because it runs at the OS level, it operates with the same level of privileges that SQL Server uses.
This is a limitation in Microsoft’s VDI (Virtual Backup Device Interface Specification). VDI requires sysadmin level privileges (not sa privileges) to execute backups. The db_backupoperator role does not have sysadmin permissions, and also doesn’t have stored procedure EXECUTE rights either, so it definitely can’t do what is needed.This is true for all 3rd party backup products that use VDI (and most do).There is a help file for the VDI specification available in this download from Microsoft. If you search for 'sysadmin' you'll see the information for security.