SQL Backup Master Blog

Some users of SQL Backup Master may encounter the following error when executing a database backup job (or testing one during the configuration process):

Job Execution Error: Cannot open backup device ‘<Path>’ Operating System error 3 (The system cannot find the path specified. BACKUP DATABASE is terminating abnormally).

The key to solving this problem is to first understand that SQL Server must be able to write database backup files directly to the temporary backup folder location specified in your backup job settings.

When SQL Server cannot access this temporary folder location, the database backup file cannot be created and the process fails with “Operating System error 3”. Now let’s look at possible underlying causes.

Possible Cause #1 – Permissions

Regardless of how you configure a backup job within SQL Backup Master, SQL Server itself runs within the security context of the account specified in the SQL Server system service configuration. To find out which account is being used click Start, click in the Start Search box, type services.msc, and then press ENTER.

Find your SQL Server instance in the services list and double-click it, then select the Log On tab.

It is this “log on” account that must have sufficient permissions to write to the temporary backup folder location. Check the permissions on the temporary backup folder by right-clicking it in Windows Explorer, selecting Properties, then navigating to the Security tab. Make sure that the account SQL Server is using has explicit read/write permissions for this folder.

Also, here’s a quick tip. If you’re uncertain as to whether folder permissions are at the root of your problem, just temporarily give “everyone” full permissions to it. If your backup job tests and executes successfully after doing so, you’ll have confirmed that permissions problem are the root issue and can narrow them down from there.

Possible Cause #2 – Mapped Drives

If you’re attempting to specify a backup folder location that resides on a remote (network ) file system, we strongly recommend that you do not use a mapped drive letter for this purpose. In Windows Vista and later, mapped drive letters are bound to the Windows security context that was used to create them, and SQL Server will usually not be able to access the mapping for this reason.

The solution to this problem is simple: use a fully qualified UNC path instead of a mapped drive letter. So, for example, instead of using “Z:\DBBackups” (where Z is the mapped drive letter), specify a fully qualified UNC path such as “\\remote-server\DBBackups”.

Possible Cause #3 – Lack of Domain Trust

If your SQL Server instance and your database backup folder are on computers in separate Active Directory domains, then a missing or expired trust between the domains may cause this problem – even if the file system permissions are configured appropriately.

You can resolve this issue by ensuring that a trust between the two domains is established. You may also need to configure the SQL Server service account with pass-through authentication between the domains.

Conclusion

When using SQL Backup Master, “Operating System Error 3” is an indication that SQL Server is unable to write to the temporary backup folder location specified in your backup job settings.

If you need further assistance with troubleshooting this problem, please don’t hesitate to open a support request with us. We’re happy to help.

Looking for a quick way to back up SQL to FTP? With SQL Backup Master, you can easily automate and schedule backups to standard FTP, FTPS (TLS/SSL), or SFTP servers. Follow the steps below to configure and run your backup job, ensuring your data is kept safe offsite.

Step 1 – Create a Backup Job

In the main SQL Backup Master window, select the Backup and Restore tab, then click the Create new database backup toolbar button. The Database Backup Editor window will appear.

Give your backup job a unique name (and optionally a description). This makes it easier to identify in the future.

Step 2 – Connect to SQL Server

In the Database Backup Editor window, click the Choose SQL Server button. This will open the Connect to SQL Server dialog box:

In the Server name field, enter or select the name of the SQL Server instance to which you’re connecting. Common examples include:

• (local)\SQLExpress – The default SQL Express named instance on the local computer.
• (local) – The local SQL Server installation without an instance name.
• Server1\SQLExpress – The default SQL Express named instance on a remote computer named “Server1.”
• Server1 – An unnamed SQL Server instance on a remote computer named “Server1.”

TIP: You can also use the drop-down arrow of the Server name field to discover local and remote SQL Server instances. When ready, click Test SQL Connection to verify connectivity, then hit OK.

Step 3 – Select Databases to Back Up

Once you’re connected, the Database Backup Editor window displays a list of databases. Check the boxes for the databases you want to include in this backup job.

If you enable the Back up all non-system databases option, any new database created on the target SQL Server in the future will be included in backups automatically.

Step 4 – Add an FTP Server Backup Destination

Under the Destinations heading in the Database Backup Editor, click the Add toolbar button. The Choose Destination window will appear. Double-click FTP Server to proceed.

The FTP Destination Settings window will open. Provide details about the FTP server you want to use (such as the server host address, username, and password). You can also configure advanced settings for FTPS, SFTP (via SSH), or specific proxy options like SOCKS4 or SOCKS5.

Click the Test button to ensure SQL Backup Master can connect and upload to your FTP server. Once configured, click OK to return to the Database Backup Editor window. Finally, select Save to store your new backup configuration.

Congratulations! You’ve successfully configured your first SQL Server database backup using SQL Backup Master and an FTP Server destination.

Step 5 – Run the Backup Job

Back in the main application window, locate your newly created backup job and click Back up now to begin the process. If the job does not complete successfully, check the log file for detailed error information.

That’s it! You are now backing up your SQL database to FTP. By automating backups with SQL Backup Master, you’ll have peace of mind knowing your critical data is protected offsite and readily available for recovery.

If you’re looking for additional backup destinations—such as Dropbox, OneDrive, or Amazon S3—be sure to explore the full feature set of SQL Backup Master by Key Metric Software.

Today we’re releasing SQL Backup Master v3.1. It offers a number of improvements and bug fixes, including important changes to Dropbox support.

Dropbox recently announced that “version 1” of their service API (application programming interface) is now deprecated, and will be shut down on June 28th, 2017. Since SQL Backup Master v3.0 and earlier make use of Dropbox API v1, those installations will no longer be able to interface with Dropbox after the announced shut down date.

For SQL Backup Master v3.1, we have updated Dropbox support to use their latest service APIs. For this reason, we encourage any SQL Backup Master users that rely on Dropbox integration to upgrade prior to June of 2017.

For more information on what’s new in SQL Backup Master v3.1, please see the full product release notes.

Key Metric Software is proud to announce the release of SQL Backup Master 3.

This new version contains many powerful new features, including:

– Support for SQL Server 2016
– Support for OneDrive as a backup destination
– Failed backup job retry (built into the scheduler)
– The ability to bypass database file compression
– New multi-core ZIP compression subsystem
– Improved (and more granular) notifications
– Extensive FTP/SFTP proxy support
– Numerous improvements to Amazon S3 support
– And much more

You can read more about the new SQL Backup Master release here:

https://www.sqlbackupmaster.com/features/whatsnew

Or download the new release now:

https://www.sqlbackupmaster.com/download

IMPORTANT: If you’re licensed for a previous version of SQL Backup Master and are interested in upgrading to this new release, you’ll need to upgrade your license before installing the new release. If you install the new version without upgrading your license first, it will revert to the features and functionality of the free version.