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 SQL Server

Microsoft SQL Server

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

You must comply with version restrictions when implementing DR for a protected object supported by eReplication. Read description in Table 1-10 before implementing DR for a Microsoft SQL Server database.
Table 1-10  DR restrictions for Microsoft SQL Server databases

Object

Restriction

Compatibility

  • SQL Server 2008 and SQL Server 2012 are supported.
  • Supported SQL Server operating systems are Microsoft Windows Server 2008 and Microsoft Windows 2012.
  • SQL Server can be deployed in a single node or a WSFC cluster and on an NTFS. However, the file system cannot be created by using dynamic volumes.
  • In the DR Star network scenario, when you create an SQL 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 SQL Server compatibility, see the OceanStor BCManager 6.5.0 eReplication Compatibility List.

Recovery modes

  • Recovery can be performed from one standalone SQL Server database to another. It means that both the production and the DR databases are standalone.
  • Recovery can be performed from an SQL Server cluster to a standalone SQL Server database. It means that the production database is deployed in a cluster and the DR database is standalone.
  • Recovery can be performed from one SQL Server cluster to another. It means that both the production and the DR databases are deployed in a cluster. The number of nodes at the production and DR sites can be different.
  • Recovery can be performed from a standalone SQL Server database to a cluster only after DR reprotection in the cluster to one standalone SQL Server database and databases in the protected group cannot be added or removed after the DR reprotection.

Recovery operations

  • Active-passive DR solution

    The solution based on mirroring (VIS) and asynchronous replication (SAN) does not support reprotection.

  • Geo-redundant solution
    • In the solution based on cascading replication (synchronous and asynchronous) or parallel replication (synchronous and asynchronous), when services are switched over to the remote DR site, reprotection cannot be implemented.
    • In the solution based on cascading replication (asynchronous and asynchronous), when services are switched over to the remote DR site, reprotection cannot be implemented.
    • In the solution based on active-active (VIS) and asynchronous replication (SAN), when services are switched over to the remote DR site, reprotection cannot be implemented.
  • Local Protection

    In solutions based on clone (SAN), clones can only be used for data test or verification.

Database files

DR protection can be implemented for data files, online log files, and control files. The requirements are as follows:
  • All files must be deployed on the same Huawei storage device.
  • In an array-based replication protection scenario, if multiple remote replications are created for all storage resources used by files, it is recommended that all these remote replications be configured in 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 SQL Server databases. The prerequisite is that VSS services have been enabled on the SQL Server operating systems.
  • The disk where the Agent's installation directory resides cannot be the disk used by the SQLServer data files.
Translation
Download
Updated: 2019-05-21

Document ID: EDOC1100075861

Views: 13938

Downloads: 68

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