Resolution:
On FabricServer 1.3, manual activation of Policies on a Failover Broker can cause synchronization issues between Primary and Failover Broker Policies. The following procedure determines if Primary and Failover Policies are out-of-sync and how to correct them:

   1. Go to webapps/livecluster/deploy/resources/fabric_config/policies on the Failover Broker.
   2. Search for lines containing the word "active" in the XML files. For example:

      &ltproperty name="active" value="True"/>

   3. If there are multiple lines with "True", the Failover Broker has incorrect Policies. Copy and paste the XMLfiles in webapps/livecluster/deploy/resources/fabric_config/policies from the primary to the failover Broker. For example:

      cp [primary_broker_FS_root]/webapps/livecluster/deploy/resources/fabric_config/policies/*.xml failover_broker_FS_root]/webapps/livecluster/deploy/resources/fabric_config/policies

   4. Restart the Failover Broker.