Share via

3.3.3 Initialization

  • Article

FRS MUST check Active Directory for replica set configurations (section 2.3). FRS MUST check if it is the primary member of the replica set by checking the frsPrimaryMember of the NTFRS replica set object (section 2.3.1.2):

  • If FRS is the primary member of the replica set, FRS MUST scan the local replica tree to add each folder and file to the IDTable. FRS MUST be ready to populate all its downstream partners based on its IDTable.

  • If FRS is not the primary member of the replica set, FRS MUST NOT scan the local replica tree. Instead, FRS MUST get its files/folders from upstream partners through inbound connections. When FRS has received all files/folders, FRS is done with the initial synchronization. FRS MUST then start monitoring its local replica tree for changes to be added to its IDTable after the initial synchronization. FRS MUST be ready to populate its downstream partners based on its latest IDTable.

Based on the inbound/outbound connection schedule (section 3.3.2.1), FRS MUST establish connections (section 3.3.4.6) with its upstream partners and downstream partners. On each outbound connection, when initial synchronization is done, FRS MUST construct a change order for each unknown file or folder in its IDTable to be sent to corresponding downstream partners. See VVJoin in section 3.3.4.4.4.1 through FrsSendCommPkt when the schedule for the connection is open (section 3.3.4.4).