Take the 2-minute tour ×
Server Fault is a question and answer site for professional system and network administrators. It's 100% free, no registration required.

My SQL Server 2008 R2 has a mapped network drive (called Y:/) which reconnects after a reboot (I just checked this).

When I try to backup a Database (TASKS -> BACKUP). The network drive Y: is not listed as a possible destination. When I try to define the Backup TO: Disk destination location.

Can someone suggest why this is? What other solutions might I have?

share|improve this question

2 Answers 2

up vote 7 down vote accepted

You should use a UNC to the directory to which you want to backup. ex: \\servername\share

Since mapped drives are only created on an interactive logon, if you schedule a backup to a mapped drive, the service account will not have access to it and fail. I can only presume this is why Microsoft excludes them from this dialog.

share|improve this answer
    
A very common problem with server processes and networked drives, permissions. Comes up more often when people are trying to setup FTP servers to some NAS, same issue though. –  Orbling Apr 7 '11 at 1:42
    
AHHH - good point. What about iSCSI? –  Pure.Krome Apr 7 '11 at 2:18
    
backups work great using the UNC path - I've had it running like a champ in the past. It's a PITA to get it working, but it does work. –  tsykoduk Apr 7 '11 at 6:37
    
iSCSI LUNs (aka drive letters) do not depend on interactive logons and are available when the system is booted, before anyone logs in. –  jftuga Apr 7 '11 at 14:30
    
am getting "Object reference not set to an instance of an object. (Microsoft.SqlServer.Management.Sdk.Sfc)" error when I try the UNC path. What am i supposed to do to rectify this. The computers are not on a domain. –  bogonko Aug 24 '12 at 9:08

You SHOULD use UNC path when possible, but if you need to authenticate with different credentials (You still don't need to assign a drive letter though) or maybe use some third party network share that does not use UNC paths, you can use xp_cmdshell to issue NET USE commands or whatever the third party share uses. Then the share will be available to the SQL Server process.

Be aware that xp_cmdshell is commonly frowned upon in security audits and the like.

share|improve this answer

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.