WO2024036990A1 - Procédé et appareil de récupération de données, dispositif de réseau et support d'enregistrement - Google Patents

Procédé et appareil de récupération de données, dispositif de réseau et support d'enregistrement Download PDF

Info

Publication number
WO2024036990A1
WO2024036990A1 PCT/CN2023/086927 CN2023086927W WO2024036990A1 WO 2024036990 A1 WO2024036990 A1 WO 2024036990A1 CN 2023086927 W CN2023086927 W CN 2023086927W WO 2024036990 A1 WO2024036990 A1 WO 2024036990A1
Authority
WO
WIPO (PCT)
Prior art keywords
data
hardware
backup
network device
written
Prior art date
Application number
PCT/CN2023/086927
Other languages
English (en)
Chinese (zh)
Inventor
林宁
Original Assignee
中兴通讯股份有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 中兴通讯股份有限公司 filed Critical 中兴通讯股份有限公司
Publication of WO2024036990A1 publication Critical patent/WO2024036990A1/fr

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/08—Configuration management of networks or network elements
    • H04L41/085—Retrieval of network configuration; Tracking network configuration history
    • H04L41/0853—Retrieval of network configuration; Tracking network configuration history by actively collecting configuration information or by backing up configuration information
    • H04L41/0856—Retrieval of network configuration; Tracking network configuration history by actively collecting configuration information or by backing up configuration information by backing up or archiving configuration information
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/06—Management of faults, events, alarms or notifications
    • H04L41/0654—Management of faults, events, alarms or notifications using network fault recovery

Definitions

  • the present application relates to the technical field of network equipment, and in particular to a data recovery method, device, network equipment and storage medium.
  • control plane and forwarding plane of a network device are controlled separately. Therefore, the control plane may calculate entry data that exceeds the forwarding plane's hardware carrying capacity. In other words, network equipment generally has the problem of table entries exceeding the limit.
  • the table entry exceeds the limit, if the software or hardware level of the network device is restarted, due to the writing order problem, the table entry data content written to the hardware after the network device is restarted and before the restart may be different.
  • the table entry data written normally is not written to the hardware after the network device is restarted. Once such a situation occurs, the traffic normally carried on the original network equipment will be disconnected after the network equipment is restarted.
  • the purpose of the embodiments of this specification is to provide a data recovery method, device, network equipment and storage medium, so as to avoid business disconnection that may occur when network equipment is restarted and improve network stability.
  • the first aspect is to provide a data recovery method, including: the network device has been written into the hardware All hardware data is backed up to obtain a backup copy; wherein the backup copy includes backup data corresponding to the hardware data, and the hardware data includes hardware entry data; when a restart of the network device is detected, Write all the backup data in the backup copy to the hardware.
  • a data recovery device including: a backup module for backing up all the hardware data written to the hardware by the network device to obtain a backup copy; wherein the backup copy includes the hardware data Corresponding backup data, the hardware data includes hardware entry data; a recovery module configured to write all the backup data in the backup copy to the hardware when a restart of the network device is detected.
  • a network device including: a processor; a memory for storing instructions executable by the processor; wherein the processor is configured to execute the instructions to implement as described in the first aspect Methods.
  • a fourth aspect provides a readable storage medium that, when instructions in the storage medium are executed by a processor of a network device, enables the network device to perform the method described in the first aspect.
  • Figure 1 is a schematic flowchart of a data recovery method according to an embodiment of this specification
  • FIG. 2 is a schematic flowchart of another data recovery method provided by an embodiment of this specification.
  • Figure 3 is a schematic flowchart of a process for restoring routing entries in a routing table according to an embodiment of this specification
  • Figure 4 is a schematic structural diagram of a data recovery device provided by an embodiment of this specification.
  • FIG. 5 is a schematic structural diagram of another data recovery device according to an embodiment of this specification. picture
  • Figure 6 is a schematic structural diagram of a network device according to an embodiment of this specification.
  • the table entry overrun refers to the fact that the number of table entries calculated by the control plane exceeds the maximum number of entries that the forwarding plane hardware can carry. Once this happens, the network device will write the maximum number of entry data that its hardware can carry. The remaining other entry data only exists on the control plane and is not actually written to the forwarding plane.
  • the entry data that has been delivered to the hardware will be delivered again, but the order of delivery cannot be guaranteed. Therefore, the network Compared with the entry data written to the hardware before the device restarts, the entry data written to the hardware after the device is restarted is still the maximum number of entries that the hardware can carry, but the written entry data will still exist. The difference is that the table entry data that was written normally before may not be written to the hardware after the network device is restarted due to writing order issues.
  • the traffic normally carried by the original network device may be interrupted or abnormal after the network device is restarted, resulting in business disconnection.
  • This kind of business The occurrence of broken links cannot be controlled or predicted. Due to the uncertainty in the writing order of table entry data, when the table entries exceed the limit, the table entry data written to the hardware after each network device restarts is uncertain, and business links may be disconnected. In the existing technology, the above problem cannot be solved. It can only provide an alarm when the table entry exceeds the limit, and prompt the user to reduce the number of table entries in the control plane, so as to avoid the occurrence of this problem as much as possible.
  • embodiments of this specification are intended to provide a data recovery method and device to avoid service interruptions that may occur when network equipment is restarted and to improve network stability.
  • the main technical concept of this application is to perform backup processing on all hardware data that has been written to the hardware by the network device, obtain a backup copy, and use the backup copy to directly restore the data when the network device is restarted. Furthermore, after using the backup copy for data recovery, the forwarding plane and control plane are processed according to certain rules to ensure that the recovered data must be hardware data that is in use and has previously existed in the network device. If the network device After restarting, the recovered data only exists in the hardware but does not exist in the control plane and will be deleted. In this way, it is ensured that the normal traffic that already exists in the network device will not be affected by the restart of the network device. After the network device is restarted and restored, the service link will be kept smooth and the original flow will not be caused by the table entry exceeding the limit. Some table entry data cannot be written to the hardware, causing unnecessary business disconnection.
  • the data recovery method provided by the embodiments of this specification is suitable for use scenarios of network devices with large-capacity table entries, especially in usage scenarios where table entries exceed the limit, and can specifically solve the situation where the table entries exceed the limit. This solves the problem of uncertainty in the entry data written to the hardware after the network device is restarted, thereby avoiding unnecessary business disconnections and ensuring network stability.
  • the data recovery method provided by the embodiments of this specification can be executed by network equipment or software installed in the network equipment.
  • the network equipment can be routers, switches, IPRAN (IP Radio Access Network, IP-based wireless access network) ) equipment, PTN (Packet Transport Network, Packet Transport Network) equipment, etc.
  • IPRAN IP Radio Access Network, IP-based wireless access network
  • PTN Packet Transport Network, Packet Transport Network
  • Figure 1 is a flow chart of a data recovery method according to an embodiment of this specification. Schematic diagram of the process, the method may include:
  • the network device may be a router, a switch, an IPRAN device, a PTN device, etc.
  • the data that has been written to the hardware by the network device is called hardware data
  • the data corresponding to the hardware data obtained by backing up the hardware data is called backup data.
  • the backup data corresponding to the hardware data may include the entire data content of the hardware data, or may include part of the data content of the hardware data.
  • the type of the hardware data may include hardware entry data.
  • the hardware entry data refers to the entry data that the network device has written to the hardware.
  • the entry data may be a routing table, ACL (Access Control List, Access control list), MAC (Media Access Control, media access control) address table, VLAN (Virtual Local Area Network, virtual LAN) allocation table corresponding type of entry data.
  • the backup copy can be stored in a memory of the network device, such as a FLASH (flash memory) of the network device; the backup copy can also be stored in a memory connected to the network device.
  • Related remote devices such as network management stations, controllers, etc.
  • the storage form of the backup copy may be a file or a table. Storing the backup copy in the local memory of the network device has better reliability and does not require special network connection support; storing the backup copy in the remote device has a faster storage speed.
  • the method of forming a backup copy may adopt a real-time generation method, that is, each piece of hardware data written by the network device to the hardware is backed up to the backup copy in real time.
  • the network device directly forms a backup copy of its hardware data.
  • real-time backup is performed to the backup copy.
  • the backup method can be by writing the backup data corresponding to the hardware data to be synchronized (a piece of hardware data written in real time) to the local memory, or by sending a message to the remote device, carrying the hardware data to be synchronized in the message. (Reality A piece of hardware data written at the time) backup data.
  • the real-time generation method has better real-time performance.
  • the method of forming a backup copy may adopt a time polling method, that is, all hardware data written by the network device to the hardware may be backed up to the backup copy according to a set time interval.
  • the network device backs up the entire hardware data of the local memory or the remote device at set time intervals.
  • the backup method can be similar to the real-time generation method, by writing the data to be synchronized to the local memory. Backup data corresponding to the hardware data (all hardware data currently written to the hardware), or send a message to the remote device, carrying the corresponding hardware data to be synchronized (all hardware data currently written to the hardware) in the message backup data.
  • the time-based polling method consumes less computing power resources on network equipment.
  • the backup data corresponding to the hardware data can be all the information of the hardware data, or partial information of the hardware data. If it is partial information, it must include at least the key of the hardware data.
  • key information refers to the necessary information that can realize the function of the data. For example, for a routing entry in a routing table, the key information includes subnet mask, routing information, next hop and exit (MAC, VLAN, physical exit), then the backup data needs to include at least the above key information. .
  • the network device restart includes software or hardware level restart, and the network device restart can be detected through system logs.
  • two aspects of technical processing need to be performed on the network device.
  • the backup copy includes backup data corresponding to the hardware data, so that the backup copy can be used for direct data recovery after the network device is restarted; secondly, after using the backup copy for data recovery, compare the backup data to ensure correctness .
  • the data recovery solution performs backup processing on all hardware data that has been written to the hardware by the network device.
  • the obtained backup copy includes backup data corresponding to the hardware data, where the hardware data includes hardware entry data;
  • the backup copy is used for data recovery, and all backup data in the backup copy is written directly to the hardware.
  • the table entries do not exceed the limit, fast service recovery can be achieved; when the table entries exceed the limit, it is guaranteed that the table entry data written to the network device hardware and the table entry data that cannot be written to the network device hardware are guaranteed to be the same. Stable and predictable, there will be no randomly selected table entry data written to the hardware.
  • the data written to the hardware after the network device is restarted is quickly consistent with the state before the restart.
  • the original normal business will not be disconnected due to the uncertainty of the table entry data written in the hardware, and the business can be quickly Recovery can effectively avoid unnecessary business disconnections, improve network stability, and thereby improve users' perception of the network.
  • the data recovery method may also include the following steps:
  • the target data includes target entry data.
  • target data the data calculated after the network device is restarted and needs to be restored to the hardware
  • type of the target data may include target entry data.
  • target entry data refers to the entry data calculated after the network device is restarted and needs to be restored to the hardware.
  • the data that needs to be delivered after the network device restarts is The data of the hardware needs to be restored to the hardware. It can be understood that the data that needs to be restored to the hardware refers to the data that has been written to the hardware before the network device is restarted. These data are lost due to the restart of the network device.
  • Status before restart status it is necessary to recalculate and deliver the hardware.
  • the target data is usually all data that needs to be delivered to the hardware after the first calculation of all software protocols is completed after the network device is restarted.
  • the target data is compared with each backup data that already exists in the hardware. If the comparison shows that there is backup data corresponding to the currently acquired target data in the hardware, , then the backup data is marked, and the marking of the backup data is used to indicate that the backup data is written successfully.
  • the software protocol In order to maintain the consistency between the data in the hardware and the data calculated by the software protocol, after the software protocol calculates each piece of target data that needs to be restored to the hardware, it must compare it with each backup data that already exists in the hardware, that is, compare This software protocol is about to deliver the target data of the hardware, whether it exists in the hardware. If the comparison finds that backup data corresponding to the target data exists in the hardware, there is no need to deliver the target data to the hardware because the corresponding backup data already exists in the hardware.
  • the target data to be delivered to the hardware by the software protocol may not be exactly the same as the backup data that already exists in the hardware, because the backup data that already exists in the hardware may only include the original Part of the information of the hardware data (including at least key information) but not all of the information, and the target data that the software protocol is about to deliver to the hardware is recalculated by the forwarding side for restart and recovery, and will include all the information of the original hardware data, but there are two
  • the key information of the data is the same and can achieve the same functions, such as the same routing and forwarding function. Therefore, the two pieces of data are corresponding data and can be treated as the same piece of data.
  • the backup data needs to be marked. For example, a set mark information can be added to the backup data.
  • all backup data in the hardware can be directly compared and marked. If there is backup data corresponding to the currently acquired target data in the hardware, the tag information is added to the backup data in the hardware.
  • the reserved field of the data in the hardware can be used to add the tag information to the backup data. For example, setting the reserved field to 1 indicates that the piece of data has been written successfully.
  • a backup table including all the backup data can be saved in the memory of the network device, so that when comparing and marking When , the hardware is not marked, but marked in the backup table. If there is backup data corresponding to the currently acquired target data in the hardware, the tag information is added to the backup data in the backup table.
  • the method further includes:
  • the target data is written into the hardware and the target data is marked.
  • the purpose of marking the target data newly written to the hardware is to prevent the target data newly written to the hardware from being mistakenly deleted during subsequent processing because it is not marked.
  • unmarked backup data it may be that the data has become invalid due to external changes during the restart of the network device, so these backup data can be deleted.
  • data computation may involve software protocols using multiple processes, or multiple software protocols for processing, there needs to be a definite indication that the target data computation that needs to be restored to the hardware is complete.
  • This instruction can be implemented by notifying the network device after the software protocol calculation is completed, or the user can set a reliable data calculation holding period (hold time) for waiting for the software protocol calculation to be completed based on experience.
  • the method for confirming the completion of target data calculation may include: confirming the completion of all target data calculations upon receiving a notification message that the data calculation is completed, and the notification message is sent by the network device. After restarting for the first time, all data statistics of the hardware will need to be distributed. It is sent when the calculation is completed. At this time, it can be considered that all target data that need to be restored to the hardware have been calculated, and the unmarked backup data in the hardware can be deleted.
  • the method of confirming the completion of the target data calculation may include: confirming that all target data calculations are completed when it is detected that the preset data calculation holding period has arrived. If the software protocol does not support sending notification messages, the data calculation retention period can be manually set.
  • the data calculation retention period is mainly to ensure that the software protocol of the network device has determined to complete the calculation of the target data that needs to be restored to the hardware.
  • the start time point of the data calculation retention period can be set flexibly.
  • you can choose the restart time of the network device you can also start a timer after the network device restarts, you can also choose the time when the software protocol starts calculating after the network device restarts, or You can select the moment when the first piece of data is written to the hardware after the network device is restarted. After a set data calculation retention period, it can be considered that all target data that need to be restored to the hardware have been calculated, and the unmarked backup data in the hardware can be deleted.
  • the deletion of unmarked backup data in the hardware can be divided into the following situations:
  • the backup data without the tag information added can be deleted from the hardware according to whether the tag information is added to each backup data in the hardware. ; If the mark information is added to the backup data in the backup table, correspondingly, the corresponding backup data can be deleted in the hardware according to the backup data recorded in the backup table without adding the mark information. .
  • the data recovery method may further include:
  • S106 Determine the difference between the maximum number of capacity items that the hardware can carry and the number of data items currently existing in the hardware.
  • the table entry exceeds the limit, there will be target table entry data in the network device that has not been written to the hardware. Therefore, after the backup table entry data in the hardware is deleted, there will be certain available resources in the hardware. source. At this time, the target table entry data that has not been written to the hardware can be written to the hardware according to certain rules (sequential or random).
  • the data is taken as an example of routing entries in the routing table. This method is exemplarily explained in two situations. Assume that the maximum capacity of the hardware routing table in the network device is 8K entries. Before the network device is restarted, the control plane calculates 10K route entries. During the restart of the network device, 100 route entries become invalid.
  • the backup copy of the routing table is stored in the local FLASH of the network device and is generated in real time.
  • the backup copy of the routing table is stored in the local FLASH of the network device and is generated in real time.
  • Step 11 Each time the network device writes a hardware routing entry into the hardware routing table, it simultaneously stores a corresponding backup routing entry in the backup copy of the routing table in FLASH.
  • Step 12 When the network device writes 8K hardware routing entries into the hardware routing table, 8K backup routing entries are also stored in FLASH.
  • the control plane of the network device continues to calculate the table entries and finally reaches 10K routing entries, but the remaining The 2K routing entries in the hardware cannot be written anymore, and the backup copy of the FLASH routing table is no longer stored synchronously.
  • Step 13 The network device restarts. There are no routing entries in the restarted network device. At this time, the network device immediately writes all 8K backup routing entries stored in FLASH to the hardware.
  • Step 14 After the network device is restarted, the routing module begins to calculate the routing entries that need to be delivered to the hardware. Usually the first calculated routing entry after the restart is the target routing entry that needs to be restored to the hardware. After each target routing entry is calculated, it is compared with The 8K backup routing entries that have been written to the hardware are compared. If there is a backup routing entry corresponding to the target routing entry, the writing is considered successful, and the route writing success flag bit is set for the backup routing entry.
  • Step 15 After the routing entry calculation and comparison is completed, 8K-100 backup routing entries in the network device hardware are marked as written successfully. Since the control plane has calculated 10K target routing entries, there are 2K target routes. The entry was not written to the hardware because the hardware resources were full.
  • Step 16 Delete the 100 backup route entries in the hardware of the network device that do not have a successful route write flag set, and add the 2K control plane target route entries that have not been written to the hardware in a predetermined way (sequential or random) Write 100 target routing entries to the hardware.
  • a remote network management station is used to store a backup copy of the routing table, and a time-based polling method is used.
  • a time-based polling method is used.
  • Step 21 Every 5 minutes, the network device sends the hardware routing table to the remote network management station by sending synchronization messages.
  • the synchronization messages can use SNMP (Simple Network Management Protocol, Simple) to communicate with the network management station.
  • Network Management Protocol Simple Network Management Protocol
  • IP Internet Protocol, Internet Protocol
  • Step 22 When the network device fills the hardware routing table with 8K hardware routing entries, no more entries can be written to the hardware at this time. After the polling time is reached, the hardware sends the 8K hardware routing entries to the remote network management station. Form a backup copy of the routing table for storage.
  • Step 23 The network device restarts. There are no routing entries in the restarted network device. At this time, the network management station finds that the network device has restarted and reconnects to the network management station. Then the network management station will deliver the 8K stored backup routing entries to In the network equipment, the network equipment immediately writes all 8K backup route entries issued by the network management station into the hardware.
  • Step 24 After the network device is restarted, the routing module begins to calculate the routing entries that need to be delivered to the hardware. Usually the first calculated routing entry after the restart is the target routing entry that needs to be restored to the hardware. After each target routing entry is calculated, it is compared with The 8K backup routing entries that have been written to the hardware are compared. If there is a backup routing entry corresponding to the target routing entry, the writing is considered successful, and the route writing success flag bit is set for the backup routing entry.
  • Step 25 After the routing entry calculation and comparison is completed, 8K-100 backup routing entries in the network device hardware are marked as written successfully. Since the control plane has calculated 10K target routing entries, there are 2K target routes. The entry was not written to the hardware because the hardware resources were full.
  • Step 26 Delete the 100 backup route entries that do not have the route write success flag set in the hardware of the network device, and add the 2K backup route entries that failed to be written into the control plane target route entries according to the predetermined method. Write 100 target routing entries to the hardware in a certain manner (sequentially or randomly).
  • the data recovery method provided by the embodiments of this specification only requires a backup process of the hardware data and the corresponding processing steps of data recovery using the backup data, so as to ensure the consistency and correctness of the data before and after the device is restarted.
  • the uncertainty of writing the table entry data after the network device is restarted can ensure the continuity of the services that have taken effect before and after the restart.
  • Applying this solution can additionally protect the original effective traffic when the table entry exceeds the limit, and will not be affected by the order in which the table entry data is written, and can eliminate unpredictable business interruption or abnormal situations in the network. , avoid unnecessary business disconnections, improve network stability, and improve users' perception of the network.
  • the data recovery method provided by the embodiment of this specification can also be used when the table entry does not exceed the limit.
  • the effect is equivalent to quickly restoring the table entry data in the hardware before the software protocol performs the table entry data recovery. It also has a relatively good effect in the scenario of rapid business recovery, so that after the network device is restarted, the normal traffic carried before the restart can be quickly restored.
  • a data recovery device 400 provided by the embodiment of this specification, as shown in Figure 4, includes:
  • the backup module 401 is used to perform backup processing on all hardware data that has been written to the hardware by the network device and obtain a backup copy; wherein the backup copy includes backup data corresponding to the hardware data, and the hardware data includes hardware table entries. data.
  • the recovery module 402 is configured to write all the backup data in the backup copy to the hardware when a restart of the network device is detected.
  • the data recovery device may also include:
  • the acquisition module 403 is configured to obtain the target data calculated after the network device is restarted and needs to be restored to the hardware one by one after the recovery module 402 writes all the backup data in the backup copy to the hardware,
  • the target data includes target entry data.
  • Marking module 404 configured to mark the backup number corresponding to the target data in the hardware when it is compared that there is backup data corresponding to the currently acquired target data in the hardware. according to.
  • the deletion module 405 is configured to delete unmarked backup data in the hardware after confirming that all target data calculations are completed.
  • the device may further include:
  • the writing module 406 is configured to determine the maximum number of pieces of data that the hardware can carry and the number of pieces of data currently existing in the hardware after the deletion module 405 deletes the unmarked backup data in the hardware. The difference between them; write the same number of pieces of target data in all target data that are not written into the hardware as the difference into the hardware.
  • the deletion module 405 is specifically configured to confirm that all target data calculations are completed when receiving a notification message that the data calculation is completed.
  • the notification message is sent by the network device after restarting. After the first time, all data calculations that need to be sent to the hardware are completed and sent; or, when the arrival of the preset data calculation retention period is detected, confirm that all target data calculations are completed.
  • the marking module 404 is used to obtain the target data calculated after the network device is restarted and needs to be restored to the hardware one by one. If there is backup data corresponding to the currently acquired target data and it is confirmed that the number of data pieces currently existing in the hardware does not reach the maximum number of pieces of data that the hardware can carry, then the target data is written to in the hardware and tag the target data.
  • the backup module 401 is specifically configured to back up each piece of hardware data written by the network device to the backup copy in real time; or, according to a set time interval, Back up all hardware data that the network device has written to the hardware to the backup copy.
  • the backup copy is stored in the memory of the network device, or the backup copy is stored in a remote device that has a connection relationship with the network device, wherein the backup copy
  • the backup data at least includes key information of corresponding hardware data.
  • the data recovery device in the embodiment of this specification can be used as the data shown in Figure 1 above.
  • the execution body of the recovery method can therefore realize the functions implemented by the data recovery method in Figure 1. Since the principles are the same, they will not be repeated here.
  • the data recovery device provided by the embodiment of this specification can realize rapid service recovery after the network device is restarted, and can ensure that the data written in the hardware must be the data that already existed before the network device was restarted; further, through data comparison, the data can be restored. Data that has become invalid during the restart process is deleted in the hardware promptly and correctly, while ensuring that the original business is not interrupted and the business accuracy is maintained.
  • This device can be used in various scenarios such as when the table item exceeds the limit and when the table item does not exceed the limit, to achieve better technical effects.
  • this embodiment of the present application also provides a network device 600, which includes a processor 601 and a memory 602.
  • the memory 602 stores programs or instructions that can be run on the processor 601.
  • each step of the above-mentioned data recovery method embodiment is implemented, and the same technical effect can be achieved. To avoid repetition, the details will not be described here.
  • Embodiments of the present application also provide a readable storage medium.
  • Programs or instructions are stored on the readable storage medium.
  • the program or instructions are executed by a processor, each process of the above-mentioned data recovery method embodiment is implemented, and can achieve The same technical effects are not repeated here to avoid repetition.
  • the processor is the processor in the network device described in the above embodiment.
  • the readable storage medium includes computer readable storage media, such as computer read-only memory ROM, random access memory RAM, magnetic disk or optical disk, etc.
  • An embodiment of the present application further provides a chip.
  • the chip includes a processor and a communication interface.
  • the communication interface is coupled to the processor.
  • the processor is used to run programs or instructions to implement the above method embodiment of data recovery. Each process can achieve the same technical effect. To avoid repetition, we will not go into details here.
  • chips mentioned in the embodiments of this application may also be called system-on-chip, system-on-a-chip, system-on-a-chip or system-on-chip, etc.
  • Embodiments of the present application provide a computer program product.
  • the program product is stored in a storage medium.
  • the program product is executed by at least one processor to implement the above data recovery method embodiments.
  • Each process can achieve the same technical effect. To avoid repetition, we will not go into details here.
  • the methods of the above embodiments can be implemented by means of software plus the necessary general hardware platform. Of course, it can also be implemented by hardware, but in many cases the former is better. implementation.
  • the technical solution of the present application can be embodied in the form of a computer software product that is essentially or contributes to the existing technology.
  • the computer software product is stored in a storage medium (such as ROM/RAM, disk , optical disk), including several instructions to cause a terminal (which can be a mobile phone, computer, server, or network device, etc.) to execute the methods described in various embodiments of this application.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)
  • Computer And Data Communications (AREA)
  • Techniques For Improving Reliability Of Storages (AREA)

Abstract

Un procédé et un appareil de récupération de données, un dispositif de réseau et un support d'enregistrement sont divulgués dans des modes de réalisation de la présente invention. Le procédé consiste à : effectuer un traitement de sauvegarde sur tous les éléments de données matérielles d'un dispositif de réseau écrits dans du matériel pour obtenir une copie de sauvegarde, la copie de sauvegarde comprenant des données de sauvegarde correspondant aux données matérielles, et les données matérielles comprenant des données d'entrée de matériel ; et lorsqu'il est détecté que le dispositif de réseau est redémarré, écrire tous les éléments de données de sauvegarde dans la copie de sauvegarde dans le matériel.
PCT/CN2023/086927 2022-08-15 2023-04-07 Procédé et appareil de récupération de données, dispositif de réseau et support d'enregistrement WO2024036990A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN202210977066.0A CN115378815A (zh) 2022-08-15 2022-08-15 数据恢复的方法、装置、网络设备及存储介质
CN202210977066.0 2022-08-15

Publications (1)

Publication Number Publication Date
WO2024036990A1 true WO2024036990A1 (fr) 2024-02-22

Family

ID=84065348

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2023/086927 WO2024036990A1 (fr) 2022-08-15 2023-04-07 Procédé et appareil de récupération de données, dispositif de réseau et support d'enregistrement

Country Status (2)

Country Link
CN (1) CN115378815A (fr)
WO (1) WO2024036990A1 (fr)

Families Citing this family (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN115378815A (zh) * 2022-08-15 2022-11-22 中兴通讯股份有限公司 数据恢复的方法、装置、网络设备及存储介质

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101150587A (zh) * 2007-10-24 2008-03-26 华为技术有限公司 一种多协议标签交换流量工程流量切换的方法、设备及系统
WO2019047855A1 (fr) * 2017-09-06 2019-03-14 新华三技术有限公司 Procédé et appareil de sauvegarde pour un bras ayant un plan de transfert et un plan de commande séparés
CN111083049A (zh) * 2019-12-13 2020-04-28 迈普通信技术股份有限公司 一种用户表项恢复方法、装置、电子设备及存储介质
US20210049043A1 (en) * 2019-08-15 2021-02-18 Cisco Technology, Inc. Dynamic hardware resource shadowing
CN115378815A (zh) * 2022-08-15 2022-11-22 中兴通讯股份有限公司 数据恢复的方法、装置、网络设备及存储介质

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101150587A (zh) * 2007-10-24 2008-03-26 华为技术有限公司 一种多协议标签交换流量工程流量切换的方法、设备及系统
WO2019047855A1 (fr) * 2017-09-06 2019-03-14 新华三技术有限公司 Procédé et appareil de sauvegarde pour un bras ayant un plan de transfert et un plan de commande séparés
US20210049043A1 (en) * 2019-08-15 2021-02-18 Cisco Technology, Inc. Dynamic hardware resource shadowing
CN111083049A (zh) * 2019-12-13 2020-04-28 迈普通信技术股份有限公司 一种用户表项恢复方法、装置、电子设备及存储介质
CN115378815A (zh) * 2022-08-15 2022-11-22 中兴通讯股份有限公司 数据恢复的方法、装置、网络设备及存储介质

Also Published As

Publication number Publication date
CN115378815A (zh) 2022-11-22

Similar Documents

Publication Publication Date Title
US9219640B2 (en) Performing failover in a redundancy group
JP4678878B2 (ja) インターネットプロトコルネットワークにおける仮想リング上での通信のためのシステムおよび方法
US20060294241A1 (en) Preserving sessions in a wireless network
CN103825817B (zh) 路由协议重启后不间断路由的实现方法和装置
CN106789638B (zh) 一种处理路由的方法及网络设备
WO2024036990A1 (fr) Procédé et appareil de récupération de données, dispositif de réseau et support d'enregistrement
US9319267B1 (en) Replication in assured messaging system
WO2016177231A1 (fr) Procédé et dispositif de commutation de sauvegarde active basée double commande
WO2018032869A1 (fr) Procédé et dispositif pour commander une transmission de multidiffusion
WO2020057445A1 (fr) Système, procédé et dispositif de communication
CN111083049B (zh) 一种用户表项恢复方法、装置、电子设备及存储介质
CN112367182A (zh) 容灾主备用设备的配置方法及装置
CN106712997B (zh) 表项恢复的方法、设备及系统
CN109379239B (zh) 一种OpenStack环境中配置接入交换机的方法及装置
CN108900441B (zh) 网络切换方法、第一电子设备及可读存储介质
WO2019085651A1 (fr) Procédé de configuration de réseau sdn, dispositif de commande, commutateur et support d'informations
WO2024093446A1 (fr) Procédé et appareil de communication de dérivation, dispositif et support de stockage lisible
US11042430B2 (en) Elastic consistency high availability in multiple boards
US10951732B2 (en) Service processing method and device
CN107846476B (zh) 一种信息同步方法、设备及存储介质
JP3304365B2 (ja) メッセージ通信制御方法および通信システム
CN104967641B (zh) 一种实现主备元服务器数据同步的方法及装置
WO2020083271A1 (fr) Appareil et procédé de convergence de liaison agrégée, et support d'informations
CN113765783B (zh) 通信方法及装置
US11956149B2 (en) Peer relationship management method and apparatus, device, and storage medium

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 23853901

Country of ref document: EP

Kind code of ref document: A1