Running 2 SolMan systems, 1 as master, 1 as (remote) slave ? ? ?
Will it be possible to run 2 SolMan systems, 1 as master, 1 as (remote) slave ? ? ?
My customer is running Solman 4.0 (only ABAP) productively in a complex landscape (hosted and remote environments).
Migration is planned to move environments to another datacenter (not on same campus) as part of a hardware consolidation project.
SolutionManager is basically used for SLD and Operations to collect data from satellite systems (mainly hosted onsite, some managed remotely) into the SolMan for EWAs.
Central Monitoring and using the MOPZ is in project planning phase.
Running 2 datacenters needs decision between 2 scenarios as far as SolMan is concerned:
1. running 1 Solman, connecting to satellites in remote datacenter thru a leased line
2. running 2 SolMans, 1 per datacenter, consolidating data in 1 "master" Solman
Scenario 1 is the simple one, but needs sizing the leased line correctly due to relatively high line fees.
As we're unable to find docu describing connection and bandwidth requirements between SolMan and satellites, no estimate can be made for the necessary leased line between the 2 datacenters.
Scenario 2 can reduce line load, but may not be feasable, as we're unable to find docu describing this setup using a "master" and "slave" SolMan.
Additionally, this scenario will be necessary to manage systems at remote customer's sites with customers already running their own SolMan.
Can anyone pls advise on both scenarios?