How to move data between two GroupWise Mobile Servers, version 3.

  • 7003508
  • 11-Jun-2009
  • 10-Dec-2013


Novell GroupWise 7
Novell GroupWise 8
Microsoft Windows 2000 Server
Microsoft Windows Server 2003 Standard Edition
Microsoft Windows Server 2003 Enterprise Edition
Novell GroupWise Mobile Server 3


Due to a HardWare issue or a purchase of new HardWare, there is a need to move GroupWise Mobile Server (GMS) data from an old to a new server. Here is a procedure how to do it in case of Windows edition of GMS using default ASA database. In case you use external database source, just point new GMS server to the external database server. Linux edition of GMS would have similar steps. 


Steps for a migration process:
A. Old / source server:
1. Stop the GMS suite from services window.
2. Start the CMD and navigate to the /DB directory
3. Here you need to find what ASA services are active and running. You can do it via command
dbsvc -q -l
It comes usually with the name of the old server.
4. Stop the ASA listed service by:
dbsvc -x <svc>
B. New server / target
1. Stop GMS suite from services window
2. Start the CMD and navigate to the /BIN directory.
3. Uninstall the GMS service by running:
<GMS HOME>\bin\syncserver -u (wait a few minutes for the service to finish)
<GMS HOME>\commsvr\bin\sg.exe -u
<GMS HOME>\commsvr\bin\commsrv.exe –u

4. Change to the /DB directory.
5. Here you need to find what ASA services are active and running. You can do it via command
dbsvc -q -l
It comes usually with the name of the old server.
6. Stop the ASA listed service by:
dbsvc -x <svc> 
7. Make copy of /DB and /PIM directories in a different directory from present, new GMS server
8. Copy /DB and /PIM directories from old / source sever on new / target GMS sever. Thanks to stopping ASA service you will be able to replace DBSync files, too.
9. Start on new server ASA service:
dbsvc -u <svc>
10. Change to the /BIN directory and install the GMS service
<GMS HOME>\bin\syncserver -i
<GMS HOME>\commsvr\bin\sg.exe –i
<GMS HOME>\commsvr\bin\commsvr.exe -i
11.Next go in the Windows Services window and for each GMS service do the following:
12.Right click on the service and open the Properties window.
13.Go on Log On tab check This Account checkbox and type the Administrator in the box and below his password. This is to assure the services will auto-start with the suite service as before the migration.
14.Restart the GMS services.

Now it shall be possible to start the Admin console from the new GMS server. After it starts, check following:
1. Under "Management \ Users" all "old server" users shall be displayed.
2. Under "Management \ Servers" there will be both a new and old servers. Set older one listed to Inactive or delete it. Make sure that new, current GMS server is set to Active still and it runs (if not start it from right-click menu option. Older server can be later deleted from a list.
3. Under "Profile Settings \ Email Accelerator \ Novell GroupWise" check if the default profile shows correct GW server settings. Those shall not be changed but rather verify it.
4. In Properties of "Intellisync Mobile Suite | Server Name| check or change the settings to the new GMS server IP / DNS.
5. In Properties of "Intellisync Mobile Suite | Authentication | Authentication sources" check the GW server settings - shall be OK as it was not changed.
6. Open an IE and type http://localhost/sgadmin
7. On the Admin Page go in Enterprise info.
8. On the Enterprise Page check the checkbox under the Enterprise Name and click on Remove Enterprise.
9. Restart the GMS service from Services window.
10. Go back to the Enterprise Page and verify if there is a new Enterprise Name listed.

In order to assure data integrity within newly imported databases, it is important to reset all imported user accounts. If this is not done, various duplicate issues, problems with installed mobile phone clients ... can happen.
Here is the rest of the procedure:
1. Start on a new GMS server Admin Console.
2. Launch WebAdmin from the console.
3. After WebAdmin console is opened, change the URL link by replacing "/admin/main.jsp..." with "/diag" (e.g., "http://x.x.x.x/admin/main.jsp;sessionid=....." becomes "http://x.x.x.x/diag" ).
4. In the main diag web page go in Cluster Wide Settings | Wireless Email.
5. Select "Reset All Accounts" web link.
After you have run Reset All Accounts, it might be necessary to reset mobile devices of migrated users. In case of the GMS3 server got new IP address, this needs to be passed to the end user. In case you use DNS entry, modify it to get to the new GMS server IP host address. 
Note that above procedure does not apply to GMS 2.x  version. In case you need to migrate data between two GMS 2.x server, please, follow the TID 7004099 How to move data between two GroupWise Mobile Servers, version 2.