Backup jobs copy over the S3 API, which not every storage type speaks. Pointing one at an SSH/SFTP-backed bucket used to be accepted without complaint — and then fail on its first run, hours later, with a technical error about adapters.

That's the worst possible time to find out. The job looked configured, it was on a schedule, and nothing had been backed up.

Compatibility is now checked when you create the job. If either end can't be copied over the S3 API, BucketPilot refuses it immediately, names the storage type, and points you at the right tool — a migration job, which is built for servers and, as of today, can be restored too.