Click here to monitor SSC
SQLServerCentral is supported by Red Gate Software Ltd.
 
Log in  ::  Register  ::  Not logged in
 
 
 
        
Home       Members    Calendar    Who's On


Add to briefcase

Backup on network fails Expand / Collapse
Author
Message
Posted Thursday, January 3, 2013 7:34 AM
Forum Newbie

Forum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum Newbie

Group: General Forum Members
Last Login: Thursday, January 30, 2014 2:30 PM
Points: 4, Visits: 76
Hi,

I am trying to configure SQL server 2005 backup to a another server drive \\server2\folder. The folder on second server is shared, shared permission and security permission are set fine.

SQL server runs with NT Authority\Network service and SQL agent runs with a domain account which is given full permission on folder.

Still the backup from SQL job fails with below error:
"Cannot open backup device '\\server2\folder\master.bak'. Operating system error 5(Access is denied.). BACKUP DATABASE is terminating abnormally.".

Please let me know what might be the issue?

Thanks

Post #1402373
Posted Thursday, January 3, 2013 11:45 AM


SSCertifiable

SSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiable

Group: General Forum Members
Last Login: Saturday, November 1, 2014 6:54 AM
Points: 5,221, Visits: 5,118
The account which actually rights the backup is the engine, not the agent.

You will need to make the SQL Engine service run as a domain account.

You could try adding the computer account in on the share permission, but never tested that so cannot confirm if it works or not.

I would consider first backing up to local disk then using something like robocopy to copy the files to the network share, for added safety and doesnt stop the backup completing if there is a network blip.




Want an answer fast? Try here
How to post data/code for the best help - Jeff Moden
Need a string splitter, try this - Jeff Moden
How to post performance problems - Gail Shaw
CrossTabs-Part1 & Part2 - Jeff Moden
SQL Server Backup, Integrity Check, and Index and Statistics Maintenance - Ola Hallengren
Managing Transaction Logs - Gail Shaw
Troubleshooting SQL Server: A Guide for the Accidental DBA - Jonathan Kehayias and Ted Krueger

Post #1402490
Posted Friday, January 4, 2013 4:18 AM
SSCommitted

SSCommittedSSCommittedSSCommittedSSCommittedSSCommittedSSCommittedSSCommittedSSCommitted

Group: General Forum Members
Last Login: Thursday, November 20, 2014 8:18 AM
Points: 1,620, Visits: 5,694
anthony.green (1/3/2013)
You could try adding the computer account in on the share permission, but never tested that so cannot confirm if it works or not.


I can confirm it *does* work, but it's not a configuration I would recommend--it gives any service running as Local System or Network Service on the SQL server machine access to the share, which is a potential security issue.
Post #1402795
Posted Friday, January 4, 2013 4:19 AM


SSCertifiable

SSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiable

Group: General Forum Members
Last Login: Saturday, November 1, 2014 6:54 AM
Points: 5,221, Visits: 5,118
paul.knibbs (1/4/2013)
anthony.green (1/3/2013)
You could try adding the computer account in on the share permission, but never tested that so cannot confirm if it works or not.


I can confirm it *does* work, but it's not a configuration I would recommend--it gives any service running as Local System or Network Service on the SQL server machine access to the share, which is a potential security issue.


Thanks for the clarification Paul, always run everything under a domain account so never had to test that particular scenario, but agreed with its a massive security flaw.




Want an answer fast? Try here
How to post data/code for the best help - Jeff Moden
Need a string splitter, try this - Jeff Moden
How to post performance problems - Gail Shaw
CrossTabs-Part1 & Part2 - Jeff Moden
SQL Server Backup, Integrity Check, and Index and Statistics Maintenance - Ola Hallengren
Managing Transaction Logs - Gail Shaw
Troubleshooting SQL Server: A Guide for the Accidental DBA - Jonathan Kehayias and Ted Krueger

Post #1402800
Posted Monday, January 21, 2013 5:12 AM
SSC-Enthusiastic

SSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-Enthusiastic

Group: General Forum Members
Last Login: Monday, November 17, 2014 3:13 AM
Points: 194, Visits: 752
I believe read/write permission should go well with the account that you're using to back those db's of your's onto a shared path. If you know how to configure the security part then fair enough, otherwise ask your administrator to look into it. Pls. use "sa" account to run all your jobs unless there is a specific need to drift away from best practice.

I would also agree what other experts have mentioned over here, instead of backing it up on the share...try backing up on local disk, and then by using robocopy you can actually dump that file to the specific shared path. This way your backup will not be interrupted, and you'll be safe

Regards,
Faisal
Post #1409499
« Prev Topic | Next Topic »

Add to briefcase

Permissions Expand / Collapse