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


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


OceanStor 2600 V3 Storage System V300R005 HyperMetro Feature Guide 06

"This document describes the implementation principles and application scenarios of theHyperMetro feature. Also, it explains how to configure and manage HyperMetro."
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).
Application Planning

Application Planning

Plan the application layer by following instructions in this section.

Planning the Oracle Database

Proper application partition and distributed data storage reduce the data traffic generated when Oracle RAC Cache Fusion reads and writes data in both DCs, further reducing private network traffic.

Application Partition

Applicable to scenarios where core service data is loosely related and upper-layer services can be isolated according to different applications. To prevent Cache Fusion from frequently transmitting data blocks among instances, the most effective solution is to store applications in different partitions, namely, to run different applications on different RAC instances for application isolation.

Data Partition

Applicable to scenarios where some applications' access to the data concentrates on a few tables. In this situation, it is difficult to isolate applications, and more refined optimization is required.

  • Partition tables according to the application types.

    Store the tables in different partitions to prevent a certain instance from using a certain partition or to achieve physically distributed data storage. For RAC applications, table partition is effective in reducing the possibility of hot data block contention.

  • Place the data of certain read-only access or the data generated by read-only access in a certain period in a read-only table space.

    When Cache Fusion is enabled, if a certain table space is read-only, access to the data in this table space can be performed locally and does not require coordination between RAC instances.

ASM Disk Groups
  • To improve file management efficiency and database performance, store different types of files in different automatic storage management (ASM) disk groups.
  • Oracle temporary table space is used to query and save buffer data and sort queried intermediate results. If there are a large number of "group by" query systems, you are advised to create an independent ASM disk group for the temporary table space to ensure that sufficient disk space is available and to improve query efficiency.
  • In Oracle RAC OLTP environments, to reduce the possibility of resource contention due to the storage of user data and system data on the same disk group, you are advised to dedicate two ASM groups respectively to the file where system table space and recovery table space reside and the file where user data resides.
  • When creating ASM disk groups, you must set redundancy levels as required. Two redundant ASM disks are configured at the storage layer. Unless there are special requirements for high availability, you are advised to set EXTERNEL redundancy for all disk groups except the disk group where Oracle RAC files are stored and use Huawei storage RAID 2.0+ technology and HyperMetro function for data protection.
Heartbeat and Cluster

Store the Oracle heartbeat information and cluster configurations in an independent HyperMetro LUN.

Planning the VMware Application

This section describes the principles for planning VMware services.

HyperMetro Consistency Group

If the space for a VM is allocated across datastores, all HyperMetro LUNs mapped to the host cluster must be added to the same HyperMetro consistency group. If cross-datastore space allocation is not used, you do not need to create a consistency group.

vMotion Network

vMotion network is a migration network defined by the virtual cluster. When VMs are migrated online between hosts, fast memory synchronization is required between hosts to achieve fast online migration. The latency must be less than 5 ms (the latency value varies with versions and 5 ms is the recommended value). The 10GE network is recommended.

Host Layer Configuration

When the VMware ESXi cluster is used with the HyperMetro solution, host layer parameters must be configured for the Permanent Device Loss (PDL) and All Paths Down (APD) scenarios.

Updated: 2018-09-03

Document ID: EDOC1000106183

Views: 28520

Downloads: 271

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