There are several methods:
1. Absolutely reliable: comparing each byte (slow).
2. Almost as reliable: checksum - MD5, SHA, etc. (relatively fast).
3. Everything else (very unreliable): comparing sizes, creation or modification dates, attributes.
I was surprised to discover that the program relies entirely on unreliable methods.
I tried this program (incremental, 7-ZIP LZMA) and found that it couldn't handle my task. I needed to make a backup of a folder with a game (6 GB) and an installed mod (700 MB). Periodically, the launcher of this mod downloads an archive containing the entire mod and unpacks it into the game folder. All other backup programs I tested (about 5) easily completed the task and created an archive of size 10 MB after updating the mod, but Reflector created an archive of size 700 MB. This means that when updating the mod, also restored the archive attribute and Reflector was easily fooled.
Why doesn't use checksum method?
Re: Why doesn't use checksum method?
Those methods need at least one backup to exist for comparation. The archive attribute (the classical method) doesn't.
--
Luis Cobian
Cobian Backup's creator
Luis Cobian
Cobian Backup's creator
-
- Posts: 2
- Joined: 17 Apr 2023, 13:46
Re: Why doesn't use checksum method?
Do you plan to add this method to your program? Without its availability, using the Reflector is too risky.
Re: Why doesn't use checksum method?
Yes, please!!!
-
- Posts: 1
- Joined: 28 Oct 2024, 03:15
Re: Why doesn't use checksum method?
It sounds like you're facing a frustrating issue with Reflector's backup method. Relying solely on unreliable methods can definitely lead to inefficiencies, especially with large files. It's surprising that it didn't utilize checksums for verification. Have you considered reaching out to their support for clarification on this?
Re: Why doesn't use checksum method?
It can use crc verification (unchecked by default)
--
Luis Cobian
Cobian Backup's creator
Luis Cobian
Cobian Backup's creator