GroupWise 2014: disaster recovery, restoring GroupWise services to a newly installed server from backup

  • 7015335
  • 05-Jul-2014
  • 21-Jul-2014

Environment

Novell GroupWise 2014

Situation

GroupWise 2014: disaster recovery, restoring GroupWise services to a newly installed server from backup.

Resolution

Although there are many steps to consider during disaster recovery, this TID presumes the following conditions:
  • The new server has been installed.
  • The Domain and Post Office data directories have been restored to the new server from backup.


Follow the steps below to install and configure MTA(s) and POA(s) for the restored directories:

  1. See documentation to Install the GroupWise Server Software.

  2. See TID 7015336 - How to install, configure new agents for a pre-existing GroupWise system.

  3. Verify proper agent configuration by visiting the GroupWise Administration of this new server:
    Note: If there is a problem with settings not being realized, saved, or transferred, see Rebuilding Domain or Post Office Databases.
    • Domain/MTA (Administration | Domains, Administration | Message Transfer Agents),
      Post Office/POA (Administration | Post Offices, Administration | Post Office Agents):
      • Is the path to the domain and post office correct? General | Folder
      • Is the Network Address correct? Agent Settings | TCP/IP Address
      • Is there a User Name and Password for HTTP? Agent Settings | HTTP
      • Is the log directory valid? Log Settings | Log File Path
        Note: Leaving this path blank is fine as the default /var/log/novell/groupwise path will be used; however, an invalid path will prevent the agent from starting. The same applies for the SSL settings below.
      • Are the SSL Settings valid? SSL Settings

  4. Start GroupWise services:
    rcgrpwise start

  5. Launch the MTA and POA HTTP WebConsoles to verify the MTP Ports and Links appear as Open.
    Note: If any agents report MTP Ports or Links as Closed, see the involved agent log files for further troubleshooting details.

Feedback service temporarily unavailable. For content questions or problems, please contact Support.