Does it matter what order is used to stop and start CA Service Manager (CA SDM) services on the Primary and Secondary server(s) in a conventional architecture?

Document ID : KB000027565
Last Modified Date : 14/02/2018
Show Technical Document Details

Introduction 

In a CA Service Desk Manager (CA SDM) conventional architecture with a primary server and multiple secondary servers, if the order which servers are stopped and restarted is not correct, the CA SDM application could have some dangling/orphaned processes left over. As a result, CA SDM application performance will be impacted and/or some totally unexpected behaviors will occur.

Question: 

Does it matter what order is used to stop and start CA Service Manager (CA SDM) services on the Primary and Secondary server(s) in a conventional architecture?

Environment:  

CA Service Desk Manager 12.x and 14.1

Conventional Architecture (primary server + secondary servers)

Windows, Unix and Linux

Answer

Yes, the order in which CA SDM servers are restarted in a conventional architecture does matter.  If the order which servers are stopped and restarted is not correct, the CA SDM application could have some dangling/orphaned processes left over. As a result, CA SDM application performance will be impacted and/or some totally unexpected behaviors will occur.

Below are the correct steps to restart CA SDM servers in a conventional architecture

Shutdown Services

1. Stop the CA Service Desk Manager daemon service on the CA SDM primary server first

2. Stop the CA Service Desk Manager daemon service on all CA SDM secondary servers next

Start-up Services

1. Start the CA Service Desk Manager daemon service on all CA SDM secondary servers first

2. Start the CA Service Desk Manager daemon service on the CA SDM primary server next

Additional Information

Restart the CA SDM Servers in Advanced Availability Configuration