FMS shared network configuration

This configuration illustrates how to map other sites onto a local site using a shared network configuration (also known as alias access configuration). In this situation, certain FSCs are shared and capable of managing volumes owned by any defined site. The added benefit of this configuration is that multiple sites/databases can be supported by a single FMS configuration. All groups are shared. All FSCs are shared. All linkparameters, entryfsc, exitfsc, and so on are shared. Volumes belong to just one enterprise. The following diagram demonstrates how to map sites onto a local site using a shared network configuration. Primary configuration file (FSC_HOME/fmsmaster_fscid.xml) Additional sites can be defined using the fmsenterprise element, which uses the same configuration defined by the local enterprise. This file is configured similar to the previous examples. See the FSC_HOME/fmsmaster.xml.template file for all available elements. The key point of this configuration file is: fmsenterprise element Define additional sites using the fmsenterprise element, which uses the same configuration defined by the local enterprise. This arrangement allows for an FSC to manage volumes owned by either site. Whatever routing is defined in the local site is shared between the sites. (These multisite enterprise elements have the DEF and XYX attributes in the following configuration file.) The advantage of this configuration is that a single FMS configuration can be defined to manage multiple sites (databases). This assumes that the common FSC can be physically shared between the sites. Copy