Skip to Content

Moving/Renaming a SolMan 7.1 System

The client I'm at right now (a bank) has a highly segregated network and divides their systems up into multiple "Security Zones". When we originally installed their Solution Manager 7.1 system we carefully explained that this single system would be responsible to manage and monitor ALL of their non-production SAP systems (Production would be covered (because of the security restrictions) by a 2nd SolMan) and they gave us two servers (app and db), two names and IP addresses to install to.

Well, it turns out they have now realized that this system is NOT a Sandbox system (turns out that's where they had it installed!) and now they want to move it to another system located in their QAS/UAT zone. This would involve changing the IP addresses and the names, and in fact the physical hardware as well.

With all the interconnections to the managed systems (we currently have it hooked into about 10 systems) and the diagnostics agents (about 10 of them, and about 10 more to come very soon on the db servers) I'm trying to think of a "clean" way to do this, but everything I think of, has tonnes of work associated with it.

Does anyone have, or know of, a client that's successfully done (or even, tried) this? Anybody seen any procedures for doing this?

Any thoughts (including thoughts that I should be thinking of retiring 😉 ) ?


Add a comment
10|10000 characters needed characters exceeded

Assigned Tags

Related questions

3 Answers

  • Best Answer
    Posted on Nov 06, 2012 at 04:05 AM
    Add a comment
    10|10000 characters needed characters exceeded

    • Former Member

      System copy would be my best guess too.

      However, you would have to do a lot of the configuration over.

      So all the connections have to be generated again, diag agents too.

      It will cost you a significant amount of time.

      So if you're really close to retirement, try to postpone it for a little while 😉

      In that case you can have someone else do your dirty work for you!

      Good luck!

  • Posted on Nov 06, 2012 at 10:49 AM

    Hi Murray

    If you don't have big scenario implementations, I would recommend you to start clean, take advantage of the "opportunity" and patch to the latest SP level.

    Doing a system copy of a Solution Manager isn't something I would recommend. A lot of rework will need to be done and you need to be careful with such a system copy because it's Netweaver + SolMan + BW + CRM what you are copying in the end so you would also need to apply product specific (BW) steps in that system copy.

    My vote = go for fresh install.

    Best regards


    Add a comment
    10|10000 characters needed characters exceeded

  • Posted on Nov 09, 2012 at 04:02 PM

    Thanks folks. That's very helpful. I'm hoping we just go with the brand new copy, but at this point they are still debating.

    Add a comment
    10|10000 characters needed characters exceeded

Before answering

You should only submit an answer when you are proposing a solution to the poster's problem. If you want the poster to clarify the question or provide more information, please leave a comment instead, requesting additional details. When answering, please include specifics, such as step-by-step instructions, context for the solution, and links to useful resources. Also, please make sure that you answer complies with our Rules of Engagement.
You must be Logged in to submit an answer.

Up to 10 attachments (including images) can be used with a maximum of 1.0 MB each and 10.5 MB total.