Filing this as a possible todo for the future (not something I need now). It would be nice to verify the backups after the write operation.

I imagine the process being an in-memory checksum of the compressed data before it is written to disk (if possible), then verifying the checksum of the file written (probably local storage only) post-write and reporting an error condition if necessary.

Saving the checksum alongside the backup would make it useful for the process to verify backups before importing a backup and to detect possible partial exports or other odd issues that could crop up regarding corruption.

This is more of a paranoia feature enhancement than anything.

Comments

ronan’s picture

This is a great idea. One minor implementation detail: the module never stores the entire backup dump in memory at one time so it can theoretically handle databases much larger than the available memory. This means the checksum will have to be calculated after the disk write (using sha1_file or md5_file) or I'll have to re-implement a hashing algorithm in PHP. The first will not guard against write errors on the file and the second will probably be pretty slow.

Andre-B’s picture

any news on this? is there a checksum verification in the newer versions of backup and migrate?

oss-usa.com’s picture

Issue summary: View changes

Ronan,

any news on this? is there a checksum verification in the newer versions of backup and migrate?

couturier’s picture

Version: 7.x-2.x-dev » 8.x-4.x-dev

I'm going to move this to the 8.x branch since most development work has ceased on the 7.x branch.

DamienMcKenna’s picture

Version: 8.x-4.x-dev » 5.0.x-dev

Moving 8.x-4.x issues to 5.0.x because the older branch is no longer supported.