A profile that originally completed in a few minutes may gradually take longer and longer as weeks and months pass. This is usually not caused by a problem with SyncBack itself, but by changes in the data being backed up and the environment in which the profile runs. This article explains the most common causes and what you can do about them.
Growing File and Folder Counts
The most common reason profiles slow down over time is simply that there are more files to process. Even with Fast Backup enabled, SyncBack must still check every file in the source to determine whether it has changed. If the number of files in the source has grown from 50,000 to 500,000 over the course of a year, the scanning phase alone will take roughly ten times longer.
This growth is often gradual and goes unnoticed. Common causes include:
- Application caches and temporary files accumulating.
- Email clients storing each message as a separate file.
- Photo and document libraries growing steadily.
- Software development projects generating build output, logs, and dependencies.
- Version control repositories expanding with history.
Review your file and folder filters periodically to ensure that SyncBack is not scanning and processing files that do not need to be backed up.
Growing Fast Backup Database
The Fast Backup database stores a record of every file that was present during the previous run. As the number of files in the source and destination grows, this database grows as well. A larger database takes longer to load at the start of a profile run and longer to query during comparison.
Performing a Fast Backup rescan (full backup) periodically rebuilds this database from scratch, which can remove stale entries for files that no longer exist. This keeps the database size proportional to the current file count rather than the cumulative total of all files that have ever existed.
Growing Log Files
If log file appending is enabled, the log file grows with every run. Over months of daily runs, log files can become very large. Writing to a large file and opening it for appending becomes slower as the file size increases.
Consider whether you need to append to the log or whether each run should create a fresh log file. If you need historical logs, you can configure SyncBack to keep a limited number of previous log files rather than appending indefinitely.
Version Accumulation
If file versioning is enabled, SyncBack keeps previous versions of files that have been modified or deleted. Over time, the number of version files can grow to many times the number of active files. This affects performance in two ways:
- During scanning, if versions are stored alongside the backed-up files (for example, in a $SBV$ subfolder), the version folders and files are encountered during directory enumeration. Although SyncBack filters them out, the file system must still return them during the directory listing, which takes time.
- Version cleanup, where SyncBack removes versions older than a configured retention period, must examine every version file to check its age. With thousands of accumulated versions, this cleanup phase can take a significant amount of time.
Review your version retention settings to ensure that old versions are being removed. If versions are accumulating beyond what you need, reducing the retention period or the maximum number of versions will help.
Disk Fragmentation
On traditional hard drives (not SSDs), files that are frequently modified become fragmented over time. Fragmented files are stored in non-contiguous locations on the disk, requiring the drive head to seek between fragments when reading or writing. This slows down both scanning and copying.
The destination of a backup profile is particularly susceptible to fragmentation because files are frequently updated, replaced, and deleted, leaving gaps on the disk that are filled by new files of different sizes.
SSDs are not affected by fragmentation because they can access any location equally fast regardless of physical layout.
Running the Windows disk defragmentation tool on hard drives used as backup destinations can restore sequential read performance. Windows typically schedules this automatically, but it may be disabled on external or network drives.
Destination Storage Filling Up
As a backup destination drive fills up, two things happen:
- The file system takes longer to find free space for new files, because it must search through increasingly fragmented free space.
- On hard drives, the remaining free space tends to be scattered in small gaps, forcing new files to be written in fragments.
Both effects cause write operations to slow down. Performance degradation becomes noticeable when the drive is above 80 to 90 percent full and becomes severe as it approaches capacity.
Monitor the free space on your backup destinations and consider archiving or removing old backups before the drive fills up.
Increased Network Latency or Congestion
If the source or destination is on a network, changes in the network environment can cause gradual slowdowns:
- Other devices or applications on the network consuming more bandwidth over time.
- Network equipment degradation or misconfiguration.
- The remote server becoming slower due to its own disk or CPU load.
- Cloud storage providers adjusting rate limits or experiencing increased load.
These changes are external to SyncBack and may not be immediately obvious. If a profile is slower but the file count and sizes have not changed significantly, network conditions should be investigated.
Antivirus Software Updates
Antivirus software is regularly updated with new scanning engines and detection rules. These updates can change the performance characteristics of the real-time scanning feature. An antivirus update that adds deeper inspection of certain file types or enables a new behavioral analysis feature can slow down file operations without any visible notification.
If a profile suddenly becomes slower after a system update, check whether the antivirus software was recently updated and whether its scanning policies have changed.
Recommendations
Review File Filters Regularly
Check that your profiles are not scanning and copying files that do not need to be backed up. Exclude temporary files, caches, build output, and other regenerable data. Reducing the file count is the most effective way to keep profile run times short.
Perform a Periodic Fast Backup Rescan
Running a full rescan occasionally clears out stale entries in the Fast Backup database and gives SyncBack a clean baseline. This is especially helpful if large numbers of files have been deleted or moved since the profile was first created.
Manage Log File Size
Switch from appending to per-run log files, or configure a limit on the number of historical logs retained.
Review Version Retention
Ensure that version retention settings match your actual recovery needs. Keeping versions for longer than necessary consumes storage space and slows down version cleanup.
Monitor Destination Free Space
Keep backup destination drives below 80 percent capacity. When a drive approaches full, archive old backups or move to a larger drive.
Check Profile Run History
SyncBack records the duration of each profile run. If you notice a gradual increase over time, compare the current file counts and sizes against earlier runs to identify whether data growth is the primary factor.