-
Notifications
You must be signed in to change notification settings - Fork 1
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Verify backups #29
Comments
👍 This is a feature that my existing hacky shell script backup solution has that this gem seemingly lacks. |
Dup of #7 |
If you've already created something like this before. Please help describe what a good verification process would be. Currently I only see it as a verification of proper uploading by the gem. It would also mean that we have to add "downloaders" to every storage option to download existing backup archives to the server running backup to generate a checksum of the file to compare it. |
As I said, my current solution is more of a hack than anything. What I'm currently doing is storing a checksum file next to the backup, then verifying the checksum before restoring. Not sure that really counts as a "verification process". It's more to verify the backup isn't corrupted before restoring. If your intention is to verify that the backup is actually a valid backup (e.g. it contains all the data you'd expect it to contain), seems to me like that the only real way to do that is to restore the backup somewhere, and check the data yourself. Another, less througough possibility would be to run tests against the backup file somehow. (Maybe check the extracted file for keywords or something. Not really sure.) |
My solution is to unpack (covered by #28) and use one of methods from http://stackoverflow.com/questions/4997693/given-two-directory-trees-how-can-i-find-out-which-files-differ (I am using |
And in case that somebody is interested in reusing my script - compare function is included in https://github.com/matkoniecz/backup-gem-extractor-crutch |
See issue backup/backup#601 (comment) for more information
The text was updated successfully, but these errors were encountered: