ear Solman Guys.
We have SAP Solution Manager 7.2 (Linux/Hana 1.0) installed with SPS 03 and upgraded to SPS 05 as a productive SAP Solution Manager Systems. We have about 100 managed Systems configured and use it primarily for System-Monitoring, Reporting (EWA, SLR) and other technical things. Now I began to instal an additional Solman 7.2 (Linux/Hana 1.0) AS-ABAP with SPS 03 as Dev-Solman. AS-Java is not installed yet on the Dev Solman. I don't want to upgrade it to SPS 05 and I don't want to make the obligatory configurations (System preparation, infrastructure configuration, Basis configuration again) and I don't want to configure all managed Systems again, but !?! I want to make a systemcopy from the productive Solman to the Dev-Solman, but as a Solman Guy I know, there are many Problems regarding that kind of System copy. Now my question. Does already exists a System Copy Guide for SAP Solution Manager 7.2 (Linux/Hana)? Here any of the Major Problems i detected in our environment. After the copy is done the dev-solman would start to synchronice all the Systems in the lmdb up to the Support Portal. That means, in the Source sytem (prod-Solman must be some steps done before starting the copy to avoid the behaivour). After the copy the Solman communicates over RFC-Destinations to all SDCCN Reporting based managed Systems and create Additional EWA sessions in the managed Systems. For that on the managed Systems there are to EWA session ready to run. One for the prod-Solman and one for the Dev-Solman. How to avoid thios behavour? If System-Monitoring is configured to communicate with an external Monitoring System each alert occurs two times. One in the prod-Solman and one in the dev-solman and both (the same) alerts will tranfserred to the external monitoring System, that means two different tickets will be generated for one and the same alert. Sure after some time this behavour stops, because there are no actual diagnostics agents are connected to the dev-solman but the already existing ones from the prod-solman coming in from the Systemcopy will be alerted. How to avoid this behaour? And so on. That means, a good System Copy Guide for a Solution Manager System is, what to de-activate on the source System before starting the physical copy to avoid many unnecessary error situations and what to be re-activated after copy for a usual Operation again? Greetings, Rob. 🙂
Bluesky
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.