How to configure multiple Symantec Critical System Protection Managers to send their events to one Microsoft SQL Database.

Article:TECH112965  |  Created: 2006-01-15  |  Updated: 2008-01-20  |  Article URL http://www.symantec.com/docs/TECH112965
Article Type
Technical Solution

Product(s)

Languages

Problem



You have multiple Symantec Critical System Protection Managers which need to send their events to a central Microsoft SQL database.


Solution



This page tells you how to configure multiple Symantec Critical System Protection management servers to communicate with a SQL database using identical SSL certificates. This configuration lets you distribute the agent traffic load among multiple management servers while still using a central event-tracking database.

To configure the Manager/Database system
  1. Install the Microsoft SQL Server.
    Refer to the Symantec Critical System Protection Installation guide for SQL Server installation requirements.
  2. Install the Symantec Critical System Protection management server on the first computer.
    Follow the SQL Production installation procedure in the installation guide. When you specify the database host name, be sure to use a name or IP that is accessible from all of the management servers.
  3. Copy the following files from the newly-installed management server. These files are required for each subsequent installation :

    C:\Program Files\Symantec\Critical System Protection\Server\tomcat\conf\Server.xml
    C:\Program Files\Symantec\Critical System Protection\Server\Agent-cert.ssl
    C:\Program Files\Symantec\Critical System Protection\Server\Manager-cert.ssl
    C:\Program Files\Symantec\Critical System Protection\Server\Ui-cert.ssl
  4. Install the management server on the next computer with the Eval+MDSE installation option.
    Make sure to use the same installation directory path that you used for the first server.
  5. Stop the Management Server service.
  6. Replace the Server.xml and the .ssl files in the new server with the files that you copied from the first server.
  7. Restart the Management Server service.
  8. The MDSE installation on the new server is no longer required for this process. You may remove it.
  9. Repeat steps 4-8 for each additional Management Server.

You can connect a Console directly to the IP address of the new management server to verify that it works properly and communicates with the database.

Legacy ID



2006031515111553


Article URL http://www.symantec.com/docs/TECH112965


Terms of use for this information are found in Legal Notices

Please Sign In

Login using SymAccount.

Knowledge Base Search

Knowledge Base Search

Rate this Article

Help us improve your support experience.

MySymantec

MySymantec

Contacting Support

Contacting Support