| Author | Chrissy LeMaire (@cl), netnerds.net |
| Availability | Windows, Linux, macOS |
Want to see the source code for this command? Check out Suspend-DbaAgDbDataMovement on GitHub.
Want to see the Bill Of Health for this command? Check out Suspend-DbaAgDbDataMovement.
Suspends data synchronization for availability group databases to halt replication between replicas.
Temporarily halts data movement between primary and secondary replicas for specified availability group databases. This stops transaction log records from being sent to secondary replicas, which is useful during maintenance windows, troubleshooting synchronization issues, or when preparing for manual failovers. While suspended, the secondary databases will fall behind the primary and cannot be failed over to until data movement is resumed.
Suspend-DbaAgDbDataMovement
[[-SqlInstance] <DbaInstanceParameter[]>]
[[-SqlCredential] <PSCredential>]
[[-AvailabilityGroup] <String>]
[[-Database] <String[]>]
[[-InputObject] <AvailabilityDatabase[]>]
[-EnableException]
[-WhatIf]
[-Confirm]
[<CommonParameters>]
PS C:\> Suspend-DbaAgDbDataMovement -SqlInstance sql2017a -AvailabilityGroup ag1 -Database db1, db2
Suspends data movement on db1 and db2 to ag1 on sql2017a. Prompts for confirmation.
PS C:\> Get-DbaAgDatabase -SqlInstance sql2017a, sql2019 | Out-GridView -Passthru | Suspend-DbaAgDbDataMovement -Confirm:$false
Suspends data movement on the selected availability group databases. Does not prompt for confirmation.
The target SQL Server instance or instances. Server version must be SQL Server version 2012 or higher.
| Alias | |
| Required | False |
| Pipeline | false |
| Default Value |
Login to the target instance using alternative credentials. Accepts PowerShell credentials (Get-Credential).
Windows Authentication, SQL Server Authentication, Active Directory - Password, and Active Directory - Integrated are all supported.
For MFA support, please use Connect-DbaInstance.
| Alias | |
| Required | False |
| Pipeline | false |
| Default Value |
Specifies the availability group containing the databases to suspend. Required when using SqlInstance parameter.
Use this to target databases within a specific AG when multiple availability groups exist on the instance.
| Alias | |
| Required | False |
| Pipeline | false |
| Default Value |
Specifies which availability group databases to suspend data movement for. Accepts multiple database names.
Use this when you need to halt synchronization for specific databases while leaving other AG databases running normally.
| Alias | |
| Required | False |
| Pipeline | false |
| Default Value |
Accepts availability group database objects piped from Get-DbaAgDatabase or other dbatools AG commands.
Use this for pipeline operations when you want to filter and select specific AG databases before suspending data movement.
| Alias | |
| Required | False |
| Pipeline | true (ByValue) |
| Default Value |
By default, when something goes wrong we try to catch it, interpret it and give you a friendly warning message.
This avoids overwhelming you with "sea of red" exceptions, but is inconvenient because it basically disables advanced scripting.
Using this switch turns this "nice by default" feature off and enables you to catch exceptions with your own try/catch.
| Alias | |
| Required | False |
| Pipeline | false |
| Default Value | False |
Shows what would happen if the command were to run. No actions are actually performed.
| Alias | wi |
| Required | False |
| Pipeline | false |
| Default Value |
Prompts you for confirmation before executing any changing operations within the command.
| Alias | cf |
| Required | False |
| Pipeline | false |
| Default Value |