Configuration failover versus volume failover

You can use File Management System (FMS) to manage different types of failover behavior. Configuration failover features are configured for each client API, either in the Fms_Bootstrap_Urls preference or the parentfsc list in the fcc.xml configuration file. (The fcc.xml file is located in the FMS_HOME directory, for example, TC_ROOT\tccs.) Volume failover features are configured with the priority= attributes of a number of elements in the fmsmaster_fscid.xml file. (This file is located in the TC_ROOT\fsc directory.) Once configuration failover delivers the assignedfsc list (and/or the directfscroutes list) to the FSC or FCC client, the client uses this information to select the initial FSC for each data request, which is the initial aspect of volume failover for Teamcenter data access. Much of the volume failover implementation is in the intermediate FSC server routing logic, though the client selection of the initial FSC server to receive each data request is also important. Warning When configuring an FMS system for volume failover, you should also consider configuring for configuration failover. Volume failover is not particularly effective if clients cannot obtain an assignedfsc list because the one and only configuration server FSC is offline. Larger deployments encompassing many remote sites and several FSC servers may choose to set up a couple of FSC servers at each site exclusively for use as configuration servers. Smaller deployments (using only a few FSC servers) should consider configuring configuration failover similarly to volume failover.