FileSync

What?

To synchronise your on-premises SQL Server database files with File Storage, you need a UNC path which has sufficient space to store backup files.

If you have more than one database backing up to the same UNC path, with the same database name (e.g. different instances), the Restore part of this tool will fail. It is recommended that you back up each instance to a separate UNC path.

Once you have compiled the assembly, you will have the following files:

• FileStorageSync.exe (Command-line executable that runs the sync)
• FileStorageSync.exe.config (Configuration file for the command-line executable)
• connections.config (Configuration file containing the Azure Storage Primary Access Key)
• RemoteStorageHelper.dll (Library with all the sync and restore methods)

The command-line executable relies on the FileStorageSync.exe.config file for its settings.

How?

Use Windows Task Scheduler to schedule the Sync tool to start a few minutes after your transaction log backups have completed.

For example, if your log backups take place every fifteen minutes, starting on the hour, you can set this tool to run every fifteen minutes, starting at five minutes past the hour.

When setting up the scheduled task, ensure the working directory is set correctly, and make sure that the user associated with the task has permission to read from the local SQL Server backup location.

Files will download from smallest to largest. A file is downloaded even if the local version exists, if the sizes do not match.