--- Sjoerd Hooft's InFormation Technology ---

User Tools

Site Tools


This shows you the differences between two versions of the page.

Link to this comparison view

groupwisechangeserver [2013/04/23 21:40] (current)
sjoerd created
Line 1: Line 1:
 += Move GroupWise to Different Server =
 +== Introduction
 +What to do when you have to move groupwise from one server to another? Novell has a pretty good [[http://​​support/​php/​​cmd=displayKC&​docType=kc&​externalId=10024917&​sliceId=&​docTypeID=DT_TID_1_1&​dialogID=90822612&​stateId=0%200%2090820671|TID]] about it, which covers it pretty well. This overview is just as that TID, only with a few extras:
 +# Copy groupwise directories needing to be moved to the new server, Domain, PO, gateway or Software directory.
 +# Launch consoleone and connect to the domain database in its new location if primary otherwise connect to the primary database and make the below changes to the moved agents object properties in consoleone.  ​
 +# Modify the UNC paths for moved Domains and or Post offices properties in consoleone to reflect their new locations on the new server or volume.  ​
 +# In the Properties of the moved  MTA and or POA change the Network address to reflect the new servers IP address. ​
 +## Also check the log settings. They also point to the old server. In my opinion the best way to deal with it is to remove the old settings and set it up again later on.
 +# If a software directory resides on the new server go to tools / system operations / software directory management and add the new software directory location. ​ In groupwise 6.5.3 or later in the properties of the post office you can select the software directory for the post office or choice to have a setting of "not set." ​
 +# If the domain that was moved was a secondary domain you will be connected to the primary while modifying the UNC / IP / software directory and will need to rebuild the secondary that was moved in order that it receives the modifications to it's Wpdomain.db. ​ In consoleone highlight the secondary domain / right click / groupwise utilities / system maintenance / rebuild database. ​ If the moved domain was a primary you are connected to the moved domain while making the modifications and only need to rebuild any moved post offices.
 +# Rebuild moved post office databases to update the post office database with the above admin changes. ​ To do this connect to the owning domain / highlight the post office / right click / groupwise utilities / system maintenance / rebuild database.
 +# Install the groupwise agents to the new server. ​ Run an agent install from the AGENTS directory under your Software Distribution Directory. ​ You may want to create a software directory using the latest groupwise support packs which will allow you to install the latest version of the groupwise agents. ​ This is a very simple way to get the latest software running as well as update an agent from and earlier version of groupwise. If you are installing on a linux platform you can also run the configure option. This is especially true when you are installing a new service pack. 
 +# Delete and re-install to the new server any gateways that were running on the old server.
 +== Afterwards ==
 +* Setup logging again
 +* Check if everything is running:
 +OES3:~ # /​etc/​init.d/​grpwise status
 +Checking status [po.dom2] ​              done
 +Checking status [dom2] ​                 done
groupwisechangeserver.txt ยท Last modified: 2013/04/23 21:40 by sjoerd