-
stable v6.6.1 -
Wings-Dedup v6.6.1
Deduplicated backups that fix themselves. On Pterodactyl Wings v1.13.1.
Security
Applied all patches from v1.13.1 Wings upstream.
Auto Backup v5.1.9
Automatic node-wide per server backups with deduplication.
Fixed
Pterodactyl v1.14.1 compatibility. Panel v1.14.1 tightened the backup-restore check so a backup can only be restored when it is both completed AND successful. The standalone edition ships its own copy of that panel file, so installing on v1.14.1 used to quietly put the looser old check back. The shipped copy now carries the v1.14.1 rule, so failed or still-running backups are correctly refused on every supported panel version. (The Blueprint edition was never affected - it patches the panel in place and leaves that check alone.)
Improved
Clearer backups list order. The Backups page now lists your own backups at the top, then the automatic system backups, and finally the database backups, so a server owner sees the backups they made first. Applies to both editions.
Create-backup button moved next to your backups. The "Create Backup" button and the "X of Y backups created" counter now sit directly under the User Backups section instead of at the very bottom of the page, since users only ever create their own backups, not system ones. Applies to both editions.
Compatibility
Now tested and supported on Pterodactyl Panel v1.12.x through v1.14.x, both Blueprint and standalone.
-
stable v6.6 -
<i class="fas fa-heart-pulse"></i> Wings-Dedup v6.6.0
Deduplicated backups that fix themselves. On Pterodactyl Wings v1.13.0.
<i class="fas fa-wrench"></i> Fixed
- A failed restore can no longer take the whole node offline. If a restore timed out or lost its connection part-way through, in a rare case it could kill Wings itself (and every server on the node) instead of just the restore. Restores are now fully isolated.
- Restoring no longer wipes a server before the backup is found. The "delete current files first" restore option now locates the backup first, so a missing or wrong-storage backup can't leave a server empty with nothing restored.
- Prune notifications now show the real numbers. The Discord "prune complete" message always reported 0 archives and 0 freed; it now reports what was actually removed, and stays quiet when there is nothing to clean. A backlog of leftover backups that earlier versions never cleaned up is now removed correctly as well.
- Offsite copies are no longer reported as done when they are not. If a transfer was interrupted at just the wrong moment, a backup could be marked as synced even though nothing reached the remote; that now correctly registers as a failure and retries.
- Deleted-server cleanup is safer. Backups for removed servers are matched more reliably on Kopia, and bulk cleanup now has guards so a malformed request can never wipe live backups.
<i class="fas fa-broom"></i> Under the hood
- A large internal cleanup from a full code review: roughly 1,300 lines of dead and duplicated code removed and the backup/sync engine simplified, plus dozens of smaller correctness fixes. Nothing changes in how you use it, it's just leaner and more reliable.
<i class="fas fa-list"></i> What it does
- Deduplicated and compressed backups, so you store a lot less.
- Borg or Kopia, your call.
- Local, hybrid (local plus offsite), or remote storage.
- Automatic offsite copy for disaster recovery.
- Archives repair themselves when something goes wrong.
<span style="font-size: small; color: #888;">Binaries for AMD64 and ARM64, each with a SHA-256 checksum. Built on Pterodactyl Wings v1.13.0.</span>