Hi

Physical server location migration project.

SERVERA[/B] : I HAVE A SENTINEL CORE 6.1.2.1 (ISCALE BUS) CURRENTLY
WITH NO DB BACKEND. THE DB BACKEND WAS NOT AND WILL NOT BE BROUGHT TO
THE NEW LOCATION.

I HAVE REBUILT A NEW *SERVERB* : SENTINEL CORE 6.1.2.1 (ISCALE BUS)
WITH ORACLE 10GR2SP4 ON THE SAME MACHINE. I HAVE CREATED A SENTINEL LINK
COLLECTOR WHICH CONNECTS TO A *SERVERC *3RD WINDOWS COLLECTOR MANAGER
(REPLACED .KEYSTORE, RAN DBCONFIG SCRIPT ETC.) AND AM SUCCESSFULLY
RECEIVING EVENTS FROM THIS COLLECTOR MANAGER AND IT'S CONNECTORS. I
INITIALLY ATTEMPTED TO IMPORT THE SERVERA'S CONFIGURATION IN TERMS OF
CORRELATION RULES, TAXONOMY SETTINGS, EVENT CONFIGURATION AND ALL
COLLECTORS AND CONNECTORS.

SINCE THE IMPORT, I HAVE IDENTIFIED THAT THERE ARE 4 KEY COLLECTORS
(FILE) WHICH ARE HIGHLY CUSTOMIZED IN TERMS OF OPERATION, SETUP ETC.

*QUESTION
Would it be possible to bring [B]ServerB *back into the mix as a second
Sentinel Link and "switch off" the communication server (iSCALE Bus)
permanently i.e. have *ServerB* act purely as a collector manager with
it's current collectors and connectors?

I do not want to corrupt the current ESEC DB by adding another
Communication Server to the mix?

Thanks in advance for the help! :0


--
Darryn van Tonder
Identity and Security Consultant
Novell Platinum Partner
------------------------------------------------------------------------
darrynv's Profile: http://forums.novell.com/member.php?userid=90727
View this thread: http://forums.novell.com/showthread.php?t=458450