No relevant resource is found in the selected language.

This site uses cookies. By continuing to browse the site you are agreeing to our use of cookies. Read our privacy policy>Search

Reminder

To have a better experience, please upgrade your IE browser.

upgrade

OceanStor BCManager 6.5.0 eReplication User Guide 02

Rate and give feedback :
Huawei uses machine translation combined with human proofreading to translate this document to different languages in order to help you better understand the content of this document. Note: Even the most advanced machine translation cannot match the quality of professional translators. Huawei shall not bear any responsibility for translation accuracy and it is recommended that you refer to the English document (a link for which has been provided).
Microsoft Exchange Server

Microsoft Exchange Server

This section introduces the DR restrictions for Microsoft Exchange Server protected objects.

DR for Microsoft Exchange Server protected objects can be conducted only when related version requirements are met. Before starting DR for a Microsoft Exchange Server database protected object, read version restrictions and limits listed in Table 1-11.
Table 1-11  DR restrictions for Microsoft Exchange Server databases

Object

Restrictions and Limits

Compatibility

  • Microsoft Exchange Server: Exchange Server 2007, Exchange Server 2010, and Exchange Server 2013
  • Microsoft Exchange Server operating systems: Microsoft Windows 2008 and Microsoft Windows 2012.
  • DR for Microsoft Exchange Server protected objects is applicable to only standalone nodes, not to clusters.
  • In the DR Star network scenario, when you create an Exchange Server protected group, only the storage with DR Star is supported (V3 series V500R007C20 and later versions, Dorado series V300R002C00 and later versions).
For details about Microsoft Exchange Server compatibility, see the OceanStor BCManager 6.5.0 eReplication Compatibility List.

Recovery modes

Recovery can be performed from one standalone Microsoft Exchange Server database to another. It means that both the production and the DR databases are deployed in standalone mode.

Recovery operations

  • In the geo-redundant solution based on cascading replication (synchronous and asynchronous) or parallel replication (synchronous and asynchronous), reprotection cannot be implemented after services are switched over to the remote DR site.
  • In the geo-redundant solution based on cascading replication (asynchronous and asynchronous), reprotection cannot be implemented after services are switched over to the remote DR site.
  • Exchange 2007 does not support reprotection. For Exchange 2010/2013, if the database is "not started", reprotection cannot be implemented after a recovery.

Database files

DR for the protected objects provides protection for data files and log files of databases only if the LUNs or volumes storing the files are on the same storage device and belong to the same replication consistency group. In the DR Star network scenario, all protected files are required to be configured in one DR Star.

Others

  • Volume Snapshot Service (VSS) can be used to ensure the data consistency between Exchange Server databases. The prerequisite is that VSS services have been enabled on the Exchange Server operating systems.
  • During DR, Exchange Server 2010 and Exchange Server 2013 can be automatically started, but Exchange Server 2007 cannot.
  • The disk where the Agent's installation directory resides cannot be the disk used by the Exchange data files.
Translation
Download
Updated: 2019-05-21

Document ID: EDOC1100075861

Views: 10669

Downloads: 55

Average rating:
This Document Applies to these Products
Related Documents
Related Version
Share
Previous Next