Moving databases from one server to another or from one location to new location on the same server is an easy job when you use the Administration Client. Just select the database(s), click on “Move”, type in the target or change the database name and let adminp do the job of creating the database in the new location and deleting the database in its old location at the end of the process.

ND8.x has the advantage that unread marks are automatically exchanged during this process. A few days ago, I had to move some databases on one cluster member from one directory to another directory on the same server. The databases are cluster replicas of the users mailfiles and the server is not their home server.

I selected the databases and typed in the target directory. I expected to see something like this in admin4.nsf after a successful move.

But the entries in admin4.nsf looked different. The process stopped after creating the new replica and triggering the “Maintain Trends Database record”

I did some tests; here is what I’ve found so far:

• This behaviour is reproducable with all databases on the cluster member that are not the users home mail files.
• It is not reproducable if the same databases are moved on a server that is not a member of a cluster ( standalone Domino ).
• If you use an Administration Client prior to 8.5 ( in this case 7.0.3 ) the requests in admin4.nsf are generated as shown in the first screenshot.
• If you move a users home mail file in a clusterd environment, the process works as expected.

So I suppose that this is a bug in the 8.5 Admin Client. I’ve already created a PMR with IBM. No feedback so far …