How to Backup SQL Server Database to Network Drive & Verify It?

Saving a copy to a network drive gives you a separate location for your SQL Server backups. Simply put, it makes them easier to access during the recovery process. You can backup SQL Server database to a network drive using native SQL Server tools such as SSMS or T-SQL, or just by using the SQL Server Backup tool.

However, network permissions, SQL Server service account access, and the difference between mapped drives and UNC paths can cause problems if you don’t configure the destination correctly.

Backup to Network Share Folder

If you need a Windows tool to automate backups across multiple SQL servers to store it into network drive, in this article you will learn about it too.

SQL Server to Network Drive Backup via Native Method vs Prapl

Functions	Native Method	Prapl SQL Backup Tool
Setup	Manual configuration	Windows application
Multiple databases	Configure individually	Unlimited Databases can be managed from one tool
Backup history	Limited or manual checking allowed	Unlimited backup history and status
Storage options	Network share	Local, NAS, and supported remote or cloud storage
Restore management	SQL Server tools	Built-in restore function workflow
Multiple database engines	Only SQL Server	Unlimited database engines are supported
Retention	Requires separate management	Built-in retention function

 

How to Backup SQL Server Database to a Network Drive Manually?

Create a shared folder. First, the destination machine needs a shared folder where SQL Server can write the backup. So, to do so, the SQL Server service account needs the appropriate permissions.

\\BackupServer\SQLBackups

Check access permissions to write the backup. Look for appropriate “Share permissions” and “NTFS/security permissions”

Important Note: Because malicious users sometimes attempt to elevate their privileges by using xp_cmdshell, xp_cmdshell is disabled by default. Use sp_configure to enable it in your SQL Server.

EXEC sp_configure 'show advanced options', 1;

GO

RECONFIGURE;

GO

EXEC sp_configure 'xp_cmdshell',1

GO

RECONFIGURE

GO

Now, you will need to define that shared drive for SQL with the xp_cmdshell command as follows:

EXEC XP_CMDSHELL 'net use H: \\RemoteServerName\ShareName'

By following this command, it should now be mapped. You can use SSMS again to browse the path and look for the new drive you just made.

Then, create a backup of the database using a T-SQL command.

BACKUP DATABASE [YourDatabase]

TO DISK = '\\BackupServer\SQLBackups\YourDatabase.bak'

WITH INIT,

COMPRESSION,

STATS = 10;

Once the SQL Server backup to the network drive is done, make sure to verify the .bak file on the network destination.

How to Take SQL Server Database Backup to a Network Drive Using a Tool?

If you need something simpler to back up SQL Server databases to a network drive without managing commands, Prapl SQL Backup Tool is another solution. It provides a centralized way to manage the process from a Windows application.

You can simply connect your SQL Server databases and choose a network or NAS destination, local machine, Amazon S3, or other supported destinations. Then, configure recurring backup schedules based on your requirements.

This tool supports full and incremental SQL Server backups and lets you set backup schedules, retention policies, and backups with compression and encryption. Most importantly, it writes backups directly to your selected storage rather than routing them through its hosted middle server.

Steps to Run the Backup Automatically

Initially, run the software on your PC and add your SQL Server instance to the software.

Now, select the database or multiple databases that you need to protect.

From the next screen, choose the network/NAS destination and configure the destination.

Finally, click the Save and Run Now button to start the backup and use the backup history/status information to confirm that the job completed successfully.

Common Problems When Backing Up SQL Server to a Network Drive

1. Access denied: If, while taking a SQL Server database backup on a network drive, access is denied, it might be happening because the SQL Server account lacks permission

Fix: Check both Share and NTFS permissions to write backups.

2. Drive not found: Secondly, in case the drive is not found during a backup job. It likely happens because the mapped drive is unavailable to the service

Fix: To fix this, make sure to use a UNC path.

3. Backup fails midway: If the backup fails midway, a network interruption might be the cause.

Fix: To run the backup again, check the network connectivity and destination.

4. Not enough space: When the network storage is full, the backup job stops in between

Fix: Therefore, make sure you have available storage in the network drive.

5. Slow backup: Sometimes, the network speed and storage performance affect the SQL Server to Network drive backup job. As a result, it takes more time than usual.

Fix: To fix this, check the network and destination performance before running the job.

Conclusion

If you want to backup SQL Server database to a network shared drive, make sure your network destination is accessible to the SQL Server service account. Though for a one-time backup, the native SQL Server method may be enough.

However, recurring backups require more attention to scheduling, storage, retention, and monitoring. If you’re managing multiple SQL Servers, Prapl SQL Backup Tool is a go-to solution. With this tool, you will be able to simplify this operation. It lets you schedule SQL Server backups, store them on network or NAS destinations, configure retention, and monitor backup history from one Windows application.