Contributor II
Contributor IIthat is good infor thanks!
so step
Put Cluster in maintenance mode is in
1 coro_config > Enable Cluster Maintenance
Enable Cluster Maintenance
Right?
what is the DRBD process to set this node to primary again ?
ModeratorHello Rob,
Yes, selecting option 1 after running coro_config will put the entire cluster in maintenance.
To failover, you would go to the current primary node and run the commands sudo systemctl stop pacemaker and then sudo systemctl start pacemaker. Keep in mind that if the cluster is in maintenance, then the failover will not occur so the cluster maintenance would have to be disabled during the failover.
Antonio Andres
Principal Technical Support Engineer | ScienceLogic
Contributor IIOK so basically stop and start the pacemaker on the server I want as primary
ModeratorHello Rob,
Quite the opposite, you run the commands on the current primary node, as this will force a failover and cause the current secondary node to promote itself.
For example, let's say DB02 is the current primary and you want DB01, the current secondary, to be the primary. You would log into the CLI of the DB02 appliance and run the commands to stop and start pacemaker. When you stop pacemaker on DB02, CRM will begin the failover process. Once the failover is complete, DB02 will be the secondary node and DB01 will be the primary node.
Antonio Andres
Principal Technical Support Engineer | ScienceLogic
Contributor IIWhat I am worried about is having the primary role grabbed somehow by the secondary
ictqamitsdb2 PRIMARY
ictqamitsdb1 SECONDARY
coro_config ENABLE MAINT on Primary
stop pacemaker on SECONDARY
boot SECONDARY down
boot down PRIMARY
Snapshot PRIMARY and SECONDARY
POWER on PRIMARY first let it come up as PRIMARY
do my upgrades (Just upgrading NEXTUI so shouldnt affect db just being cautious)
POWER on SECONDARY let is come up
do my upgrades (Just upgrading NEXTUI so shouldnt affect db just being cautious)
ON PRIMARY coro_config disable maintenance mode
ModeratorHello Rob,
Are you planning to perform an AP2 upgrade on your system? If so, then the steps provided are not the supported steps. The steps to install a new AP2 on your stack are included in the release notes for the AP2 release and only involve uploading the new AP2 file onto the appliance, un-taring the file, running the install command and restarting the nextui service.
If something goes wrong, there are rollback commands in the release notes as well. Aside from not supporting taking snapshots of the SL1 appliances, the steps provided are very aggressive and greatly increase the risk of an outage. You can simply install the new AP2 appliance as instructed on the 2 CDB appliances without needing to failover or shut down any appliances.
Antonio Andres
Principal Technical Support Engineer | ScienceLogic
