November 2026
BackupKit 2026.11.1
Backups from FTP that hold every file, hidden ones included, fixes for files that were lost or renamed on the way to your PC and for empty files that would not restore from S3-compatible storage, a fix for scheduled backups that ran on time and were still reported late, and a simpler toolbar in the storage browser.
The storage browser
- • New folder is one click. The New button above your files opened a menu with a single item, New folder. The toolbar now shows New folder itself, and on My Computer and every folder on your PC, Show in Explorer by name, not just its icon. On the Storages page, where New’s only item could not be used, the toolbar shows Add storage and Reorder storages instead.
FTP, FTPS and SFTP
- • Backups from FTP include hidden files. Files such as .htaccess and .env, and folders such as .well-known, are backed up from every FTP server. To keep them out of the storage browser, turn off “Show hidden files and folders” in Settings for FTP or SFTP — backups include them either way.
- • Names with accents and other alphabets are backed up under their own names from FTP servers that don’t announce UTF-8 — zażółć.txt stays zażółć.txt.
- • FTPS certificates that Windows trusts are accepted without a question, so scheduled backups keep running when a server renews its certificate. A self-signed certificate is asked about once, as before.
- • Folders behind a symbolic link open in the storage browser, such as the www folder of cPanel hosting. Backups leave links out, so nothing is backed up twice.
- • Backups from SFTP leave links out too, as backups from FTP do. A link to a folder, such as www, is no longer backed up a second time, and a link that leads nowhere no longer stops a compressed backup of the site.
- • Go to a folder above your home folder. The new folder button at the top level of an FTP or SFTP storage opens a path such as /var/www in the storage browser. A folder the server won’t show you says so in plain words.
- • Copy and paste in the storage browser take everything in a folder, hidden files and folders such as .git included.
- • Backups from FTP use several connections at once, up to the number in Settings > FTP (five unless you change it), and each FTP storage can set its own under Max Connections. When a server accepts fewer connections, BackupKit works with the ones it gets — every file is backed up.
Fixes
- • A scheduled backup that ran on time is no longer reported late. If you kept the time the new-backup wizard suggested, the schedule was saved to the second (13:15:28, say), while the backup runs on the minute (13:15:00). A backup that finished within those few seconds looked as if it had not run yet: its card showed today’s time as the next backup after it had already run, and once the wait under Settings > Monitoring had passed (an hour by default), BackupKit said the backup was late. Scheduled times now count on the minute, as backups run, so the backups you already have are fixed with nothing to change. New backups suggest a time on the minute. Daily and weekly schedules were affected; a backup whose time you picked yourself was not.
- • Files whose names differ only in capital letters are no longer lost. A server can hold Logo.png and logo.png in one folder; Windows takes them for the same name. A backup to your PC saved one over the other and listed both as backed up. Now the first is kept, and the backup says the second could not be saved, and why.
- • Names with “.part” in them are kept. A file such as video.part1.rar, backed up from a server or a cloud to your PC, was saved as video1.rar, and a file in a folder named like old.parts was not backed up. Both keep their names now.
- • Backups with empty files restore from S3-compatible storage. An empty file, such as a Python package’s __init__.py, could not be downloaded from some S3-compatible servers (MinIO among them, “Bad Request”), so the restore of a backup that held one stopped. Empty files now come back like any other.
- • A compressed backup that cannot download a file says which. A compressed backup of a server or a cloud names each file it could not download, and why, instead of “Download transfer failed with some invalid items”.
- • A busy error log no longer closes BackupKit. If another program, or another copy of BackupKit, had BackupKit’s error log open at the moment BackupKit wrote to it, BackupKit could close with “The process cannot access the file because it is being used by another process”. This happened most often when BackupKit started while another copy of it had stopped responding. BackupKit now waits a moment for the log and carries on either way.