Odd permissions issue when backing up to a network location

Question

Post reply

Odd permissions issue when backing up to a network location

Jeff Shurak

SSCrazy

Points: 2361
More actions
July 11, 2013 at 2:33 pm

#395124

I have a 2005 box and 3 2008 boxes. All 2008 boxes backup fine to the network location however, I'm getting a 'Cannot open backup devices '\\server\drive'. Operating system error 5(Access is denied). ' error. I'm using the same account on all 4 servers with full control over the directory. Logged into the 2005 machine I can open up the network location and create files. Any ideas?
*Edit - The service account also has full control over this directory.

Viewing 8 posts - 1 through 7 (of 7 total)

You must be logged in to reply to this topic. Login to reply

durai nagarajan SSCoach Points: 15778 More actions · Answer 1

Is that 2005 box using an alias user to take backup?

Regards
Durai Nagarajan

John Mitchell-245523 SSC Guru Points: 148809 More actions · Answer 2

Is your backup running as a job? Does the SQL Server Agent account have access to the target folder?

John

Jeff Shurak SSCrazy Points: 2361 More actions · Answer 3

Thanks for the replies.

The agent account is the same as the service account, so it has full control over the directory. Can't execute as a job or in a query window.

No alias. I can't write write using my own login, I can write backups from the other three. The other three are windows/sql server 2008 while this is windows 2003/sql 2005 for what its worth.

Steve Jones - SSC Editor SSC Guru Points: 736455 More actions · Answer 4

I would start to suspect timing (check computer times) or some other Kerberos/SPN issue from this machine to others.

I might try changing the service account, restarting, then changing it back and restarting. I've seen weird issues like this in the past (SQL2K). Haven't heard of it in some time, but otherwise you might need to log in as the service account and do some troubleshooting from this, and another, machine.

Jeff Shurak SSCrazy Points: 2361 More actions · Answer 5

We have this resolved. It was an NTFS/sharing confilct. Thanks

Steve Jones - SSC Editor SSC Guru Points: 736455 More actions · Answer 6

thanks for the update. Any resolution steps others could try?

Jeff Shurak SSCrazy Points: 2361 More actions · Answer 7

I don't have the exact steps to solve as a coworker found the issue. I'm guessing whoever initially set up access did not allocate the proper access at both levels, resulting in the least restrictive permission being enforced.