CN115297129A

CN115297129A - Data communication network establishing method and device

Info

Publication number: CN115297129A
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: 2022-11-04
Anticipated expiration: 2042-08-02
Also published as: CN115297129B

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: building a strong synchronous standby machine of the same city machine room in a manner of reworking the standby machine; and 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 disaster remote manner or daily interest calculation DCN. The invention can realize the rapid establishment of the DCN for disaster recovery in different places or daily interest calculation DCN under the distributed database architecture. If the problem exists, the reason of the problem can be quickly known; the return state can be changed and inquired quickly; the impact of an increase in the sudden DCN delay on the pinch-off action can be reduced.

Description

Data communication network establishing method and device

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

A Data Communication Network (DCN) processing method for building disaster recovery in different places and daily information based on a distributed architecture has a service requirement that static Data of a database needs to be acquired at a certain time point, and service operation is performed by using the static Data, and the main service cannot be affected by the operation of acquiring the static Data.

The series of operations are not only complicated and time-consuming, but also prone to errors.

The existing technology has the defect that the DCN cannot be built quickly 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 (distributed data network) establishment cannot be rapidly realized under a distributed database architecture, and comprises the following steps:

building a strong synchronous standby machine of the same city machine room in a manner of reworking the standby machine;

and canceling the first DCN currently used, and creating a second DCN on the strong synchronous standby machine, wherein the second DCN is used for disaster recovery in different places or daily interest-bearing DCN.

An embodiment of the present invention further provides a device for establishing a data communication network, so as to solve a problem that a DCN cannot be quickly established under a distributed database architecture, where the device includes:

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

and 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 a remote disaster DCN or a daily interest DCN.

The embodiment of the present invention further provides a computer device, which includes a memory, a processor, and a computer program stored in the memory and capable of running on the processor, and when the processor executes the computer program, the data communication network establishment method is implemented.

An embodiment of the present invention further provides a computer-readable storage medium, where a computer program is stored, and when the computer program is executed by a processor, the data communication network establishment method is implemented.

An embodiment of the present invention further provides a computer program product, where the computer program product includes a computer program, and when the computer program is executed by a processor, the method for establishing a data communication network is implemented.

In the embodiment of the invention, compared with the technical scheme that the functions of reworking the standby machine and building the DCN cannot be rapidly realized in the prior art, and only the click operation can be performed on the graphical interface through the existing platform, the method and the system for building the DCN have the advantages that the strong synchronous standby machine in the same city is built in a manner of reworking the standby machine, then the second DCN used for disaster recovery in different places or daily interest recovery is built on the strong synchronous standby machine, the steps of obtaining static data of a database, performing business operation by developers and recovering the database to an active state are not limited, and the click operation can be performed on the graphical interface only through the existing platform, so that the DCN can be rapidly built for disaster recovery in different places or daily interest recovery under a distributed database architecture.

Furthermore, since the shell script calls the OSS interface to operate, certain operation risk can be avoided, the DCN interruption time is not too long, otherwise, the risk that the DCN library cannot catch up with the production library exists, the DCN can be quickly reconstructed in a script mode, and if a problem exists, the reason of the problem can be quickly known;

furthermore, when the DCN is reconstructed, the bendcnslave value of zk information (which becomes a DCN standby machine) 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;

furthermore, since the DCN delay needs to be confirmed when the pinch-off action is performed to cancel the DCN, the influence on the operation of the messaging service is evaluated, the DCN delay does not exceed a predetermined time, for example, 2 seconds, and the DCN delay is confirmed in a script manner, it can be considered that the time difference between the pinch-off action and the evaluation of the DCN delay is almost zero, and the influence of the improvement of the sudden DCN delay on the pinch-off action can be reduced.

Drawings

In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the drawings used in the embodiments or the prior art descriptions will be briefly described below, it is obvious that the drawings in the following description are only some embodiments of the present invention, and other drawings can be obtained by those skilled in the art without creative efforts. In the drawings:

FIG. 1 is a schematic flow chart illustrating an implementation 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 illustrating a DCN establishment procedure according to 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 diagram of a computer device according to an embodiment of the present invention.

Detailed Description

In order to make the objects, technical solutions and advantages of the embodiments of the present invention more apparent, the embodiments of the present invention are further described in detail below with reference to the accompanying drawings. The exemplary embodiments and descriptions of the present invention are provided to explain the present invention, but not to limit the present invention.

The inventor notices in the process of invention that:

a DCN processing method for building a strong synchronous standby machine of a same-city machine room, building remote disaster recovery and daily information based on a distributed architecture has business requirements that static data of a database needs to be acquired at a certain time point every morning, business operation is carried out by utilizing the static data, and the main business cannot be influenced by the operation of acquiring the static data.

Generally, the method comprises the following three steps of obtaining static data of the database at a certain time point in the morning, carrying out business operation by developers and restoring the database to an active state. The series of operations are not only complicated and time-consuming, but also prone to errors.

At present, under a distributed database architecture, the functions of redoing a standby machine and building a DCN cannot be rapidly realized, only click operation can be performed on a graphical interface through an existing platform, batch processing should be performed as fast as possible aiming at the systematic operations, and when the graphical interface is abnormal, further analysis is needed, modification and maintenance cannot be directly performed according to reported error information, so that the problems that rapid batch processing cannot be performed and an error log cannot be obtained by inquiring task progress are solved.

Based on this, the embodiment of the present invention provides a processing scheme for building a strong synchronous standby machine in a same-city machine room, building a remote disaster recovery device, and a DCN for daily interest under a distributed architecture, and an OSS (Object Storage Service) interface is quickly called through a shell script, so as to implement functions of redoing the standby machine, creating the remote disaster recovery device DCN, and creating the daily interest recovery device DCN, and can quickly query an operation state and evaluate information such as DCN delay change zk information.

The following examples are given by way of illustration.

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

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

and 102, canceling the first DCN currently used, and creating a second DCN on the strong synchronous standby machine, wherein the second DCN is used for preparing a remote disaster recovery DCN or a daily interest recovery DCN.

Specifically, the scheme mainly realizes the contents of two aspects:

1. and developing a redo standby script, wherein a data operator can carry out remote operation on the file server, and can redo the strong synchronous standby by calling an OSS interface and in a redo standby mode, and if the binlog is stopped, all the standby are required to be redone.

Binary log (Binary log), referred to as Binlog for short. Binlog is a binary log that records changes in the structure of the data table and modifications to the data of the table, and does not record select and show operations. Binlog is a record in the form of events and also includes the elapsed time for the execution of the statement. Binlog is MySql Server's own Log, but Redo Log is based on a Log specific to the InnoDB engine.

The most important use scene for starting the Binlog log is master-slave copy, a Binlog function is started in a master library, so that the master library can transmit the Binlog to a slave library, and the slave library can recover data to achieve master-slave data consistency after taking the Binlog.

2. And a DCN script is created, a data operator can carry out remote operation through a file server, and a plurality of databases can simultaneously create the DCN by calling an OSS interface. And each database instance builds a remote disaster recovery or daily interest calculation DCN in a DCN creating mode.

In the development process, the DCN delay can be evaluated, zk information can be changed when the DCN is rebuilt, development and rework of the standby machine script and creation of the DCN script can be achieved through the script, and time and human 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. redoing the standby machine module: a strong synchronous standby machine of the same city machine room is built in a reworking standby machine mode.

2. Rebuilding the DCN module: and constructing the remote disaster recovery or daily interest calculation DCN in a DCN creating 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, DCN delay is evaluated, an allopatric disaster recovery device or a daily interest calculation DCN is built in a mode of building the DCN, and zk information is changed in the process of rebuilding.

The specific implementation is further described below.

The embodiment provides a batch processing scheme under a distributed architecture, which rebuilds a standby machine and rebuilds a DCN by calling an OSS interface, and mainly comprises the following steps:

1. and (3) a rework standby machine, namely, a strong synchronous standby machine of the same city machine room is built in a rework standby machine mode, the rework standby machine is called through an oss interface, the task ID and the return value of the rework standby machine are taken, whether the rework standby machine succeeds or not is judged, if the rework standby machine succeeds, the task ID is used for inquiring the progress of the rework standby machine, and if the rework standby machine fails, the corresponding log is checked, and the error reason is judged.

That is, in the implementation, after the strong synchronous spare aircraft of the same city computer lab is built through the mode of remaking the spare aircraft, can also further include:

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

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

In practice, strong synchronous replication: the application initiates an update request, the Master copies data to the Slave after finishing the operation, the Slave returns success information to the Master after receiving the data, and the Master replies to the application after receiving the feedback of the Slave. The Master copies data to the Slave synchronously.

The strong synchronous replication requires any request for successful response service, and besides the successful disk-down of the host, the successful disk-down of at least one standby machine is required. Therefore, a request is sent to the standby machines immediately after the host machine, and the host machine can only respond to the service successfully after one of the two standby machines responds successfully. That is, any request that successfully answers the front-end service must have two copies, one on the primary node and one on the standby node. Therefore, strong synchronization is a critical guarantee for multiple copies of data.

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

and redoing the standby machine, canceling the currently used first DCN and creating a second DCN.

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

canceling DCN, and calling an OSS interface to cancel DCN synchronization tasks;

and calling an OSS interface to enable a plurality of databases to simultaneously create the DCN.

In practice, in computer science, shell is commonly called Shell (to distinguish it from core) and refers to software (command interpreter) for providing an operation interface for users. 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 preset series of commands; 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.

The OSS (Object Storage Service) is a cloud Storage Service that provides a large amount of security, low cost, and high reliability.

The OSS has a platform independent RESTful API (REST style API, i.e. REST is an architectural style, independent of programming language, independent of platform, using HTTP as transport protocol) interface, which can store and access any type of data at any application, at any time, and in any place.

Mass data can be easily moved into or out of OSS using an API (Application Programming Interface) Interface, SDK (Software Development Kit) Interface, or OSS migration tool provided. After the data is stored in the OSS, a Standard storage (Standard) can be selected as a main storage mode for mobile applications, large websites, picture sharing or hot videos and audios, and a low-frequency Access storage (initial Access) and an Archive storage (Archive) with lower cost and longer storage time limit can be selected as a storage mode for data which is not accessed frequently.

Storage type (Storage Class):

the OSS provides three storage types of standard, low-frequency access and archiving, and comprehensively covers various data storage scenes from hot to cold. The standard storage type provides high-reliability, high-availability and high-performance object storage service and can support frequent data access; the low-frequency access storage type is suitable for storing data which are not accessed frequently (the average monthly access frequency is 1 to 2 times), and the storage unit price is lower than that of the standard type; the archive storage type is suitable for archive data that needs to be preserved for a long period of time (more than half a year is recommended), and is the lowest cost among the three storage types. See the storage type introduction for details.

Storage space (Bucket):

a storage space is a container for storing objects (objects), all of which must belong to a certain storage space. The storage space has various configuration attributes including region, access authority, storage type, and the like. Different types of storage spaces can be created to store different data according to actual requirements. Create memory space please see create memory space.

Object/file (Object):

an object is a basic unit of OSS stored data, also called 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 Key that is unique inside the memory space. The object meta-information is a group of key-value pairs, which represent some attributes of the object, such as the last modification time, size, etc., and also can store some customized information in the meta-information.

Territory (Region):

the territory represents the physical location of the data center of the OSS. And selecting a proper region to create a Bucket according to the cost, the request source and the like.

Access domain name (Endpoint):

endPoint represents the access domain name of the OSS to the external service. The OSS provides service to the outside in the form of HTTP RESTful API, which requires different domain names when accessing different regions. The domain names required to access the same region through the intranet and the extranet are also different.

Access key (AccessKey):

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

2. Reconstructing DCN, which can be divided into four steps:

firstly, evaluating DCN delay, and if the delay does not exceed 2 seconds, considering that the operation of canceling DCN can be carried out;

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

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

and fourthly, creating a DCN synchronous task, taking the task ID and the return value of the created DCN, judging whether the DCN is created successfully, if so, inquiring the progress of creating the DCN by using the task ID, and if not, checking a corresponding log and judging the error reason.

That is, in the implementation, before canceling the currently used first DCN, the method further includes:

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

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

if the first DCN is successfully cancelled, inquiring the progress of cancelling the first DCN by using the task ID;

and if the first DCN is cancelled unsuccessfully, checking the corresponding log and determining the error reason.

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

and changing zk information into information which is not already a DCN standby machine.

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

if the second DCN is successfully established, inquiring the progress of establishing the second DCN by using the task ID;

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

In practice, zk is a file directory in which only a small amount of data can be stored. Each node (each file or folder) in a directory is called a node. A connection node is called a server or a client, the server has the ability to create the node, the client has the ability to listen to the node, and the connection can be called a connection because each connection has the ability to create and listen. The created node (node) may be persistent (persistent), and the server is not deleted after disconnection; or short-lived (ephemeral), automatically deleted after the server is disconnected; the created node (node) 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 default of the external service port of the ZK is 2181, when the client is started, a long connection of a Transmission Control Protocol (TCP) is firstly established with the ZK server, and from the establishment of the first link, the life cycle of the client session is also started.

The SessionTimeout value of Session is used to detect the timeout of a client call back. When the client connection is disconnected due to various reasons such as too much server pressure, network failure or active disconnection of the client, the previously created Session is still valid as long as the client can restart to connect any one server in the cluster within the time specified by the Session Timeout.

The file system of ZK adopts a tree-structured hierarchical directory structure, which is very similar to the Unix file system. Each directory is called a ZNode in the ZK, and each ZNode has a unique path identifier, namely a name. The ZNOde may contain data and child ZNOdes (a temporary node cannot have a child ZNOde). The data in the ZNode may have multiple versions, so querying the data under a certain path needs to bring up the version number. The client application may set a monitor (watch) on the ZNode.

ZK has realized the publish-subscribe mode through the watch mechanism, ZK has provided the publish-subscribe function of the distributed data, a publisher can let a plurality of subscribers monitor a certain topic object at the same time, when this subject object state changes, will notify all subscribers, make them make corresponding processing, ZK has introduced the watch mechanism and has realized this kind of distributed notice function. The ZK allows the client to register a Watcher snoop with the server, and when some specified events of the server trigger the Watcher, 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 consisting of multiple servers, a leader, and follow-ers. The leader provides read-write service, and other machines except the leader only can provide read service.

Each server stores a copy of data with consistent total data, reads the folders in a distributed mode, writes are forwarded by the real-time updating requests of the leader, the real-time updating requests of the leader are sequentially carried out, the updating requests from the same client sequentially execute data updating atomicity according to the sending sequence of the updating requests, and the sequential data updating is successful or failed. The data view is consistent in real time no matter which server the client is connected to, and the client can read the latest data within a certain event range.

Fig. 3 is a schematic diagram illustrating a DCN establishing process, and as shown in fig. 3, batch processing under a distributed architecture may include:

step 301, building a strong synchronous standby machine of the same city machine room by means of reworking the standby machine;

and 302, building a remote disaster recovery or daily interest calculation DCN in a DCN creating mode.

The embodiment of the invention also provides a data communication network establishing device, which is described in the following embodiment. Because the principle of the device for solving the problems is similar to the data communication network establishment method, the implementation of the device can refer to the implementation of the data communication network establishment method, and repeated details are not repeated.

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

the standby machine module 401 is used for building a strong synchronous standby machine of a machine room in the same city 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 strong synchronous standby device, where the second DCN is used for disaster recovery in different areas or daily interest-bearing 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 presence of a gas in the gas,

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

In implementation, the standby machine module is further used for inquiring the progress of the rework standby machine by using the task ID if the rework standby machine is successful after the strong synchronous standby machine of the same city machine room is built in a rework standby machine mode; and if the redo standby 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 currently used, and cancel the first DCN if the delay does not exceed a preset time.

In implementation, the DCN module is further configured to query, by using the task ID, a progress of canceling the first DCN if the first DCN is successfully canceled after the first DCN currently used is canceled; and if the first DCN is cancelled unsuccessfully, checking the corresponding log and determining the error reason.

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

In implementation, the DCN module is further configured to, after the second DCN is created, query the progress of creating the second DCN by using the task ID if the second DCN is successfully created; and if the second DCN is failed to be established, checking the corresponding log and determining the error reason.

When the technical scheme provided by the embodiment of the invention is implemented, the implementation can be carried out as follows.

Fig. 5 is a schematic diagram of a computer device, as shown in fig. 5, the computer device includes:

the processor 500, which is used to read the program in the memory 520, executes the following processes:

building a strong synchronous standby machine of the same city machine room by a reworking standby machine mode;

the method comprises the steps that a first DCN used at present is cancelled, a second DCN is established on a strong synchronous standby machine, and the second DCN is used for preparing a DCN in a disaster remote mode or a DCN for daily interest calculation;

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

In the implementation, build the strong synchronous machine of preparing for of same city computer lab through the mode of doing as ready machine again after, further include:

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

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

In an implementation, after the second DCN is created, the method further includes:

Wherein in fig. 5, the bus architecture may include any number of interconnected buses and bridges, with one or more processors, represented by processor 500, and various circuits, represented by memory 520, being linked together. The bus architecture may also link together various other circuits such as peripherals, voltage regulators, power management circuits, and the like, which are well known in the art, and therefore, will not be described any further herein. The bus interface provides an interface. The transceiver 510 may be a number of elements including a transmitter and a receiver that provide 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 a machine room in the same city is built in a manner of reworking the standby machine; and constructing the remote disaster recovery or daily interest-calculating DCN in a DCN creating mode.

Furthermore, since the OSS interface is called by the shell script for operation, certain operation risk can be avoided, the DCN interruption time is not too long, otherwise, the risk that the DCN library cannot catch up with the production library exists, the DCN can be rebuilt more quickly by using the script, and if the problem exists, the reason of the problem can be known quickly;

As will be appreciated by one skilled in the art, 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 has been 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 above-mentioned embodiments are intended to illustrate the objects, technical solutions and advantages of the present invention in further detail, and it should be understood that the above-mentioned embodiments are only exemplary embodiments of the present invention, and are not intended to limit the scope of the present invention, and any modifications, equivalent substitutions, improvements and the like made within the spirit and principle of the present invention should be included in the scope of the present invention.

Claims

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

and canceling the currently used first data communication network DCN, and creating a second DCN on the strong synchronous standby machine, wherein the second DCN is used for disaster recovery of the DCN or daily interest-bearing DCN.

2. The method of claim 1, wherein calling an Object Storage Service (OSS) interface via shell script performs one or a combination of the following operations:

3. The method of claim 1, wherein after the strong synchronous standby machine of the same city machine room is built by means of the rework standby machine, the method further comprises the following steps:

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

4. The method of claim 1, wherein before canceling the currently used first DCN, further comprising:

5. The method of claim 1, wherein after canceling the currently used first DCN, further comprising:

6. The method of claim 1, wherein after canceling the currently used first DCN, further comprising:

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

7. The method of claim 1, wherein after creating the second DCN, further comprising:

8. A data communication network establishment apparatus, comprising:

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

and 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 disaster recovery in different places or daily interest-bearing DCN.

9. The apparatus of claim 8, wherein the standby module is further to call an OSS interface via a shell script to redo the standby; and/or the presence of a gas in the gas,

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

10. The device of claim 8, wherein the standby machine module is further used for inquiring the progress of the rework standby machine by using the task ID if the rework standby machine is successful after the strong synchronous standby machine of the same city machine room is built in a rework standby machine mode; and if the redo standby machine fails, checking the corresponding log and determining the error reason.

11. The apparatus of claim 8, wherein the DCN module is further configured to evaluate a delay of the first DCN before canceling the first DCN currently in use, and cancel the first DCN if the delay does not exceed a predetermined time.

12. The apparatus of claim 8, wherein the DCN module is further configured to query for progress in canceling the first DCN with the task ID after canceling the currently used first DCN if canceling the first DCN is successful; and if the first DCN is cancelled unsuccessfully, checking the corresponding log and determining the error reason.

13. The apparatus of claim 8, wherein the DCN module is further for changing the zk information to not have been a DCN standby after canceling a first DCN currently in use.

14. The apparatus of claim 8, wherein the DCN module is further configured to query a progress of creating the second DCN with the task ID after creating the second DCN if the creation of the second DCN is successful; and if the second DCN is failed to be established, checking the corresponding log and determining the error reason.

15. A computer device comprising a memory, a processor and a computer program stored on the memory and executable on the processor, wherein the processor implements the method of any one of claims 1 to 7 when executing the computer program.

16. 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 any of claims 1 to 7.

17. A computer program product, characterized in that the computer program product comprises a computer program which, when being executed by a processor, carries out the method of any one of claims 1 to 7.