5 ms·
> What the heck... Was I expected to extract the archive and go through all the files one by one (there are thousands of them) to check if every file was proper
by ryan87 3y ago
> What the heck... Was I expected to extract the archive and go through all the files one by one (there are thousands of them) to check if every file was properly backed up?
There are a lot of silent pitfalls like that in my experience. For example, if you use folder level encryption with Synology Active Backup for MS365 it can silently mangle the file names due to path length restrictions. You'll end up with files that have "file name too long" as part of the file name.
That's why I'm trying to reconcile every file in this data set. I don't trust anything without being able to personally verify it at this point.
- bob1029 3y ago> For example, if you use folder level encryption with Synology Active Backup for MS365 it can silently mangle the file names due to path length restrictions. Is this Microsoft's fault or Synology's fault? Much of this discussion sounds like an inability to distinguish between first and third party products.
- ryan87 3y ago> Is this Microsoft's fault or Synology's fault? It's 100% on Synology. > Much of this discussion sounds like an inability to distinguish between first and third party products. Yeah. Did I explain it badly or something? I thought I made it clear that I'm having an issue with 3rd party backup solutions and that it's possible they're using some shared API from Microsoft, but most people seem to be focused on OneDrive specific issues.
- hulitu 3y ago> Is this Microsoft's fault or Synology's fault? It it were Microsoft's fault the filenames would have bin filena~1, filena~2 etc. /s