CN115297129B

CN115297129B - Method and device for establishing data communication network

Info

Publication number: CN115297129B
Application number: CN202210920645.1A
Authority: CN
Inventors: 王见广
Original assignee: Bank of China Ltd
Current assignee: Bank of China Ltd
Priority date: 2022-08-02
Filing date: 2022-08-02
Publication date: 2024-04-16
Anticipated expiration: 2042-08-02
Also published as: CN115297129A

Abstract

The invention discloses a method and a device for establishing a data communication network, which relate to network security, wherein the method comprises the following steps: setting up a strong synchronous standby machine of the same city machine room in a mode of reworking the standby machine; and canceling the first DCN which is currently used, and creating a second DCN on the strong synchronous standby machine, wherein the second DCN is used for preparing the DCN in a different disaster or daily accounting DCN. The invention can realize the quick realization of building the DCN under the distributed database architecture for preparing the DCN in different places or daily accounting DCN. If a problem exists, the cause of the problem can be known quickly; the return state can be quickly changed and inquired; the impact of the increase in sudden DCN delay on the pinching action can be reduced.

Description

Method and device for establishing data communication network

Technical Field

The present invention relates to the field of network security technologies, and in particular, to a method and an apparatus for establishing a data communication network.

Background

The processing method of DCN (Data Communication Network ) based on the construction of different disaster recovery and daily information under the distributed architecture has business requirements that static data of a database needs to be acquired at a certain time point, business operation is performed by utilizing the static data, and the operation of acquiring the static data cannot affect main business.

This series of operations is not only complicated and time-consuming, but also prone to error.

The prior art has the defect that the DCN cannot be quickly built under the distributed database architecture at present.

Disclosure of Invention

The embodiment of the invention provides a data communication network establishment method, which is used for solving the problem that DCN (direct current network) establishment cannot be realized quickly under a distributed database architecture, and comprises the following steps:

setting up a strong synchronous standby machine of the same city machine room in a mode of reworking the standby machine;

and canceling the first DCN which is currently used, and creating a second DCN on the strong synchronous standby machine, wherein the second DCN is used for preparing the DCN in a different disaster or daily accounting DCN.

The embodiment of the invention also provides a data communication network establishment device, which is used for solving the problem that DCN can not be quickly established under a distributed database architecture, and comprises the following steps:

the standby machine module is used for building a strong synchronous standby machine of the same city machine room in a mode of reworking the standby machine;

and the DCN module is used for canceling the first DCN which is currently used, creating a second DCN on the strong synchronous standby machine, wherein the second DCN is used for preparing the DCN in a different place disaster or daily accounting DCN.

The embodiment of the invention also provides computer equipment, which comprises a memory, a processor and a computer program stored on the memory and capable of running on the processor, wherein the processor realizes the data communication network establishment method when executing the computer program.

The embodiment of the invention also provides a computer readable storage medium, wherein the computer readable storage medium stores a computer program, and the computer program realizes the data communication network establishment method when being executed by a processor.

The embodiment of the invention also provides a computer program product, which comprises a computer program, and the computer program realizes the data communication network establishment method when being executed by a processor.

In the embodiment of the invention, compared with the technical scheme that the functions of restarting a standby machine and building a DCN can not be realized quickly in the prior art, the method can only be used for clicking operation on a graphical interface through the existing platform, and the method can be used for building a strong synchronous standby machine of a same city machine room in a mode of restarting the standby machine first, then creating a second DCN for preparing the DCN or daily accounting DCN in a different place on the strong synchronous standby machine, and is not limited to the steps of acquiring static data of a database, performing business operation by a developer and recovering the database to an active state, and is also not limited to the steps of clicking operation on the graphical interface only through the existing platform, so that the DCN can be quickly realized to build the DCN for preparing the DCN or the daily accounting DCN in a different place under a distributed database architecture.

Furthermore, as the shell script is used for calling the OSS interface to operate, a certain operation risk can be avoided, the DCN interruption time is not too long, otherwise, the risk that the DCN library catches up with the production library exists, the DCN can be rebuilt more quickly in a script mode, and if a problem exists, the cause of the problem can be known quickly;

further, when the DCN is rebuilt, the value of bendcnslave (becoming a DCN standby machine) of zk information is changed, the change state is inquired, the whole operation is complicated, the zk information is changed in a script mode, and the return state can be quickly changed and inquired;

further, since the DCN delay needs to be confirmed when the DCN is canceled by the pinching operation, the influence on the operation of the information service is evaluated, and the DCN delay does not exceed a predetermined time, for example, 2 seconds, the DCN delay is confirmed by means of a script, it can be considered that the time difference between the pinching operation and the DCN delay evaluation is almost not large, and the influence of the sudden increase of the DCN delay on the pinching operation can be reduced.

Drawings

In order to more clearly illustrate the embodiments of the invention or the technical solutions in the prior art, the drawings that are required in the embodiments or the description of the prior art will be briefly described, it being obvious that the drawings in the following description are only some embodiments of the invention, and that other drawings may be obtained according to these drawings without inventive effort for a person skilled in the art. In the drawings:

fig. 1 is a schematic diagram of an implementation flow of a DCN establishment method according to an embodiment of the present invention;

fig. 2 is a schematic diagram of a DCN establishment architecture according to an embodiment of the present invention;

fig. 3 is a schematic diagram of a DCN establishment procedure in an embodiment of the present invention;

fig. 4 is a schematic structural diagram of a DCN establishment apparatus according to an embodiment of the present invention;

FIG. 5 is a schematic diagram of a computer device according to an embodiment of the present invention.

Detailed Description

For the purpose of making the objects, technical solutions and advantages of the embodiments of the present invention more apparent, the embodiments of the present invention will be described in further detail with reference to the accompanying drawings. The exemplary embodiments of the present invention and their descriptions herein are for the purpose of explaining the present invention, but are not to be construed as limiting the invention.

The inventors noted during the course of the invention that:

the DCN processing method based on the distributed architecture for building the strong synchronous backup machine of the same city machine room, building the different disaster recovery and daily accounting has the service requirement that static data of a database needs to be acquired at a certain time point in the early morning every day, the static data is utilized for carrying out service operation, and the operation of acquiring the static data cannot influence the main service.

Generally, the method comprises the following three steps of acquiring static data of a database at a certain early morning time point, performing business operation by a developer and recovering the database to an active state. This series of operations is not only complicated and time-consuming, but also prone to error.

At present, under the distributed database architecture, the functions of quickly realizing the redo machine and building the DCN cannot be realized, clicking operation can be performed on a graphical interface only through the existing platform, batch processing should be performed as quickly as possible aiming at the systematic operation, and when the graphical interface is abnormal, further analysis is performed, modification and maintenance cannot be performed directly according to the reported error information, so that the problems that the quick batch processing cannot be realized and the error log is obtained on the query task progress are solved.

Based on this, in the embodiment of the invention, a processing scheme of building a strong synchronous standby machine of a co-city machine room, building a remote disaster preparation and a DCN of daily information under a distributed architecture is provided, and the functions of reworking the standby machine, creating the remote disaster preparation DCN and creating the daily information DCN are realized by quickly calling an OSS (Object Storage Service ) interface through shell scripts, and the information such as quickly inquiring the operation state and evaluating DCN delay change zk information can be provided.

The following description is made with reference to examples.

Fig. 1 is a schematic flow chart of an implementation of a DCN establishment method, as shown in fig. 1, may include:

step 101, building a strong synchronous standby machine of a same city machine room in a mode of reworking the standby machine;

step 102, canceling the first DCN used currently, and creating a second DCN on the strong synchronous standby machine, wherein the second DCN is used for preparing the DCN in a different disaster or daily accounting DCN.

Specifically, the scheme mainly realizes the following two aspects:

1. and developing a redo backup machine script, wherein a data operator can remotely operate on the file server, redo the strong synchronous backup machine by calling an OSS interface in a redo backup machine mode, and if binlog is disabled, redo all backup machines.

Binry log (Binary log), binlog for short. Binlog is a binary log that records all data table structure changes and table data modifications, and does not record select and show operations. Binlog is recorded in the form of events and also includes the time spent executing a statement. Binlog is the MySql Server's own Log, but redox Log is based on the unique Log of the InnoDB engine.

The most important use scenario of the Binlog log is master-slave replication, and the Binlog function is started in the master library, so that the master library can transmit the Binlog to the slave library, and after the slave library is taken to the Binlog, data recovery is realized to achieve master-slave data consistency.

2. And creating a DCN script, wherein a data operator can remotely operate through a file server, and a plurality of databases can simultaneously create the DCN by calling an OSS interface. Each database instance builds a remote disaster relief or daily information DCN by means of creating the DCN.

In the development process, the DCN delay can be evaluated, zk information is changed when the DCN is rebuilt, the development of the redo machine script and the creation of the DCN script can be realized through the script, and the time and the artificial error rate can be shortened.

Fig. 2 is a schematic diagram of a DCN establishment architecture, and as shown in fig. 2, at least one functional architecture capable of implementing DCN establishment may include:

1. and (5) a redo backup machine module: and (5) setting up a strong synchronous standby machine of the same city machine room in a mode of reworking the standby machine.

2. Reconstructing a DCN module: and building a remote disaster backup or daily information DCN by a DCN creation mode.

To realize the two functions, a strong synchronous standby machine of the same city machine room is built in a mode of reworking the standby machine, the DCN delay is estimated, the remote disaster recovery or daily information DCN is built in a mode of building the DCN, and zk information is changed in the reconstruction process.

The specific implementation will be further described below.

In an embodiment, a batch processing scheme under a distributed architecture is provided, and by calling an OSS interface, a standby machine is reconstructed, and a DCN is reconstructed, which mainly includes:

1. the method comprises the steps of setting up a strong synchronous backup machine of a same city machine room in a backup machine mode, calling the os interface to the backup machine, taking the task ID and the return value of the backup machine, judging whether the backup machine is successful or not, if so, inquiring the progress of the backup machine by using the task ID, if not, checking the corresponding log, and judging the error reason.

That is, in implementation, after the strong synchronous standby machine of the same city machine room is built by a mode of reworking the standby machine, the method further comprises the following steps:

if the redo machine is successful, inquiring the progress of the redo machine by using the task ID;

if the backup machine fails, checking the corresponding log, and determining the error reason.

In practice, strongly synchronized replication: the application initiates an update request, after the Master (host) finishes the operation, the data is copied to the Slave (standby), after the Slave receives the data, successful information is returned to the Master, and after the Master receives the feedback of the Slave, the Master responds to the application. The Master copies data to the Slave in synchronization.

The strong synchronous replication requires that any one answer to the request of service success is successful in at least one standby machine in addition to the host machine. So that after a request arrives at the host, the request is sent to the standby machine immediately, and after one of the two standby machines is successful in response, the host machine can respond to the success of the service. That is, any request that successfully responds to the front-end service must have two copies, one on the primary node and the other on the backup node. Therefore, strong synchronization is a critical guarantee for multiple copies of data.

In implementation, the shell script invokes the OSS interface to perform one or a combination of the following operations:

the method comprises the steps of restarting the machine, canceling a first DCN which is currently used and creating a second DCN.

Specifically, an OSS (Object Storage Service ) interface is quickly called through shell scripts, so that a redo machine is realized;

canceling DCN, calling OSS interface to cancel DCN synchronous task;

by invoking the OSS interface, multiple databases are allowed to create DCNs simultaneously.

In practice, shell is commonly known as Shell (used to distinguish from core) in computer science, and refers to "software (command interpreter, command parser) that provides an operation interface for a user". It is similar to command. Com and later cmd. Exe under DOS. It receives the user command and then invokes the corresponding application.

It is also a programming language. As a command language, it interactively interprets and executes a command input by a user or automatically interprets and executes a series of commands set in advance; as a programming language, it defines various variables and parameters and provides many control structures that are unique in high-level languages, including loops and branches.

OSS (Object Storage Service, object store service) is a mass, secure, low cost, highly reliable cloud storage service provided.

OSS has a RESTful API (REST style API, meaning REST is an architectural style, programming language independent, platform independent, HTTP is used as a transport protocol) interface that can store and access any type of data at any application, at any time, at any place.

Massive data can be easily moved into or out of OSS using a provided API (Application Programming Interface ), SDK (Software Development Kit, software development kit) interface, or OSS migration tool. After the data is stored in the OSS, standard storage (Standard) can be selected as a main storage mode of mobile applications, large websites, picture sharing or hot spot audio and video, and low-frequency access storage (Infrequent Access) and Archive storage (Archive) with lower cost and longer storage period can be selected as storage modes of infrequently accessing the data.

Storage type (Storage Class):

OSS provides standard, low frequency access, archival three storage types, covering a wide variety of data storage scenarios from hot to cold. Wherein the standard storage type provides highly reliable, highly available, high performance object storage services capable of supporting frequent data access; the low-frequency access storage type is suitable for long-term storage of data which is not frequently accessed (average access frequency of 1 to 2 times per month), and the storage unit price is lower than that of the standard type; the archive storage type is suitable for archive data which needs to be stored for a long period of time (more than half a year is recommended), and the unit price is the lowest among the three storage types. For details, please refer to the storage type introduction.

Storage space (socket):

a storage space is a container for storing objects (objects), all of which must be affiliated with a certain storage space. The storage space has various configuration attributes including region, access rights, storage type, etc. Different types of storage space can be created to store different data according to actual requirements. For creating the storage space, please refer to creating the storage space.

Object/file (Object):

an object is a basic unit of OSS storage data, also known as a file of OSS. The Object is composed of Meta information (Object Meta), user Data (Data), and a file name (Key). The object is identified by a unique Key within the memory space. The object meta-information is a set of key value pairs, which represents some attributes of the object, such as last modification time, size, and the like, and can store some custom information in the meta-information.

Region (Region):

the territory represents the physical location of the data center of the OSS. The appropriate zone creation socket may be selected based on the cost, the source of the request, etc.

Access domain name (Endpoint):

endpoint represents the domain name that the OSS accesses to an external service. OSS provides services externally in the form of HTTP RESTful API, requiring different domain names when accessing different regions. The domain names required to access the same region through the intranet and extranet are also different.

Access key (AccessKey):

the Access Key (AK) refers to Access Key Id and Access Key secret used in access identity authentication. OSS verifies the sender identity of a request by using an AccessKeyId and AccessKeySecret symmetric encryption method. The Access Key Id is used for identifying the user; access Key secret is the key that the user uses to encrypt the signature string and the OSS uses to verify the signature string, and must be kept secret.

2. The reconstruction of DCN can be divided into four steps:

first, evaluate DCN delay, if delay does not exceed 2 seconds, consider that DCN cancellation can be performed;

secondly, canceling the DCN, calling an OSS interface to cancel the DCN synchronous task, taking the task ID and the return value of canceling the DCN, judging whether canceling the DCN is successful or not, if so, inquiring the progress of canceling the DCN by using the task ID, if not, checking a corresponding log, and judging the error reason;

thirdly, changing zk information, acquiring and changing the value of bendcnslave (becoming a DCN standby machine), and changing the value from 1 to 0;

fourth, create DCN synchronous task, take task ID and return value to create DCN, judge whether to create DCN successfully, if successful, use task ID to inquire the progress of creating DCN, if failed, check corresponding log, judge error cause.

That is, in implementation, before canceling the first DCN that is currently in use, further includes:

and evaluating the delay of the first DCN, and if the delay does not exceed the preset time, canceling the first DCN.

In an implementation, after canceling the first DCN that is currently used, the method further includes:

if the first DCN is successfully canceled, inquiring the progress of canceling the first DCN by using the task ID;

if the first DCN is failed to be canceled, the corresponding log is checked, and the error reason is determined.

the zk information is changed to not already be a DCN standby machine.

In an implementation, after creating the second DCN, further includes:

if the second DCN is successfully created, inquiring the progress of creating the second DCN by using the task ID;

if the second DCN is failed to be established, the corresponding log is checked, and the error reason is determined.

In practice zk is a file directory in which only small amounts of data can be stored. Each node (each file or folder) in a directory is referred to as a node. The connections on a node are referred to as servers or clients, which possess the ability to create a node, and clients have the ability to monitor the node, which may be referred to as connections, because each connection has the ability to create and monitor. The created node may be persistent, and the server is not deleted after disconnection; or short (ephemeral), and automatically deleting after the server is disconnected; the nodes (nodes) created may or may not be ordered. When the node changes, the node is pushed to the corresponding monitoring client.

Session refers to a client Session. The external service port of the ZK is 2181 by default, when the client starts, a TCP (Transmission Control Protocol ) long connection is first established with the ZK server, and from the first link establishment, the life cycle of the session of the client is also started, through this long connection, the client can maintain an active session with the server through heartbeat detection, can also send a request to the ZK server and receive a response, and can also receive a watch time notification from the server through this connection.

The SessionTimeout value of Session is used to detect the timeout of a client call. When the client is disconnected due to the fact that the server is too high in pressure, the network malfunctions or the client is disconnected actively, the Session created before is still valid as long as the client can restart to connect any one of the servers in the upper cluster within the time specified by the Session Timeout.

The file system of the ZK adopts a tree structure hierarchical directory structure, which is very similar to the Unix file system. Each directory is called a ZNode in ZK, and each ZNode has a unique path identifier, i.e. name. The ZNode may contain data and child znodes (temporary nodes cannot have child znodes). The data in ZNode can have multiple versions, so the data under a certain path needs to be queried with version number. The client application may set up a monitor (watch) on the ZNode.

ZK realizes a publish-subscribe mode through a watch mechanism, ZK provides a publish-subscribe function of distributed data, a publisher can enable a plurality of subscribers to monitor a certain subject object at the same time, when the state of the subject object changes, all subscribers are notified, so that the subscribers can make corresponding processing, and the ZK introduces the watch mechanism to realize the distributed notification function. ZK allows clients to register a watch with the server, and when a number of specified events at the server trigger the watch, an event notification is sent to the specified client. And this event notification is done through the Session of the TCP long connection.

ZK is a cluster of servers, a leader, and followers. The leader provides a read-write service, and machines other than the leader can only provide a read service.

Each server stores all data of a data copy to be consistent, the distributed read follower forwards the writing by the leader real-time update request, the leader real-time update request is sequentially carried out, the update requests from the same client sequentially execute data update atomicity according to the sending sequence, and the data update is successful or fails in sequence. Globally unique data view, clients are consistent real-time no matter which server the clients are connected to, and clients can read up-to-date data within a certain event range.

FIG. 3 is a schematic diagram of a DCN establishment procedure, and as shown in FIG. 3, batch processing under a distributed architecture may include:

step 301, setting up a strong synchronous standby machine of a same city machine room in a mode of reworking the standby machine;

step 302, building a remote disaster backup or daily information DCN by means of creating the DCN.

The embodiment of the invention also provides a data communication network establishment device, as described in the following embodiment. Because the principle of the device for solving the problem is similar to that of the data communication network establishment method, the implementation of the device can refer to the implementation of the data communication network establishment method, and the repetition is omitted.

Fig. 4 is a schematic structural diagram of a DCN establishment apparatus, and as shown in fig. 4, may include:

the standby module 401 is configured to build a strong synchronous standby machine of the same city machine room by reworking the standby machine;

the DCN module 402 is configured to cancel a first DCN currently used, and create a second DCN on the strongly synchronized standby, where the second DCN is used for preparing a DCN in a different disaster area or a daily accounting DCN.

In the implementation, the standby machine module is further used for calling an OSS interface to redo the standby machine through the shell script; and/or the number of the groups of groups,

the DCN module is further used for calling the OSS interface through the shell script to cancel the first DCN currently used or create the second DCN.

In implementation, the backup module is further configured to query the progress of the rework machine by using the task ID if the rework machine is successful after the strong synchronous backup of the same city machine room is built by using the rework machine; if the backup machine fails, checking the corresponding log, and determining the error reason.

In an implementation, the DCN module is further configured to evaluate a delay of the first DCN before canceling the first DCN that is currently in use, and cancel the first DCN if the delay does not exceed a preset time.

In implementation, the DCN module is further configured to query, after canceling the first DCN currently used, a progress of canceling the first DCN with the task ID if canceling the first DCN is successful; if the first DCN is failed to be canceled, the corresponding log is checked, and the error reason is determined.

In an implementation, the DCN module is further configured to change zk information to not already become a DCN standby after canceling the first DCN that is currently used.

In implementation, the DCN module is further configured to query, after the second DCN is created, a progress of creating the second DCN with the task ID if the creating of the second DCN is successful; if the second DCN is failed to be established, the corresponding log is checked, and the error reason is determined.

In implementing the technical scheme provided by the embodiment of the invention, the method can be implemented as follows.

FIG. 5 is a schematic diagram of a computer device, as shown in FIG. 5, including:

the processor 500, configured to read the program in the memory 520, performs the following procedures:

canceling a first DCN which is currently used, and creating a second DCN on a strong synchronous standby machine, wherein the second DCN is used for preparing the DCN in a different disaster or daily information DCN;

a transceiver 510 for receiving and transmitting data under the control of the processor 500.

In implementation, after the strong synchronous standby machine of the same city machine room is built by a mode of reworking the standby machine, the method further comprises the following steps:

In an implementation, before canceling the first DCN that is currently used, the method further includes:

the zk information is changed to not already be a DCN standby machine.

In an implementation, after creating the second DCN, further includes:

Wherein in fig. 5, a bus architecture may comprise any number of interconnected buses and bridges, and in particular one or more processors represented by processor 500 and various circuits of memory represented by memory 520, linked together. The bus architecture may also link together various other circuits such as peripheral devices, voltage regulators, power management circuits, etc., which are well known in the art and, therefore, will not be described further herein. The bus interface provides an interface. The transceiver 510 may be a number of elements, i.e., including a transmitter and a receiver, providing a means for communicating with various other apparatus over a transmission medium. The processor 500 is responsible for managing the bus architecture and general processing, and the memory 520 may store data used by the processor 500 in performing operations.

In the technical scheme provided by the embodiment of the invention, a strong synchronous standby machine of the same city machine room is built in a mode of reworking the standby machine; and building a remote disaster backup or daily information DCN by a DCN creation mode.

It will be appreciated by those skilled in the art that embodiments of the present invention may be provided as a method, system, or computer program product. Accordingly, the present invention may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects. Furthermore, the present invention may take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, and the like) having computer-usable program code embodied therein.

The present invention is described with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems) and computer program products according to embodiments of the invention. It will be understood that each flow and/or block of the flowchart illustrations and/or block diagrams, and combinations of flows and/or blocks in the flowchart illustrations and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.

These computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture including instruction means which implement the function specified in the flowchart flow or flows and/or block diagram block or blocks.

These computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.

The foregoing description of the embodiments has been provided for the purpose of illustrating the general principles of the invention, and is not meant to limit the scope of the invention, but to limit the invention to the particular embodiments, and any modifications, equivalents, improvements, etc. that fall within the spirit and principles of the invention are intended to be included within the scope of the invention.

Claims

1. A method of establishing a data communication network, comprising:

canceling a first data communication network DCN which is currently used, and creating a second DCN on a strong synchronous standby machine, wherein the second DCN is used for preparing the DCN in a different disaster or daily information DCN;

the shell script calls an Object Storage Service (OSS) interface to perform the following operations:

the method comprises the steps of redoing a standby machine, canceling a first DCN which is currently used, and creating a second DCN;

after the strong synchronous standby machine of the same city machine room is built in a mode of reworking the standby machine, the method further comprises the following steps: if the redo machine is successful, inquiring the progress of the redo machine by using the task ID; if the backup machine fails, checking a corresponding log, and determining an error reason;

before canceling the first DCN currently in use, further comprising: evaluating the delay of the first DCN, and if the delay does not exceed the preset time, canceling the first DCN;

after canceling the first DCN currently used, further comprising: if the first DCN is successfully canceled, inquiring the progress of canceling the first DCN by using the task ID; if the first DCN is failed to be canceled, checking a corresponding log, and determining an error reason;

after canceling the first DCN currently used, further comprising: changing zk information into a DCN standby machine which is not already made; zk is a file directory in which data is stored;

after creating the second DCN, further comprising: if the second DCN is successfully created, inquiring the progress of creating the second DCN by using the task ID; if the second DCN is failed to be established, the corresponding log is checked, and the error reason is determined.

2. A data communication network establishment apparatus, comprising:

the DCN module is used for canceling the first DCN used currently and creating a second DCN on the strong synchronous standby machine, wherein the second DCN is used for preparing the DCN in a different place disaster or daily accounting DCN;

the standby machine module is further used for calling an OSS interface to redo the standby machine through the shell script;

the DCN module is further used for calling an OSS interface through the shell script to cancel the first DCN which is currently used and create a second DCN;

the backup module is further used for inquiring the progress of the backup machine by using the task ID if the backup machine is successful after the strong synchronous backup machine of the same city machine room is built by the backup machine mode; if the backup machine fails, checking a corresponding log, and determining an error reason;

the DCN module is further used for evaluating the delay of the first DCN before canceling the first DCN used currently, and canceling the first DCN if the delay does not exceed the preset time;

the DCN module is further used for inquiring the progress of canceling the first DCN by using the task ID if the canceling of the first DCN is successful after canceling the first DCN which is currently used; if the first DCN is failed to be canceled, checking a corresponding log, and determining an error reason;

the DCN module is further used for changing zk information into a DCN standby machine after canceling the first DCN which is currently used; zk is a file directory in which data is stored;

the DCN module is further used for inquiring the progress of creating the second DCN by using the task ID if the second DCN is successfully created after the second DCN is created; if the second DCN is failed to be established, the corresponding log is checked, and the error reason is determined.

3. A computer device comprising a memory, a processor and a computer program stored on the memory and executable on the processor, characterized in that the processor implements the method of claim 1 when executing the computer program.

4. A computer readable storage medium, characterized in that the computer readable storage medium stores a computer program which, when executed by a processor, implements the method of claim 1.

5. A computer program product, characterized in that the computer program product comprises a computer program which, when being executed by a processor, implements the method of claim 1.