How can we help you today? How can we help you today?
pgrove
I have 3 domain machines in the test 1. SQLServer1 (Win2k3 w/ SQL2005) - Redgate SQLBackup Agent 5.3 - Domain service account for agent - "MYDOMAIN\Service-SQLBackup" - MYDOMAIN\Service-SQLBackup is a Local Server Admin, SysAdmin SQL Role - MYDOMAIN\User1 - Member of only "SQLServer1\User" local group, SysAdmin SQL instance role - MYDOMAIN\User2 - Member of SQLServer1\Administrators local group, SysAdmin SQL instance role 2. FileServer1 (Win2k3) BackupsShare1 - MYDOMAIN\Service-SQLBackup - Full Permissions to Share, Change Permission to FileSystem. - MYDOMAIN\User1 - Full permissions to share, Read/List/Execute permission to FileSystem. - MYDOMAIN\User2 - Full permissions to share, Read/List/Execute permission to FileSystem. 3. Workstation1 (Windows XP) - Red Gate SQL Backup 5 Management Console - Registered/Connected to SQLServer1's SQL instance What I know: 1. Agent works fine, backs up full locally every day, logs every hour. Sends copy to \\FileServer1\BackupShare1\SQLServer1\<<Filename>>.SQB 2. User1 and User2 are identical, except User2 is in the Local Admin group on SQLServer1. 3. Both users can get to, and add, server names (i.e. "FileServer1") in the "File Browser" dialog, "Network Shares" option. 4. Both users can see the server name and a "Twisty" (plus sign) next to the server. 5. When User1 clicks the twisty, in flickers for a second, then the twisty disappears. 6. When User2 clicks the twisty, the network shares on FileServer1 are listed. He can then browse down to the files. 7. Both users can manually enter the full path and filename and the files will restore. 8. Workaround: If I add User1 to the Local Administrators group on SQLServer1, he too can work just as well as User2 (he can use the twisty, and browse for the files). Problem: This is used primarily by developers to set/reset development and QA testing databases. Often times they are pulling these files from the archive so they have recent production data. I don't want to give them Local Administrator rights to the Windows server. It gives them: Remote desktop access Access to other SQL instances that they shouldn't have access Too many permissions, that can "enable" security on developed software to require unauthorized SysAdmin permissions on SQL / comments
I have 3 domain machines in the test 1. SQLServer1 (Win2k3 w/ SQL2005) - Redgate SQLBackup Agent 5.3 - Domain service account for agent - "MYDOMAIN\Service-SQLBackup" - MYDOMAIN\Service-SQLBackup i...
0 votes