Hello K2 Community,
I am trying to figure out the best way to join a cold standby node to our prod farm. As a standard operating procedure, I like to keep a few preconfigured K2 Five nodes on standby. Since K2 Five does not offer autoscaling, I figured this is the quickest way to add resiliency to our production should we require additional capacity or if we lose one of the K2 nodes. A node = Windows VM + K2 Five.
Cloning Windows VMs from the golden image did not work for us - Azure has naming dependencies at the VM level that are challenging to deal with. What we ended up doing was to preinstall vanilla K2 Five on a separate instance of the database, then when needed, run the Configure path of the K2 Five installer, check the 'reconfigure the farm' option and use the target environment DB name. I hope my explanation makes sense.
i.e.
production farm is connected to k2-sql00
cold standby node k2-vm1 runs with k2-sql01
cold standby node k2-vm2 runs with k2-sql02
when joining k2-vm1 to the k2-farm reconfigure k2-vm1 from k2-sql01 to k2-sql00.
This operation works with K2 Five (5.2) May 2019 CU however despite checking out as all green at the end of this procedure, K2 Configuration Analysis does trigger some SQL exceptions.
Has anyone seen any documentation that describes the process of joining nodes to production?
Few things I'd like to minimize include
- any downtime
- any impact on my existing farm configuration (for some reason we always feel funny when having to run the full reconfigure on Production)
- operating with self-invented best practices that may not be supported by K2 Support
Is there a better way to do it?
Thanks in advance.
-BJ
Best answer by Mikhail2
View original