Results 1 to 4 of 4
  1. #1
    Join Date
    Sep 2002
    Chattanooga, TN

    Unhappy Unanswered: backup across network

    SQL Server newbie question ~ how can I backup a database to a directory in mounted network drive. when I attempt, the server tells me the drive/device is inaccessible. but from the command line, no problem accessing the directory. i have done research on the web and MSN site -- and the info states that it may have to do with permissions. if I can see the drive from command line -- can SQL Server "NOT" see it also? please let me know where I'm falling off the brain wagon....tia

  2. #2
    Join Date
    Jul 2002
    Maybe I'm missing the point, but I've been told not to specify logical drive letters (like D, rather to use server names, for instance \\server\ etc.

  3. #3
    Join Date
    Aug 2004
    Before a couple of days I have to solve the same problem by massive google search on the web
    The problem is that the account on which the SQL server runs hasn't got privileges to see the network. By default, when installed SQL server is executing under system account 'LocalSystem' which hasn't got rights to view the network. Even if you try to backup the database from Enterprise Manager and select a file the dialog just shows local hard drives without network.
    So to make backup accross network the user that SQL Server runs onto has to be changed to someone who has the rights for seeing network - fixed user 'Administrator' or any account that access the computer with administrator rights. In Enterprise Manager right-click on SQL server and select properties from the context menu. In the Properties window go to Security tab page, and select radio button 'This account' at the bottom of the window. Next to the radio button appear textboxes for user name and password where name and password of user who can see the network is entered.
    Also when specifying the path in 'backup database' command use the notation '//server_name/shared_directory/file_name'. Directory where the backup will be made have to be shared on the network and the computer where SQL server runs have to be able to access it (sharing to 'Everyone' group will do this).

  4. #4
    Join Date
    Apr 2004
    Kansas City, MO

    You might be better off using \\servername\directory\filename. Just an fyi.

    01010111011010000111100100100000011000010111001001 10010100100000011101000110100001100101011100110110 01010010000001110000011001010110111101110000011011 00011001010010000001110011011011110010000001110011 011101000111010101110000011010010110010000111111
    When life gives you a lemon, fire the DBA.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts