Mount databases into SQL AlwaysOn Availability Groups
Disable comment:
Mount to a SQL Server AAG using a snapshot pool
This approach is the fastest way to create a new SQL Server AlwaysOnAvailability group for short-term use. The mounted application runs inthe snapshot pool, and achieves the same performance as data captured in thesnapshot pool.
Note: Be sure there is enough space in the snapshot pool for the availability group and regular snapshots.Mount the databases being added to the SQL availability group to each nodein the AG, one node at a time. SeeMount a SQL Server database.
Select the required host.
Select the SQL instance.
Specify the roll-forward time, being sure to specify the same time duringmounts to each node.
UnderAdvanced Options, deselectRecover Database After Restore.
Enter a name, or a prefix or suffix. Use the same name, prefix, orsuffix on all nodes.
Repeat the process for each availability group member.
Once all databases are mounted as virtual databases on each availabilitygroup node, using SQL, select the SQL instance that is the primary and foreach database recover it:
`recoverdatabase(name)withrecovery`Keep the secondary database copies in restoring state.
When the master database has been restored, using SQL, create the newavailability group and join the primary and secondary databases as describedinAdd virtual databases to a new SQL Server AlwaysOn Availability group.
Clone to a SQL Server availability group independently from the snapshot pool
To clone to a SQL AlwaysOn Availability group that resides independently fromthe snapshot pool, perform a clone operation for the databases on each node inthe SQL AlwaysOn Availability group as described inClone SQL Server databases.Be sure to deselectRecover database after restore and to specify the sameroll-forward time for each clone operation.
Add virtual databases to a new SQL Server AlwaysOn Availability group
After all databases for the new AG have been recovered, use SQL Studio or T-SQLto add the databases to the SQL AlwaysOn Availability group:
From SQL Studio, select the SQL availability group.
Add the databases to the availability group.
ClickNext. You are prompted to select a synchronization method.SelectJoin only; theJoin only operation forms the primary andsecondary databases into an availability group.
Monitor the progress of the operation. When the operation is complete,both the primary and secondary databases are in sync.
If autodiscover applications is not enabled, manually discoverapplications on the availability group host.
After discovery is complete, the databases appear in theApp Manager asmembers of the SQL availability group.
Capture members of an availability group just like any other database.
The Backup and DR Microsoft SQL Server DBA guide
This page is one in a series of pages specific to protecting and recoveringMicrosoft SQL Server databases with Backup and DR.You can find additional information at:
- Backup and DR for Microsoft SQL Server Databases
- Prepare SQL Server databases for Backup and DR Service
- Add a SQL Server database host and discover databases
- Configure backup plans for Microsoft SQL Server instances and databases
- Application details and settings for Microsoft SQL Server instances and databases
- Mount a SQL Server database
- Mount databases into SQL Always On Availability Groups
- Manage an active mount
- Migrate a SQL Server database
- Clone SQL Server databases
- Recover SQL Server backups
Except as otherwise noted, the content of this page is licensed under theCreative Commons Attribution 4.0 License, and code samples are licensed under theApache 2.0 License. For details, see theGoogle Developers Site Policies. Java is a registered trademark of Oracle and/or its affiliates.
Last updated 2026-02-19 UTC.