Hi
For us the most reliable method is stopping the queues (and clients) and wait a bit until currently running jobs finish. Unfortunately this is necessary because Jobs on Java Agents (we have a lot of SQL Agents) will crash if you stop the agent. All OS Agents can remain running, theres no need to stop them.
Usually all objects keep in the state they were before in.
Basically you could keep the clients and queues running when shutting down the AE - the only risc is if at the moment of shutdown any script is being calculated.....
Last year we had a DB Outage on our Sandbox env for half a day, there were several issues with CPs and JCPs (CP3 was a real CP and after Db was back a JCP, agents tried to reconnect recurringly and dumped a trace) we had to restart the whole system...
Out of my experience, a DB outage of <10min is no big deal for the AE, for longer ones I would shut down the AE.
cheers, Wolfgang
------------------------------
Support Info:
if you are using one of the latest version of UC4 / AWA / One Automation please get in contact with Support to open a ticket.
Otherwise update/upgrade your system and check if the problem still exists.
------------------------------
Original Message:
Sent: Jun 21, 2022 09:12 AM
From: monica areni
Subject: Stopping Automic db for patching
Hello everyone,
the database of our Automic's installation will be stopped for three hours due to system's patching activities.
I'm trying to find out which is the fastest method for stopping all the JOBS, JOBP scheduled during the maintenance window, and restarting them at the activities's end.
Thank you in advance!
Monica