changing architecture after building the components.
Got a situation where I built the following for our DR environment which is out of state. Stand alone setup. No configurations have been done to them yet.
Admin Consoles
AC001 (primary)
AC002 (secondary)
Identity Provider Servers - were to be clustered
IDP001
IDP002
Instead of the stand alone setup above, we've had a change in architecture. Assuming we have plenty of bandwidth, we'd like to have the following setup:
Admin Consoles - sync up with a primary console at our main location
AC001 (secondary)
AC002 (secondary)
Identity Provider Servers - to be added to the existing IDP cluster at our main location
IDP001
IDP002
The goal being that if changes are made to Production, they automatically get replicated to the DR site.
I need to have the two IDP servers break their association with the the two ACs above at the DR site and join up with an existing Admin Console in Production.
Note: no LAGs have been built yet.
Is there a way this can be done with out wiping out the server & doing a reinstall? Or will things like NICI, eDir objects, CA certs, etc. get all screwed up?
TIA
__________________
[FONT=Trebuchet MS][COLOR=Red]Mark G. Harvey
NetMaker, Inc.[/COLOR][/FONT]
|