Showing results for 
Show  only  | Search instead for 
Did you mean: 

This product reached the end of support date on March 31, 2021.

What application services need to be stopped on AMD, CAS, ADS and console during server maintenance?


On a fresh DCRUM infrastructure install in an enterprise environment, the contracted DBA team installed primary and temp SQL databases on the wrong drive and now have a maintenance window to migrate. Looking for what application services need to be gracefully stopped on each element to prevent problems and to also document for future maintenance. My apologies if this is in the Dynatrace documentation and I just can't find it. DBA team will be backing up, stopping and starting all SQL services and instances.

Dynatrace 17.0 installed on all:

AMD on a physical server with RedHat 7.3

RUM console, CAS and CAS SQL on virtual Windows Server 2012, SQL 2012

ADS and ADS SQL on virtual Windows Server 2012, SQL 2012


Dynatrace Pro
Dynatrace Pro

I would open a support ticket to get confirmation but off the top of my head... shutting down the services for the CAS, ADS, and SQL should be sufficient. When you bring everything back online the CAS and ADS can then resume processing data that was sent to the AMD(s) during the maintenance window.

The correct order for shutdown would be to bring the CAS/ADS offline, then SQL. Then reversing it when the maintenance is over, bring SQL up first then the CAS/ADS.