TL;DR — Résumé Rapide
Qu'est-ce que fsdmhost.exe et pourquoi il consomme beaucoup de mémoire. Guide pour diagnostiquer les problèmes de mémoire élevée sur Windows Server.
fsdmhost.exe is a Windows Server process that stands for File Server Data Management Host. It is the host executable for file server resource management tasks, most notably data deduplication. If you have noticed this process consuming significant CPU, memory, or disk resources on a Windows Server, this article explains what it does, why it uses those resources, and how to manage it.
What Does fsdmhost.exe Do?
The fsdmhost.exe process is part of the File Server Resource Manager (FSRM) and Data Deduplication features in Windows Server. It hosts several data management services:
- Data Deduplication - The primary reason most administrators encounter this process. It identifies and removes duplicate data on NTFS and ReFS volumes, significantly reducing storage consumption.
- File Classification - Classifying files based on content or properties for compliance and storage management.
- File Management Tasks - Automated file operations such as expiration and custom actions based on classification.
The process is located at:
C:\Windows\System32\fsdmhost.exeIf you see the process running from a different location, investigate further as that could be suspicious.
Understanding Data Deduplication
Data deduplication is a storage optimization feature available in Windows Server 2012 and later. It works by splitting files into variable-size chunks (32-128 KB), computing a hash for each chunk, and storing only one copy of each unique chunk. Duplicate chunks are replaced with references to the single stored copy.
How Deduplication Saves Space
Consider a file server hosting 100 virtual machine templates where each VM image contains a similar copy of the operating system. Without deduplication, this could consume terabytes of storage. With deduplication, the common OS files are stored once and each image references the same chunks, often achieving 50-90% space savings.
Typical deduplication ratios by workload:
| Workload | Typical Savings |
|---|---|
| General file shares | 30-50% |
| Software deployment shares | 70-80% |
| VHD/VHDX libraries | 80-95% |
| User home folders | 30-50% |
| Sauvegarde target volumes | 50-80% |
The Deduplication Process
Data deduplication runs as a set of background jobs hosted by fsdmhost.exe:
- Optimization - Scans the volume for files that meet the deduplication policy, chunks them, and deduplicates the data. This is the most resource-intensive job.
- Garbage Collection - Removes unreferenced data chunks that are no longer needed after files have been deleted or modified.
- Integrity Scrubbing - Verifies the integrity of all deduplicated data by checking chunk hashes and repairing corruption from the redundancy data.
- Unoptimization - Reverses deduplication on a volume if the feature is being disabled.
Why fsdmhost.exe Uses High Resources
The data deduplication process is inherently resource-intensive because it must:
- Read every file on the volume to identify deduplication candidates.
- Compute cryptographic hashes (SHA-256) for every data chunk.
- Write deduplicated chunk data to the chunk store.
- Maintain metadata about chunk references.
- Read and write extensively to disk during all of these operations.
Initial Deduplication Pass
The most resource-intensive period is the initial optimization when deduplication is first enabled on a volume. During this phase, every eligible file on the volume must be processed. Depending on the volume size, this can take hours or days and will consume significant CPU, memory, and disk I/O.
After the initial pass completes, subsequent optimization jobs only process new or modified files, which is significantly less resource-intensive.
Ongoing Resource Utilisation
Even after the initial pass, the following jobs continue to run on their default schedules:
| Job | Default Schedule | Resource Impact |
|---|---|---|
| Optimization | Hourly | Medium (new/changed files only) |
| Garbage Collection | Weekly (Saturday 2:35 AM) | Medium to High |
| Integrity Scrubbing | Weekly (Saturday 3:35 AM) | Medium |
Monitoring fsdmhost.exe
Using Task Manager
Open Task Manager and look for fsdmhost.exe in the Details tab. You can monitor its CPU, memory, and disk usage in real time.
Using PowerShell
Consultez la documentation actuelle de deduplication status and job activity:
# View deduplication status for all volumes
Get-DedupStatus
# View currently running deduplication jobs
Get-DedupJob
# View deduplication savings for a specific volume
Get-DedupStatus -Volume "D:" | Format-ListThe Get-DedupStatus output includes useful metrics:
- SavedSpace - Total storage saved by deduplication.
- OptimizedFilesCount - Number of files that have been deduplicated.
- InPolicyFilesCount - Number of files eligible for deduplication.
- LastOptimizationTime - When the last optimization job ran.
Managing Resource Utilisation
Scheduling Deduplication Jobs
Move resource-intensive jobs to off-peak hours:
# View current schedules
Get-DedupSchedule
# Modify the optimization schedule to run at night
Set-DedupSchedule -Name "BackgroundOptimization" -Start "02:00" -DurationHours 4
# Create a custom throughput optimization schedule
New-DedupSchedule -Name "NightlyOptimization" -Type Optimization -Start "01:00" -DurationHours 6 -Days Sunday,Wednesday -Priority NormalLimiting Resource Consumption
# Set maximum memory percentage for deduplication (default is 25%)
Set-DedupVolume -Volume "D:" -OptimizePartialFiles $false
# Set the minimum file age before deduplication (default is 3 days)
Set-DedupVolume -Volume "D:" -MinimumFileAgeDays 5
# Exclude specific file types from deduplication
Set-DedupVolume -Volume "D:" -ExcludeFileType @("*.vhdx", "*.bak")
# Exclude specific folders
Set-DedupVolume -Volume "D:" -ExcludeFolder @("D:\Databases", "D:\Temp")Stopping a Running Job
If a deduplication job is causing immediate problems:
# Stop all running deduplication jobs
Stop-DedupJob -Volume "D:"
# Stop a specific job type
Stop-DedupJob -Volume "D:" -Type OptimizationDépannage Problèmes Courants
fsdmhost.exe Consuming Excessive Resources Continuously
If resource usage does not normalize after the initial deduplication:
- Check that optimization jobs are not running continuously due to high data churn.
- Verify the volume has adequate free space (at least 15-20% free).
- Review the event log under Applications and Services Logs > Microsoft > Windows > Deduplication for errors.
- Consider increasing the
MinimumFileAgeDaysto reduce the number of files processed.
Deduplication Errors in Event Log
Common event IDs and their meanings:
- Event 6153 - Optimization job failed. Check for volume errors or insufficient disk space.
- Event 6159 - Garbage collection failed. May indicate corruption in the chunk store.
- Event 6170 - Scrubbing found and repaired data integrity issues.
fsdmhost.exe Running When Deduplication Is Not Enabled
If the process runs even though you have not enabled deduplication, it may be hosting other FSRM features like file classification or file screening. Check which FSRM features are installed:
Get-WindowsFeature FS-Resource-Manager
Get-WindowsFeature FS-Data-DeduplicationDisabling Data Deduplication
If you decide to disable deduplication on a volume:
# Disable deduplication (starts unoptimization in background)
Disable-DedupVolume -Volume "D:"
# Monitor unoptimization progress
Get-DedupStatus -Volume "D:"Disabling deduplication does not immediately restore files to their original state. The unoptimization process runs in the background and can take a significant amount of time depending on the volume size and the amount of deduplicated data.
Dépannage: fsdmhost.exe et Consommation Élevée de Mémoire
“fsdmhost.exe high memory” et “microsoft file server data management host high memory” sont parmi les préoccupations les plus courantes des administrateurs. Cette section offre un guide ciblé pour diagnostiquer et résoudre la consommation excessive de mémoire.
Pourquoi fsdmhost.exe Utilise Beaucoup de Mémoire
Le moteur de déduplication met en cache les métadonnées du chunk store en RAM pour accélérer les recherches. Plus le volume dédupliqué est grand, plus ce cache est important. Les causes spécifiques incluent:
- Cache du chunk store — L’index du chunk store de déduplication est chargé en mémoire pour des recherches rapides de hash. Sur des volumes avec des millions de chunks dédupliqués, cela peut consommer plusieurs gigaoctets de RAM.
- Exécutions du ramasse-miettes — Pendant le GC, le moteur doit parcourir l’intégralité de la carte de références des chunks, augmentant temporairement l’utilisation de la mémoire.
- Grands volumes avec déduplication activée — Les volumes dépassant 1-2 To avec des taux de déduplication élevés nécessitent naturellement plus de mémoire pour les métadonnées.
- Tâches simultanées multiples — Si l’optimisation et le GC s’exécutent en même temps, l’utilisation de la mémoire augmente brusquement.
Diagnostic de l’Utilisation de la Mémoire
# Vérifier le statut actuel de la déduplication et les économies
Get-DedupStatus | Format-List
# Vérifier la configuration de déduplication du volume
Get-DedupVolume | Format-List
# Vérifier l'utilisation de la mémoire de fsdmhost.exe directement
Get-Process fsdmhost -ErrorAction SilentlyContinue | Select-Object Name, WorkingSet64, VirtualMemorySize64
# Voir les tâches de déduplication actives
Get-DedupJobVous pouvez également utiliser le Moniteur de performances (perfmon) pour suivre le compteur Process > Working Set du processus fsdmhost au fil du temps, ce qui aide à identifier si la consommation de mémoire est corrélée avec les fenêtres de tâches planifiées.
Solutions pour la Consommation Élevée de Mémoire
- Configurer les limites de mémoire — Restreignez le pourcentage de mémoire système que la déduplication peut utiliser:
# Limiter la dédup à 15% maximum de la mémoire système (par défaut 25%)
Set-DedupVolume -Volume "D:" -OptimizeMemoryPercentage 15- Planifier les tâches en heures creuses — Évitez les pics de mémoire pendant les heures de bureau:
Set-DedupSchedule -Name "BackgroundOptimization" -Start "02:00" -DurationHours 4-
Augmenter la RAM du serveur — Si le serveur a moins de 8 Go de RAM et héberge de grands volumes dédupliqués, envisagez une mise à niveau. Microsoft recommande 1 Go de RAM par 1 To de données dédupliquées comme référence.
-
Vérifier la corruption du chunk store — La corruption peut amener le moteur à utiliser des ressources excessives lors des tentatives de réparation:
# Exécuter une tâche de vérification d'intégrité
Start-DedupJob -Volume "D:" -Type Scrubbing- Redémarrer le service de déduplication — Si l’utilisation de la mémoire est anormalement élevée et ne diminue pas après la fin des tâches:
Stop-Service DedupSvc
Start-Service DedupSvcCela vide le cache du chunk store en mémoire et force le service à le reconstruire à partir du disque, ce qui peut résoudre les fuites de mémoire ou les entrées de cache bloquées.
Articles Connexes
- What Is Andrea ST Filters Service?
- What Is www.msftncsi.com?
- What Is 1e100.net?
- Exchange TooManyObjectsOpenedException — Store.exe High Memory
Résumé
fsdmhost.exe est le processus File Server Data Management Host dans Windows Server, principalement responsable des opérations de déduplication des données. Une utilisation élevée des ressources est attendue pendant la déduplication initiale d’un volume et pendant les tâches planifiées d’optimisation, de ramasse-miettes et de vérification d’intégrité. Pour gérer son impact sur les performances du serveur, planifiez les tâches en heures creuses, configurez les limites de mémoire avec Set-DedupVolume -OptimizeMemoryPercentage et surveillez le statut de la déduplication via PowerShell. La consommation de ressources devrait se stabiliser après la fin de l’optimisation initiale.