Decommissioning
WARNING: Decommissioning operations result in non-reversible loss of data.
Decommissioning involves the removal of managed objects such as hosts, databases and technical systems. This includes removal of all related artefacts such as customer network, LMDB namespace, data from Monitoring and Alerting Infrastructure (MAI), reporting data, configuration data, logs, alerts and work-modes.
Removing a host or a technical system from the LMDB will remove all data related to the corresponding LMDB object (identified by its GUID); therefore, the LMDB cleanup is the last step of the decommissioning operation. Decommissioning requires permissions for the RSRSM_SSI_CLEANUP report and administrative access for the technical system.
If you plan to move a technical system from one customer network to another, you must first decommission this system from the old customer network.
The general approach for decommissioning is to:
- First decommission the technical system (like AS ABAP, AS JAVA)
- Then decommission the database used by the technical system, if it is not used by other technical systems
- Then decommission the hosts
- Databases and hosts can only be deleted if they are no longer used by other managed objects
WARNING:
- The tools provided to cleanup customer networks or technical systems can be instructed to also cleanup unused hosts. The tool to cleanup hosts will only cleanup a host if it is not used. During the cleanup process a host may go to an unused state if the technical system using the host was cleaned up.
- A host is considered to be unused, if it is no longer used/referenced by other LMDB entities. It is not checked if the host is still used by SAP Focused Run features like Open Component Monitoring or Stand-Alone Host Monitoring. Please pay attention to this.