Server PriorityThe initial Sync Primary is determined by the server order. This is the order in which the servers start. After a cluster starts, server priority determines the roles of servers when the primary server goes down. Server OrderTo start a cluster, make sure that the first NAS started is the server you want to act as the Sync Primary. The Sync Server started before any of the other servers becomes the Sync Primary. Thereafter, each Sync Server started becomes a Sync Backup until the number of MaxBackups is reached. When the maximum number of Sync Backups has been met, all remaining Sync Servers started become Sync Alternates. Server PriorityIf the Sync Primary fails, the Sync Backup with the highest priority (which is the lowest integer value) becomes the new Sync Primary. When a Sync Backup becomes a Sync Primary and the number of Sync Backups falls below the value of MaxBackups, the Sync Alternate with the highest priority is promoted. Sync Alternates act like Sync Locals until they are promoted to Sync Backups. When assigning priority, assign numbers between 0 and 65,535. The lowest integer value has the highest priority. Therefore, 0 is the highest possible priority. Tthe lower the value, the higher the priority. Sync LocalSync Local machines do not have priority settings and are ineligible to become Sync Servers. If the Sync Local goes through its entire SyncServers registry key without finding the Sync Primary, the Sync Local assumes that the cluster is down and acts as a local server.
|