UPGRADING TO LOTUS NOTES 7 AND LOTUS DOMINO 7

Smart Upgrade server failover to another clustered server
Smart Upgrade server failover is available with clustered servers. To use this feature, paste the database link for the Smart Upgrade database to a Configuration Settings document on a clustered server. When the Notes client user logs on, the user's home server's Configuration Settings document is checked to access the link to the Smart Upgrade database. Smart Upgrade then checks that server for the database link to the Smart Upgrade database. If the server containing the Smart Upgrade database is available, it uses that Smart Upgrade database. If the server containing the Smart Upgrade database is not available, Smart Upgrade searches, by database replica ID and database name, for a replica server within the cluster and tries to open the database on a replica server. If it locates and opens the database, that Smart Upgrade database on that replica server is used.

When a Notes client user receives the Smart Upgrade prompt and clicks OK to initiate the upgrade, the name of the server containing the Smart Upgrade database and its Replica ID are written to the NOTES.INI settings SmartUpgradeDBpath={server name}!!{database file name} and SmartUpgradeReplicID=xxxxxxx. Smart Upgrade looks for the user's home mail server. If the user's home mail server is not accessible, Smart Upgrade uses the previously-saved NOTES.INI variable SmartUpgradeReplicID= and path to search for the replicated Smart Upgrade database within the clustered servers. If the user's home mail server is accessible, the Smart Upgrade database on that server is used.

If all attempts to run the Smart Upgrade fail, the user receives a message indicating that no Smart Upgrade database is available.

See also