We are planning on moving a large number (4.500) of db’s from one server to several other servers. For this action we have written some LotusScript agents that use the AdminP classes to move (replicate and delete) the db’s to the new server. Some (known) issues solved in the code. So far so good.
Most of the users have local replica’s of the db’s and that’s where trouble begins. We were counting on AdminP to take care of background replication like it takes care of the workspace icons (works fine). Unfortunately that is not the case.
Error Messages on the replicator tab appear: “None of the selected databases has a replica on the server” and “Failed with NEW SERVER”. We were hoping on a Catalog problem. But even after a load catalog on the Domain server the problem is still there.
Off course we could solve the problem (probably) by modifying the users bookmark.nsf, but we are hoping on a better en easier solution. Why is AdminP incomplete on this matter?
Any thoughts? What are we missing here?
Highly appreciated.