Computer Associates BABWBR1151S38 Implementation Guide - Page 227

Configuring Firewalls to Optimize Communication ■ Agent for Microsoft SQL Server *.ldf *.mdf Except distmdl.ldf and distmdl.mdf, which cannot be skipped ■ Agent for Microsoft Exchange Server for database level backups and document level backups *.chk *.log Res1.log Res2.log *.edb *.stm Note: This release of CA ARCserve Backup does not support brick level backups on Microsoft Exchange Server databases. In previous releases of CA ARCserve Backup, the SkipDSAFiles registry key was used to define the include and skip value for brick level backups. Configuring Firewalls to Optimize Communication In an environment where you are using multiple CA ARCserve Backup servers that reside across a firewall, or there is a firewall within a Storage Area Network (SAN) fibre loop, you must configure your servers to ensure the use of fixed ports and interfaces. The configuration on your CA ARCserve Backup servers must match your firewall configuration so that CA ARCserve Backup servers can communicate with each other. A CA ARCserve Backup server communicates with other CA ARCserve Backup servers using a set of Remote Procedure Call (RPC) services. Each service can be identified by an interface (IP address) and a port. When you share data and tape libraries between CA ARCserve Backup servers, the services communicate with each other using the interface and port information provided by the RPC infrastructure. RPC infrastructure, however, does not ensure specific port assignment. Therefore, you must know your RPC infrastructure and port number assignments to configure your firewall properly. To achieve static binding, additional configuration is required. You can customize your environmental port communication settings by modifying the ports configuration file (PortsConfig.cfg) located in the following directory: CA\SharedComponents\ARCserve Backup Chapter 7: Configuring CA ARCserve Backup 227