Disaster recovery using NE configurations

12

It applies to scenarios in which no common method can quickly recover services interrupted due to a database issue (such as database loss).
Disaster recovery using NE configurations involves the following operations: load the configuration data script exported from the NMS to the NE, activate the script to initiate an NE reset so that the NE re-issues service data to all boards. In this way, NE configuration data is restored.
Compared with common recovery methods, this disaster recovery method uses the NMS script file as the data source.
Note:
Disaster recovery using NE configurations is highly risky. It may interrupt services. Therefore, you are advised to use this method only when necessary and under onsite assistance and instructions from Huawei engineers. Preferentially use common maintenance and recovery methods in case of a database damage issue.

Other related questions:
Policy-driven automatic disaster recovery supported by the OceanStor ReplicationDirector
The OceanStor ReplicationDirector (mainstream version: V100R003C10) supports policy-driven automatic disaster recovery by using Huawei disk array features (such as remote replication, snapshot, and three data centers in two cities) and VIS features (such as remote replication, snapshot, and mirror). Policy-driven automatic disaster recovery simplifies disaster recovery, reduces management complexity, and improves management efficiency. To implement disaster recovery, you only need to configure a disaster recovery policy based on your requirements. A disaster recovery policy defines the protection mode and scheduling policy that the disaster recovery system uses to provide protection for protected objects. A disaster recovery policy is created using the policy template when a protected group is created.

Applications scenarios supported by OceanStor ReplicationDirector in the disaster recovery data center solution (geo-redundant mode)
The disaster recovery data center solution (geo-redundant mode) supports the following applications: Mainstream databases: Oracle (RAC), Microsoft SQL Server (MSFC), and IBM DB2 (VCS and PowerHA) Mainstream application: Microsoft Exchange Server File system: NTFS Others: LUNs

Application types supported by OceanStor ReplicationDirector in the local protection solution
The local protection disaster recovery solution supports the following applications: Mainstream databases: Oracle (RAC), Microsoft SQL Server (MSFC), and IBM DB2 (VCS) Mainstream application: Microsoft Exchange Server Files system: NTFS Others: LUNs

Introduction to OceanStor ReplicationDirector in the local protection disaster recovery solution
The local protection disaster recovery solution uses snapshot technology to ensure local availability of host services. This solution can use VIS snapshots of protected objects to roll back data, preventing data loss and virus attacks. The OceanStor ReplicationDirector Server is installed on the DR management host deployed in the production center and the OceanStor ReplicationDirector Agent is installed on production application hosts to ensure DR data consistency. This solution supports the snapshot (array and VIS) technology.

Disaster recovery alarm monitoring supported by the OceanStor ReplicationDirector
The OceanStor ReplicationDirector (mainstream version: V100R003C10) supports disaster recovery alarm monitoring. The OceanStor ReplicationDirector monitors alarm reporting when disaster recovery resources go offline, objects in a protected group are not in the consistency protection relationship, data synchronization for protected groups fails, and RPO does not meet requirements.

If you have more questions, you can seek help from following ways:
To iKnow To Live Chat
Scroll to top