Using FBackup Version 9 Build 199 with backup type:mirror backup, i came accross a situation that destination files (*.docx) become corrupted.
I will try to describe the case:
In source there is a document file (A.docx) that has null content (is empty).
In destination there is a document file with the same name (A.docx) that has content.
When running the mirror backup, the application takes into consideration the difference between the source and destination files and prompts the user to continue or stop/abort the mirror backup.
See log below:
"[22/3/2021 12:12:58 μμ] \\BACKUP\user\D\Personal\IQBOARDS.jpg OK
[22/3/2021 12:12:58 μμ] Warning: Size of file "\\BACKUP\user\D\Personal\Αναφορά Παραπόνου PELMATOGRAMIMA-ELITE.docx" in destination (13598) is different than the size stored in catalog (13540)
Test finished in 0 second(s) at 22/3/2021 12:12:58 μμ, 2 file(s) and 0 folder(s) tested, 0 error(s) and 1 warning(s) found"
When choosing no (choice that equals to aborting the backup process) the destination file (A.docx) becomes corrupted as when i try to open the file with MS Word 2010 it mentions that the file is corrupted and as a next step the recovery dialog is shown. Finally when i choose to recover the file, instead of having its initial content, it has null content that comes from the source file.
So to sum up:
- 1. Canceling the mirror backup leaves corrupted files in destination.
2. Canceling the mirror backup does not stop the copy from source to destination process.