Upgrading Good Mobile Messaging and Good Mobile Control Servers

Transcription

1 Good Mobile Messaging Server Good Mobile Control Server for IBM Lotus Domino Upgrading Good Mobile Messaging and Good Mobile Control Servers Updated: 09/25/15 1 Introduction 1 2 Pre-Upgrade Instructions Domino Health Checks 3 3 Upgrading from Earlier Versions of Good Mobile Messaging/Good Mobile Control Servers Best Practices Performing the Upgrade Upgrading Good Mobile Control Server Upgrading Good Mobile Messaging Server 13 4 Upgrading in a Cluster Upgrading the Primary GMC Server in a Good Cluster Upgrading the Standby GMC Server in a Good Cluster Upgrading the Primary GMM Server in a Good Cluster Upgrading the Secondary GMC Server in a Good Cluster 20 5 Error Conditions 21 1 Introduction This note describes how to upgrade to Good Mobile Messaging server and Good Mobile Control server Upgrading is tested and supported for the two most recent previous versions. Upgrading from earlier versions will require additional steps to complete the upgrade; in this case, contact your Good technical-support representative for the appropriate additional upgrading steps and additional software required. Upgrades should be performed in the order given in this note. If Good Mobile Control server and Good Mobile Messaging server are installed on the same machine, they must both be upgraded, in that order, before all the services can be started. 1

2 Note: All GMM Servers less than version 6.3.x must be upgraded to and the GMC Server must be restarted for multi-device support to commence. Client upgrades are not required. Note: Stop the GMC, GMM, and Domino services before beginning the upgrade. Important: If you downgrade the Good Mobile Messaging Server from this release, any devices that you have added after the upgrade will be automatically deleted and will no longer synchronize with the user s account; the Good application will have to be reinstalled on the device and it will have to resync to restore functionality. Domino 6.x servers are not supported in this release. Domino Primary servers must be or higher; 8.x is recommended. Domino Secondary servers used by the Good Mobile Messaging Server must be and above. 2 Pre-Upgrade Instructions Before performing the upgrade, the Domino server on which Good Messaging Server runs should be shut down; this should stop the Good Mobile Messaging services. Starting with Domino 8.5.x and above there is one more service to be stopped before proceed with upgrade Lotus Domino Diagnostic Service.You need to verify that the Good Mobile Control and the Good Mobile Messaging services have been stopped, using Microsoft Windows service control manager. Warning: Downgrading the Good Mobile Messaging Server is not recommended. Warning: If the Good Mobile Messaging Server and Good Mobile Control Server use different SQL instances, and you uninstall Good Mobile Control, its SQL instance will not be removed. If you remove the GMC SQL instance manually, all GMC user data will be removed from it. GMM Server instance data will remain in its instance. For security, a patch is required for SQL Server. Without the hotfix, the GMC service will start but within a few seconds will crash. Several errors will appear in the Windows Event Log. The key log message that appears in the EMF.log file is: com.good.base.goodexception: org.apache.commons.dbcp.sqlnestedexception: Cannot create PoolableConnectionFactory (Connection reset) GMC supports SQL 2005 and The following patches are available. These are the minimum patch levels required for GMC to work correctly with remote SQL 2008; later versions are supported: SQL Server 2008 SP3 CU3 16 Jan SQL Server 2008 R2 SP1 CU6 16 Apr SQL Server 2008 R2 SP2 26 July 2012 Upgrading GMC will not upgrade SQL 2005 to The latest version of Good Mobile Messaging Server and Good Mobile Control Server, support the latest version of Good Mobile Messaging Client, as well as the two previous versions of the Client; in the same way, the latest version of the Good Mobile Messaging Client supports the latest version of Good Mobile Messaging Server, Good Mobile Control Server, and the two previous versions. However, note that new features in the latest version are not supported on the two previous versions. 2

3 2.1 Domino Health Checks This Good Mobile Messaging Server performs Domino health checks. If problems are encountered with respect to Domino s health running on the GMM machine, automatic recovery will be initiated. For this feature to work correctly and to avoid installation issues, check the following before upgrading to this GMM version: If the host and Domino names are different, add the following in the etc\hosts file to match them. Add the Domino fully qualified domain name in Windows: C:\Windows\System32\drivers\etc\hosts Add the following 3 lines, which include the Domino name and host name resolved to the local IP address: ttmsqa.hyperv.goodexample.com <- Use the Domino fully qualified name for your organization ttmsqa/goodexample <- Your Domino Domain name ttms01test.hyperv.goodexample.com <- Your fully qualified host name of the server) Details are documented by IBM here admin85.doc%2fh_checking_name_resolution_9400_steps.html admin85.doc%2fh_tcp_ip_error_messages_client_or_server.html 3 Upgrading from Earlier Versions of Good Mobile Messaging/Good Mobile Control Servers. 3.1 Best Practices Good Mobile Messaging software is designed for quick and easy upgrade. However, as with all mission-critical software, you will want to test and upgrade your Good Mobile Messaging Servers, Good Mobile Control Servers, and Good Mobile Messaging Client Software according to the best practices implemented in your IT organization. For example: 1. Although Good Mobile Messaging software is thoroughly tested, some organizations will choose to run Good Mobile Messaging Server, Good Mobile Control Server, and Good Mobile Messaging Client in a test environment before installation. Such testing can vary in length from a day up to a week. 2. Next, organizations with multiple Good Servers may choose to at first upgrade the Good Mobile Messaging Server and Good Mobile Control Server for a single GoodAdmin account with limited IT users/handhelds. In such a case, they may let the upgraded components run for up to a week. 3. After the server has been configured and operates correctly for a period of time, these organizations upgrade a larger number of handhelds as a pilot program. 4. Finally, the rest of the handhelds on the server are upgraded. 5. Using this conservative approach, the rest of the servers are upgraded to the new version. Each server runs for a day before the remaining handhelds are upgraded. Upgrade the Servers before the handhelds. 3

4 3.2 Performing the Upgrade To upgrade Good Mobile Messaging Server and Good Mobile Control Server, do the following. Upgrade the Servers before the handhelds. Note: For Domino health checks performed during Good Mobile Messaging Server installation or upgrade, add the GoodAdmin service account used for the installation to Security Settings > Local Policies > User Rights Assignment > Debug Programs. Use the following procedures to upgrade: Before starting the upgrade, stop the Lotus Domino Server service and Lotus Domino Diagnostics Service (8.5.x and above). Stop Good Mobile Control service and Good Messaging Domino Directory services. If GMM is installed on the same machine, also stop the Good Messaging Server and Good Server Domino Directory services Upgrading Good Mobile Control Server Note: Before upgrading, Lotus Domino Server must be stopped. Note: With this GMC version, GFE command-line utilities require Java 8. The Java upgrade (part of the GMC upgrade) will overwrite existing Java files and folders; the cert store will be overwritten with default certs. Back up any SSL certs before upgrading to this version; add these certs again after the upgrade is complete. 1. Launch installer. To do so, run setup.exe from the root of the installation setup.exe. An upgrade screen is displayed. 4

5 2. Upgrade the Good Mobile Control server first. Click Add/Remove. 3. For a fresh install, some component checks may display information as in the above screen. Click Install to continue. 5

6 4. A License Agreement window will display. Click Next to display the terms of the agreement. 5. Click Yes to accept the terms of the agreement. A Host Section screen is displayed. 6

7 6. Click the radio button for Use existing SQL server Instance on local machine, and click Next. 7. An Installed Instances screen is displayed. Click OK to locate a named instance. 7

8 8. Click on Next to locate database instances. 9. Click on Next button to display the GMC Registration form. 8

9 10. Click on Next after providing the license and serial number. A screen for setting a proxy is displayed. 11. Click on Next to display a directory source page. 9

10 12. Click on Next to display a database configuration page. 13. Click on Next button to get administrator login user page. 10

11 14. Click on Next for choosing automatic backup directory page. 15. Check the Disable automatic backup and click on Next button. 16. Click the OK button when prompted to disable automatic database backups. 11

12 17. Choose Yes and click on Next button. 18. Click on Next button. 12

13 19. Check the Start Good Mobile Messaging server and Click on Finish button to complete GMC upgrading Upgrading Good Mobile Messaging Server After upgrading Good Mobile Control Server, upgrade Good Mobile Messaging Server 1. Click on Add/Remove Program for upgrading Good Mobile Messaging server. 13

14 2. The upgrade screen will be displayed. 3. Choose Next. A License Agreement screen is displayed. Accept the agreement. 14

15 4. A screen is displayed upon which you choose whether the server is to primary or secondary. Choose Primary. 5. If you are using a proxy server for the GMM connection to the Internet, enter the required information on the next screen displayed. 15

16 Relay connectivity is now checked by the installation program. 6. A screen is displayed for Windows account information. 7. A database information screen is displayed. This is the database used by the Messaging Server. 16

17 When upgrading the GMM server, a new database is not created. The installer proceeds with the previous database only. If you enter any changed or invalid values on this screen, a warning is displayed. 8. Next, a screen is displayed for Good Mobile Control information. If a cold-failover backup GMC is being used, enter that GMC s information here. 9. Complete the remaining screens by Clicking Next. 17

18 10. Choose Finish. The Good Mobile Messaging Server upgrade is complete. You are returned to the initial installation screen. 18

19 4 Upgrading in a Cluster 4.1 Upgrading the Primary GMC Server in a Good Cluster Note :- Applies only Windows 2003 Server cluster Note: Before upgrading the primary server, make sure that the resources are owned by primary server and are offline. From the primary server host machine, launch the Microsoft Cluster Administrator. 1. Log on to primary server host machine. Launch the Microsoft Cluster Administrator. Make sure the primary server is the owner of all resources including the shared drive. If not, move the resources to the primary server. 2. Select the Cluster Group that contains the Good Server resource, Good Cache resource, and Good Mobile Control Server resource. 3. Right-click on each resource and choose Take Offline, or for each resource from the File menu choose Take Offline. 4. Now go to Windows Service Manager (type Services.msc in Start>>Run), and start SQL server(gmc) service manually. To upgrade GMC, the SQL service must be up and running. 5. Click on Setup.exe and install /upgrade the new version of Good Mobile Control Server. Do not start the service when prompted 6. Click on Setup.exe and install the new version of Good Mobile Messaging Server and complete the setup. Do not start the Good services when prompted. 7. From Start/Programs/Administrative Tools, launch the Services program. Verify that the Good service and Good Mobile Control service are not running and are set to Manual. If not, set the service to Manual. This setting is required. Note: During the upgrade process DONOT bring online the GMC services from the cluster administrator. After successful upgrade, start the GMC service from Windows Services Console, and confirm that it is working and GMC is running fine. Now Primary node is upgraded and running. 4.2 Upgrading the Standby GMC Server in a Good Cluster Note: Before upgrading the standby Server, ensure that the resources are owned by the standby Server and are taken off-line. Also stop/take off line the services from Node 1 and do a changeover to node 2. Also after successful upgrade of GMC on primary node, stop GMC service and SQL server for GMC service from Windows Services Console. 1. Log on to the secondary Server host machine and launch the Microsoft Cluster Administrator. Make sure that the secondary Server is the owner of all resources including the shared drive. If not, move the resources to the secondary Server. 2. Select the Cluster Group that contains the Good Server resource, Good Cache resource, and Good Mobile Control Server resource. 3. Right-click on each resource and choose Take Offline, or for each resource, from the File menu choose Take Offline. 4. Navigate to the directory on the shared Quorum Disk where the GMC Server is installed. Delete the file called emfdbfiles.lck. Important: Do not delete any other files. You must manually delete this file, which is created during the upgrade of the Primary GMC Server, before installing the Standby GMC Server. This file will be recreated when the Standby GMC Server starts up later. 19

20 5. Now go to Windows Service Manager (Type Services.msc in Start>>Run), and start SQL server(gmc) service manually. To upgrade GMC SQL service must be up and running. 6. Click on Setup.exe and install/upgrade the new version of Good Mobile Control Server. Do not start the service when prompted. 7. Click on Setup.exe and install the new version of Good Mobile Messaging Server and complete the set up. Do not start the Good services when prompted. 8. Verify that the Good service and Good Mobile Control service are not running and are set to manual. If not, set the services to Manual. The services must be set to manual. After successful upgrade start GMC service from Windows Services Console, and confirm that it is working and GMC is running fine. 9. From the Cluster Administrator, select the Cluster Group that contains the Good Cache lock resource and the Good Service resource. Right-click on the Cluster Group and choose Bring Online. 10. From the Cluster Administrator, select the group that contains the Good Mobile Control Service resource. Right-click on the group and choose Bring Online. The upgrade is complete and now node 2 is up. After this move the Group back to primary if needed. 4.3 Upgrading the Primary GMM Server in a Good Cluster Note :- Applies only to Windows 2003 Server cluster 1. All the resources are allocated to primary node; if not move the group to primary node. After successful upgrade of GMC, all the services including domino server resource must be up and running. 2. Prior to run the installation setup; bring down the domino server resource from cluster administrator, which will also bring down Good Messaging service and Good Domino Directory service. Make sure GMC server service is up and running. 3. Now launch GMM server setup and upgrade GMM as per admin guide. DONOT start Domino server service at the end of the installation. 4. After successful upgrade start GMM service from Windows Services console, and make it is working and GMM is running fine. Note: During upgrade process DONOT bring online GMM services from cluster administrator. Upgrade of GMM on primary node is completed. 4.4 Upgrading the Secondary GMC Server in a Good Cluster 1. After successful upgrade of GMM on primary node, stop GMM service, Good Domino Directory service, and Domino server service from Windows Services Console. 2. Now move all the resources to standby node from Cluster Administrator. Make sure all the Good-related resources are offline (from Cluster Administrator right-click on the resource name and click on Bring Offline) and cluster name, cluster IP, and shared drive are up and running. 3. Navigate to the directory on the shared Quorum Disk where the GMM Server is installed. Delete the lock file dbfiles.lck on the shared file server. By default the file is found in Q Drive and GMM Server\Cache Directory is located. 20

21 4. Launch GMM server setup and upgrade GMM as per admin guide. DONOT start Domino server service at the end of the installation. 5. After successful upgrade start GMM service from Windows Services console, and make it is working and GMM is running fine. Note: During upgrade process DONOT bring online GMM services from cluster administrator. Upgrade of GMM on standby node is completed. 1. Again after successful upgrade of GMM on standby node, stop GMM service, Good Domino Directory service, and Domino server service from Windows Services console. 2. Move all the resources to primary node from Cluster Administrator. 3. Right-click on GMM service, Good Domino Directory service, and Domino server resource and bring them online. Now check that GMM is running fine, and failover is also working fine. 5 Error Conditions Note: In extremely rare circumstances, upgrading the Good Mobile Messaging Server or Good Mobile Control Server may fail if for some reason the previous server installation parameters have been altered in the registry. If you encounter upgrade problems, use the following procedure: 1. Uninstall Good Mobile Messaging Server. When doing so, use the Typical uninstall option (or Preserve Users in older GoodLink Server versions). If uninstall fails, use Add/Remove Programs. 2. Install Good Mobile Messaging Server using the same cache directory, license key, and serial number as for your previous installation. 3. Upgrade handhelds to the most recent available version. Good Technology, Inc All rights reserved. Good, Good Technology, the Good logo, Good Mobile Messaging, Good Mobile Control, Good Mobile Connection, Good Mobile Intranet, Good Mobile Defense, Good Mobile Application Services, GoodAccess, GoodInfo, GoodLink, and Powered by Good are trademarks of Good Technology, Inc. All other trademarks and service marks contained herein are the property of their respective owners. Good Technology, Inc., and its products are not related to, sponsored by, or affiliated with Research In Motion Limited. For information concerning other intellectual property rights of Good and others, go to 21