The Enterprise Relay Server Setup program allows you to upgrade from a previous ver-sion of relay server or to simply remove a previous verver-sion. If necessary, you can also re-install relay server manually. Both procedures are outlined in the following sections, along with general upgrade instructions:
• Upgrading from ERS 2.5x to ERS 3.0
• Upgrading a Relay Server (General Instructions)
• Manually Re-installing a Relay Server Upgrading from ERS 2.5x to ERS 3.0
Because ERS version 3.0 has a new queue store that is incompatible with the 2.5 store, the upgrade process from ERS 2.5x to 3.0 requires a manual export of the 2.5 data before run-ning the upgrade installer, and then a manual import process after the upgrade installation has completed. If you omit the manual export and import process, all data from the ERS 2.5 installation will be lost. After installing ERS 3.0 and starting the relay service, you must synchronize the newly upgraded relay server with the Enterprise Management Server (EMS).
Note: If you are upgrading both a relay and management server to version 3.0, upgrade the relay server before upgrading the management server. Also, note that the upgrade procedure below requires one of the following EMS builds (build num-bers appear in the lower right corner of the EMS administrative interface):
• EMS version 2.5j build 1825 (recommended).
• EMS version 3.0.4 build 2234 PRIME 10/27/04 or later. Verify the version on your CD media as this version string does not appear in the EMS UI.
Note: Allow about 1 hour per each 10 GB of queue store files for the relay export pro-cess to complete.
To export the 2.5 data and synchronize ERS 3.0 with the management server, follow these steps:
1. Do a full system backup.
2. Use DbWriteTest to confirm that volumes meet relay server requirements and to determine whether the hardware can support typical relay throughput, as described above in “Testing Relay Hardware Throughput with DBWritetest”.
3. Ensure that the Enterprise Management Server (EMS) is one of the following versions (build numbers appear in the lower right of the EMS window):
• EMS version 2.5j build 1825 (recommended).
• EMS version 3.0.4 build 2234 PRIME 10/27/04 or later. Verify the version on your CD media as this version string does not appear in the EMS UI.
4. Check the management server for relay-related alerts (including synchronization alerts). If any alerts appear, contact your Groove Networks support representative for information about clearing them.
5. Verify management-to-relay server SOAP communications as follows:
a. From the management server administrative Web interface, add a test user to a management domain group that is provisioned with this relay server.
b. Check the Application log in the Windows event viewer for a log entry that records the added user. If the expected log entry appears, go to the next sub-step.
c. If no log entry appears for the added user, you may have a management-relay server communications problem. Contact your Groove Networks support representative for information about resolving the condition.
d. From the management server’s SQL database, check that the GMSRelayJobs for EMS 2.5j (GMSJobs for EMS 3.0d) table is empty. (You can use the SQL Enterprise Manager and choose Return All Rows for the table.) If the table is empty, proceed with the upgrade process. If not, contact your Groove Networks support representative for assistance.
6. Backup (export) the Groove Relay service key, and backup all certificate files using the Relay Configuration Control Panel applet, as describe above in “Backing Up Relay Server Key Files”.
7. While the 2.5 relay server is running, go to the administrative Web pages and click the ‘Statistics’ link, then go to the ‘TotalQueues’ in the Queue/Store Stats section
and note the TotalQueue number (which will help you gauge the export progress later).
8. Shutdown the 2.5 relay server and disable the service from the Windows service control manager. Also, disable any error-recovery restart settings in the relay service control manager.
9. Export the 2.5 relay data by opening a command window from the relay server installation directory and typing the following:
RQExport –n –f PathName\RelayName-yymmdd where
PathName = Path to a location that has enough free space to export all the data in the Relay (typically 10 to 50 percent of the total space used by the RQS Store.xxx files).
RelayName-yymmdd = Any valid file name you chose.
-n = Switch for compatibility when upgrading from an older Relay version.
The RQExport may run for some time exporting data. Progress is reported as ‘X of Y queues exported’. X is the number of queues that have data and were exported;
while Y is the total number of queues examined so far. When Y equals the number you recorded from TotalQueues, the export is complete. Note the value of X for use during the import described later in this procedure.
10. To prevent operating system memory fragmentation during relay operation, set the following registry value:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager
HeapDeCommitFreeBlockThreshold=dword:00040000
The value is in hex. After setting this value, restart the operating system for the changes to take effect. For more about this setting, see the Microsoft Knowledge Base Article 315407.
11. Once the export completes successfully, reboot the relay server machine.
12. Install the Enterprise Relay Server version 3.0. Since you are upgrading from a 2.5 installation, the program warns you that manual export of the 2.5 data is necessary.
The RQExport procedure above is the manual export referred to.
Note: The installation should display the upgrade path (2.5 to 3.0). If an ‘upgrad-ing...’ message does not appear, cancel the installation and contact Groove Networks support.
Note: When prompted to confirm the FFQ directory, make sure that the FFQ direc-tory points to the biggest logical drive.
13. Before starting the newly installed 3.0 Relay for the first time, set the following registry values to prevent clients from connecting to the new ERS 3.0 installation before it has been synchronized with the management server:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Groove Relay\Parameters
HTTPPort=dword:00000000 Port=dword:00000001
SSLPort=dword:00000000
14. Set the version 3.0 relay service to Manual start, then start the service from the Windows service control manager.
15. Make sure that you can browse to the new relay server administrative Web page, (https://localhost:8010 or https://<relayname>.<domain>.com:8010).
16. Confirm EMS-ERS communications by doing the following:
a. From a command line prompt on the Enterprise Management Server (EMS), make sure that you can ping the ERS by name. For example: type the following:
ping ers.mycompany.com
Four replies should appear, similar to the following:
Reply from 192.168.1.100: bytes=32 time<10ms TTL=128 Reply from 192.168.1.100: bytes=32 time<10ms TTL=128 Reply from 192.168.1.100: bytes=32 time<10ms TTL=128 Reply from 192.168.1.100: bytes=32 time<10ms TTL=128
b. Make sure that you can telnet port 8009 from the management server to the relay server. For example, type the following:
telnet ers.mycompany.com 8009
A blank screen should appear (errors appear if the connection attempt fails) c. Press Ctrl-] to leave the command prompt.
d. Type quit [enter] to exit.
17. If you are running EMS version 2.5j build 1825, assure that the relay and management servers are synchronized by doing the following:
a. Synchronize the relay server with the 2.5j Enterprise Management Server(s) to which this relay is provisioned, by going to the applicable SQL server, loading the Enterprise Manager, and proceeding as described below.
b. Expand the appropriate EMS SQL database tree view, and choose ‘return all rows’ for the GMSRelayServer table (right-click the view, then choose ‘Open Table’ and ‘return all rows’).
c. Find the row that contains the relay server name under the DeviceUrl column whose Status column is 1 (not -1). Do NOT modify the Status column. If no relay has a Status of 1, STOP IMMEDIATELY, and contact Support.
d. Tab over several columns to RebuildUserDatabase and set the value to 1 for the relay server, then close the table.
e. From the management server administrative Web site, go to the Relay Server properties page in the domain where the relay server is provisioned and refresh the page. An Alert should appear.
f. Click the Relay tab and a Rebuild User Database button should appear next to the relay server in the EMS page. Click this button.
g. Go the relay server event log (using the relay server administrative Web pages or the Windows event viewer) and confirm that the relay server is receiving users from the management server, and wait for the relay event log to stop reporting that new users are being added. The Rebuild User Database button should disappear.
h. If the Rebuild User Database button does not disappear, change the relay purge interval by a day, in either direction (by clicking the relay server link in a management domain’s Relay Server set and editing the relay purge interval fields in the Properties window). Then re-click the Rebuild User Database button.When all users are added, you can reset the purge interval as desired.
For details about changing relay server purge intervals, see the Groove Management Server Domain Administrator’s Guide.
18. If you are running EMS version 3.0 build 2234, assure that the relay and managements servers are synchronized by doing the following:
a. From the management server administrative Web site, go to the Relay Server set in the domain where the relay server is provisioned.
b. Click the relay server link.
c. Change the relay purge interval by a day (in either direction), forcing the management server to contact the relay server and download users.
For details about changing relay server purge intervals, see the Groove Management Server Domain Administrator’s Guide.
d. Go the relay server event log (using the relay server administrative Web pages or the Windows event viewer) and confirm that the relay server is receiving users from the management server, and wait for the relay event log to stop reporting that new users are being added. The Rebuild User Database button should disappear. When all users are added, you can reset the purge interval as desired.
19. Shutdown the new 3.0 Relay Server and disable the service from the Windows service control manager.
This completes the special steps needed to upgrade a managed Relay. You can now continue with the instructions below and import the ERS 2.5 data that you exported.
20. Make sure that the 3.0 Relay service is not running.
21. Open a command window from the Relay installation directory and type the following:
22. RQImport –f PathName\RelayName-yymmdd
where PathName\RelayName-yymmdd is the path name that you supplied to the RQExport command. Progress is reported as “Importing queue N”. When N equals the last value of X reported from the RQExport command above, the import is complete.
23. Re-enable the port settings by deleting the three registry values that you created previously:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Groove Relay\Parameters
HTTPPort Port SSLPort
24. Set the version 3.0 relay service to manual start, then start the service from the Windows service control manager.
25. Monitor the event log for errors and ensure the Stats page shows users and devices connecting.
26. If the relay appears to be running correctly without errors, set the relay service Automatic start.
All previously existing data should now be available to Groove clients.
Upgrading a Relay Server (General Instructions)
To upgrade from a previous version of the Enterprise Relay Server (other than version 2.5x) or to remove a previous installation, follow these steps:
1. Stop the existing version of the relay service, from the Windows service manager.
2. From Windows, run the Groove Relay Setup.exe file to launch the installer wizard and follow the instructions.
3. If a window appears asking you to close a process in order to proceed, do so, then click Next. The install software detects when any of the following processes are running and displays a message requesting that you close it:
• Enterprise Relay Server
• Relay server configuration control panel applet
• Windows Control Panel
• Windows EventViewer
• Windows Performance Monitor (PerfMon)
• Windows Services window
4. Select an option from the Repair or Remove window. The options do the following:
• Repair/Upgrade - Replaces missing or currupt relay server files, saves relay registry entries, and updates software to the current relay server version.
Note: The repair process saves existing relay registry entries as is; they are not updated.
• Remove - Uninstalls the existing version of the relay server.
5. Follow the installer wizard to the end, then click Finish to re-install the relay server.
6. Restart the relay service from the Windows service manager.
Manually Re-installing a Relay Server
To re-install a relay server manually, follow these steps:
1. Stop the relay service using the Windows service manager. If this is not successful, do the following:
a. Set the Service Startup mode to Disabled then kill the relay process (relay.exe) using the Task Manager. You may need to give your local administrator account debugging privileges in order to kill the process via the Task Manager.
Or, you can download a program, such as Sysinternal's Process Explorer, that already has the correct permissions to kill a service process. Process Explorer (Copyright © 1998 - 2001 Mark Russinovich) is available at: http://
www.sysinternals.com/ntw2k/freeware/procexp.shtml
b. If the service still does not stop, try restarting the machine.
c. If you disabled the service, remember to re-enable it when you are finished.
2. Run regedit.exe and use the Registry/Export command to backup all the files and directories, as described in “Backing Up Initial Relay Server Key Files” of the Getting Started section of this guide. Make sure to backup all values under these keys:
• HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Groove Relay\Parameters
• HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Groove Relay\ManagementServer
3. Use the Windows Control Panel to uninstall (remove) the Groove Relay application.
Note: If you uninstall the relay service while it is running, restart the relay server machine before re-installing the service.
4. Run the Groove Relay Setup.exe file for the new version of the relay server and follow the relay install instructions in “Installing and Configuring a Relay Server”.
Note: When the installer launches the relay server configuration control panel applet at the end of the installation process, do NOT reconfigure the server settings. Just press Cancel to exit the control panel applet. In the next step, the server configuration will be restored from the backed-up registry keys.
5. Restore to the relay registry all of the files and directories, including the two keys, that you backed up in step 2:
• HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Groove Relay\Parameters
• HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Groove Relay\ManagementServer
6. After the installation, using the Windows services manager, adjust the server startup parameters, and verify the other server settings.
Caution: Do not generate any new relay server private key and certificate files, SOAP key and ID files, and SSL key and certificate files. Doing so will perma-nently prevent existing Groove clients from accessing the relay server.