September 12, 2024 at 7:47 am
Hello All,
We have a domain account running sqlserver service.this account has r/w access to a network share, but backups are still failing. what are we missing here ?
Even the the said computer$ has r/w to the network share
I can access the network share from the said server.
But when I run the job it says the directory does not exist.
When i try to take a backup manually from ssms it says - cannot open backup device.
Is this some network issue ? If yes - can someone please point out where I need to check and what needs to be checked.
Thanks
September 12, 2024 at 9:18 am
Verify both the share permissions and the NTFS permissions, just because it has access to the share doesn't mean it has access to the actual disk.
Also then map the UNC path in windows explorer as the engine account, can the drive map itself?
September 12, 2024 at 9:37 am
Thanks for the response @Ant-Green
share permissions - the network share folder has r/w access permissions to the sql service account ?
And how do I check NTFS permissions..is it not ....what I mentioned above.
right click on folder..adding sqlservice account..full control
Also then map the UNC path in windows explorer as the engine account, can the drive map itself? - Yes I was able to map the network share on the server.
just because it has access to the share doesn't mean it has access to the actual disk - how do I check this ? access to the actual disk ??
September 12, 2024 at 9:44 am
RDP to the UNC server, find the folder, and verify the engine account has full control access to the folder.
September 12, 2024 at 10:10 am
Thanks for the response @Ant-Green
Also then map the UNC path in windows explorer as the engine account, can the drive map itself? - Yes I was able to map the network share on the server.
Which account did you use to map the drive? You're account or the Engine account?
If you tested it as you thats a false test.
Map it as the Engine using, use a different account or RDP to the SQL host as the engine service account and test it that way, but really you're service accounts shouldn't have interactive logon rights, so really you shouldn't be doing this.
September 12, 2024 at 10:18 am
I logged in with my credentials to the sqlserver and not the domain account which the engine is currently running under..
September 12, 2024 at 10:23 am
I logged in with my credentials to the sqlserver and not the domain account which the engine is currently running under..
That is a false test, you need to be testing it as the engine, not as yourself, while yes you are having issues, even if you was to ad-hoc a backup it's still the engine going to be writing the file, so test it as the engine, not as you.
September 12, 2024 at 10:35 am
I tried doing a manual backup(logged in as I) from the server to the network path and it failed...did not work even for me...
need to get hold of the service account credentials under which the engine is running...
September 12, 2024 at 4:33 pm
Another thought - are you running the backup with the UNC path and FQDN OR are you trying to backup to a drive letter?
Backup to a drive letter will likely fail as network drives are mapped at the user level and require login to map. UNC paths do not require login as they don't need to map to a letter.
The above is all just my opinion on what you should do.
As with all advice you find on a random internet forum - you shouldn't blindly follow it. Always test on a test server to see if there is negative side effects before making changes to live!
I recommend you NEVER run "random code" you found online on any system you care about UNLESS you understand and can verify the code OR you don't care if the code trashes your system.
Viewing 9 posts - 1 through 8 (of 8 total)
You must be logged in to reply to this topic. Login to reply