This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(262.40000000000003, 2%, 35%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EJP%3C/text%3E%3C/svg%3E)
We have SCOM 2019 using SQL 2017 in a multi subnet cluster. We are trying to design a BCP/ DR steps to manually failover the operationsDB cluster.
We want this to use PowerShell and have it as a script if possible.
The script would need to write the event to the event log and move the cluster over to the other site.
I have been looking online for references and possible scripts to do this, I have been reviewing the links below. to come up with such actions.
Any help on pointing me to an existing script, providing code logic, etc. would be appreciated, I assume other admins have done this for their environments thus why I am asking about how to script this process to work with little user action for BCP/DR actions.
https://learn.microsoft.com/en-us/sql/database-engine/availability-groups/windows/perform-a-forced-manual-failover-of-an-availability-group-sql-server?view=sql-server-ver15
http://lifeofageekadmin.com/using-powershell-move-cluster-resources-preferred-node/
http://lifeofageekadmin.com/using-powershell-failover-cluster-resources-patching/
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(208, 69%, 30%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ESG%3C/text%3E%3C/svg%3E)
Please note that moving an Availability Group via any commands that would implement a cluster API call to move a group is NOT SUPPORTED. This includes but is not limited to WMI execution methods, cluster api calls, cluster utilities such as Failover Cluster Manager, PowerShell, etc. The only supported way is to use TSQL or the accompanied SQL Server module specific PowerShell commands.
It can and will cause you issues should you choose to not follow supported operations.
-Sean
Should the below commands work for moving the cluster over without issue?
import-module failoverclusters
Get-ClusterNode "servername" | Get-ClusterGroup | Move-ClusterGroup
Just a quick question:
is it important for you to move every cluster role or is it more important to move your DBs in the AAG to the next node?
What I have learned is that if you want to move an AAG, then use the commands from SQL Server side AND NOT the role failover from cluadmin.msc
That is the thing @SeanGallardy-1365 poined out
It is 1 group, that would be manually moved. I know in the failover cluster I could use the commands listed above to move the group from the primary node to the secondary (We know data loss is to be expected).
We are assuming this can be done successfully within failover clustering... we do not want to be modifying SQL (which is what we would have to do if we changed the availability group within SQL).
We are trying to make this happen as simple as possible and without involving to many roles and features.
https://learn.microsoft.com/en-us/sql/database-engine/availability-groups/windows/perform-a-planned-manual-failover-of-an-availability-group-sql-server?view=sql-server-ver15
https://learn.microsoft.com/en-us/system-center/scom/plan-sqlserver-design?view=sc-om-2019#sql-server-always-on
That is NOT correct if this is an Availability Group but would be fine for an Clustered Instance.
-Sean
During our manual process we are using the fail over cluster gui to perform the failover, flushing the dns cache, and restarting services.
We are not going into SMSS and touching the availability group
Hi there,
no complete solution.
I am not a fan of reinventing the wheel, so maybe take a look at the dbatools cmdlets
Especially
http://docs.dbatools.io/#Invoke-DbaAgFailover
That would at least help to failover your availability group(s) easily.
Hi @Joseph Patrick ,
Any update from this thread, did the reply could help you? If the response helped, do "Accept Answer". This can be beneficial to other Q&A members reading the thread.
Best regards,
Cathy