Bit of an old chestnut I know but I can't solve this one.
I can issue a BACKUP command from the query window to the local C drive and it backs up the database.
I cannot backup to a mapped network drive.
The SQL Server Agent account is 'LocalSystem' which I assume will not have the authorities to write to a mapped drive.
However I am running the backup from a query window in SQL Server Management Studio from an account that is windows authenticated sysadmin.
The windows account can access the mapped drive in my windows session and copy files with windows explorer but for some reason my
SQL Server Management Studio will not do it.
I figured I need to run the backup command as a T-SQL step in an SQL agent job - with a 'Run AS' value of a proxy account.
I have set up a credential and a proxy to the same domain windows account that can manipulate data on the mapped drive.
However the T-SQL step won't let me select the proxy account to run the step!
At first I though I had not set the credential and proxy up properly but I can select it on steps for an SSIS package, just not a Y-SQL step.
I don't understand why.
So my questions are:-
Why Can't I run the backup command from a query window to a UNC location even when I have the windows authorities to the mapped drive location?
Why do T-SQL steps not allow you to select a 'Run As' proxy?
Is there anything else I can do to achieve a backup to a mapped drive from inside SQL Server without changing the Agent Service account?
Dazed and confused.
Remember.. 'Depression is just anger without enthusiasum'.
I can issue a BACKUP command from the query window to the local C drive and it backs up the database.
I cannot backup to a mapped network drive.
The SQL Server Agent account is 'LocalSystem' which I assume will not have the authorities to write to a mapped drive.
However I am running the backup from a query window in SQL Server Management Studio from an account that is windows authenticated sysadmin.
The windows account can access the mapped drive in my windows session and copy files with windows explorer but for some reason my
SQL Server Management Studio will not do it.
I figured I need to run the backup command as a T-SQL step in an SQL agent job - with a 'Run AS' value of a proxy account.
I have set up a credential and a proxy to the same domain windows account that can manipulate data on the mapped drive.
However the T-SQL step won't let me select the proxy account to run the step!
At first I though I had not set the credential and proxy up properly but I can select it on steps for an SSIS package, just not a Y-SQL step.
I don't understand why.
So my questions are:-
Why Can't I run the backup command from a query window to a UNC location even when I have the windows authorities to the mapped drive location?
Why do T-SQL steps not allow you to select a 'Run As' proxy?
Is there anything else I can do to achieve a backup to a mapped drive from inside SQL Server without changing the Agent Service account?
Dazed and confused.
Remember.. 'Depression is just anger without enthusiasum'.