You make a backup to have a means of restoring data.
This is most of the time asynchronous and happens at certain time intervals, which means that a backup is always at an old state.
A sync happens synchronous, which means all copies are up to date.
That’s the main difference.
To have valid source for a restore, which is the sole reason for backups, it is totally uninteresting, if you restore from a backup or from a sync location that is not currently synced to anymore!
You just need a valid copy, and a former sync is a perfectly valid copy and works perfectly fine to restore data - it is in fact a backup, as soon as you stop the sync process, like with devices that are off or have internet disabled.
Doing this to a synced device actually makes this sync into a backup!
Can we now stop to nitpick?
I’m working in Unix, Backup and Restore since nearly 30 years.
create & delete of folders with finder works
copy / upload of files doesn’t work
edit:
touch test.txt via terminal is functional.
open the file with editor, edit & save is also functional
then duplicate, copy & paste via finder with this file is also functional
So, I have now tried to connect via webdav using Finder. This works perfectly. I can also create new folders directly via the Finder and upload files using drag and drop. Strange… I can’t say whether that worked last week.
Last week, last month… it’s all the same as DEVONthink 3.9.6 has been out for several months now. No hotfixes, no patches, so no modifications on our side of things.
There is no synchronicity. It is all sequential by nature unless we’re talking Quantum Computing. THAT is nitpicking!
Backup is “Datensicherung”. If incrementally added data from my iPhone is synced with syncstore, it is, by definition, saved, i.e. backed up and made available for accessing (restoring) through (to) other devices. How complete that is, is another question. That’s why there’s the warning by our friends from DT - > Liability.
So it IS a backup. Even if I don’t stop the sync process. At this point, it turns into something comparable to live state recovery which uses one of many incremental snapshots for restoring to a state required. With Sync, the latter part is missing. However, using, for example, CCC (CarbonCopyCloner, a sync software dubbed “Backup for Mac”), you can turn on “SafetyNet” that keeps track of things that would fall through the cracks during sync as they’ve been removed from either source of destination volume. That’s part of a backup strategy and ultimately business continuity planning/management (which I was referring to).
Nothing else did I say. So, a classical Shakespeare… ((-;
I got 62 in this industry and, at one point in time, my employer bought Veritas…
I called IONOS support again and FINALLY got some useful information:
As it seems, the cause was an older problem with Micro$oft Office accessing WebDAV.
Both companies rolled out a “fix” for this and this fix then caused our problems!
The technical details are a bit strange, as numerous other Apps on macOS, Windows, iPadOS and Android did not have any problems!
For the final fix to be rolled out, the companies first need to roll out fixes for their own WebDAV access software!
A new fix was rolled out for Windows and they are working on Apple devices - after that, they can fix the issue on their servers.
This should be done in a few days, from what I understood.