Computer Associates BABWBR1151S38 Implementation Guide - Page 52

Database Requirements Remote Database Considerations Using a remote database provides a simple and transparent method of sharing a single database as if the database resides locally. When you use this configuration, you do not need a database on the local machine because all information is saved to the remote database. This configuration is best under the following conditions: ■ There is not enough space locally for the database. ■ There is no organizational requirement and you want to take advantage of the ease of management that comes with having a single location for the database. ■ You require a separate server that is not a CA ARCserve Backup server to function as a dedicated as a Microsoft SQL Server machine. ■ To protect SQL Server instances in a cluster-aware environment, you must manually install the Agent for Microsoft SQL Server on all of the cluster nodes. Note: For information about backing up and restoring Microsoft SQL Server Databases, see the Agent for Microsoft SQL Server Guide. ■ Use the Server Configuration Wizard to configure ODBC communication between a remote ARCserve database and the ARCserve primary or stand-alone server. This wizard lets you configure efficient communication between servers, especially when you have more than one CA ARCserve Backup server in your environment. ■ To ensure that CA ARCserve Backup can communicate with the system that is hosting the ARCserve database instance, you should enable TCP/IP communication between the SQL Server database instance and the ARCserve server. Note: For more information, see How to Enable TCP/IP Communication on Microsoft SQL Server Databases (see page 53). Important! Microsoft SQL Server 2008 Express Edition does not support remote database communication. Note: For information about configuring devices and modifying the database protection job, see the Administration Guide. 52 Implementation Guide