cluster & Client setup & failover fails

[email protected]
Newsgroups gmane.linux.suse.domino
Message-ID <OFCCA0EAD2.E492840E-ON4A256E3C.0025B3A2-4A256E3C.0025897A@boystown.com.au>
Dear Friends,   I have 2 Domino Mail servers setup in a cluster with all 
the mail files replicated on both servers. I can setup a client to use 
either server, but I am not sure of how to setup a client to use whichever 

one is available. I.e. I can specify a mail "Home/mail server:" if I edit 
the location document on the client and specify a single server. If  I 
shut down the mail server specified as the Home/Mail server in the client, 

I expected the client to use any other available mail server in the 
cluster, but that does not work. It only looks at the mail server I 
specified and nothing is reported in the server logs. 

I have also tried specifying the cluster name as the Home/Mail server on 
the client. When I do this the client displays some messages in the status 

bar indicating that it is correctly searching and identifying the mail 
servers in the cluster but then prompts me for a list of servers to use 
when trying to locate the mail file, but that fails with a messages 
reading something like "unable to find mail file". When this happens the 
server logs: 
16/02/2004 03:06:24 PM  Unable to redirect failover from 
ClusterName!!mail\mailfile.nsf
16/02/2004 03:07:25 PM  Unable to redirect failover from 
clustername!!catalog.nsf 

I have checked the replica IDs on the various databases and all is well. I 
also know that clients can be configured to use either server without any 
problems, but FAILOVER fails. 
Any thoughts/comments would be greatly apreciated. 

Thanks for your help, 
Markus Bergh.
#####################################################################################
This e-mail message has been scanned for viruses by our email server and cleared.
#####################################################################################
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.