Examples of load balancing FMS data

The following examples illustrate how to load balance FMS data by assigning equal priorities to various elements. Parent FSCs The parentfsc element selects the FSC server(s) from which an FCC attempts to download its configuration information. An FCC randomly selects from among elements of equal priority. In the following example, the parentfsc setting results in an FCC first attempting to download its configuration from either fsc1 or fsc2 approximately half of the time. When considered as an overall effect among all clients, the requests for FCC configuration information are distributed approximately equally between fsc1 and fsc2. Copy Direct FSC routes If the fscgroup element contains cross-mounted resources, you can load balance direct FSC routing. An FCC randomly selects from among elements of equal priority. Note This feature applies only when direct FSC routing is enabled on the FCC. In the following example, if the primary configuration file contains the following elements, the FCC directs requests for data on the volume vol1 approximately equally among FMS servers fsc1 and fsc2. Copy <filestore groupid="fsgroup1 priority="0""/> Entry FSCs The entryfsc attribute within the fscgroup element of the fmsmaster_fscid.xml file defines which of the FSCs in the FSC group are preferred for access from outside the FSC group. An FSC randomly selects from among elements of equal priority. In the following example, the presence of the following elements cause requests coming from other FSC groups to be sent to router1 and router2 each approximately half of the time: Copy