Hello Remco,

The SQL logon user or Windows user name must be added to the
SQL Server SYSADMIN fixed server role before it can be used
by Data Protection for SQL.

More specifically, Data Protection for SQL uses the Microsoft recommended
Virtual Device Interface (VDI) API to perform backups and restores of
SQL Server databases. The VDI API requires the SYSADMIN server role in
order
to perform these operations. The Microsoft VDI specification states this:
      "The server connection for SQL Server that is used to issue the
       BACKUP or RESTORE commands must be logged in with the
       sysadmin fixed server role."

   Reference:
http://www.microsoft.com/en-us/download/details.aspx?id=17282


Thank you,

Del

----------------------------------------------------


"ADSM: Dist Stor Manager" <ADSM-L AT vm.marist DOT edu> wrote on 12/18/2013
06:23:40 AM:

> From: Remco Post <r.post AT PLCS DOT NL>
> To: ADSM-L AT vm.marist DOT edu,
> Date: 12/18/2013 06:24 AM
> Subject: sql2012 rights
> Sent by: "ADSM: Dist Stor Manager" <ADSM-L AT vm.marist DOT edu>
>
> Hi all,
>
> at my current customer we're now for the first time deploying TSM 6.
> 4 for SQL on a sql2012 on win2012r2. Until now we were just running
> the TSM for SQL as local system without any problems. This doesn't
> appear to work any more on the new deployment and the DBA is not
> eager (very much not eager!) to create a service account for TSM
> with sysadmin rights on his database server.
>
> So now the question, has anyone tried running TSM with a service
> account on SQL 2012 that has less rights than SYSADMIN? And if so,
> what were the results and which rights did you grant to the service
account?
>
> --
>
> Met vriendelijke groeten/Kind Regards,
>
> Remco Post
> r.post AT plcs DOT nl
> +31 6 248 21 622
>