I have a “master” DB that people work out of. I have the “master” DB replicate a subset of documents over to a replica copy on another server. I use the Space Saver option and only replicate the contents of three views. Each view holds a different slice of information.
Now I believe it updates everything ok (there are 1000s of documents updated on a daily basis so kind of hard to check every one of them) but there is one thing not working. There is one view that holds Closed documents from today and back 90 days. Index for this view is set to Automatic. What happens is when it initially replicates (& when I clear out the replication history) it works perfectly but then everyday after that when it replicates on it’s scheduled time, the documents that pass the 90 Day threshold aren’t removed from the replica DB on the other server. They are removed from the view in the “master” DB when I look at it.
Other information on replication settings:
Replication setting has Design Elements, Agents and Deletions checked off. The Documents in Specified Views or Folders is checked off with the three views seleted in the window below that.
What am I doing wrong? I searched here but no one had a solution that worked sooo, that is why I am posting…I just don’t get why it will work perfectly initially and everytime I clear out the replication history but not after that (both scheduled and manual replication)…just doesn’t make sense…so it must be something I am missing…any help will be appreciated.
Subject: Replicating a subset of documents to a replica on another server.
I haven’t really used the options to replicate a subset of documents, so I’m not really sure about this.
You replicate 3 views from the master DB. One of these views contain docs that are up to 90 days old. I guess you have an agent that changes these documents when they get older than 90 days, so that they are no longer included in the view. Since the master DB probably does not replicate whatever view they end up in, they are not updated in the replica, and so they remain in the 90 day view on the replica.
Possible solution: You could try to also replicate the view where the documents end up after 90 days, which should (theoretically) remove them from the 90 day view.
As I said, I could be way off base here, but anyways…
Subject: RE: Replicating a subset of documents to a replica on another server.
The 3 views I use for replication, I put on the replica copy. Thought about that first…I think it was suggested before in another posting about “troubles with replication”.
The one view is set to only show 90 days of closed tickets using @now or @today (tried both) to determine 90 days…and the view index is automatic. Can’t use that in replication formulas or I would’ve used that instead…view indexes update all day every hour I believe.
Just doesn’t make sense, whatever is indexed in the view, it should replicate those over only (and delete the ones that pass that time) but then again, I am not a full blown admin so like I said, I am sure I am missing something.
Not off base…I just happened to already think of this :). Well if anyone has other suggestions…anything is welcome!
Subject: RE: Replicating a subset of documents to a replica on another server.
You are aware that using @now or @today or anything similar is not recommended? That it is way better to have an agent mark documents to be included in the view or not. That the view index will constantly be rebuilt unneeded?
Subject: RE: Replicating a subset of documents to a replica on another server.
Aware that it isn’t something you should do unless you have to but the agent isn’t an option in this particular instance.
The view being rebuilt constantly when the indexer runs isn’t an issue either (that runs fine, no errors, no server hits, no performance issues, etc).
If the replication setting says to replicate what is in a view…it should do that…having the clear out the history to get it to work seems wrong somehow…well thanks for trying to help though, greatly appreciated…