A Log Collection Method and Device for Reducing the Public Network Bandwidth of a Disaster Recovery Platform across Different Regions

Abstract

A method and device for collecting logs to reduce the public network bandwidth of a remote disaster recovery platform. The method includes: adding a private network address through a console, having one or more private network addresses so that the console and the disaster recovery machine are in the same local area network; setting the console address, mapping the console address through a universally unique identifier, adding the private network address and the public network address to the console, where the console address parameter supports multiple addresses; configuring node information by the console, setting the console address of the disaster recovery machine as the private network address, setting the console address of the working machine as the public network address, the console sending the private network address to the disaster recovery machine and sending the public network address to the working machine; the disaster recovery machine and the working machine collecting log data and sending the log data to the console through the set console address, where the disaster recovery machine sends through the private network address and the working machine sends through the public network address; the present invention can reduce the public network bandwidth during the process of collecting logs in a remote disaster recovery platform.

Description

Technical Field

[0001] The present invention relates to the technical field of off-site disaster recovery log collection, and particularly to a log collection method and device for reducing the public network bandwidth of an off-site disaster recovery platform. Background Art

[0002] A disaster recovery platform refers to a disaster recovery software control module configured and managed through a Web interface. The control module realizes data disaster recovery by adding real-time data replication rules, scheduled data replication, and application high-availability rules. The log modules of the production server (working machine or source machine Source, hereinafter referred to as the working machine) and the backup server (disaster recovery machine or target end Target, hereinafter referred to as the disaster recovery machine) are used to collect logs and send them to the console. The console (the host where it is located is hereinafter referred to as the control machine) analyzes and locates errors encountered during the data disaster recovery process through the received logs of the working machine and the disaster recovery machine. An off-site disaster recovery platform is an application scenario where the working machine, the disaster recovery machine, and the console are not in the same geographical area.

[0003] The existing log collection module is generally set in the following way: When logging in to the console for the first time, a console address needs to be set, which can be a domain name and an IP address, to ensure that the node (the node refers to the working machine or the disaster recovery machine) can access it. When registering the node, the console address is sent to the node, and during the execution of the disaster recovery task, the log module of the node collects relevant logs and sends the logs to the console through this address. Although this solution has a simple configuration and the log modules of the working machine and the disaster recovery machine send logs to the same console address, its disadvantage is that when the working machine and the disaster recovery machine are not in the same geographical area, the log module of the node, especially the disaster recovery machine, will occupy public network resources when transmitting logs to the console. Summary of the Invention

[0004] To overcome the deficiencies of the above-mentioned prior art, the object of the present invention is to provide a log collection method for reducing the public network bandwidth of an off-site disaster recovery platform, so as to reduce public network bandwidth resources during the log collection process of the off-site disaster recovery platform, and has the advantages of simple configuration and flexibility.

[0005] To achieve the above object, the present invention proposes a log collection method for reducing the public network bandwidth of an off-site disaster recovery platform, including the following steps:

[0006] Add a private network address through the console, and there is one or more private network addresses to make the console and the disaster recovery machine in the same local area network;

[0007] Set the console address, map the console address through a universally unique identifier, and add the private network address and the public network address to the console, wherein the console address parameter supports multiple addresses;

[0008] Configure node information using the console, set the console address of the disaster recovery machine to a private network address, and set the console address of the working machine to a public network address. The console sends the private network address to the disaster recovery machine and the public network address to the working machine;

[0009] The disaster recovery machine and the working machine collect log data and send the log data to the console through the set console address. Among them, the disaster recovery machine sends it through the private network address, and the working machine sends it through the public network address.

[0010] Further, the disaster recovery machine and the working machine collect log data, including:

[0011] The log collection module of the disaster recovery machine and the log collection module of the working machine collect task logs, and compress the log data through the data processing module.

[0012] Further, the method further includes:

[0013] The console receives the log data and decompresses the log data through the data processing module.

[0014] Further, for setting the console address, mapping the console address through a universally unique identifier also includes:

[0015] When editing the console address, the universally unique identifier remains unchanged;

[0016] When no node uses the console address, the console address and the universally unique identifier are deleted together;

[0017] When a node uses the console address, the universally unique identifier is prohibited from being deleted.

[0018] Further, for configuring node information using the console, setting the console address of the disaster recovery machine to a private network address, and setting the console address of the working machine to a public network address, and the console sending the private network address to the disaster recovery machine and the public network address to the working machine, it also includes:

[0019] Save the console addresses set by the disaster recovery machine and the working machine, and the universally unique identifier corresponding to the console address through the node table;

[0020] When the console updates the console address, synchronously update it to the node table and node configuration information according to the universally unique identifier.

[0021] Further, the method further includes:

[0022] When responding to the need to batch update the console address information of nodes, update the console address information of multiple nodes through the console, and set the console address for multiple nodes at the same time.

[0023] To achieve the above object, the present invention also proposes a log collection device for reducing the public network bandwidth of a remote disaster recovery platform, including:

[0024] A local area network address adding module, which is used to add a private network address through the console, and when there is one or more private network addresses, the console and the disaster recovery machine are in the same local area network;

[0025] A console address setting module, which is used to set the console address, map the console address through a universally unique identifier, and add the private network address and the public network address to the console, where the console address parameter supports multiple addresses;

[0026] A node information configuration module, which is used to configure node information by using the console, set the console address of the disaster recovery machine as a private network address, and set the console address of the working machine as a public network address. The console sends the private network address to the disaster recovery machine and sends the public network address to the working machine;

[0027] A log data sending module, which is used for the disaster recovery machine and the working machine to collect log data and send the log data to the console through the set console address, where the disaster recovery machine sends through the private network address and the working machine sends through the public network address.

[0028] Further, the log data sending module is also used for:

[0029] The log collection module of the disaster recovery machine and the log collection module of the working machine collect task logs, and compress the log data through a data processing module.

[0030] Further, the device also includes a log data receiving module, which is used for:

[0031] The console receives the log data and decompresses the log data through the data processing module.

[0032] Further, the console address setting module is also used for:

[0033] When editing the console address, the universally unique identifier remains unchanged;

[0034] When no node uses the console address, the console address and the universally unique identifier are deleted together;

[0035] When there is a node using the console address, the universally unique identifier is prohibited from being deleted.

[0036] Compared with the prior art, the present invention consists of a console supporting multi-address management and a data processing module. When the console configures nodes, it sends the console address to the nodes, and then the nodes send the log data to the console after processing by the data compression module; among them, the data processing module includes a data compression module and a data decompression module. The working machine and the disaster recovery machine need to be processed by the data compression module before sending the logs, and the console needs to be processed by the data decompression module after receiving the log data; the present invention compresses the data before the working machine and the disaster recovery machine send the log data to the console to reduce the data volume, thereby reducing the network bandwidth. In the scenario of off-site disaster recovery, the console and the disaster recovery machine are placed in the same local area network. The console's Private IP is used to receive the log data of the disaster recovery machine, and the Public IP is used to receive the log data of the working machine, avoiding occupying public network resources, so as to achieve the purpose of reducing the public network bandwidth. BRIEF DESCRIPTION OF THE DRAWINGS

[0037] Figure 1 It is a flowchart of the steps of a log collection method for reducing the public network bandwidth of an off-site disaster recovery platform according to the present invention;

[0038] Figure 2 It is an architecture diagram of the existing log collection of an off-site disaster recovery platform disclosed by the present invention;

[0039] Figure 3 It is an improved architecture diagram of the log collection of an off-site disaster recovery platform in an embodiment disclosed by the present invention;

[0040] Figure 4 It is a flowchart of the steps of a preferred embodiment disclosed by the present invention;

[0041] Figure 5 It is an architecture diagram of the data processing module in an embodiment disclosed by the present invention;

[0042] Figure 6 It is a structural schematic diagram of a log collection device for reducing the public network bandwidth of an off-site disaster recovery platform according to the present invention. EMBODIMENTS

[0043] The following specific examples and the accompanying drawings are used to illustrate the embodiments of the present invention. Those skilled in the art can easily understand other advantages and effects of the present invention from the content disclosed in this specification. The present invention can also be implemented or applied through other different specific examples, and various details in this specification can also be modified and changed based on different viewpoints and applications without departing from the spirit of the present invention.

[0044] Figure 1 It is a flowchart of the steps of a log collection method for reducing the public network bandwidth of an off-site disaster recovery platform according to the present invention. As Figure 1As shown in the figure, a log collection method for reducing the public network bandwidth of a disaster recovery platform in different locations according to the present invention includes the following steps:

[0045] Step S101: Add a private network address through the console so that there is one or more private network addresses, enabling the console and the disaster recovery machine to be in the same local area network;

[0046] Step S102: Set the console address, map the console address through a universally unique identifier, and add the private network address and the public network address to the console. Among them, the console address parameter supports multiple addresses;

[0047] Step S103: Use the console to configure node information, set the console address of the disaster recovery machine as the private network address, and set the console address of the working machine as the public network address. The console sends the private network address to the disaster recovery machine and sends the public network address to the working machine;

[0048] Step S104: The disaster recovery machine and the working machine collect log data and send the log data to the console through the set console address. Among them, the disaster recovery machine sends through the private network address, and the working machine sends through the public network address.

[0049] Specifically, Figure 2 is the architecture diagram of the existing log collection of the disaster recovery platform in different locations disclosed in the present invention. As Figure 2 shown, when logging in for the first time, set the console address, which can be a domain name and an IP address to ensure that the node (working machine or disaster recovery machine) can be accessed; when registering the node, send the console address to the node; during the execution of the disaster recovery task, the node collects relevant logs and sends the logs to the console through this address. That is to say, the existing methods for sending logs of the disaster recovery platform in different locations all adopt the form of public network addresses. Figure 3 is the improved architecture diagram of the log collection of the disaster recovery platform in different locations according to an embodiment disclosed in the present invention. As Figure 3 shown, first, the console ensures that there are at least two IPs, one public network address, that is, Public IP; one private network address, that is, Private IP; and place the console and the disaster recovery machine in the same local area network; secondly, when adding the console IP in the console configuration module, add a universally unique identifier (UUID) to map this IP; thirdly, when adding a node to the console, the working machine selects the console Public IP, and the disaster recovery machine selects the Private IP; finally, the disaster recovery machine sends logs to the console through the internal network Private IP, and the working machine sends logs to the console through the public network Public IP.

[0050] Furthermore, referring to Figure 3 and Figure 5, in step S104, the disaster recovery machine and the working machine collect log data, including:

[0051] The log collection module of the disaster recovery machine and the log collection module of the working machine collect task logs, and the log data is compressed by the data processing module.

[0052] Further, referring to Figure 5 , the method further includes the following steps:

[0053] The console receives the log data and decompresses the log data through the data processing module.

[0054] Further, in step S102, when setting the console address and mapping the console address through a universally unique identifier, the following steps are further included:

[0055] When editing the console address, the universally unique identifier remains unchanged;

[0056] When no node uses the console address, the console address and the universally unique identifier are deleted together;

[0057] When a node uses the console address, the universally unique identifier is prohibited from being deleted.

[0058] Specifically, when adding a console IP in the console configuration module, a unique UUID is added to map the IP. When editing the IP, the UUID remains unchanged. When no node uses the IP, deleting the IP also deletes the UUID. When a node uses the IP, deletion is prohibited.

[0059] Further, in step S103, the following steps are further included:

[0060] The console addresses set by the disaster recovery machine and the working machine, and the universally unique identifier corresponding to the console address are saved through the node table;

[0061] When the console updates the console address, it is synchronously updated to the node table and node configuration information according to the universally unique identifier.

[0062] Specifically, when adding a node to the console, the working machine selects the console Public IP, and the disaster recovery machine selects the Private IP. At this time, the node table will save the selected IP and its UUID. When the console updates the console address, it is synchronously updated to the node table and node configuration information according to the UUID.

[0063] Further, the method further includes the following steps:

[0064] When it is necessary to batch update the console address information of nodes, the console address information of multiple nodes is updated through the console, and the console addresses are set for multiple nodes at the same time. That is to say, the console can batch update the console address information of nodes and set the console addresses for multiple nodes at the same time.

[0065] Figure 4 It is a flowchart of the steps of a preferred embodiment disclosed by the present invention. As Figure 4 shown, a preferred embodiment disclosed by the present invention includes the following steps:

[0066] Step S201: Add a local area network address through the console, and there is at least one Private IP so that the console and the disaster recovery machine are in the same local area network;

[0067] Step S202: The console address parameter of the console supports multiple addresses, and the Private IP and Public IP are added to the console;

[0068] Step S203: Configure node information through the console, set the console address of the disaster recovery machine to Private IP, and set the console address of the working machine to Public IP. The console sends the Private IP to the disaster recovery machine and the Public IP to the working machine;

[0069] Step S204: The log collection modules of the working machine and the disaster recovery machine collect task logs, and the data processing module compresses the log data;

[0070] Step S205: After the data is compressed, the working machine sends it to the console through the Public IP, and the disaster recovery machine sends it to the console through the Private IP;

[0071] Step S206: After receiving the node logs, the console decompresses the data through the data processing module.

[0072] Figure 5 It is an architecture diagram of the data processing module of an embodiment disclosed by the present invention. As Figure 5 shown, the data processing module consists of a data compression module and a data decompression module. After the log collection modules of the disaster recovery machine and the working machine collect task logs, the raw log data is GZIP compressed by the data compression module, and the data to be sent is formed after compression and sent to the console; after the console receives the log data, it is GZIP decompressed by the data decompression module, and the received data is decompressed into raw data to reduce the data volume and reduce the public network bandwidth resources.

[0073] Figure 6The figure is a schematic structural diagram of a log collection device for reducing the public network bandwidth of a disaster recovery platform in different locations according to the present invention. To achieve the above object, the present invention also provides a log collection device for reducing the public network bandwidth of a disaster recovery platform in different locations, including:

[0074] A local area network address adding module 31, configured to add a private network address through a console, and having one or more private network addresses to enable the console and the disaster recovery machine to be in the same local area network;

[0075] A console address setting module 32, configured to set the console address, map the console address through a universally unique identifier, and add the private network address and the public network address to the console, wherein the console address parameter supports multiple addresses;

[0076] A node information configuration module 33, configured to configure node information by using the console, set the console address of the disaster recovery machine as a private network address, and set the console address of the working machine as a public network address, and the console issues the private network address to the disaster recovery machine and issues the public network address to the working machine;

[0077] A log data sending module 34, configured to collect log data by the disaster recovery machine and the working machine, and send the log data to the console through the set console address, wherein the disaster recovery machine sends through the private network address and the working machine sends through the public network address.

[0078] Specifically, Figure 2 The figure is an architecture diagram of log collection of an existing disaster recovery platform in different locations disclosed by the present invention. As Figure 2 shown, when logging in for the first time, set the console address, which can be a domain name and an IP address, to ensure that the node (working machine or disaster recovery machine) can be accessed; when registering a node, issue the console address to the node; during the execution of the disaster recovery task, the node collects relevant logs and sends the logs to the console through this address. That is to say, the existing methods of sending logs of the disaster recovery platform in different locations all adopt the form of a public network address. Figure 3 The figure is an improved architecture diagram of log collection of a disaster recovery platform in different locations according to an embodiment disclosed by the present invention. As Figure 3 shown, first, the console ensures that there are at least two IPs, one public network address, that is, a Public IP; one private network address, that is, a Private IP; and the console and the disaster recovery machine are placed in the same local area network; secondly, when adding the console IP in the console configuration module, add a unique UUID to map this IP; thirdly, when adding a node to the console, the working machine selects the console Public IP and the disaster recovery machine selects the Private IP; finally, the disaster recovery machine sends logs to the console through the internal network Private IP, and the working machine sends logs to the console through the public network Public IP.

[0079] Further, referring to Figure 3 and Figure 5 , the log data sending module 34 is further configured to:

[0080] The log collection module of the disaster recovery machine and the log collection module of the working machine collect task logs, and the log data is compressed by the data processing module.

[0081] Further, referring to Figure 5 , the device further includes a log data receiving module, configured to:

[0082] The console receives the log data, and the log data is decompressed by the data processing module.

[0083] Further, the console address setting module 32 is further configured to:

[0084] When editing the console address, the universally unique identifier remains unchanged;

[0085] When no node uses the console address, the console address and the universally unique identifier are deleted together;

[0086] When a node uses the console address, the universally unique identifier is prohibited from being deleted.

[0087] Specifically, when adding a console IP in the console configuration module, a unique UUID is added to map the IP. When editing the IP, the UUID remains unchanged; when no node uses the IP, deleting the IP also deletes the UUID; when a node uses the IP, deletion is prohibited.

[0088] Further, the node information configuration module 33 is further configured to:

[0089] Save the console addresses set by the disaster recovery machine and the working machine, and the universally unique identifier corresponding to the console address, through the node table;

[0090] When the console updates the console address, synchronously update it to the node table and the node configuration information according to the universally unique identifier.

[0091] Specifically, when adding a node to the console, the working machine selects the console Public IP, and the disaster recovery machine selects the Private IP. At this time, the node table will save the selected IP and its UUID, and when the console updates the console address, it will be synchronously updated to the node table and the node configuration information according to the UUID.

[0092] Further, the device further includes a batch update module, configured to:

[0093] When it is necessary to batch update the console address information of nodes, the console address information of multiple nodes is updated through the console, and the console addresses are set for multiple nodes at the same time. That is to say, the console can batch update the console address information of nodes and set the console addresses for multiple nodes at the same time.

[0094] It should be noted that the device for reducing the public network bandwidth in the process of collecting logs of a disaster recovery platform in different locations according to the present invention has a one-to-one correspondence with the above method. For other parts not described, refer to the content in the above method and will not be elaborated here.

[0095] In summary, for the method and device for reducing the public network bandwidth in the process of collecting logs of a disaster recovery platform in different locations according to the present invention, the console and the disaster recovery machine are placed in the same local area network. The console uses the Private IP to receive the log data of the disaster recovery machine and uses the Public IP to receive the log data of the working machine, avoiding occupying public network resources. At the same time, the data processing module is adopted to compress the log data of the nodes and then send it to the console, and the data received by the console is decompressed to reduce the data volume, so as to achieve the purpose of reducing the public network bandwidth. In addition, when the console modifies the console address, it will be synchronized to the key nodes, which is simple and flexible.

[0096] The above embodiments are only used to illustrate the principle and its effects of the present invention, rather than to limit the present invention. Any person skilled in the art can modify and change the above embodiments without departing from the spirit and scope of the present invention. Therefore, the scope of the protection of the rights of the present invention shall be as listed in the claims.

Claims

1. A log collection method for reducing the public network bandwidth of a remote disaster recovery platform, comprising the following steps: Add a private network address through the console, and having one or more private network addresses enables the console and the disaster recovery machine to be in the same local area network; Set the console address, map the console address through a universally unique identifier, and add the private network address and the public network address to the console, where The console address parameter supports multiple addresses; Use the console to configure node information, set the console address of the disaster recovery machine as a private network address, and set the console address of the working machine as a public network address. The console sends the private network address to the disaster recovery machine and sends the public network address to the working machine; The disaster recovery machine and the working machine collect log data and send the log data to the console through the set console address. Among them, the disaster recovery machine sends through the private network address, and the working machine sends through the public network address.

2. The log collection method for reducing the public network bandwidth of the off-site disaster recovery platform according to claim 1, wherein The disaster recovery machine and the working machine collect log data, including: The log collection module of the disaster recovery machine and the log collection module of the working machine collect task logs, and compress the log data through the data processing module.

3. The log collection method for reducing the public network bandwidth of the off-site disaster recovery platform according to claim 2, wherein The method further includes: The console receives the log data and decompresses the log data through the data processing module.

4. A log collection method for reducing the public network bandwidth of a disaster recovery platform in different locations, as described in claim 1, characterized in that For the setting of the console address, mapping the console address through a universally unique identifier further includes: When editing the console address, the universally unique identifier remains unchanged; When no node uses the console address, the console address and the universally unique identifier are deleted together; When a node uses the console address, the universally unique identifier is prohibited from being deleted.

5. The log collection method for reducing the public network bandwidth of the off-site disaster recovery platform according to claim 4, wherein For the use of the console to configure node information, set the console address of the disaster recovery machine as a private network address, and set the console address of the working machine as a public network address. The console sends the private network address to the disaster recovery machine and sends the public network address to the working machine, further includes: Save the console addresses set by the disaster recovery machine and the working machine, and the universally unique identifier corresponding to the console address through the node table; When the console updates the console address, synchronously update it to the node table and node configuration information according to the universally unique identifier.

6. The log collection method for reducing the public network bandwidth of the off-site disaster recovery platform according to claim 1, characterized in that, The method further includes: In response to the need to batch update the console address information of nodes, update the console address information of multiple nodes through the console, and set the console address for multiple nodes at the same time.

7. A log collection device for reducing the public network bandwidth of a remote disaster recovery platform, comprising: A local area network address addition module, configured to add a private network address through the console, and having one or more private network addresses enables the console and the disaster recovery machine to be in the same local area network; A console address setting module, configured to set the console address, map the console address through a universally unique identifier, and add the private network address and the public network address to the console, wherein the console address parameter supports multiple addresses; A node information configuration module, configured to use the console to configure node information, set the console address of the disaster recovery machine as a private network address, and set the console address of the working machine as a public network address. The console sends the private network address to the disaster recovery machine and sends the public network address to the working machine; A log data sending module, which is used for the disaster recovery machine and the working machine to collect log data and send the log data to the console through the set console address. Among them, the disaster recovery machine sends through a private network address, and the working machine sends through a public network address.

8. The log collection device for reducing the public network bandwidth of the off-site disaster recovery platform according to claim 7, wherein, The log data sending module is further used for: The log collection module of the disaster recovery machine and the log collection module of the working machine collect task logs, and the log data is compressed through the data processing module.

9. The log collection device for reducing the public network bandwidth of the off-site disaster recovery platform according to claim 8, characterized in that, The device further includes a log data receiving module, which is used for: The console receives the log data and decompresses the log data through the data processing module.

10. The log collection device for reducing the public network bandwidth of the off-site disaster recovery platform according to claim 7, wherein The console address setting module is further used for: When editing the console address, the universally unique identifier remains unchanged; When no node uses the console address, the console address and the universally unique identifier are deleted together; When a node uses the console address, the universally unique identifier is prohibited from being deleted.

Images