Post reply

Backup to another server issue

  • September 25, 2008 at 2:04 pm

    #382837

    I have a Maintenance plans that backs up the databases on a SQL Server 2005 server to a drive on the same server.

    I want to change the plans to save the backups to another network server and I have an error.

    The SQL Server Agent service is using a domain account.

    This account belongs to the local admin group on the other server and also has full rights to the folder it will be saving the backups to. I can map a drive to the other server using this domain account and copy files to the folder.

    Here is the error I get:

    Executing the query "EXECUTE master.dbo.xp_create_subdir N'\\\\backup3\\backups\\Cognos\\SQLServer_Backups_Dev\\System\\master'

    " failed with the following error: "xp_create_subdir() returned error 183, 'Cannot create a file when that file already exists.'". Possible failure reasons: Problems with the query, "ResultSet" property not set correctly, parameters not set correctly, or connection not established correctly.

    Any help would be appreciated.

    Terry

  • September 26, 2008 at 2:18 pm

    #877957

    Hi Terry,

    I don't know of anyway to do a direct MSSQL backup to a shared or mapped drive or to a UNC.

    You have to do the backup to a local (DASD, SAN, etc) and then move the backup file using Windows.

    The Red Gate or Idera tools may be able to do this.

    Good luck.

  • September 26, 2008 at 2:50 pm

    #877973

    You've got incorrect pathing, and the error is you're creating a folder that exists. There isn't error checking here on this, as the maintenance plans are very basic.

    You don't want to back up remotely. The backup process throws pages out as quickly as possible and if you have any network hiccup, they'll fail.

  • September 27, 2008 at 9:44 pm

    #878125

    1.check the backup location & create folders manually.

    2.check weather file exists in backup location / delete or rename it.

    3.give different file name.

  • September 28, 2008 at 7:39 am

    #878159

    I had to change the SQl Server service to use the domain account instead of local. I already had the SQL Server Agent service changed to use the dommain account, but it turns out I needed both services changed.

  • September 28, 2008 at 7:58 am

    #878169

    Thanks for the update.

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

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