And our support is especially friendly, professional, and very much human 
8 Likes
Yes, very much so!
First class.
1 Like
Thanks for bringing it up, too. Did not find it at first. Sorry for repeating the issue in another thread…
So, it seems to be required to put it on my Synology although I would prefer an encrypted cloud location for better redundancy (all in one household kills all in case of houshold emergecy)
Happy Sunday!
Thanks for your reply. Saves me from trying to move over to my Synology (so far, that is)
I gave up on their phone support. Annoying…
d’accord!
1 Like
True. Called them and explained the issue. Was put on hold for a few minutes so support could check what’s happening. Couldn’t find/see anything not working but notified engineering. Then told me to send an email to support with the error message - while I was on phone the with the actual “support”. I doubt this is going to resolve soon …
Remember the sync is not a backup so redundancy may not be valuable.
1 Like
Now, it is a backup for loss of single devices or even the Sync Location!
Of course not against things like “I delete all content from within DT” - in this case, all copies would be deleted too.
IONOS support?
Yes, as I wrote - creepy.
They asked me the same thing 3 times over mail, each time a different person. Needed to explain over phone and multiple times over mail.
And they did not like that I used a different mail address than the one that is configured in my customer data.
I heard nothing back from them, and the issue still persists - effectively disabling any use of DT or DTTG, at least for adding and changing content.
I consider temporarily going back to my own WebDAV server, but that would need a new VM.
OneDrive is sadly not supported and I am not willing to give money to Apple.
OK if you want to do that …
Me, I’m going with what is documented in the “DEVONthink Manual” , page 20 (3.9.6 version) which it clearly says:
Note: As noted in our FAQ, sync is not a backup, neither advertised nor advocated as such. While database restoration may be possible with sync data, it is not meant to be relied upon or used in lieu of proper primary backups.
There is other good advice about backups in that section of the “DEVONthink Manual”.
1 Like
I tried Wireshark.
Captured everything, as I was not sure if other IPs that that of the WebDAV server (85.214.3.97) would be involved.
And then filter for ip==85.214.3.97
I can only see some sequences of TCP Retransmission and TCP Dup ACK, which should be normal.
I am not sure what to look for in detail.
I see lines like “Change Cipher Spec, Application Data” and “Server Hello, Change Cipher Spec, Application Data”
Any idea how to save the displayed lines in a file?
Marking a region and then exporting as CSV does only store one line, as it seems.
I understand that, also that this is the best advice.
But “normally” other devices or Sync Locations are very good synced backups!
And in my former problems with DTTG, I used that quite some times - repopulating the Sync Location from one device and then from there to all the other devices.
1 Like
I just toured the IONOS website for no reason other than it being Saturday. They claim to have “more than 30 years of experience”, which is listed as the top reason for choosing them. Yet they changed their brand name in 2018 and again in 2020, which would be a red flag to me if I were to select a mission-critical service.
3 Likes
Redundancy is not exclusively related to backup but to business continuity. Not being able to continue working on another device because data is not synced interrupts business continuity. Particularly if you use various devices for different tasks while on the road/at home…
Whatever the manual says: Syncing IS a backup of newly created content (incremental content) while on the road on iOS. As simple as that. In case of loss of the device, I can sync the incremental content to my MacOS machine.
Terminology is another thing and liability yet another.
I’m migrating back to my Synology. Their service levels of self created problems suck.
Nope. Sync is sync. If you create content on one device and then accidentally delete it from another, synced one, it’s gone. Forever. A sync replicates state. As simple as that.
A backup, otoh, preserves state so that you can recover lost data.
2 Likes
As I wrote, that fully depends on the type of problem and required type of recovery.
For lost or broken devices, the Sync is a totally fine backup!
It’s a valid copy.
This is of course different, when you change data and this get’s synced to all other devices.
But even then: My iPads are not all constantly online.
So if I ever synced crap down the online devices, I can still use the last iPad as a backup: Start DTTG without internet access, set up a new Sync location first and then recover all other devices.
So, Sync is indeed a very useful way to have backups! Only in one scenario this would not work - all devices online and then a very bad change to all of them.
That you can use sync for the purpose of backup does not mean sync is backup.
Similarly, that I can use Microsoft PowerPoint to take notes does not mean PowerPoint is a note-taking app. I may insist on saying so and actually present a valid argument, but most people who have actually used PowerPoint would still disagree with me.
Language (or “terminology”) exists by convention. Established terms like sync, backup and note-taking contains conventional definitions and implications.
2 Likes
As does Backup whereas you have different types of backup here as well. Life state recovery is a sync by nature but backup in effect.
It all boils down to BCP/M and, here, sufficient redundancy to enable you to carry on where you left if disaster stroke. To that extend, even RAID is Backup. Or Sync. Whatever you prefer. It gives you redundancy and peace of mind. In the absence of iOS backing up DT2G data to iCloud, syncing incremental data to a sync store is equvalent to backing up data.
Backup in German is “Datensicherung” and that is what syncing does. Wether or not it fullfills all requirements of a full blown backup solution with bit-/sector copy is irrelevant as those also don’t deliver to that promise as long as you keep working on your source machine.
Wherever a dogmatic discussion will lead to: Securing data to an independentz alternative storage is delivering to business continuity management. Call it as you wish. It is a means of dragging on in case of disaster. Perfect or not.
And currently, STRATO inhibits me to carry on working as my new data from my iPhone is only on my iPhone and, hence, I cannot access it from my MBP.