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

AMI Smart Meter Reading Solution V200R010C10 Planning and Design Guide

This document describes the overall and detailed design of functions and services in the AMI Smart Meter Reading Solution.
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).
Remote Disaster Recovery Design

Remote Disaster Recovery Design

As the AMI solution develops and is applied, electric power companies increasingly depend on the information system network to support various services, and more data is generated. Main service functions of the AMI solution depend on application systems, and device data is stored in databases of application systems. If application systems and databases are secure, the AMI service runs properly. How to ensure data security and how to provide secure, highly-efficient, reliable, and high-quality services are key issues of the AMI solution. Disaster recovery technology is used to ensure data and service security. The technology can prevent data loss to reduce economic losses, immediately restore application systems and communication networks, and ensure normal running of functions and services of application systems. To ensure data and service security of the AMI solution and improve system reliability, Huawei AMI solution integrates the remote disaster recovery solution to provide disaster recovery services.

Remote disaster recovery indicates that one or more sets of identical applications or databases are established in different areas. When a disaster occurs, data can be rapidly switched and services can be restored immediately. The remote disaster recovery solution uses the production center and disaster recovery center that are deployed in different areas. There must be reachable routes between the two centers so that data can be backed up. Each data center needs to be configured with all application systems and databases of the application layer of the AMI solution. Normally, the production center performs data and service exchange with terminals. When an exception occurs, an administrator determines whether faults can be rectified. If switching conditions are met, all services are switched to the disaster recovery center to ensure service running.

Remote Disaster Recovery Deployment

The remote disaster recovery solution can be deployed in the single-node system or cluster mode, and supports only server deployment. The solution uses the F5 load balancer to implement switching between the production center and disaster recovery center, causing high deployment costs. The solution is often used on a large-scale network where many terminals are deployed. The cluster deployment mode is recommended to ensure reliability. The F5 load balancer achieves switching between the production center and disaster recovery center and load balances services of application systems.

The production center and disaster recovery center are configured with complete AMI application systems, including the third-party application system (optional), EEM, DCP, and corresponding databases. The versions of application systems, operating system versions of servers, time zone and time settings, and software configurations of the two centers must be consistent. Application systems of the production center use its databases, and application systems of the disaster recovery center use its databases. The databases of the production center periodically back up data and synchronize data to the databases of the disaster recovery center to ensure data consistency and service running after an active/standby switchover.

DNS can be used to access the third-party application system and EEM. The DNS server needs to be deployed in the production center and disaster recovery center. Users can directly use domain names to access application systems and detect short service interruptions, but cannot detect the active/standby switchover.

Table 1-5 describes the solution deployment design.
Table 1-5  Remote disaster recovery deployment

Solution Selection

Deployment Mode

Deployment Solution

Number of Connected Smart Meters

Application System

Database

Load Balancing

Remarks

AMR solution

Server deployment

Single-node system

0-100,000

  • EEM
  • DCP

MySQL database in the single-node system

-

The production center and disaster recovery center are configured with the EEM, DCP, and MySQL database in the single-node system, and application systems of each data center share the MySQL database of the data center.

0-6,000,000

Oracle database in the single-node system

The production center and disaster recovery center are configured with the EEM, DCP, and Oracle database in the single-node system, and application systems of each data center share the Oracle database of the data center.

Cluster deployment

0-100,000

MySQL HA

F5 load balancer

The production center and disaster recovery center are configured with MySQL HA, and the EEM and DCP in each data center share the MySQL database.

0-6,000,000

  • Oracle RAC
  • Oracle HA

The production center and disaster recovery center can be configured with Oracle RAC or Oracle HA, and the EEM and DCP in each data center share the Oracle database. When there are more than 100,000 devices, Oracle RAC is recommended to ensure reliability.

Small-sized AMI solution

Server deployment

Single-node system

0-20,000

  • Third-party application system
  • EEM
  • DCP
  • Database of the EEM and DCP: MySQL database in the single-node system
  • Database of the third-party application system: Oracle database in the single-node system

-

The production center and disaster recovery center are configured with the third-party application system, EEM, DCP, Oracle database, and MySQL database. The EEM and DCP share the MySQL database, all applications are deployed in the single-node system, and the Oracle and MySQL database perform data backup.

  • Database of the EEM and DCP: Oracle database in the single-node system
  • Database of the third-party application system: Oracle database in the single-node system

In addition to the third-party application system, EEM, and DCP in the single-node system, the production center and disaster recovery center are configured with corresponding databases. The EEM and DCP share one database, and each database performs data backup.

Cluster deployment

  • Database of the EEM and DCP: MySQL HA
  • Database of the third-party application system: Oracle RAC or Oracle HA

F5 load balancer

The production center and disaster recovery center are configured with the third-party application system in cluster mode, EEM cluster, DCP cluster, and corresponding databases. The EEM and DCP share the MySQL database, MySQL HA is deployed, and the third-party application system uses Oracle RAC or Oracle HA.

  • Database of the EEM and DCP: Oracle RAC or Oracle HA
  • Database of the third-party application system: Oracle RAC or Oracle HA

The production center and disaster recovery center are configured with the third-party application system in cluster mode, EEM cluster, DCP cluster, and corresponding databases. Oracle RAC or Oracle HA is used, the EEM and DCP share the database, and the third-party application system uses an independent database.

Standard AMI solution

Server deployment

Single-node system

0-100,000

  • Third-party application system
  • EEM
  • DCP
  • Database of the EEM and DCP: MySQL database in the single-node system
  • Database of the third-party application system: Oracle database in the single-node system

-

The production center and disaster recovery center are configured with the third-party application system, EEM, DCP, Oracle database, and MySQL database. The EEM and DCP share the MySQL database, all applications are deployed in the single-node system, and the Oracle and MySQL database perform data backup.

0-6,000,000

  • Database of the EEM and DCP: Oracle database in the single-node system
  • Database of the third-party application system: Oracle database in the single-node system

In addition to the third-party application system, EEM, and DCP in the single-node system, the production center and disaster recovery center are configured with corresponding databases. The EEM and DCP share one database, and each database performs data backup.

Cluster deployment

0-100,000

  • Database of the EEM and DCP: MySQL HA
  • Database of the third-party application system: Oracle RAC or Oracle HA

F5 load balancer

The production center and disaster recovery center are configured with the third-party application system in cluster mode, EEM cluster, DCP cluster, and corresponding databases. The EEM and DCP share the MySQL database, MySQL HA is deployed, and the third-party application system uses Oracle RAC or Oracle HA.

0-6,000,000

  • Database of the EEM and DCP: Oracle RAC or Oracle HA
  • Database of the third-party application system: Oracle RAC or Oracle HA

The production center and disaster recovery center are configured with the third-party application system in cluster mode, EEM cluster, DCP cluster, and corresponding databases. Oracle RAC or Oracle HA is used, the EEM and DCP share the database, and the third-party application system uses an independent database. When there are more than 100,000 devices, Oracle RAC is recommended to ensure reliability.

Networking of the Remote Disaster Recovery Solution

The remote disaster recovery solution can be deployed in the single-node system or cluster mode, and only server deployment is supported. The AMR solution, small-sized AMI solution, and standard AMI solution support remote disaster recovery. The remote disaster recovery solution needs to use the F5 load balancer to implement service and network switching, but the costs are high. It is recommended that the remote disaster recovery solution be deployed in cluster mode. The remote disaster recovery solution in cluster mode does not support software load balancing, so application systems implement load balancing through the F5 load balancer.

Remote Disaster Recovery of the AMR Solution
Only the EEM and DCP of the AMR solution are deployed, and they can be deployed in the single-node system or cluster mode. The EEM and DCP of the production center share the database of the production center, the EEM and DCP of the disaster recovery center share the database of the disaster recovery center, and the production center and disaster recovery center have the F5 load balancer deployed. Server deployment is used as an example to describe the networking of remote disaster recovery, as shown in Figure 1-6.
Figure 1-6  Networking of remote disaster recovery
Remote Disaster Recovery of the Small-sized AMI Solution

The small-sized AMI solution is used when there are at most 20,000 smart meters. When remote disaster recovery is deployed, the application system selection, deployment precautions, and networking architecture are the same as those of the standard AMI solution. For details, see Remote Disaster Recovery of the Standard AMI Solution.

Remote Disaster Recovery of the Standard AMI Solution
The standard AMI solution supports server and VM deployment. If remote disaster recovery is deployed, only server deployment is supported. The remote disaster recovery solution can be deployed in the single-node system or cluster mode, and the application layer needs to be configured with the third-party application system. In addition to the EEM, DCP, and database, the production center and disaster recovery center need to be configured with the third-party application system and database and the F5 load balancer needs to be used to implement load balancing and active/standby switchover. Cluster deployment is used as an example to describe the networking of remote disaster recovery, as shown in Figure 1-7.
Figure 1-7  Networking of remote disaster recovery of the standard AMI solution
Translation
Download
Updated: 2019-03-07

Document ID: EDOC1100069579

Views: 5425

Downloads: 6

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