Make DB Validation more robust? Or at least leave some tolerance?
-
Hi all,
every now and then, for the same scheduled job, the DB validation fails. It’s saying something like:
DB VALIDATION FAIL: count check table "wp_XYZ_usermeta" START: 1038464 END: 1038469 DELTA: 5 COUNT: 1038519 SQL FILE SIZE CHECK OK, SIZE: 2158625327 DB VALIDATION 1: failed to validate Runtime error in database dump Message: DB VALIDATION 1: failed to validate
Unfortunately, the Backup is aborted – whereas I’d like it to continue as I’d rather have a 99.9999% Backup including all files instead of No Backup at all.
Is there a way via Hook / Filter to deactivate the DB Validation OR tell it to continue via a tolerance of accepted count-difference?
Interestingly, the same jobs runs 3 times in a row with no Problem and then all of a sudden has this problem ?? Weird
That would be really beneficial!
Viewing 4 replies - 1 through 4 (of 4 total)
Viewing 4 replies - 1 through 4 (of 4 total)
- The topic ‘Make DB Validation more robust? Or at least leave some tolerance?’ is closed to new replies.