Comments
Sort by recent activity
I just noticed this
execute master..sqbdir '\\recovery' gives me a listing
execute master..sqbdir '\\recovery\' does not. / comments
I just noticed this
execute master..sqbdir '\\recovery' gives me a listing
execute master..sqbdir '\\recovery\' does not.
If I do execute master..sqbdir '\\recovery' I get the directory listing at the share level. If I go execute master..sqbdir '\\recovery\sqlbackups' it doesn't return anything and it should. I'm running this from my machine and I'm admin on \\recovery. This used to work until 5.4 / comments
If I do execute master..sqbdir '\\recovery' I get the directory listing at the share level. If I go execute master..sqbdir '\\recovery\sqlbackups' it doesn't return anything and it should. I'm r...
keymoo wrote:
Thanks Jason, when running
sc sdshow "SqlBackupAgent"
I get
D:(A;;CCLCSWRPWPDTLOCRRC;;;SY)(A;;CCDCLCSWRPWPDTLOCRSDRCWDWO;;;BA)(A;;CCLCSWLOCRRC;;;AU)(A;;CCLCSWRPWPDTLOCRRC;;;PU)
To answer your other questions
- There is only one default instance of SQL Server (2000 SP3)
- The SQL Backup Agent is running as a domain account called sa-SQLBackup and is in sysadmin server role in SQL Server. It is a normal account on the server (i.e. not a local admin).
Just make it local admin and that will fix everything. / comments
keymoo wrote:
Thanks Jason, when running
sc sdshow "SqlBackupAgent"
I get
D:(A;;CCLCSWRPWPDTLOCRRC;;;SY)(A;;CCDCLCSWRPWPDTLOCRSDRCWDWO;;;BA)(A;;CCLCSWLOCRRC;;;AU)(A;...
keymoo wrote:
brosato wrote:
Just make it local admin and that will fix everything.
Very funny - actually I did do that just as a test and I got identical behaviour.
I wasn't trying to be funny actually. That's what I had to do to get it working. Although I have another server that's set up identical and it works without being local admin. / comments
keymoo wrote:
brosato wrote:
Just make it local admin and that will fix everything.
Very funny - actually I did do that just as a test and I got identical behaviour.
I wasn't trying to be ...
keymoo wrote:
brosato wrote:
Just make it local admin and that will fix everything.
Very funny - actually I did do that just as a test and I got identical behaviour.
Oh, make sure you restart the service after adding the account to local admin. / comments
keymoo wrote:
brosato wrote:
Just make it local admin and that will fix everything.
Very funny - actually I did do that just as a test and I got identical behaviour.
Oh, make sure you rest...
keymoo wrote:
try reading this http://www.catb.org/~esr/faqs/smart-questions.html
Maybe I'm not asking a question. It's possible I'm just complaining about having to give admin rights to an account on the instance and the server just to perform a backup. I didn't really believe anyone was listening.
Oh, and thanks for your non answer of my non question. [image] / comments
keymoo wrote:
try reading thishttp://www.catb.org/~esr/faqs/smart-questions.html
Maybe I'm not asking a question. It's possible I'm just complaining about having to give admin rights to an a...
Well, I have it working right now without the account being a memeber of the sysadmin role. What's up with that? / comments
Well, I have it working right now without the account being a memeber of the sysadmin role. What's up with that?
Never mind. BUILTIN\ADMINISTRATORS got me. It doesn't work. / comments
Never mind. BUILTIN\ADMINISTRATORS got me. It doesn't work.
Even after giving sysadmin rights to the account I still get an error
BACKUPTHOR: Backup - Failed
===========================
Performing full backups - Failed
This operation failed with errors.
Backing up ASPState (full database) to:
E:\BACKUP\FULL_(local)_ASPState_20081121_111211.sqb
VDI error 1000: Failed to recognize the SQL Server instance name. Check that the SQL Backup service startup user has read/write rights to access the SQL Server service information. You can do this by using the "sc sdshow/sc sdset" commands.
Memory profile
Type Maximum Minimum Average Blk count Total
Commit 51642368 4096 102764 8211 843796480
Reserve 4128768 8192 48890 7354 359542784
Free 432054272 4096 4140696 228 944078848
Private 51642368 4096 77288 14978 1157632000
Mapped 1536000 4096 159326 49 7806976
Image 5808128 4096 70446 538 37900288 / comments
Even after giving sysadmin rights to the account I still get an error
BACKUPTHOR: Backup - Failed
===========================
Performing full backups - Failed
This operation failed with errors.
Ba...
petey wrote:
Your configuration looks fine. The only permission that the SQL Backup Agent service startup account needs to have is 'Query configuration' (CC), on the SQL Server service.
I would suggest turning on auditing for the 'Object Access' category (e.g. using secpol.msc), run a backup, and check using the Event Viewer which object accesses are being denied.
I just gave it everything to remove all doubt. Well, auditing doesn't show any failure on object access. Matter of fact, it doesn't show any success for object access either. There are no log entries for the SQL Backup service account at all. / comments
petey wrote:
Your configuration looks fine. The only permission that the SQL Backup Agent service startup account needs to have is 'Query configuration' (CC), on the SQL Server service.
I would...