82 Sentinel 6.1 Installation Guidenovdocx (en) 7 January 2010The DAS_Binary process is responsible for event database insertion. Because event databaseinsertions can be an event flow bottleneck, load balancing the DAS_Binary process typically resultsin a significant performance gain, in terms on events per second throughput. Additionally, theCorrelation Engine and Collector Manager components can be load balanced by installing instancesof these components on additional machines5.2.1 Multiple DAS_Binary ProcessesAlthough not true load-balancing, it is possible to configure multiple DAS_Binary instances in aSentinel system to improve performance of event insertion. This should only be considered afteranalyzing the system for bottlenecks and finding that DAS_Binary has fully utilized the CPU.DAS_Binary is the process that manages event insertion into the database, and the highest eventrates Novell has achieved in internal testing were with multiple DAS_Binary processes.For more information on the Sentinel 6.1 performance test results, see the Novell Documentationsite (http://www.novell.com/documentation/sentinel61).Multiple DAS_binary processes can be installed on the same machine or distributed across multiplemachines. You must have a mapped drive (Windows) or mounted drive (Unix) for the secondaryDAS_Binary to work with aggregation.Distributing Multiple DAS_binary Instances Across Different MachinesIMPORTANT: Before you proceed, ensure that you have installed the Sentinel Server includingthe DAS. This installation is referred to as the Sentinel Server or the primary DAS_Binary.1 Use the Sentinel installer to install the DAS component on each of the other machines that youwant to run a DAS_Binary process. All DAS_Binary should connect to the same database;therefore, during installation provide the same database connection information you providedfor the initial DAS installation.2 On all machines where you want to run the DAS_Binary, including the primary DAS_Binary,make the following modifications:2a Log in as esecadm (UNIX) or an Administrator (Windows) to any one of the machinesthat run an instances of the DAS_Binary process and locate the configuration.xml filein the $ESEC_HOME/config (%ESEC_HOME%\config on Windows) directory.2b Add the following information to services section of the configuration.xml file:strategyid="sentinel_client" subscriptiongroup="dasbin" />2c Save the configuration.xml file.3 On the machines that are running secondary DAS_Binary processes, make the followingmodifications. A secondary DAS_Binary is the one that is not running on the main SentinelServer.3a Remove the file sentinelhost.id from the $ESEC_HOME/data (%ESEC_HOME%\data onWindows) directory. This will force the Collector Manager on this machine to generate anew ID rather than using the same one that Sentinel Server’s Collector Manager is using.3b The other DAS processes should be disabled. To do this, in the process section of theconfiguration.xml file on the DAS_Binary-only machines, set the min_instancesattribute as follows:min_instances=”0”
