Updates

BackupKit 2026.11.3: Big Backups Keep Their Pace, Servers Get Faster

A 200 GB backup that crawled after its first hour led to this release. Big backups now keep their pace to the last file, about as fast as Windows' own robocopy in our tests, small files upload four times faster over SFTP to a distant server, and restores keep what came back.

· 5 min read · Vlad Fedoniuk

BackupKit 2026.11.3 is out, the third release this November. Most of the three deal with two things: large backups that took far longer than they should, and backups to SFTP and FTP servers that spent their time waiting. Below is what changed, with the measurements.

Big backups keep their pace

It started with a refund request. A customer backed up 200 GB from a laptop to an external disk: about 70% arrived in the first hour, and the rest took another five to six. The cause was ours, and it was in every release. After each file copied to a disk on your PC, BackupKit listed the destination folder again and stored that listing in a record that grew with every file. Each file cost about 1 ms more for every 1,000 files already copied, so a 176,000-file backup spent about four extra hours on bookkeeping.

Now the last file costs the same as the first. I measured this with real file sets against Windows' own robocopy, running three files at a time as a backup does, on the same files and the same disk:

TestBefore2026.11.3robocopy
70,000 small files to another folder on an NVMe drive23 min 40 s26 s–
176,472 files, 19.6 GB, a hard drive to itself–38 min 15 s43 min 29 s
176,472 files, 82 GB, a hard drive to a USB disk–2 h 39 min2 h 31 min
Restore of the 19.6 GB backup into an empty folder–57 min 28 s–

After the 19.6 GB backup and its restore, I compared every one of the 176,472 files with the original by SHA-256, and all were identical. On the USB disk both BackupKit and robocopy wrote at the disk's own 10–15 MB/s, so the disk set the speed.

Large files behave better too. With a backup to another drive, the progress bar now moves while a big video or disk image is being copied, and Stop takes effect at once instead of waiting for that file to finish, with no half-copied file left behind.

The same customer hit two smaller problems, and both are fixed. The folder picker in Create Backup froze on a large folder or on a USB disk that had gone to sleep. It now stays responsive while the folder loads. And there was no obvious way to back up to MEGA, so the picker's list of storages now has Add storage, which connects a new one without leaving the wizard.

Backups to SFTP, FTP and FTPS servers are faster

For a small file, the network barely matters. What costs time is waiting for the server to answer each step. BackupKit used to make six round trips per file over SFTP and eight over FTP. It now makes two and four, and sends them together. These are uploads of 1,000 small files, using the transfer engine that BackupKit shares with FTPie, over a simulated line. Each figure is the median of several runs, and every run on the new code was checked by SHA-256:

1,000 small files2026.11.12026.11.3
SFTP, a distant server (40 ms, 100 Mbit/s)97.2 s24.5 s4.0×
FTP, a distant server113.9 s55.8 s2.0×
FTPS, a distant server139.1 s80.1 s1.7×
SFTP, a local network or NAS31.5 s4.9 s6.4×
FTP, a local network or NAS38.5 s9.3 s4.1×
FTPS, a local network or NAS37.0 s9.5 s3.9×

This applies to backups that copy files one by one. A compressed backup is a single file, and it benefits from the next fix instead.

  • Big files no longer crawl to a distant SFTP server. Each 32 KB block used to wait for the server's reply. On the same 40 ms line, 3 GB took 18 minutes 44 seconds. It now uploads at the line's full speed, about 4 minutes 20 seconds at 100 Mbit/s.
  • A dropped connection no longer ends a backup. SFTP, FTP, FTPS, Google Drive, OneDrive and Dropbox now wait up to two minutes for the connection to come back, then carry on. In a test that cut the line for 10 seconds partway through three 1 GB uploads, no SFTP run survived on 2026.11.1 (0 of 3). Now every run did: 12 of 12 over SFTP, 5 of 5 over FTP and 2 of 2 over FTPS.
  • Uploads to OneDrive are up to twice as fast. Files up to 250 MB now go in one piece instead of in chunks. If your connection is slow or metered, Settings → Transfers → Upload big files in chunks brings chunks back, so less has to be sent again after a drop.
  • Stopping a backup to an FTP server no longer breaks the connection. After a stop, every later backup to that server could fail with “Malformed PASV response” until BackupKit was restarted.
  • Work on a storage no longer gets slower the more you use BackupKit. Replacing a file, or renaming or deleting a folder, used to read the whole record of what BackupKit had listed on that storage, which took about two seconds per file once it held a few hundred thousand items. It now reads only the part it changes.

Restores

  • A restore that runs into a problem keeps what came back. It used to throw everything away. Now the files that were missing are put in place, nothing already there is replaced, and BackupKit lists what it could not restore.
  • Restoring to the original folder keeps what you have added since. A restore used to replace each folder whole, which sent newer files to the Recycle Bin along with the folder's icon and settings. It now puts back the backup's files one by one.
  • One file that cannot be restored no longer stops the rest, and the unpacked copy of a compressed or encrypted backup is deleted before the restore's closing message appears. Left open, that message used to keep gigabytes on disk until BackupKit next started.
  • Restoring to the original folder on a server is faster. On FTP, SFTP, a NAS or Dropbox, BackupKit looks up each file directly instead of listing the whole folder again for every file it replaces.

Earlier this month: 2026.11.1 and 2026.11.2

  • One folder that cannot be read no longer stops the whole backup. A folder in use by another program, just removed, or on a disk that was not ready ended the run with “Failed to load folders”, and nothing was backed up. Now everything else is backed up, and that folder is named in the activity with the reason.
  • Paths of exactly 258 or 259 characters no longer end a backup.
  • Files whose names differ only in capitals are no longer lost. A server can hold Logo.png and logo.png in one folder. A backup to your PC used to save one over the other and still list both. Now the first is kept, and the backup says why the second could not be saved.
  • Names with “.part” in them are kept (video.part1.rar was saved as video1.rar), and backups that contain empty files restore from S3-compatible storage such as MinIO.
  • Backups from FTP include hidden files such as .htaccess and .env, and use several connections at once (five by default).
  • A scheduled backup that ran on time is no longer reported late, and BackupKit no longer accumulates Windows handles while it runs.

Get it

BackupKit updates itself, so you may already have 2026.11.3; check Settings → About. If not, download it here. It installs over your current copy and keeps your backups and settings. Every change is in the release notes for 2026.11.3, 2026.11.2 and 2026.11.1.

If a backup of yours still takes longer than it should, tell me. The fix for large backups started with exactly that kind of message.

Vlad Fedoniuk

Vlad Fedoniuk

I'm the founder and developer of BackupKit and FTPie, dedicated to creating innovative software solutions that simplify and enhance your digital life. Connect with me on X (formerly Twitter) , LinkedIn , or via email at [email protected]