If BucketPilot has been copying a server's files, it can now put them back.

Until today, restore existed only for bucket-to-bucket backup jobs. That left the data most likely to be irreplaceable — a web root, a document store, an application directory on a Linux box — with a backup and no way home. Every migration job can now be restored, and either end of the recovery can be a server.

Three recovery paths, all one click:

• •Server → cloud → server. A job backing up an SSH/SFTP machine into S3, Cloudflare R2, or Google Cloud Storage can now push those files back down to the original server.
• •Server → server. Cross-machine replication reverses cleanly, so the mirror machine becomes a recovery source.
• •Cloud → server → cloud. An offline copy pulled down to your own hardware can be sent back up to the bucket.

A restore is the reverse of the job that made it. It reads from wherever the job wrote and writes back to wherever the job read — including undoing the folder mapping the job applied, so files land at the paths they originally had rather than nested a level deeper.

It restores your files, and only your files. When a job copies the *contents* of a directory into a destination folder, that folder can also hold files the job never put there. A restore now consults the job's own manifest — the record of what each run actually copied — and leaves anything else alone, reporting it rather than pushing it onto your source machine.

The safety rules are the same ones a recovery tool should have, and they aren't configurable:

• •Nothing is ever deleted at the destination of a restore.
• •Files already present are left untouched, so a newer file is never buried under an older copy. Rolling back to the backup's contents is an explicit, off-by-default choice.
• •Writes to a server are atomic — a file is written to a temporary path and renamed into place, so an interrupted restore leaves either the old file or nothing, never a half-written one.
• •If the backup directory can't be read, the restore fails and says so instead of reporting that it found nothing.

Restore is available on Pro; restoring onto an SSH/SFTP server requires Business, the same plan that covers copying to one. Jobs that read from Azure Blob Storage can't be restored — Azure is supported as a migration source only — and BucketPilot now says so upfront rather than failing partway.