Order of Server restart for SDM
Article ID: 27565
Updated On:
Products
Issue/Introduction
In a CA Service Desk Manager (CA SDM) with multiple 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.
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?
How about Advanced Availability architecture?
Environment
Release: 12.6 or higher
Component: CA Service Desk Manager
Resolution
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
For AA architecture, shutdown like
1. stop all app servers one by one
2. stop standby server
3. stop background server
to start, reverse the order as mentioned above
Additional Information
Feedback
