You are here: Microsoft SQL Protection > Requirements for protecting SQL > Requirements for SQL databases located on SMB 3.0 shares

Requirements for SQL databases located on SMB 3.0 shares

SQL Server 2012 and higher can host SQL instances with disk storage located on SMB 3.0 shares. For details, see the following topics:

ClosedPrerequisites and considerations for protecting SQL databases located on SMB 3.0 shares
• The Unitrends appliance software and Windows agent must be release 8.1 or higher.
• The File Server and the File Server VSS Agent Service roles must be installed on the server hosting the shares. For instructions on installing these roles, see KB 1334.
• The Windows agent installed on the SQL Server must be granted read/write access to remote SMB 3.0 shares. For instructions on granting this access, see Granting the Windows agent read/write access to remote SMB 3.0 shares.
• The SQL Server hosting the databases and the server hosting the SMB shares must belong to the same Windows domain.
• The database can contain one or more files located on SMB 3.0 shares. All files can reside on the same SMB 3.0 share or on different shares hosted by one or more servers in the same domain. All servers participating in the database backup must belong to the same domain.
• For files located on remote SMB 3.0 shares, the Windows agent creates a VSS snapshot on the remote server and then exposes it to the SQL Server through the SMB share pathing. The agent then backs up the database files from the remote snapshot location. When the backup completes, all VSS snapshots created for the backup are removed from the server hosting the SMB share.
ClosedGranting the Windows agent read/write access to remote SMB 3.0 shares

The Windows agent installed on the SQL Server must be granted read/write access to remote SMB 3.0 shares. You can grant this access using one of the following methods:

• On the SQL Server, change the login account for the Unitrends Windows agent service "bpagent" to the domain administrator account. Using these credentials provides all necessary access to the SMB shares. This is the most secure option for SMB access. Note, however, that file-level backups of the SQL Server may encounter files whose permissions do not allow domain administrator access. If successful file-level backups for the SQL Server cannot be created and SMB share security is less of an issue, then the method below is recommended.
• Run the agent as local system account on the SQL Server and grant it read/write permission for the SMB shares. For instructions, see KB 1335.

Once you have satisfied the SMB 3.0 prerequisites and have granted the Windows agent access to the SMB 3.0 shares, run backups and restores using these procedures: Executing SQL backups and Restoring SQL backups.