Install the Backup and DR Service agent on the database hosts.
Make sure the database permissions are set correctly.
SQL database discovery considerations
backup/recovery appliances support Microsoft SQL Server on Microsoft Windows
server.
Discovery relies on SQL VSS writer. For the discovery to work correctly, SQL
VSS writer must be installed and running on the host.
Appliances can manage Microsoft SQL Servers, SQL instances,
consistency groups of SQL Server databases, and SQL availability groups.
For a SQL failover appliance, the discovery needs to be run on
either the active node—or node IP—or appliance node—or
appliance IP. Otherwise, clustered databases aren't discovered.
Add the host
Add the host to the management console. If the host has already been added, then
edit the host and make sure to set all the configurations correctly.
Click Manage>Hosts, then click + Add Host.
On the Add Host page, complete the following:
Name: Provide the database server name.
IP Address: Provide the database server IP and click the
plus sign (+).
Appliances: Select the checkbox for the appliance.
Host Type: Make sure this is Generic.
Click Add at bottom right to add the host. The host is added.
Right-click the host and select Edit.
Leave the Staging Disk Format as Block.
Enter the username and password that you set up in
Application Discovery Credentials.
Select Save.
Discover SQL Server instances and databases
Use the following instructions to discover SQL Server instances and databases:
Select SQL Server on the Add Application page, then select the
SQL Server database host. If you have many hosts, you can use the
search feature or use the filter to see only hosts that are managed by
a specific backup/recovery appliance.
Select the host and click Next.
This runs the discovery on the SQL Server host and discovers all SQL Server
instances and databases running on it.
Find the discovered instances and databases in the App Manager
To find the newly-discovered database, go to the App Manager Applications
list. All applications known to the management console of all types are listed.
Use the Type application filter to show only SQL Server
database instances. The new SQL Server instances and databases appear in the
list as unmanaged—the shield icon.
The Backup and DR Microsoft SQL Server DBA guide
This page is one in a series of pages specific to protecting and recovering
Microsoft SQL Server databases with Backup and DR.
You can find additional information at:
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Hard to understand","hardToUnderstand","thumb-down"],["Incorrect information or sample code","incorrectInformationOrSampleCode","thumb-down"],["Missing the information/samples I need","missingTheInformationSamplesINeed","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-08-25 UTC."],[[["\u003cp\u003eBefore protecting SQL Server databases, ensure your network configuration and firewall ports are reviewed, install the Backup and DR Service agent on database hosts, and verify database permissions.\u003c/p\u003e\n"],["\u003cp\u003eSQL Server discovery requires the SQL VSS writer to be installed and running, and it can manage SQL Servers, instances, consistency groups, and availability groups.\u003c/p\u003e\n"],["\u003cp\u003eTo add a host, navigate to Manage > Hosts, click "+ Add Host," provide the database server details, select the appliance, set the host type to Generic, and then edit the host to configure the Staging Disk Format and application discovery credentials.\u003c/p\u003e\n"],["\u003cp\u003eDiscover SQL Server instances and databases by selecting SQL Server in the App Manager, choosing the relevant host, which will then discover all SQL instances and databases.\u003c/p\u003e\n"],["\u003cp\u003eNewly discovered SQL Server instances and databases will be listed as unmanaged in the App Manager Applications list, and can be filtered by the Type filter.\u003c/p\u003e\n"]]],[],null,["# Add a SQL Server database host and discover the database\n\nBefore you can protect SQL Server databases, complete the following:\n\n- Review your network configuration, including firewall ports. Pay close\n attention to our notes on how to [SQL database discovery considerations](#discover).\n\n- Install the Backup and DR Service agent on the database hosts.\n\n- Make sure the database permissions are set correctly.\n\nSQL database discovery considerations\n-------------------------------------\n\n- backup/recovery appliances support Microsoft SQL Server on Microsoft Windows\n server.\n\n- Discovery relies on SQL VSS writer. For the discovery to work correctly, SQL\n VSS writer must be installed and running on the host.\n\n- Appliances can manage Microsoft SQL Servers, SQL instances,\n consistency groups of SQL Server databases, and SQL availability groups.\n\n- For a SQL failover appliance, the discovery needs to be run on\n either the active node---or node IP---or appliance node---or\n appliance IP. Otherwise, clustered databases aren't discovered.\n\nAdd the host\n------------\n\nAdd the host to the management console. If the host has already been added, then\nedit the host and make sure to set all the configurations correctly.\n| **Note:** If you have added the Windows server to Backup and DR Service as a Compute Engine instance or as a VMware VM, then a host for this VM already exists and you don't need to add it again using the following procedure. Instead, find and edit that host.\n\n1. Click **Manage** \\\u003e **Hosts** , then click **+ Add Host**.\n\n2. On the **Add Host** page, complete the following:\n\n - **Name**: Provide the database server name.\n\n - **IP Address** : Provide the database server IP and click the\n **plus sign (+)**.\n\n - **Appliances**: Select the checkbox for the appliance.\n\n - **Host Type** : Make sure this is **Generic**.\n\n3. Click **Add** at bottom right to add the host. The host is added.\n\n4. Right-click the host and select **Edit**.\n\n5. Leave the **Staging Disk Format** as **Block**.\n\n6. Enter the username and password that you set up in\n **Application Discovery Credentials**.\n\n7. Select **Save**.\n\nDiscover SQL Server instances and databases\n-------------------------------------------\n\nUse the following instructions to discover SQL Server instances and databases:\n\n1. Click **App Manager** \\\u003e **Applications** , select\n **Add Application**.\n\n2. Select **SQL Server** on the **Add Application** page, then select the\n SQL Server database host. If you have many hosts, you can use the\n search feature or use the filter to see only hosts that are managed by\n a specific backup/recovery appliance.\n\n | **Note:** When adding SQL instances that participate in Microsoft Server Failover Clusters, either: \n | Run the wizard once for each node in the cluster, or else \n | Add all applications and multi-select all nodes at once. With this method, apply protection from the **Applications Listing** view by selecting **Manage Backup Plan** for the SQL instance.\n3. Select the host and click **Next**.\n This runs the discovery on the SQL Server host and discovers all SQL Server\n instances and databases running on it.\n\n | **Note:** Discovery on any one node adds other nodes of cluster as well. \n | To discover system DBs, run discovery on each node. System DBs can be protected as part of a SQL instance. \n | Availability Group databases can be protected as part of a SQL AG application. \n | You can take a backup image of a secondary by specifying the AG backup preference from application advanced settings. \n | Log truncation on the primary is managed by SQL Server, even when backing up db or logs on a secondary.\n\nFind the discovered instances and databases in the App Manager\n--------------------------------------------------------------\n\nTo find the newly-discovered database, go to the **App Manager Applications**\nlist. All applications known to the management console of all types are listed.\nUse the **Type** application filter to show only SQL Server\ndatabase instances. The new SQL Server instances and databases appear in the\nlist as unmanaged---the shield icon.\n\nThe Backup and DR Microsoft SQL Server DBA guide\n------------------------------------------------\n\nThis page is one in a series of pages specific to protecting and recovering\nMicrosoft SQL Server databases with Backup and DR.\nYou can find additional information at:\n\n- [Backup and DR for Microsoft SQL Server Databases](/backup-disaster-recovery/docs/concepts/backupdr-for-sql-server)\n- [Prepare SQL Server databases for Backup and DR Service](/backup-disaster-recovery/docs/configuration/prepare-sql-server)\n- [Add a SQL Server database host and discover databases](/backup-disaster-recovery/docs/configuration/discover-sql-server)\n- [Configure backup plans for Microsoft SQL Server instances and databases](/backup-disaster-recovery/docs/backup/back-up-sql-server)\n- [Application details and settings for Microsoft SQL Server instances and databases](/backup-disaster-recovery/docs/backup/app-details-settings-sql-server)\n- [Mount a SQL Server database](/backup-disaster-recovery/docs/access-data/mount-sql-server)\n- [Mount databases into SQL Always On Availability Groups](/backup-disaster-recovery/docs/access-data/mount-sql-server-aag)\n- [Manage an active mount](/backup-disaster-recovery/docs/access-data/manage-active-mounts)\n- [Migrate a SQL Server database](/backup-disaster-recovery/docs/access-data/mount-and-migrate-sql-server-2)\n- [Clone SQL Server databases](/backup-disaster-recovery/docs/access-data/clone-sql-server)\n- [Recover SQL Server backups](/backup-disaster-recovery/docs/restore-data/restore-sql-server)\n\nWhat's Next\n-----------\n\n[Configure backup plans for Microsoft SQL Server instances and databases](/backup-disaster-recovery/docs/backup/back-up-sql-server)"]]
