MFT Root Groups
Root Groups handle sharing file states between overlapping Root Paths.
Normally you do not need to be concerned about the internal Root Group processing. Unless you have overlapping Root Paths between your jobs, each Root Path will have its own Root Group assigned and no file state history is shared between root paths.
MFT processes file history by Root Group, meaning that multiple Root Paths and Jobs may be affected by a single file change. This is normally a good thing as it provides more efficient storage and processing.
If you create Root Paths within other Root Paths, a shared Root Group is used automatically and their file history is shared.
Sometimes you might create a shared Root Group when it is not desired. This happens if you create a root path for a folder and then create many root paths within that folder. If you create them in that sequence, they will share a common Root Group and the processing of one Root Path may degrade or delay processing of other Root Paths within the group. You would normally want a single job processing the parent folder or no job for the parent folder.
For example, if you created these Root Paths on a volume in the order below, they would share a Root Group. The roots would need to be in different jobs, but they share history.
C:\FolderA
C:\FolderA\FolderA1
C:\FolderA\FolderA2
If you create the root folders for the subfolders first, they each get their own Root Group because at that time they do not overlap. If you create a root for a parent folder of one of the roots, it will select the Root Group from one of the subfolder Root Paths.
If you get yourself in a situation where you want to break Root Paths into their own Root Group, this can be done with an option in the MFT Desktop program on a Root Path. We recommend you contact Software Pursuits support if you are not clear about when you should or should not do this.
The option on a Root Path is a check box labeled, "Check to for the Root Path to be in its own Root Group." The option is used when you click Apply or Save and is not saved in the database. The option will delete the existing root path and its history and create a new Root Path in a new Root Group.