Some background: I am using CrashPlan for Small Business version 220.127.116.116. Part of my backup set includes all of my music files. However, because the original Date Created and Date Modified file properties are important to me (for file integrity, audit, and sorting purposes), when I use MP3tag to update ID3 information (add missing album art or tags, etc.) I always enable the built-in "Preserve file modification time when saving tags" setting that preserves those dates/times. However, my backup software doesn't detect any changes to the file when I use this setting in MP3tag, so it never overwrites the older version with the updated one.
I contacted CrashPlan technical support about this too, and here was their response:
"When we scan, we first look at the date modified and the file size to see if either has changed. If neither has changed, we hash a metadata block provided by the OS to try to see if there's any other differences. The OS decides when that block is updated and what it includes differs, so we don't have any control over that, but this is, at a high level, how we detect that a file has changed. Once we detect a file has changed, we include it in the backup to upload a new version.
In this behavior, both our file verification scan and the real time file watcher functionality behave similarly in how they decide to create new versions. So there's no other scan we can do that would catch a file that both of those features have deemed does not need a new version."
Are there other tags or file attributes (besides Date Modified) that I can use within MP3tag to force my updated files to be detected and seen by my backup software (or the OS)? I'm using Windows 10 Pro 64-bit. Thank you in advance for any ideas.