Error "Hashes for "xxx.yy" differ. Verification failed

client
1

Hello,

I have UrBackup v2.2.11.2193 on CentOS 7.5.1804 and all my local backups are OK!

I have configured one Internet Client, with v2.2.6.0 on CentOS 7.4.1708 making backup of files (samba). I’m having trouble in some archives, see the log:

2018-06-11 05:58:42: ERROR: Hashes for “/backup///180608-1717/dados/publico/CAIXA/Cobranca/BDPRINCIPAL.mdb" differ. Verification failed.
2018-06-11 05:58:43: ERROR: Hashes for "/backup///180608-1717/dados/publico/CAIXA/Cobranca/BDSINCO.MDB” differ. Verification failed.
2018-06-11 06:25:26: ERROR: Backup verification failed
2018-06-11 06:25:31: ERROR: Backup failed
2018-06-11 06:25:32: WARNING: Exponential backoff: Waiting at least 40m before next file backup
2018-06-11 14:11:30: WARNING: Writer NTDS has failure state VSS_WS_FAILED_AT_POST_SNAPSHOT with error VSS_E_WRITERERROR_NONRETRYABLE. UrBackup will continue with the backup but the associated data may not be consistent.
2018-06-11 14:11:30: WARNING: Writer is in error state during snapshot creation. Writer data may not be consistent. This means the files open by this application (e.g. databases) will be backed up in a crash consistent state instead of a properly shutdown state. Properly written applications can recover from system crashes or power failures.
2018-06-11 14:11:30: WARNING: Writer NTDS has failure state VSS_WS_FAILED_AT_POST_SNAPSHOT with error VSS_E_WRITERERROR_NONRETRYABLE. UrBackup will continue with the backup but the associated data may not be consistent.
2018-06-11 14:11:30: WARNING: Writer NTDS has failure state VSS_WS_FAILED_AT_POST_SNAPSHOT with error VSS_E_WRITERERROR_NONRETRYABLE. UrBackup will continue with the backup but the associated data may not be consistent.
2018-06-11 14:11:30: WARNING: Writer is in error state during snapshot creation. Writer data may not be consistent. This means the files open by this application (e.g. databases) will be backed up in a crash consistent state instead of a properly shutdown state. Properly written applications can recover from system crashes or power failures.
2018-06-11 17:25:53: WARNING: Error getting complete file “zyNLQOF8qXqijaOQIkY7|dados/publico/CAIXA/Caixa Programado/SIACC_CLI.ldb” from . Errorcode: CANNOT_OPEN_FILE (3)
2018-06-11 17:25:53: WARNING: Error getting complete file “zyNLQOF8qXqijaOQIkY7|dados/publico/CAIXA/Caixa Programado/SIACC_aux.ldb” from . Errorcode: CANNOT_OPEN_FILE (3)
2018-06-11 17:25:54: WARNING: Client calculated hash of "/backup///180611-1621/dados/publico/CAIXA/Caixa Programado/SIACC_CLI.MDB" differs from server calculated hash. The file is being backed up without a snapshot so this is most likely caused by the file changing during the backup. The backed up file may be corrupt and not a valid, consistent backup. (Hash: tree-sparse)
2018-06-11 17:26:16: WARNING: Client calculated hash of "/backup///180611-1621/dados/publico/CAIXA/Caixa Programado***/SIACC_CLI.MDB" differs from server calculated hash. The file is being backed up without a snapshot so this is most likely caused by the file changing during the backup. The backed up file may be corrupt and not a valid, consistent backup. (Hash: tree-sparse)
2018-06-11 17:32:39: WARNING: Error getting complete file “zyNLQOF8qXqijaOQIkY7|dados/publico/RH/Nelio - Amir/Nelio em Server1/Nelio/~ar2DCD.xar” from . Errorcode: CANNOT_OPEN_FILE (3)
2018-06-11 17:33:33: WARNING: Not all folder metadata could be applied. Metadata was inconsistent.
2018-06-11 17:40:17: ERROR: Hashes for "/backup///180611-1621/dados/publico/CAIXA/Caixa Programado/SIACC_CLI.MDB" differ. Verification failed.
2018-06-11 17:40:17: ERROR: Hashes for “/backup///180611-1621/dados/publico/CAIXA/Caixa Programado/SIACC_CLI.ldb" differ. Verification failed.
2018-06-11 17:40:17: ERROR: Hashes for "/backup///180611-1621/dados/publico/CAIXA/Caixa Programado/SIACC_aux.ldb” differ. Verification failed.
2018-06-11 17:40:17: ERROR: Hashes for “/backup///180611-1621/dados/publico/CAIXA/Caixa Programado/SIACC_CLI.MDB” differ. Verification failed.
2018-06-11 18:10:42: ERROR: Hashes for “/backup//***/180611-1621/dados/publico/RH/Nelio - Amir/Nelio em Server1/Nelio/~ar2DCD.xar” differ. Verification failed.
2018-06-11 18:12:57: ERROR: Backup verification failed
2018-06-11 18:12:57: ERROR: Backup failed
2018-06-11 18:12:58: WARNING: Exponential backoff: Waiting at least 1h 20m before next file backup

My backupdirs and flags are:

PATH NAME FLAGS

/backup backup symlinks_optional,one_filesystem,share_hashes
/mnt/dados dados symlinks_optional,one_filesystem,share_hashes

How i can fix this?

2

@uroni can you help me bro?

3

Per the error in the log you posted:
The file is being backed up without a snapshot so this is most likely caused by the file changing during the backup.
and considering it’s a .mdb and .ldb (database files and their lock files) it’s probably having active changes while the backup is running. Files are being modified, hence the hash failure.

This looks like a file backup error, have you excluded the database path, and used the Configure components to backup section to use the SQL aware VSS functions to backup the database?