When you create a new sync group and add the entire D drive to it, the existing sync configuration and tiered data within the previously synced folders should remain intact. Here’s what generally happens:
- Existing Tiered Data: The tiered data within the folders already synced by the current sync group will stay as is. The new sync group will not affect the data already tiered; it will only start managing the data in the new scope (i.e., the entire D drive).
- New Sync Group: The new sync group will handle the synchronization for the entire D drive. This means any folders or files within the D drive that weren't previously part of the existing sync group will now be included in the new sync group’s synchronization and tiering processes.
- Data Management: Azure File Sync will continue to manage and optimize the data based on the new sync group’s policies. This includes handling cloud tiering for files and folders within the new scope as defined by the new sync group’s configuration.
- No Duplication: The data on the D drive won't be duplicated. Instead, the sync service will integrate the entire D drive into its existing tiering and synchronization logic.
In summary, creating a new sync group and adding the entire D drive to it will extend the synchronization scope without disrupting the existing tiered data. Just make sure to verify the settings to ensure that the new sync group is configured to meet your needs