Repeated migration failures

This is a continuation of https://teamupdraft.com/forums/ticket/repeated-migration-failures/#post-7545677 which was closed out prematurely.

Essentially, I was using the SendTo feature to migrate sites. The backup to the new sites reported success. Repeatedly, the restoration on the new site failed due to a defective archive.

Updraft support says:

Just to clarify, the backup archive is checked for completeness/integrity when the restoration process attempts to unpack and restore it. This is why the transfer itself may complete, but an issue with an archive may only become apparent when the restoration begins.

An incomplete or corrupted archive can occur for several reasons, including interruptions during backup creation or transfer, server resource limitations, storage/filesystem issues, or network-related interruptions.

I understand your concern that the transfer was reported as successful despite the issue only being detected during restoration. I’ll pass your feedback to our development team, particularly regarding whether additional integrity checking could be performed during the “Send To…” process itself.

I fully understand that archives can be corrupted; that’s why it’s important to verify them. I can’t understand why hashes aren’t computed and compared. This seems like downright malfeasance if not incompetence.

If this happens on site migration, why would it be any different with backups to Updraft Vault, S3, etc.?

At this time, I don’t have confidence in Updraft. I’m afraid that it’s back to cron jobs to backup the database and rsync everything to a remote server.

Also as an aside, I find it unseemly to close out a thread without truly resolving it. Sounds like a cover-up.