Hi,
We have 2 BO 4.0 servers INTEGBO01 and INTEGBODR01 in two different
datacenters.
INTEGBO01 points to ebo_cms schema and INTEGBO01DR points to ebo_cms_dr
in ENTI database of the primary data center
There is active replication of database going from the Primary Dat Center
to the secondary data center. In the event of primary data center going
down we would want to connect INTEGBODR01 to the ebo_cms schema of the
ENTI database in the secondary data center. PLease let us know if the
following steps are right for switching.
Shut down and disable the DR SIAs and INTEGBO01 SIA
Change the configuration tab of IntegbODR01 to point to ebo_cms
ENTI.AESO in sceondary
Use the cluster key of Integbo01 as we are connecting to ebo_cms and
that clusterkey will decrypt all the cryptographic keys in the CMS repository
Change the cluster name to reflect INTEGBODR01
Start the SIA
Delete the INTEGBO01 Entries in the CCM from CMC and Just Keep
INTEGBODR01 CMS
Shutdown and disable the SIA
Add new default servers
o Click on Add Server Intelligence Agent on the CCM
o Type in SIA name, port. Select Create default servers and also check
off Recreate SIA on local host
Once new SIA is created make sure it is started up.
- Log into INTEGBODR01 CMC and delete all servers except the CMS
server Import the INTEGBODR01 server configuration using CCM
Change the filestore path to the one used by IntegBO01 from CMC
Check if the IntegBODR01 server is back up
We followed the steps and had trouble bringing the cms start and had to
rollback when we did our DR trial.
Can you please let us know if the steps are right and in case if it is wrong please let me know the right steps.
Thanks
Chandra
BOConsul 
(BOB member since 2005-01-12)