Introduction to load balancing FMS data

You can load balance FMS data by distributing the network access load among same-priority elements. Do this by setting selected XML elements to equal priority. When elements of equal priority are encountered, FMS attempts to distribute the network access load among the same-priority items. Lower-priority (numerically larger) elements are processed only after all of the higher-priority (numerically smaller) elements are depleted without successful fulfillment of the request. You can assign same-priority values to the following elements: Element Location accesson Within the filestoregroup and fsc elements in the fmsmaster_fscid.xml file assignedfsc Within the clientmap elements in the fmsmaster_fscid.xml file defaultfsc Within the multisiteimport elements within the fmsenterprise elements in the fmsmaster_fscid.xml file entryfsc Within the fscgroup elements in the fmsmaster_fscid.xml file exitfsc Within the fscgroup elements in the fmsmaster_fscid.xml file filestore Within the fsc elements in the fmsmaster_fscid.xml file fscmaster The fsc.xml file logvolume Within the filestoregroup and fsc elements in the fmsmaster_fscid.xml file parentfsc The fcc.xml file transientvolume Within the filestoregroup and fsc elements in the fmsmaster_fscid.xml file volume Within the filestoregroup and fsc elements in the fmsmaster_fscid.xml file Note The routethrough elements within grouproute elements of the fmsmaster_fscid.xml file cannot be load balanced. This functionality is triggered entirely by the values of existing XML priority attributes. Load balancing FMS elements requires no DSD or structural configuration changes. Load balancing is fully backward compatible with existing and previous FMS configurations where unique priorities were rigidly enforced. Existing configurations using unique priorities will experience no behavioral effect from the implementation of the load balancing capabilities.