If using AlwaysOn configuration for SQL Server 2012
NMM supports the SQL Server 2012 feature AlwaysOn. AlwaysOn allows a database to have multiple replicas. There can be a maximum number of four secondary replicas. These replicas can be configured to be in either synchronous or asynchronous mode.
A database that is configured as AlwaysOn is treated by NMM as a normal database, and a backup of this database can be performed from the primary or secondary replica because the replicas are considered to be databases that are residing on separate instances. However, there are some restrictions on secondary replicas of the AlwaysOn database, and not all backup types are supported for secondary replicas.
To perform backup of secondary replicas, the Readable Secondary option of SQL Server 2012 AlwaysOn configuration must be set to “Yes.” Enable this option for both primary and secondary replicas, because during the backup process, secondary replicas may become primary and vice versa.
SQL Server 2012 has also introduced the new functionality Availability Group with AlwaysOn. Availability Group is a logical group of databases that have the AlwaysOn capability. The Availability Group is failed over to other nodes as a group, that is, all the databases which are part of the Availability group are failed over during the failure or manual failover.
The Microsoft website describes the AlwaysOn Availability Group functionality in SQL Server 2012, and provides detailed information about how to configure your setup to utilize this support.
If your setup contains an SQL Server with AlwaysOn configuration, then before recovery you must perform certain additional steps. You can either use the SQL Server Management Studio GUI or the query window.
To perform the steps from the SQL Server Management Studio GUI:
Open the SQL Server Management Studio and remove the content database from Availability Group. Right-click the content database and select Remove Database from Availability Group.
Perform recovery.
After recovery is successful, go to the SQL Server Management Studio and add the content database back to Availability Group:
Right-click the Availability databases and select the Add Database to Availability Group option.
In the Add Database to Availability Group dialog box:
In the Select Databases page that appears, select WSS_Content_AO_webApp1 and click Next.
In the Select Initial Data Synchronization page that appears, select the Full option and specify the synchronization location, and click Next.
The synchronization may fail with an error, in case a secondary replica copy with same name exists.
Delete the secondary replica copy that is in restoring mode.
Rerun the validation.
The content database is added back to Availability Group.
Return to the NMM GUI and click Continue in the dependency dialog box. Continue with the remaining steps.
To perform the steps from the SQL Server Management Studio GUI:
On the primary replica server, use the following command:
ALTER AVAILABILITY GROUP [Group9] REMOVE DATABASE [Weekly_test_weekly_data_backup_db9]
On the secondary replica server, delete the AlwaysOn database, which is in restoring state.
实际上不管是在active节点或者可以readonly的节点应该都是可以执行的
还有一篇这个的help
In the Save Set attribute, specify the components to be backed up:
AlwaysOn Group referring SQL default instance — MSSQL#AG1
AlwaysOn Group referring SQL default instance — MSSQL#AG1:Database1
AlwaysOn Group referring SQL named instance — MSSQL$NamedInstance#AG2
AlwaysOn Group referring SQL named instance — MSSQL$NamedInstance#AG2:Database2
但是 我不管是在命令行或者saveset 都出错。
在客户端networker for MSSQL Module 打开准备选择备份数据库时发现,在always on环境中的recover model 为 simple 和 在always on的recover module为 full的数据库就不能被选中。是客户端软件的问题么
Fenglin1
6 Operator
•
2074 帖子
2621
0
已发布 August 24th, 2015 01:00
这篇KB里面的方法试试看
https://support.emc.com/kb/199614