Harald_Heidinger_152

How to minimize the downtime at the update process of the Automation Engine

Discussion created by Harald_Heidinger_152 on Jun 20, 2016
Until Version 11.2 where the Zero Downtime Update is available the Automation Engine update including updating the Initialdata reqires the complete deactivation of all of the CP and WP processes at least for the time the Initialdata is loaded.

Please note, except the Step #1 this will only help you in case you are running your Automation Engine on a multi server environment. If your CP and WP processes are located on a single machine, all points following point 1 are not suitable for you, since for the Automation Engine process update in your environment the processing has to be switched off too.

For a multi server environment, this timeframe where the Initialdata is loaded can be minimized by following the steps described below.

#1) Before you update your Automation Engine and Initialdata, ensure that you progress a full reorganization of your reports and statistics within all clients including client 0 > Note, this step does not necessarily fit to the update process, but having the database on a state where all old reports and statistics are cleaned up will increase the speed of the initialdata-load.

#2) Switch off the CP and WP processes on one of the Automation Engine Nodes (we call it "first node" in this tutorial) and update them to the new Version, dont switch them on again that point. During this process you can run the CP and WP processes on the other node(s) since the switched off processes on the node you do the upgrade on, do not have connection that time.

#3) Switch off the CP and WP processes on the second machine ("second node" in that tutorial), and run the Initialdata update. During the initialdata update runs (which can take several minutes in a productive environment), you can update the Automation Engine processes on this machine, but if you want to focus on the initialdata update you can stay with it too.

#4) After the Initialdata update started successfully, you can start the CP and WP processes on the "first node", dont forget to process a coldstart on one single WP at this time, since after the update of the Automation Engine and/or Initialdata always requires a coldstart.

#5) while the CP and WP processes on the "first node" are already up and running, you can now take the time to update the serverprocesses on the "second node" if you havent done it during point 3. After all WP and CP processes are on the new version, you can start also the processes of the remaining node and you have your multi server environment up and running on the new version.

Q&A;

Q: Why this is not suitable for me if i m running my CP and WP processes on one single machine?

A: Since for updating the Automation Engine processes need to be switched off during the update of itself and of the Initialdata, you can not run CP and WP Processes on another node during the Automation Engine is updated on the first Node, However, the Point 1 might be of use for you too, since the reorganization of your database will increase the speed Initialdata load in any case.

Q: You mention the client 0 also to be reorganized, why is it important since no activities are running on it?

A: You are right, in client 0 you dont run any activities, however all Agent, CP&WP logs are stored within client 0 reports. By and by this is going to be a significant factor on the database space, in your reorganizing process you always should consider also to reorganize client 0 on a regular base.

Q: After the update of the Initialdata and/or Automation Engine, you require that a coldstart has to be done, why?

A: The coldstart ensures that the system tables will not contain any information which might be not compatible with the new version, during the update, the system tables within the database need to be cleared out, so the system can fill them with the data suitable for the new version.

Q: You mentioned Zero Downtime Update, what is that?

A: Zero Downtime Update is a new feature in Version 11.2 and later, it allows to run the update of your Automation Engine and Initialdata during the Automation Engine and all of your processes are still running. It is kind of a concurrent operation for the timeframe of the update. Further Information on this you can find within Automic Documentation:

http://docs.automic.com/documentation/AE/11.2/english/AE_WEBHELP/help.htm?product=awa#uczamg.htm%3FTocPath%3DAdministration%2520Guide%7CInstallation%7CUpgrade%2520Installation%7CZero%2520Downtime%2520Upgrade%7C_____0

Outcomes