• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 278
  • Last Modified:

Replica isn't updated

I made a replica from a database ( not mailfile) to another server. (server to server)
But the new replica seems as it would be a new copy, no new documents arrives into it.

 What should I change so that the new replica receives the new documents?

There are databases on both servers which replicates with each other, thus the connection and setup must be OK.
0
verto33
Asked:
verto33
1 Solution
 
Sjef BosmanGroupware ConsultantCommented:
The server need Manager rights in the databases.
0
 
Sjef BosmanGroupware ConsultantCommented:
Look on the console or in the log.nsf database, under Replication. Both servers need sufficient permission to update the replica on the other server. Normally, you should set it to Manager, with Delete permission.
0
 
mssturgeonCommented:
Another thing to check is that you connection doc is not limiting the replication to individual databases or directories via the "Files/Directories to Replicate" field.
0
What does it mean to be "Always On"?

Is your cloud always on? With an Always On cloud you won't have to worry about downtime for maintenance or software application code updates, ensuring that your bottom line isn't affected.

 
madheeswarCommented:
Create a new replica from scratch.
And what is the connection between these 2 servers?
0
 
qwaleteeCommented:
I suggest trying a manual replication.  Let's assume the following:

Server with original copy: Older/Verto
Server with new copy: Duplicate/Verto
File path+name on server Duplicate/Verto: applications\stubborn.nsf

Go to the console of Duplicate/Verto and type the following:
REPL OLDER/VERTO APPLICATIONS\STUBBORN.NSF

If you do this when the server is idle, you can easily see the messages it generates.  You can certainly look in the log for the replicator output, both in Miscellaneous Events, and in the Replication Events.

You might also want to change your replicator log level.  The server won't really show anything ever, because DOLS replication is push-pull replication all handled by teh client (it shows as regular user activity on the server, but no replication activity).  However, you can modify the log level of client in the DOLS's INI file, and I believe the replicator respects the same settings as available on the server.  This just means more detailed informartion shows in Miscellaneous Events.
0
 
CRAKCommented:
1st check the databases' properties: if their replica id's differ, start with madheeswar's suggestion to create a new replica.
If they match, go by the other experts' suggestions. In that case you may also need to check both database's replication settings (properties > 1st tab > replication settings > other-icon > Temporarily disable....)

0

Featured Post

New feature and membership benefit!

New feature! Upgrade and increase expert visibility of your issues with Priority Questions.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now