New answers tagged

0

I know this is an old thread but the information provided is simply wrong. The agent is most certainly considered a clustered service and you can see that by looking at the resources in failover cluster manager. I'm running into a similar problem and stumbled on this thread. In my case it's showing "N" for is_clustered on both the Agent and SQL Server but ...


0

Compromise achieved, after a wasted morning. King Sysadmin decided that nothing could ever be on C as a primary, not even for a moment. Even my compromise of automatic jobs that would email all of us was refused. Having said that, I set C as manual failover, so now when A reboots, all AGs (currently five of them) fail over to B. He's okay with me ...


5

In order to have the failover cluster role fall-back to the "primary" node, you need to: Configure the primary node. Right-click the cluster role. Click "Properties". On the "General" tab, configure the "Preferred Owners" such that the desired primary node is the only "preferred" owner. Switch to the "Failover" tab, and choose the option for "Allow ...


6

Converted from comments: Are you referring to the core cluster resources? If yes, the answer is no, failover of the cluster role for the availability group would not impact the core cluster resources. The core cluster resources will of course fail over to another node if the current owner is rebooted or loses connectivity, but that behavior is not ...


0

As far as I read the right way is to use the init.d/systemd scripts of MySQL/MariaDB in order to stop a node. This will inform WSREP/Galera that the replication must stop and will save on the disk, in the MySQL/MariaDB data folder, in a file the last transaction number that the node has committed (So that next time it will boot, the nodes will compare their ...


0

If your talking about doing a DC1 controlled shutdown, as hinted in one of your comments, AKA do a fail over to DC2 without data loss. While both DC1 and DC2 are online: You need to change the 2ndarys in DC2 to synchronous mode. make sure all the ownership settings of the objects in the Windows failover cluster are set so DC2 can take ownership of the ...


0

After DC 1 is down, since your secondary availability group [distributedag] is asychronous and is in manual failover mode, it is still in secondary role, so you will need to connect to [distributedag] listener and execute command: USE master ALTER AVAILABILITY GROUP [distributedag] FORCE_FAILOVER_ALLOW_DATA_LOSS This will force your secondary AG at DC2 to ...


0

(This assumes you are using `ENGINE=InnoDB.) Your table must have a primary key: You have 3 choices: (preferred) You explicitly provide such. There is a UNIQUE index with non-null column(s). (Sloppy, just make it the PK) (not a good option) A hidden PK will be provided. The PK will be clustered and unique. That is the only choice for a pk in MySQL. ...


Top 50 recent answers are included