Backup and Recovery Tip:
Backing Up and Restoring
Connectors on Exchange 2000

Posted: July 03, 2002

Introduction

Exchange 2000 includes several types of connectors that enable your Exchange
organization to communicate with the messaging systems of other companies. When the
correct connector is used, communication with another messaging system is not visible to
the Exchange user. However, if you install a connector for another messaging system,
you must perform additional steps when you back up and restore Exchange 2000.

Note: For more information about backing up and restoring Exchange 2000, see the
technical paper, Disaster Recovery for Microsoft Exchange 2000 Server.

Exchange 2000 Connectors

The following connectors for other messaging systems are included with Exchange 2000.

Lotus Notes. This connector has built-in messaging, directory synchronization,
and meeting request capabilities.

Microsoft Mail. The Microsoft Mail connector connects servers running Exchange
2000 to servers running Microsoft Mail. The directory on the server running Microsoft
Mail is synchronized to Microsoft Windows 2000 Active Directory® directory service
through the Microsoft Mail connector using the Microsoft Mail Directory Synchronization
protocol. One server (it can be either Exchange or MS Mail) is configured as a directory
synchronization requestor. The other server is configured as a directory synchronization
server. The directory synchronization requestor periodically polls the directory
synchronization server for any changes to the foreign directory and provides any
changes that have occurred to its own directory. The directory synchronization server
replies with the changes to its directory and updates its directory with the changes
provided by the requestor.

Lotus cc:Mail. This connector supports DB8-type cc:Mail post offices. Lotus
cc:Mail users are added to the Windows 2000 Active Directory as contacts or as mail enabled
users. Directory synchronization is built into the connector, and no additional
files are required to configure the synchronization.

Novell GroupWise. The Novell GroupWise connector provides messaging
connectivity, allows mail and directory synchronization between GroupWise and
Exchange, and supports calendar functionality, such as meeting requests.

Note: For more information about the Lotus Notes connector, Microsoft Mail connector,
cc:Mail connector, and Novell GroupWise connector, see Exchange 2000 online Help.

Backing Up and Restoring Exchange 2000 and Connectors to
Other Messaging Systems

The following procedure works for Exchange 2000 organizations that have installed
connectors for other messaging systems:

1. On a server running Exchange 2000 that is running one or more of the connectors
included with Exchange, configure the connectors according to the following
instructions and verify that they are functional.
§ Microsoft Mail connector. Back up the Microsoft Mail shadow post office that is in the subdirectory \connect\msmcon\maildata and its subdirectories.

§ cc:Mail connector. You do not need to back up the \ccmcdata directory
and subdirectories because the cc:Mail connector can recreate these after the
recovery process. However, you must back up and restore the cc:Mail import and
export files installed on your servers running Exchange because these are external
programs that interface with Lotus cc:Mail.

§ Lotus Notes connector. Back up the Lotus Notes client software,
including the software directory and configuration file, such as Notes.ini, on the
connector computer. The Lotus Notes client installation program installs the Lotus
Notes Windows 2000 Registry setting
(HKEY_LOCAL_MACHINE\SOFTWARE\Lotus\Notes), which you back up as part of
the Windows 2000 System State data in a later step.

§ Novell GroupWise connector. Ensure that GroupWise Gateway Network
Service can be restored correctly.

§ Lotus Notes and Novell GroupWise connectors. Back up \conndata
and its subdirectories. After the recovery process, erase the work files *.seq and
*.ck in the directory Conndata before starting the Lotus Notes or Novell GroupWise
services. The directory Conndata and its subdirectories contain the mapping rules
and correlation tables used by the connectors.

Note: To ensure that your data does not become outdated, back up
\Conndata\Tables frequently. If the correlation table is corrupted, the connector is
recreated, but much of the correlation information is lost.
2. Back up the Windows 2000 System State data by using the latest Backup utility
update that is included with Windows 2000.
3. Back up the Exchange 2000 storage groups on the server by using the Backup
utility that is included with Windows 2000.
4. Restart the computer and reinstall Windows 2000. Select a computer name that is
different from the original computer name.
5. Restore the Windows 2000 System State data on the computer on which you
reinstalled Windows, and then restart the computer.
6. Install Exchange 2000 in disaster recovery mode by typing the following file name
at the command prompt:
setup/disasterrecovery
Make sure to select each connector that you previously selected.
7. After setup is complete, restore all the Exchange storage groups.

Note: Select the Last Backup Set check box if you have a distinct file, or select the
Mount database after restore check box to mount the database.
8. Restart the computer and perform the following procedures for your connector:

§ Microsoft Mail connector: restore maildata to override the Microsoft Mail
shadow post office.

§ cc:Mail connector: restore the cc:Mail import and export files.

§ Lotus Notes connector: restore the Lotus Notes client program on the
server and verify that the Windows 2000 Registry setting of the Lotus Notes client
works by operating the Lotus Notes client program on the server running Lotus
Notes.

§ Novell GroupWise connector: after restoring the GroupWise Gateway
Network Service, verify that you can read and write files to the GroupWise API
directory.

9. Verify that the restored connectors start.

This tip is provided by the Microsoft Exchange User Education team.
For additional information, see the Microsoft TechNet Exchange Web site.