CR 2.3.11
Windows 10
I've been playing with modifying how I do full backups. I'm considering using the uncompressed option and then using 7zip on the folder on my own. I've turned on using crc to check the validity of the copy. Back in the day, verification was accomplished by reading the backup media after the backup was completed and doing a bit-level comparison of the source, but I guess no one wants that level of verification these days.
I'm using the Google Drive desktop app that let's me map my Google Drives to a Windows system drive letter. I know the file system that Google uses isn't compatible with NTFS, but why does that cause the crc check in CR to fail? If the crc is calculated by reading the file into memory, calculating the crc, and then calculating the crc of what was written to the destination, shouldn't they match?
My testing when source and destination are both on my system works great. But my Google Drives cause every file's crc to fail.
Thoughts?
Windows 10
I've been playing with modifying how I do full backups. I'm considering using the uncompressed option and then using 7zip on the folder on my own. I've turned on using crc to check the validity of the copy. Back in the day, verification was accomplished by reading the backup media after the backup was completed and doing a bit-level comparison of the source, but I guess no one wants that level of verification these days.
I'm using the Google Drive desktop app that let's me map my Google Drives to a Windows system drive letter. I know the file system that Google uses isn't compatible with NTFS, but why does that cause the crc check in CR to fail? If the crc is calculated by reading the file into memory, calculating the crc, and then calculating the crc of what was written to the destination, shouldn't they match?
My testing when source and destination are both on my system works great. But my Google Drives cause every file's crc to fail.
Thoughts?
Statistics: Posted by AreteOne — 01 May 2023, 02:44 — Replies 1 — Views 5