Timeline for SQL Server 2 node availability group - deleting secondary server, to be replaced later
Current License: CC BY-SA 4.0
3 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Mar 31, 2022 at 13:42 | comment | added | Shanky | If you are migrating to DC do you know you can add node to WSFC from other DC, or create separate WSFC and AG in new DC and configure AG between the WSFC's in 2 DC( DAG). Assuming you have stretched VLAN or some connectivity. Removing secondary and disturbing current AG would not be a good idea. | |
| Mar 31, 2022 at 13:16 | comment | added | Bobogator | Thanks for the reply. The removal of the secondary node is due to a datacenter move, not due to saving money on licensing...the node will be added back once the datacenters are ready. I'm worried about the AG and/or cluster and/or quorum thinking the old secondary is still in play, which could cause the entire AG to go offline , so I want to make sure the environment is configured appropriately. I like the idea of the cluster and AG sticking around even with just the primary node, as Tony suggested, then when ready I can simply add the new vm to the cluster and AG and seed and add the dbs. | |
| Mar 31, 2022 at 8:47 | history | answered | Shanky | CC BY-SA 4.0 |