9.4 Moving a Domain

You cannot use ConsoleOne to move a Domain object to a different location in the eDirectory tree because it is a container object. Only leaf objects can be moved. If you need to change the context, graft the GroupWise domain to its corresponding eDirectory object in the new container location. See Section 5.16, GW / eDirectory Association for more information about grafting objects.

You can, however, move the domain directory and the domain database (wpdomain.db) by copying the domain directory structure and all its contents to the new location.

IMPORTANT:Follow these instructions if you want to move a domain on a NetWare or Windows server to another directory on the same server or to a different NetWare or Windows server. If you want to move a domain located on a NetWare or Windows server onto a Linux server, see the GroupWise Server Migration Guide.

  1. Back up the domain, as described in Section 31.0, Backing Up GroupWise Databases.

  2. In ConsoleOne, browse to and right-click the domain to move, then click Properties to display the domain Identification page.

  3. In the UNC Path field, change the UNC path to the location where you want to move the domain, then click OK to save the new location.

    The location change is propagated throughout your GroupWise system.

  4. Stop the MTA and any gateways running for the domain.

  5. On Linux:

    1. In a terminal window, log in as root, then provide the root password.

    2. Use cp to copy the domain directory and database to the new location:

      cp -r domain_directory destination
      
  6. On Windows:

    1. Use xcopy with the /s and /e options to copy the domain directory and database to the new location:

      xcopy domain_directory /s /e destination
      

      These options re-create the same directory structure even if directories are empty.

    2. Give rights to all objects that need to access the domain database.

      For example, if the new location is on a different server, the Windows MTA and GroupWise administrators who run ConsoleOne need adequate rights to the new location, as described in Section 79.0, GroupWise Administrator Rights.

  7. Give rights to all objects that need to access the domain database.

    For example, if the new location is on a different server, the NetWare MTA and GroupWise administrators who run ConsoleOne need adequate rights to the new location, as described in Section 79.0, GroupWise Administrator Rights.

  8. Edit the MTA and gateway startup files to reflect the changes, then restart the MTA and gateways.

    See Section 41.1.7, Adjusting the MTA for a New Location of a Domain or Post Office.

  9. When you are sure the domain is functioning properly in its new location, delete the original domain directory and its contents.

If you need to move the MTA along with its domain, see Section 41.1.6, Moving the MTA to a Different Server.