You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/database-engine/availability-groups/windows/perform-a-forced-manual-failover-of-an-availability-group-sql-server.md
+5-6Lines changed: 5 additions & 6 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -172,13 +172,13 @@ ms.author: mathoma
172
172
```
173
173
174
174
> [!NOTE]
175
-
> To view the syntax of a cmdlet, use the **Get-Help** cmdlet in the [!INCLUDE[ssNoVersion](../../../includes/ssnoversion-md.md)] PowerShell environment. For more information, see [Get Help SQL Server PowerShell](../../../relational-databases/scripting/get-help-sql-server-powershell.md).
175
+
> To view the syntax of a cmdlet, use the **Get-Help** cmdlet in the [!INCLUDE[ssNoVersion](../../../includes/ssnoversion-md.md)] PowerShell environment. For more information, see [Get Help SQL Server PowerShell](../../../powershell/sql-server-powershell.md).
176
176
177
177
3. After forcing an availability group to fail over, complete the necessary follow-up steps. For more information, see [Follow Up: Essential Tasks After a Forced Failover](#FollowUp), later in this topic.
178
178
179
179
**To set up and use the SQL Server PowerShell provider**
180
180
181
-
- [SQL Server PowerShell Provider](../../../relational-databases/scripting/sql-server-powershell-provider.md)
181
+
- [SQL Server PowerShell Provider](../../../powershell/sql-server-powershell-provider.md)
182
182
183
183
## <a name="FollowUp"></a> Follow Up: Essential Tasks After a Forced Failover
184
184
@@ -312,13 +312,13 @@ ms.author: mathoma
312
312
313
313
- **Blogs:**
314
314
315
-
[SQL Server Always On Team Blogs: The official SQL Server Always On Team Blog](https://blogs.msdn.microsoft.com/sqlalwayson/)
315
+
[SQL Server Always On Team Blogs: The official SQL Server Always On Team Blog](/archive/blogs/sqlalwayson/)
316
316
317
-
[CSS SQL Server Engineers Blogs](https://docs.microsoft.com/archive/blogs/psssql/)
317
+
[CSS SQL Server Engineers Blogs](/archive/blogs/psssql/)
318
318
319
319
- **Whitepapers:**
320
320
321
-
[Microsoft SQL Server Always On Solutions Guide for High Availability and Disaster Recovery](https://go.microsoft.com/fwlink/?LinkId=227600)
321
+
[Microsoft SQL Server Always On Solutions Guide for High Availability and Disaster Recovery](/previous-versions/sql/sql-server-2012/hh781257(v=msdn.10))
322
322
323
323
[Microsoft White Papers for SQL Server 2012](https://social.technet.microsoft.com/wiki/contents/articles/13146.white-paper-gallery-for-sql-server.aspx#[Category]SQLServer2012)
324
324
@@ -332,4 +332,3 @@ ms.author: mathoma
332
332
[Monitoring of Availability Groups (SQL Server)](../../../database-engine/availability-groups/windows/monitoring-of-availability-groups-sql-server.md)
333
333
[Windows Server Failover Clustering (WSFC) with SQL Server](../../../sql-server/failover-clusters/windows/windows-server-failover-clustering-wsfc-with-sql-server.md)
Copy file name to clipboardExpand all lines: docs/database-engine/availability-groups/windows/perform-a-planned-manual-failover-of-an-availability-group-sql-server.md
+3-4Lines changed: 3 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -89,7 +89,7 @@ A planned manual failover is supported only when the primary replica and the tar
89
89
2. Use the **Switch-SqlAvailabilityGroup** cmdlet.
90
90
91
91
> [!NOTE]
92
-
> To view the syntax of a cmdlet, use the **Get-Help** cmdlet in the [!INCLUDE[ssCurrent](../../../includes/sscurrent-md.md)] PowerShell environment. For more information, see [Get help for SQL Server PowerShell](../../../relational-databases/scripting/get-help-sql-server-powershell.md).
92
+
> To view the syntax of a cmdlet, use the **Get-Help** cmdlet in the [!INCLUDE[ssCurrent](../../../includes/sscurrent-md.md)] PowerShell environment. For more information, see [Get help for SQL Server PowerShell](../../../powershell/sql-server-powershell.md).
93
93
94
94
The following example manually fails over the *MyAg* availability group to the secondary replica with the specified path:
95
95
@@ -99,8 +99,8 @@ A planned manual failover is supported only when the primary replica and the tar
99
99
100
100
To set up and use the SQL Server PowerShell provider:
101
101
102
-
- [SQL Server PowerShell provider](../../../relational-databases/scripting/sql-server-powershell-provider.md)
103
-
- [Get help for SQL Server PowerShell](../../../relational-databases/scripting/get-help-sql-server-powershell.md)
102
+
- [SQL Server PowerShell provider](../../../powershell/sql-server-powershell-provider.md)
103
+
- [Get help for SQL Server PowerShell](../../../powershell/sql-server-powershell.md)
104
104
105
105
## <a name="FollowUp"></a> Follow up: After you manually fail over an availability group
106
106
If you failed over outside the [!INCLUDE[ssFosAuto](../../../includes/ssfosauto-md.md)] of the availability group, adjust the quorum votes of the Windows Server failover clustering nodes to reflect your new availability group configuration. For more information, see [Windows Server failover clustering (WSFC) with SQL Server](../../../sql-server/failover-clusters/windows/windows-server-failover-clustering-wsfc-with-sql-server.md).
@@ -117,4 +117,3 @@ A planned manual failover is supported only when the primary replica and the tar
117
117
* [Failover and failover modes (AlwaysOn availability groups)](../../../database-engine/availability-groups/windows/failover-and-failover-modes-always-on-availability-groups.md)
118
118
* [Perform a forced manual failover of an availability group (SQL Server)](../../../database-engine/availability-groups/windows/perform-a-forced-manual-failover-of-an-availability-group-sql-server.md)
Copy file name to clipboardExpand all lines: docs/database-engine/availability-groups/windows/prereqs-migrating-log-shipping-to-always-on-availability-groups.md
+6-7Lines changed: 6 additions & 7 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -53,7 +53,7 @@ ms.author: mathoma
53
53
54
54
**For more information:**
55
55
56
-
[Converting a log shipping configuration to Availability Group](https://blogs.msdn.microsoft.com/sqlalwayson/2012/01/09/converting-a-logshipping-configuration-to-availability-group/) (a SQL Server blog)
56
+
[Converting a log shipping configuration to Availability Group](/archive/blogs/sqlalwayson/converting-a-logshipping-configuration-to-availability-group) (a SQL Server blog)
57
57
58
58
## <aname="RelatedTasks"></a> Related Tasks
59
59
**Log shipping**
@@ -80,17 +80,17 @@ ms.author: mathoma
80
80
81
81
-**Blogs:**
82
82
83
-
[Converting a logshipping configuration to Availability Group](https://blogs.msdn.microsoft.com/sqlalwayson/2012/01/09/converting-a-logshipping-configuration-to-availability-group/)
83
+
[Converting a logshipping configuration to Availability Group](/archive/blogs/sqlalwayson/converting-a-logshipping-configuration-to-availability-group)
84
84
85
-
[Add a Log Shipping Primary Database and Secondary Database(s) to an Existing Availability Group](https://blogs.msdn.microsoft.com/sqlalwayson/2012/02/01/add-a-log-shipping-primary-database-and-secondary-databases-to-an-existing-availability-group/)
85
+
[Add a Log Shipping Primary Database and Secondary Database(s) to an Existing Availability Group](/archive/blogs/sqlalwayson/add-a-log-shipping-primary-database-and-secondary-databases-to-an-existing-availability-group)
86
86
87
-
[SQL Server Always On Team Blogs: The official SQL Server Always On Team Blog](https://blogs.msdn.microsoft.com/sqlalwayson/)
87
+
[SQL Server Always On Team Blogs: The official SQL Server Always On Team Blog](/archive/blogs/sqlalwayson/)
88
88
89
-
[CSS SQL Server Engineers Blogs](https://docs.microsoft.com/archive/blogs/psssql/)
89
+
[CSS SQL Server Engineers Blogs](/archive/blogs/psssql/)
90
90
91
91
-**Whitepapers:**
92
92
93
-
[Migration Guide: Migrating to Always On Availability Groups from Prior Deployments Combining Database Mirroring and Log Shipping](https://msdn.microsoft.com/library/jj635217)
93
+
[Migration Guide: Migrating to Always On Availability Groups from Prior Deployments Combining Database Mirroring and Log Shipping](/previous-versions/sql/sql-server-2012/jj635217(v=msdn.10))
94
94
95
95
[Microsoft White Papers for SQL Server 2012](https://social.technet.microsoft.com/wiki/contents/articles/13146.white-paper-gallery-for-sql-server.aspx#[Category]SQLServer2012)
96
96
@@ -101,4 +101,3 @@ ms.author: mathoma
101
101
[Overview of Always On Availability Groups (SQL Server)](../../../database-engine/availability-groups/windows/overview-of-always-on-availability-groups-sql-server.md)
102
102
[Monitoring of Availability Groups (SQL Server)](../../../database-engine/availability-groups/windows/monitoring-of-availability-groups-sql-server.md)
0 commit comments