LO76114: CLUSTER FAILOVER DOES NOT WORK AS EXPECTED IF DATA DIRECTORY CONTENT IS COPIED FROM OTHER MACHINE.
Closed as fixed if next.
There are two machines used at the steps below. Notes client needs to be installed as multi-user installation at each of the client machine. The name of Window users needs to be the same at each of the client machines. For example, if the Windows user name is "test user1" at the first machine, the same name "test user1" needs to be used at the second machine. This is done so under an assumption that Notes client at the second machine works exaactly the same as at the first machine by coping all of Notes client's data content from the fist machine to the second machine. If you use Window 7 for the first client machine, the second machine's OS also needs to be Windows 7 as well. If the first machine's OS is Windows XP, the second machine's OS needs to be XP as well. I assume that you have set up a Domino cluster where two Domino servers belong to. The first server is ServerA and the second server is ServerB. A user that you use for testing is registered so that his home server is ServerA and ServerB has a replica of the user's mail file. *** Steps *** Server_Availability_Threshold=100 is set at ServerB's notes.ini so that it prevents users from accessing the server if ServerA is available. 1. Run both ServerA and ServerB. 2. Install Notes client (multi-user install) to the first client machine. 3. Setup the Notes client at the first client machine. Client machine connects to ServerA and finishes its setup. Notes workspace only lists a replica of the user's mail file at ServerA. Cluster.ncf lists both ServerA and ServerB. 4. Exit Notes client. 5. Install Notes client (multi-user install) to the second client machine. 6. Copy the content of Notes client's data directory of the first client machine to the second machine. (All local path location in notes.ini is applicable at the second machine as the directory structure is the same.) 7. Shut down ServerA. ServerB is now the only server that is running at this point. 8. Launch Notes client at the second client machine. 9. Select the mail database icon and try to open the mail file. The customer expects that Notes client fails over to a replica at Server B but it does not occur. Notes client can open databases at server B if you explictly opens them.
Failover starts working with doing both of the next operation. 1. Edit location document and set information for the secondary server. 2. Pressing ctrl + O and connect to ServerB. Once you succeeds in connecting to ServerB (you do not need to open a replica at ServerB), failover starts working.
This APAR is closed as FIN. We have deferred the fix to a future release.
This APAR is associated with SPR# ASHH99BBYL. This APAR is closed as FIN. We have deferred the fix to a future release.
Reported component name
Reported component ID
Last modified date
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Applicable component levels