Hi all, I want to take another crack at asking a question. Thank you for your patience.
I have a database in Location 1. I want an exact replica of the database to exist in Location 2. If I make a change to the database in Location 1, I want that change to occur in Location 2. I want to be able to access Location 2, but I do not want changes made in Location 2 to appear in Location 1.
Does DEVONthink support a safe way of doing this?
May I ask why you need this? What’s the use case?
Thank you for asking!
Can this be done?
You need to be clearer with your language. What is a “location” here?
Location 1 is a hard drive, internal or external via USB.
Location 2 is not an iPhone or an iPad. It is not another Mac. It is not a syncstore.
Could it be a location on the network, such as network attached storage?
Please let me know.
Is this about backups, per your other thread?
Please answer @vinschger’s question. It’s easier to find a solution to a problem than to answer your question. Or rather: The answer to your first question as well as to your “Could it be a location on …” variant is “yes”.
But I doubt that you were after a simple yes-no reply.
No, why would you say that? you asked me to clarify the locations and I tried. Was it not clear enough?
Did I clarify what I meant by “location” to your satisfaction or do you require further clarification?
There may be products out there than can do what you want. But DT does not do that by itself.
And what is the bloody point of it? You want a one-way sync instead of a backup? What for? How would your hypothetical database 2 help you in which situation?
But you still haven’t clarified what the intent or purpose is. Based on your other thread, about backups, I am asking – as @vinschger did – why are you asking. It’s almost surely not academic, like “I wonder if I could do this just to do it.”, so what are you hoping to accomplish?
If it is indeed a one-way sync, as @chrillek suggests, then no that is not directly supported. You could use a local sync store on the NAS but…
Can I just get my money back. It sounds like you have a faulty product.
I’m not sure why you think something is faulty.
Regarding a refund, you can contact our Sales department by opening a support ticket, bearing in mind refund requests must be made within 14 days of purchase.
You confirmed that it doesn’t support a one way sync. That’s a pretty major defect and there’s tons of misleading advertising about it. Thank you for providing the email.
It’s not a defect nor have we ever advertised anything stating we support a one-way sync. Our sync is a mirroring sync, i.e., bi-directional by design, and exactly how most sync engines work. This includes iCloud Drive, OneDrive, Dropbox, etc. It has been the core of Apple’s marketing hype about iCloud for a very long time.
You’re welcome.
I’ve been very clear that I want to have two copies of my database. Many people call that syncing. I don’t care what it’s called, it’s what I want. Instead of helping me achieve my goal, you went around in circles and argued semantics until you finally said “It doesn’t support that”.
Very unprofessional.
I may be just one customer, but I am one customer who is very unhappy at the moment.
@bluefrog is the most helpful, patient, and professional support agent I have ever been in contact with. I use a wide range of software from various companies.
As noted, your use case remains unclear. If you are willing to answer the outstanding questions, we may be able to assist you more effectively.
We can’t (and shouldn’t) tell people something is supported if it isn’t. There would be no benefit to anyone to do so.
Also, there weren’t any semantics being argued. People, myself included, were asking for clarification on what you hoped to accomplish so you could be better assisted. If you just wanted to make a copy, you would have done so. But your inquiry here is asking for advice and direction. However, it’s difficult (or impossible) to provide direction when you haven’t said what you specifically want to do with said copy. If I came to you and said, “I want to move.”, you would ask, “Okay… move where?” and likely “Well, why do you want to move? Job opportunities, safety, weather…?” That was the intent and purpose of the requests for more details on this thread.
If you want a copy, make a copy. What’s the problem with drag & drop or using cp in the terminal?
You’ve described a backup, essentially. You want the copy in Location 2 to be detached from the parent in Location 1, so that you can do whatever you want in Location 2. And you want copying to occur routinely when there’s a change in Location 1, not as a one-time copy. That’s a backup.