Error when attempting to back up SQL database to another server on network

  • When trying to back up a SQL database (running on Windows Server 2003) to a hard disk on another server on the network, I receive the following error message:

    Microsoft SQL-DMO (ODBC SQLState:42000) cannot open backup device "pathname" Device error or device offline. See the server error log for more details.

    Can anyone assist on this?

  • You need to map the drive on other server to your server.

  • I am trying to back it up to a network share on the other server.  What will the mapping have to point to to do this?

  • Post the SQL command you are using to backup your database.  It will help in debugging the error.  Also, be sure that the user that SQL Server runs under has sufficient rights to right to the network share.

     

  • I am attempting to back up a SQL database through Enterprise Manager.  In the tree, I right click on the database, choose All Tasks, then choose Backup Database.  In that window, for my destination, I add to my destination set \\servername\sharename.  When I execute is when I get the error.  How can I get the database backed up to that share?  The user has permission to the destination.

  • What exactly are you entering in the destination, and how are you entering it?

  • The destination is a hidden share on another server.  I am entering the destination as \\servername\sharename$.

  • And what about the filename for the backup file?  What is it?

  • DEB backup

  • http://msdn2.microsoft.com/en-us/library/ms179313.aspx

    Does it help?

  • Your destination should look something like this:

    \\servername\sharename$\dbbackupfile.bak

    If you have a space in the file name, you may also need to surround the entire destination string in double quotes.  Personally, I don't like spaces in filenames.

     

  • Will that solution work with SQL 2000 server?  That is what I am running.

  • It should.  However, I would recommend that you backup to a local drive and then copy the backup file to the network share and then if needed delte the local copy after a successful copy is completed.  That way, it there is a network failure while copying the file to the network share, you just restart the copy, and the actual backup isn't affected.

  • It works for both 2000/2005. However, it is not recommended to have this kind of backup. There are two main reasons:

    1. Lower speed, in general;

    2. Less reliable, in general;

Viewing 14 posts - 1 through 14 (of 14 total)

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