Symantec Critical System - Manual (Page 37)

37 Installing Symantec Critical System Protection on Windows
Installing the management server
■ Evaluation installation using existing MS SQL instance
You can install an evaluation installation on SQL Server. The SQL Server
instance must exist and be running before you perform the installation. The
SQL Server can be local or remote.
■ Production installation with Tomcat and database schema
You can install a production installation that installs Tomcat and creates
the database schema. This option installs on SQL Server. The SQL Server
instance must exist and be running before you perform the installation. The
SQL Server can be local or remote.
■ Tomcat component only
You can install a production installation that only installs the Tomcat
component, and points to a remote database. This option requires that you
provide the file paths to a server.xml file and a server-cert.ssl file from an
installed management server.
Warning: The management server installation makes network connections to
populate both the evaluation and production databases. For local installations,
these connections are internal. Quite often, host-based firewalls either block
these connections or display messages that prompt you to decide whether to
allow the connections. In both situations, the connections time out and the
database is not set up correctly.
Before starting the management server installation, do one of the following:
■ Permit all programs to initiate connections on port 1433 or your site-
specific SQL Server port. Several programs connect to the database during
the installation process.
■ Disable all host-based firewalls on the management server computer and on
the database server if it is on a remote computer. You can enable the
firewalls after installation completes.
Installing the management server into a database instance
previously used for Symantec Critical System Protection
If you are installing the Symantec Critical System Protection management
server into an existing SQL Server (or MSDE) instance that contained a previous
Symantec Critical System Protection server database, you must clean the
previous Symantec Critical System Protection database and user accounts from
the instance.