Received the status -- Source and destination servers are not clustered -- trying to create xxx\xxx.nsf on server/xxx_xx; a replica creation request has been generated for further processing

Hi

I am having problems creating a replica of a database between servers.

Both servers are in the same Domino Domain and I have already moved over mail and other databases from one server to another with no problems.

However, when I select the database to replicate and select ‘create replica’ it does not go to plan!

It creates a replica of the database on the other server but with minimal data in it.

In adminp.nsf I see this message…

“rceived the status – Source and destination servers are not clustered – trying to create xxx\xxxxy.xxx on server/xxx_xx; a replica creation request has been generated for further processing.”

Which I am lead to believe is just for information and can safely be removed.

I then deleted the half replicated database.

On the main database I deleted the full text index, removed the ACL tick to enforce a consistent ACL across replicas, and given the new server - Manager access in the database ACL. As well as clear the replication history on the current database.

I then selected ‘create replica’ and this time I get the same message in admin.p as well as “Title: xxxdatabase Path: xxx\xxxx.nsf; Error: File already exists”.

Which is untrue because that folder and database no longer exists on the other server.

Even if I select to ‘create replica’ in a different folder I am stuck in the same loop above.

The live database is sitting on a R8.5 IFP2 server, the new server is R9.0.1 IFP4.

I have read there is a bug using different Administrator console versions and have tried both v8.5 and V9 to no avail.

Any help appreciated.

Thanks

Subject: Suggestion

First thing I would do is upgrade your 8.5 Server to 8.5.3FP6 Interim Fix9 just so you have the latest 8.5.3 fixes… and then try again…

jpaganet@us.ibm.com

Subject: Fixed

Thanks John for your suggestion. I just wanted to say the 8.5 server needed a restart for something else and over the weekend it finally replicated over to the 9.0.1 server.