Backup Error 605: No files could be created.

Compresses, encrypts, secures and monitors SQL Server backups.

Moderators: JonathanWatts, Chris Auckland, eddie davis, Colin Millerchip, Brian Harris, james.billings, RBA, petey

Backup Error 605: No files could be created.

Postby SQL_ME_RICH » Mon Apr 07, 2014 6:58 pm

Hello -

Working with a 14 day evaluation edition of SQL Backup 7.6. Was able to backup my database fine locally, but I am getting the following error when attempting to backup to a mapped drive (which is out on my SAN and a more realistic place for me to gauge speed against). Also - The path "H:\\Backups" does exist - it is my home directory and I have full control over it. The folder "Backups" also exists so I am a bit thrown by what the error below is trying to say by "Failed to create output folder". I specify it in the dialog box as I am building the backup sequence (not via T-SQL but the GUI).

Any thoughts on if this is a restriction of the eval version or if something else is amiss here, would be most helpful. Again - I have full control to the H drive, can created edit and delete anything I put out there.

Thank you and here is the error from the dialog in SQL Backup upon failure...

"MYSERVER": Backup - Failed
=============================

Performing full backups - Failed
--------------------------------

This operation failed with errors.

Backing up MYSERVER (full database) to:
H:\\Backups\\FULL_(local)_MYSERVER_20140407_104657.sqb
Warning 200:
4/7/2014 10:46:57 AM: Warning 480: Failed to create output folder: H:\\Backups\\.
4/7/2014 10:47:27 AM: Warning 480: Failed to create output folder: H:\\Backups\\.
4/7/2014 10:47:57 AM: Warning 480: Failed to create output folder: H:\\Backups\\.
4/7/2014 10:48:27 AM: Warning 480: Failed to create output folder: H:\\Backups\\.
4/7/2014 10:48:57 AM: Warning 480: Failed to create output folder: H:\\Backups\\.
4/7/2014 10:49:27 AM: Warning 480: Failed to create output folder: H:\\Backups\\.
4/7/2014 10:49:57 AM: Warning 480: Failed to create output folder: H:\\Backups\\.
4/7/2014 10:50:27 AM: Warning 480: Failed to create output folder: H:\\Backups\\.
4/7/2014 10:50:57 AM: Warning 480: Failed to create output folder: H:\\Backups\\.
4/7/2014 10:51:27 AM: Warning 480: Failed to create output folder: H:\\Backups\\.
4/7/2014 10:51:57 AM: Warning 480: Failed to create output folder: H:\\Backups\\.
Warning 480: Failed to create output folder: H:\\Backups\\.
Warning 605:
Error 605: Error creating backup file(s). No files could be created.
SQL Backup exit code: 605



Updating SQL Server information - Successful
--------------------------------------------

This operation completed successfully.
SQL_ME_RICH
 
Posts: 64
Joined: Tue May 08, 2012 10:41 pm

Postby SQL_ME_RICH » Mon Apr 07, 2014 7:06 pm

Nevermind - looks like a UNC is what is needed to get this to work. Question though - I thought you guys addressed being able to back up to mapped drives in a earlier release? Is that not the case? Do you really have to specify a UNC to anything other than the C:DRIVE of a system that has SQL Backup installed?
SQL_ME_RICH
 
Posts: 64
Joined: Tue May 08, 2012 10:41 pm

Postby eddie davis » Wed Apr 09, 2014 9:48 am

Hi SQL_ME_RICH,

Thank you for your forum post.

As you have discovered SQL Backup does not support mapped drives and never will do. I believe it is a Windows limitation, when an account logs in as a service it behaves differently from when the account is used to log in as normal Windows user. One of the limitations is the support of mapped drives.

SQL Backup will support the path to a physically connected disk or UNC path to a network share.

Many Thanks
Eddie
Eddie Davis
Technical Support Engineer
Red Gate Software Ltd
E-mail: support@red-gate.com
eddie davis
 
Posts: 943
Joined: Wed Jun 14, 2006 3:47 pm
Location: Red Gate Software


Return to SQL Backup 7

Who is online

Users browsing this forum: No registered users and 2 guests