WO2016062116A1 - 一种虚拟化网络备份、恢复的方法和相应装置 - Google Patents

一种虚拟化网络备份、恢复的方法和相应装置 Download PDF

Info

Publication number
WO2016062116A1
WO2016062116A1 PCT/CN2015/083087 CN2015083087W WO2016062116A1 WO 2016062116 A1 WO2016062116 A1 WO 2016062116A1 CN 2015083087 W CN2015083087 W CN 2015083087W WO 2016062116 A1 WO2016062116 A1 WO 2016062116A1
Authority
WO
WIPO (PCT)
Prior art keywords
backup
vnfm
nfvo
vnf
request
Prior art date
Application number
PCT/CN2015/083087
Other languages
English (en)
French (fr)
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 WO2016062116A1 publication Critical patent/WO2016062116A1/zh

Links

Images

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/40—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks using virtualisation of network functions or resources, e.g. SDN or NFV entities

Definitions

  • This paper covers the field of backup and recovery, especially the backup, recovery methods and corresponding devices under the virtualized network.
  • NFV Network Function Virtualization management and Orchestration domain
  • the biggest potential risk of the application of virtualization technology is the data security issue, especially the virtualization of the telecom core network.
  • the underlying CMS platform provides a relatively comprehensive security guarantee, such as an active/standby mechanism and remote disaster recovery, it can implement fast service recovery from the bottom of the hardware.
  • the underlying backup cannot ensure the consistency of the data backup of the entire system, and the backup and recovery of the network topology relationship between each VNF in the entire system cannot be achieved, which has certain limitations.
  • Data backup of the telecommunication network device can also be implemented by the functional entity at the service level.
  • the data management and recovery of the lower-level network element device is implemented by the EMS (Element Management Systems) of the service domain, and the network element itself Data backup and recovery function can also be implemented Now, these are the traditional backup and recovery methods for telecom physical devices.
  • EMS lement Management Systems
  • this method exposes a congenital defect: it cannot achieve fast backup and recovery of its own physical resources, including hosts, networks, and so on.
  • This document provides a method for backup and recovery of virtualized networks and corresponding devices to achieve fast backup and recovery of physical resources.
  • a method for backing up a virtualized network comprising:
  • the network function virtualization scheduler NFVO receives a backup request, and the backup request includes a VNF backup request or a VNFM backup request or an NFVO backup request;
  • the NFVO When the backup request is the VNF backup request, the NFVO performs a VNF backup operation according to the VNF backup request;
  • the NFVO When the backup request is the VNFM backup request, the NFVO performs a VNFM backup operation according to the VNFM backup request, and performs a backup operation of each VNF managed by the VNFM after the VNFM backup succeeds;
  • the NFVO When the backup request is the NFVO backup request, the NFVO performs an NFVO backup operation according to the NFVO backup request, and after the NFVO backup succeeds, performs a backup operation of each VNFM managed by the NFVO; and succeeds in each VNFM backup. After each VNFM management, each VNF backup operation is performed.
  • the NFVO performs the VNF backup operation according to the VNF backup request, including:
  • the VNFM generates a VNF backup data packet according to the VNF backup request;
  • the VNF backup data packet includes backup data information of the VNF and configuration information of the VNF;
  • the VNF backup data packet is uploaded through the cloud management system CMS.
  • the NFVO When the backup request is the VNFM backup request, the NFVO performs a VNFM backup operation according to the VNFM backup request, and performs the VNFM after the VNFM backup is successful.
  • the backup operations for each VNF managed include:
  • the VNFM generates a VNFM backup data packet according to the VNFM backup request, where the VNFM backup data packet includes backup data information of each VNF managed by the VNFM, configuration information of the VNFM, and configuration information of each VNF. ;
  • the VNFM backup data packet is uploaded through the CMS.
  • the NFVO When the backup request is the NFVO backup request, the NFVO performs an NFVO backup operation according to the NFVO backup request, and after the NFVO backup succeeds, performs a backup operation of each VNFM managed by the NFVO; and succeeds in each VNFM backup.
  • the backup operations for each VNF managed by each VNFM are:
  • the NFVO generates an NFVO backup data packet according to the NFVO backup request, the NFVO backup data packet includes backup data information of each VNF managed by the NFVO, configuration information of the NFVO, and each VNFM managed by the NFVO Configuration information and configuration information of each VNF;
  • the NFVO backup data packet is uploaded through the CMS.
  • the configuration information of the VNF includes the VNF system configuration information and VNF-VNF topology association information;
  • the configuration information of the VNFM includes the VNFM system configuration information, VNFM-VNF topology association information, and NFVO-VNFM topology association information;
  • the configuration information of the NFVO includes virtual machine specification information, system configuration information of each VNFM and each VNF, and topology related information of the NFVO-VNFM-VNF.
  • a method for restoring a virtualized network comprising:
  • the network function virtualization scheduler NFVO receives a recovery request, and the recovery request includes a VNF recovery request or a VNFM recovery request or an NFVO recovery request;
  • the recovery request is the VNF recovery request
  • the NFVO is restored according to the VNF Seeking to perform VNF recovery operations
  • the NFVO When the recovery request is the VNFM recovery request, the NFVO performs a VNFM recovery operation according to the VNFM recovery request;
  • the NFVO When the recovery request is the NFVO recovery request, the NFVO performs an NFVO recovery operation according to the NFVO recovery request.
  • the NFVO performs a VNF recovery operation according to the VNF recovery request, including:
  • the VNFM receives the VNF recovery request, and performs an instance recovery on the VNF according to the VNF recovery request;
  • the VNF performs data recovery on the VNF
  • a recovery success response message is sent to the NFVO through the VNFM.
  • the NFVO performs a VNFM recovery operation according to the VNFM recovery request, including:
  • the NFVO performs the VNFM instance recovery, and the VNFM data recovery is performed after the VNFM instance is successfully restored, and the VNFM restored data is consistent with the data of each VNF managed by the VNFM.
  • the NFVO performing the NFVO recovery operation according to the NFVO recovery request includes:
  • the NFVO performs the NFVO instance recovery, and the NFVO data recovery is performed after the NFVO instance is successfully restored, and the NFVO restored data is consistent with the data of each VNFM and each VNF managed by the NFVO.
  • a backup device for a virtualized network comprising:
  • the first receiving module is configured to: receive a backup request, where the backup request includes a VNF backup Request or VNFM backup request or NFVO backup request;
  • the backup module is configured to perform a VNF backup operation according to the VNF backup request when the backup request is the VNF backup request, and perform a VNFM backup operation according to the VNFM backup request when the backup request is the VNFM backup request. And performing a backup operation of each VNF managed by the VNFM after the VNFM backup succeeds; when the backup request is the NFVO backup request, performing an NFVO backup operation according to the NFVO backup request, and after the NFVO backup is successful, proceeding The backup operation of each VNFM managed by NFVO; and the backup operation of each VNF managed by each VNFM after each VNFM backup is successful.
  • the backup module includes:
  • a first generating unit configured to: when the backup request is the VNF backup request, generate a VNF backup data packet according to the VNF backup request; the VNF backup data packet includes backup data information of the VNF and the VNF Configuration information;
  • the first uploading unit is configured to: upload the VNF backup data packet by using a cloud management system CMS.
  • the backup module includes:
  • a second generating unit configured to: when the backup request is the VNFM backup request, generate a VNFM backup data packet according to the VNFM backup request, where the VNFM backup data packet includes backup data information of each VNF managed by the VNFM The configuration information of the VNFM and the configuration information of each VNF;
  • the second uploading unit is configured to: upload the VNFM backup data packet by using the CMS.
  • the backup module includes:
  • a third generating unit configured to: when the backup request is the NFVO backup request, generate an NFVO backup data packet according to the NFVO backup request, where the NFVO backup data packet includes backup data information of each VNF managed by the NFVO The configuration information of the NFVO, configuration information of each VNFM managed by the NFVO, and configuration information of each VNF;
  • the third uploading unit is configured to: upload the NFVO backup data packet through the CMS.
  • the configuration information of the VNF includes the VNF system configuration information and VNF-VNF topology association information;
  • the configuration information of the VNFM includes the VNFM system configuration information, VNFM-VNF topology association information, and NFVO-VNFM topology association information;
  • the configuration information of the NFVO includes virtual machine specification information, system configuration information of each VNFM and each VNF, and topology related information of the NFVO-VNFM-VNF.
  • a recovery device for a virtualized network comprising:
  • the second receiving module is configured to: receive a recovery request, where the recovery request includes a VNF recovery request or a VNFM recovery request or an NFVO recovery request;
  • the recovery module is configured to: when the recovery request is the VNF recovery request, perform a VNF recovery operation according to the VNF recovery request; and when the recovery request is the VNFM recovery request, perform a VNFM recovery operation according to the VNFM recovery request; When the recovery request is the NFVO recovery request, the NFVO recovery operation is performed according to the NFVO recovery request.
  • the recovery module includes:
  • the first instance recovery unit is configured to: when the recovery request is the VNF recovery request, receive the VNF recovery request, and perform instance recovery on the VNF according to the VNF recovery request;
  • a first data recovery unit configured to: perform data recovery on the VNF
  • the response unit is set to: send a recovery success response message.
  • the recovery device includes:
  • a second instance recovery unit configured to: when the recovery request is the VNFM recovery request, perform the VNFM instance recovery;
  • a second data recovery unit configured to: after the VNFM instance is successfully restored VNFM data recovery, the VNFM recovered data is consistent with the data of each VNF managed by the VNFM.
  • the recovery module includes:
  • a third instance recovery unit configured to: when the recovery request is the NFVO recovery request, perform the NFVO instance recovery;
  • the third data recovery unit is configured to perform the NFVO data recovery after the NFVO instance is successfully restored, and the data of the NFVO recovery is consistent with the data of each VNFM and each VNF managed by the NFVO.
  • a computer readable storage medium storing computer executable instructions for performing the method of any of the above.
  • the above solution can implement fast backup and recovery of physical resources. It can not only improve the inherent shortage of traditional backup and recovery methods, but also save the recovery time required for system operation interruption in specific scenarios, and reduce operational risks and operation and maintenance costs caused by system hardware and software failures. It can also be used to quickly realize the replication and migration of telecommunication services across systems, and truly realize the flexible deployment of telecommunication services.
  • FIG. 1 is a flowchart of a method for virtualizing network backup in Embodiment 1 of the present invention
  • Embodiment 2 is a flowchart of a method for virtualized network recovery in Embodiment 1 of the present invention
  • FIG. 3 is a schematic diagram of an apparatus for virtualized network backup in Embodiment 1 of the present invention.
  • FIG. 4 is a schematic diagram of an apparatus for virtualized network recovery in Embodiment 1 of the present invention.
  • FIG. 5 is a flowchart of a VNF backup in Embodiment 2 of the present invention.
  • FIG. 7 is a flowchart of a VNFM backup in Embodiment 2 of the present invention.
  • FIG. 9 is a flow chart of NFVO backup in the second embodiment of the present invention.
  • the embodiment of the present invention proposes to add a backup and recovery function to the Orchestrator module (the resource scheduling scheduler, hereinafter referred to as NFVO) in the NFV-MANO domain, and cooperate with the VNFM (VNF management) module to implement unified data of the VNFs managed in the domain.
  • Backup and recovery including:
  • the backup content includes virtual machine and network specification data, Guest OS image resource, system configuration data, and service data. All backup data can be customized according to its own attribute characteristics under the premise of ensuring consistency.
  • the backup data can be backed up. It can be stored in a third-party network shared storage, or it can be directly stored in the cloud storage through the CMS. Users do not need to care about the storage location.
  • VNF migration such as the switching of the underlying VM.
  • the NFV-MANO domain mainly includes three functional entities, which are NFVO, VNFM, and VNFs according to the hierarchical range.
  • the backup and recovery methods in the embodiments of the present invention are mainly performed around the three functional entities.
  • the solution is as follows:
  • the NFVO module provides a backup control function master control interface. According to the scope and its dependencies, the backup objects are divided into three levels, namely NFVO layer, VNFM layer and VNFs layer. Each level of backup data generates a separate package package, which enables data backup through shared storage or cloud storage systems.
  • the data information that the NFVO layer needs to back up includes:
  • Virtual machine specification information such as CPU, memory, storage and other specifications.
  • the data information that needs to be backed up by the VNFM layer includes:
  • VNFM own system configuration description information
  • the data information that needs to be backed up by the VNFs layer includes:
  • the data backup and recovery function of the NFVO layer is completed by the NFVO module itself, and the backup data information is directly obtained from the NFVO itself.
  • the CMS interface can be called to implement cloud storage.
  • the data backup and recovery functions of the VNFM layer and the VNFs layer are mainly implemented by the VNFM module, wherein the service data of the VNFs can be obtained through the VNFs self-backup recovery function.
  • the backup and recovery function requires three levels of data backup to have a parent-child dependency. That is, NFVO and VNFM are parent and child. VNFM and VNFs are parent-child relationships.
  • the backup of the child layer must be consistent with the parent layer.
  • the backup packets for each layer must be time stamped.
  • Recovery supports single-layer single VNF recovery, and also supports system-level recovery of multiple layers of multiple VNFs.
  • the backup data of each layer is prepared from the sub-layer first, and the sub-layer backup data closest to the recovery time point is obtained according to the backup data timestamp, and then the parent closest to the sub-layer time point is obtained.
  • Layer backup data is obtained from the sub-layer first, and the sub-layer backup data closest to the recovery time point is obtained according to the backup data timestamp, and then the parent closest to the sub-layer time point is obtained.
  • Multi-layer data recovery If it is required to restore the VNFs and VNFM data of 2014.8.13, the backup and recovery function first obtains the VNFs layer backup data closest to 2014.8.13 (2014.8.13), and then obtains the timestamp of the backup data closest to the VNFs. The VNFM backup data (2014.8.11) is ready for recovery.
  • the backup and recovery function selects the backup data of 2014.8.17 of VNFs, 2014.8.15 of VNFM, and 2014.8.11 of O for recovery.
  • NFVO provides a backup recovery strategy and backup data cleanup function, and retains data backups for a period of time according to the backup strategy. When data is cleaned, the data consistency of each layer needs to be guaranteed.
  • NFVO supports VNF backup and recovery operations between different VNFMs.
  • the VNF backup recovery under the same VNFM needs to be performed in the order of topology dependencies between each other.
  • an embodiment of the present invention provides a backup method for a virtualized network, where the method includes:
  • Step 11 The network function virtualization scheduler NFVO receives a backup request, where the backup request includes a VNF backup request or a VNFM backup request or an NFVO backup request;
  • Step 12 When the backup request is the VNF backup request, the NFVO performs a VNF backup operation according to the VNF backup request.
  • the NFVO When the backup request is the VNFM backup request, the NFVO performs a VNFM backup operation according to the VNFM backup request, and performs a backup operation of each VNF managed by the VNFM after the VNFM backup succeeds;
  • the NFVO When the backup request is the NFVO backup request, the NFVO performs an NFVO backup operation according to the NFVO backup request, and after the NFVO backup succeeds, performs a backup operation of each VNFM managed by the NFVO; and succeeds in each VNFM backup. After each VNFM management, each VNF backup operation is performed.
  • the NFVO performs the VNF backup operation according to the VNF backup request, including:
  • the VNFM generates a VNF backup data packet according to the VNF backup request;
  • the VNF backup data packet includes backup data information of the VNF and configuration information of the VNF;
  • the VNF backup data packet is uploaded through the cloud management system CMS.
  • the NFVO When the backup request is the VNFM backup request, the NFVO performs a VNFM backup operation according to the VNFM backup request, and performs a backup operation of each VNF managed by the VNFM after the VNFM backup is successful, including:
  • the VNFM generates a VNFM backup data packet according to the VNFM backup request, where the VNFM backup data packet includes backup data information of each VNF managed by the VNFM, configuration information of the VNFM, and configuration information of each VNF. ;
  • the NFVO When the backup request is the NFVO backup request, the NFVO performs an NFVO backup operation according to the NFVO backup request, and after the NFVO backup succeeds, each of the NFVO management is performed.
  • the backup operation of VNFM; and the backup operation of each VNF managed by each VNFM after each VNFM backup is successful includes:
  • the NFVO generates an NFVO backup data packet according to the NFVO backup request, the NFVO backup data packet includes backup data information of each VNF managed by the NFVO, configuration information of the NFVO, and each VNFM managed by the NFVO Configuration information and configuration information of each VNF;
  • the configuration information of the VNF includes the VNF system configuration information and VNF-VNF topology association information;
  • the configuration information of the VNFM includes the VNFM system configuration information, VNFM-VNF topology association information, and NFVO-VNFM topology association information;
  • the configuration information of the NFVO includes virtual machine specification information, system configuration information of each VNFM and each VNF, and topology related information of the NFVO-VNFM-VNF.
  • step 11 After step 11, before step 12, there are also:
  • Step 13 NFVO checks if there is a backup condition
  • the NFVO When the backup condition is met, the NFVO performs a corresponding backup operation according to the backup request.
  • the embodiment of the present invention further provides a method for restoring a virtualized network, which corresponds to the backup method provided by the embodiment of the present invention, and the method includes:
  • Step 21 The network function virtualization scheduler NFVO receives a recovery request, where the recovery request includes a VNF recovery request or a VNFM recovery request or an NFVO recovery request;
  • Step 22 When the recovery request is the VNF recovery request, the NFVO performs a VNF recovery operation according to the VNF recovery request.
  • the NFVO When the recovery request is the VNFM recovery request, the NFVO performs a VNFM recovery operation according to the VNFM recovery request;
  • the recovery request is the NFVO recovery request
  • the NFVO is restored according to the NFVO Request an NFVO recovery operation.
  • the NFVO performs a VNF recovery operation according to the VNF recovery request, including:
  • the VNFM receives the VNF recovery request, and performs an instance recovery on the VNF according to the VNF recovery request;
  • the VNF performs data recovery on the VNF
  • a recovery success response message is sent to the NFVO through the VNFM.
  • the NFVO performs a VNFM recovery operation according to the VNFM recovery request, including:
  • the NFVO performs the VNFM instance recovery, and after the instance is successfully restored, the VNFM data recovery is performed, and the VNFM restored data is consistent with the data of each VNF managed by the VNFM.
  • the NFVO performing the NFVO recovery operation according to the NFVO recovery request includes:
  • the NFVO performs the NFVO instance recovery, and the NFVO data recovery is performed after the instance is successfully restored, and the NFVO restored data is consistent with the data of each VNFM and each VNF managed by the NFVO.
  • step 21 After step 21, before step 22, the following steps can also be performed:
  • Step 23 The NFVO check whether there is a recovery condition
  • the NFVO When the recovery condition is satisfied, the NFVO performs a corresponding recovery operation according to the recovery request.
  • an embodiment of the present invention further provides a backup device for a virtualized network, where the device includes:
  • the first receiving module 31 is configured to: receive a backup request, where the backup request includes a VNF backup request or a VNFM backup request or an NFVO backup request;
  • the backup module 32 is configured to: when the backup request is the VNF backup request, according to the The VNF backup request performs a VNF backup operation.
  • the VNFM backup operation is performed according to the VNFM backup request, and the backup operation of each VNF managed by the VNFM is performed after the VNFM backup is successful.
  • the backup request is the NFVO backup request
  • the NFVO backup operation is performed according to the NFVO backup request, and after the NFVO backup is successful, the backup operation of each VNFM managed by the NFVO is performed; and after each VNFM backup is successful, A backup operation for each VNF managed by each VNFM.
  • the backup module 32 includes:
  • a first generating unit configured to: when the backup request is the VNF backup request, the VNFM generates a VNF backup data packet according to the VNF backup request; the VNF backup data packet includes backup data information of the VNF and the VNF Configuration information;
  • the first uploading unit is configured to: upload the VNF backup data packet by using a cloud management system CMS.
  • the backup module 32 further includes:
  • a second generating unit configured to: when the backup request is the VNFM backup request, generate a VNFM backup data packet according to the VNFM backup request, where the VNFM backup data packet includes backup data information of each VNF managed by the VNFM The configuration information of the VNFM and the configuration information of each VNF;
  • the second uploading unit is configured to: upload the VNFM backup data packet by using the CMS.
  • the backup module 32 further includes:
  • a third generating unit configured to: when the backup request is the NFVO backup request, generate an NFVO backup data packet according to the NFVO backup request, where the NFVO backup data packet includes backup data information of each VNF managed by the NFVO The configuration information of the NFVO, configuration information of each VNFM managed by the NFVO, and configuration information of each VNF;
  • the third uploading unit is configured to: upload the NFVO backup data packet by using the CMS.
  • the configuration information of the VNF includes the VNF system configuration information and VNF-VNF topology association information;
  • the configuration information of the VNFM includes the VNFM system configuration information, VNFM-VNF topology association information, and NFVO-VNFM topology association information;
  • the configuration information of the NFVO includes virtual machine specification information, system configuration information of each VNFM and each VNF, and topology related information of the NFVO-VNFM-VNF.
  • the embodiment of the present invention further provides a recovery device for a virtualized network, which corresponds to a backup device of a virtualized network in the embodiment of the present invention, and the device includes:
  • the second receiving module 41 is configured to: receive a recovery request, where the recovery request includes a VNF recovery request or a VNFM recovery request or an NFVO recovery request;
  • the recovery module 42 is configured to: when the recovery request is the VNF recovery request, perform a VNF recovery operation according to the VNF recovery request; when the recovery request is the VNFM recovery request, perform a VNFM recovery operation according to the VNFM recovery request.
  • the recovery request is the NFVO recovery request
  • the NFVO recovery operation is performed according to the NFVO recovery request.
  • the recovery module 42 includes:
  • the first instance recovery unit is configured to: when the recovery request is the VNF recovery request, receive the VNF recovery request, and perform instance recovery on the VNF according to the VNF recovery request;
  • a first data recovery unit configured to: perform data recovery on the VNF
  • the response unit is configured to: send a recovery success response message to the NFVO through the VNFM.
  • the recovery device 42 further includes:
  • a second instance recovery unit configured to: when the recovery request is the VNFM recovery request, perform the VNFM instance recovery;
  • the second data recovery unit is configured to perform the VNFM data recovery after the VNFM instance is successfully restored, and the VNFM restored data is consistent with the data of each VNF managed by the VNFM.
  • the recovery module 42 further includes:
  • a third instance recovery unit configured to: when the recovery request is the NFVO recovery request, perform the NFVO instance recovery;
  • the third data recovery unit is configured to perform the NFVO data recovery after the NFVO instance is successfully restored, and the data of the NFVO recovery is consistent with the data of each VNFM and each VNF managed by the NFVO.
  • the process of the VNF backup in this embodiment is as follows:
  • Step 101 USER sends a VNF backup request to NFVO.
  • Step 102 After receiving the request, the NFVO first performs command information verification to check whether the backup requirement is met, and if yes, the next step is returned if not met.
  • Step 103 The NFVO sends a VNF backup request to the VNFM.
  • Step 104 The VNFM collects and backs up backup data such as the configured VNF system configuration information and topology related information.
  • Step 105 The VNFM sends a VNF data backup request to the VNF.
  • Step 106 The VNF receives the backup request of the VNFM and starts the backup of the service data.
  • Step 107 After the VNF backup succeeds, notify the VNFM that the backup is successful, and prepare to uniformly package and generate the backup data packet.
  • Step 108 After the VNFM is successfully packaged, the NFVO backup is successfully notified, and data uploading is prepared.
  • Step 109 The NFVO receives the response from the VNFM, and notifies the CMS to prepare to upload the backup data.
  • Step 110 The backup data is uploaded successfully, and the CMS feeds back the NFVO data backup successfully.
  • Step 111 The NFVO feedback USER data backup is successful.
  • the VNF recovery process in this embodiment is as follows:
  • Step 201 USER sends a VNF recovery request to the NFVO.
  • Step 202 After receiving the request, the NFVO first performs verification to check whether the recovery requirement is met, and if the verification passes, the next step is performed, otherwise the return fails.
  • Step 203 The NFVO notifies the CMS to prepare the VNF backup data for recovery.
  • Step 204 After receiving the notification of the NFVO, the CMS checks and prepares related resources, and notifies the NFVO after preparing for OK.
  • Step 205 The NFVO sends a resume VNF request to the VNFM.
  • Step 206 After receiving the NFVO request, the VNFM first starts the VNF instance recovery.
  • Step 207 After the VNF instance is successfully restored, the VNFM notifies the VNF to perform service data recovery.
  • Step 208 The VNF receives the data recovery request of the VNFM and starts data recovery.
  • Step 209 Notify the VNFM after the VNF data recovery is successful.
  • Step 210 The VNFM notifies the NFVO data recovery success.
  • Step 211 NFVO notifies USER that the data recovery is successful.
  • the process of the VNFM backup in this embodiment is as follows:
  • Step 301 USER sends a VNFM data backup request to the NFVO.
  • Step 302 After receiving the request, the NFVO performs verification to check whether there is a backup condition.
  • Step 303 After the NFVO check is passed, the VNFM is notified to perform VNFM data backup.
  • Step 304 After receiving the backup request, the VNFM starts to perform VFNM data backup, which mainly includes VNFM own system configuration data information, VNFM-VNFs network topology description information, and NFVO-VNFM network topology description and the like.
  • Step 305 After the VNFM backup is successful, the VNFM backup data packet is generated, and the VNF is notified to perform data backup.
  • Step 306 The VNF receives the backup of the VNFM, and starts to perform VNF data backup, including VNF system configuration data new, VNF-VNF network topology information, VNF service data information and the like.
  • Step 307 After the VNF backup is successful, the VNF backup data packet is generated, and the VNFM backup is successful, and the data is ready to be uploaded.
  • Step 308 The VNFM receives the backup success information of the VNF, and the NFVO backup is successful, and the data is ready to be uploaded.
  • Step 309 The NFVO receives the backup success information of the VNFM, and notifies the CMS to prepare to upload the backup data packets of the two layers.
  • Step 310 The backup data packet is successfully uploaded, and the CMS feeds back the NFVO upload.
  • Step 311 The NFVO feedback USER data backup is successful.
  • the process of VNFM recovery in this embodiment is as follows:
  • Step 401 USER sends a VNFM recovery request to the NFVO.
  • Step 402 After receiving the request, the NFVO performs verification to check whether the VNFM recovery condition is met.
  • Step 403 After the verification is passed, the data recovery of the VNFM is started. First, the VNFM instance is restored. After the recovery is successful, the VFNM data recovery is performed.
  • Step 404 After the data recovery is successful, the NFVO returns to the USER and the recovery is successful.
  • the flow of the NFVO backup in this embodiment is as follows:
  • Step 501 USER sends an NFVO face data backup request to the NFVO.
  • Step 502 After receiving the request, the NFVO performs verification to check whether there is a backup condition.
  • Step 503 After the verification is passed, the data backup on the NFVO is started, which mainly includes configuration information of all virtual machine specifications, mirroring and version of VNFM and VNFs, and network topology information of NFVO-VNFM-VNFs.
  • Step 504 After the NFVO backup is successfully packaged, the NFVO backup data is generated, and the notification is notified. VNFM performs data backup.
  • Step 505 The VNFM receives the backup request of the NFVO, and starts the VNFM data backup, including the VNFM self-configuration data information, the VNFM-VNFs network topology description information, and the NFVO-VNFM network topology description and the like.
  • Step 506 After the VNFM backup is successfully completed, the VNFM layer backup data is generated, and the VNFs are notified to perform data backup.
  • Step 507 The VNF receives the backup request of the VNFM, and starts the VNF data backup, including the VNF system configuration data new, the VNF-VNF network topology information, and the VNF service data information and the like.
  • Step 508 After the VNF backup succeeds, the VNF backup data is generated, and the VNFM backup is successful, and the data is ready to be uploaded.
  • Step 509 The VNFM receives the backup success information of the VNF, and the NFVO backup is successful, and the data is ready to be uploaded.
  • Step 510 The NFVO receives the backup success information of the VNFM, and notifies the CMS to upload three levels of backup data.
  • Step 511 The backup data is successfully uploaded, and the CMS feeds back the NFVO data upload.
  • Step 512 The NFVO feedback USER backup is successfully restored.
  • all or part of the steps of the above embodiments may also be implemented by using an integrated circuit. These steps may be separately fabricated into individual integrated circuit modules, or multiple modules or steps may be fabricated into a single integrated circuit module. achieve.
  • the devices/function modules/functional units in the above embodiments may be implemented by a general-purpose computing device, which may be centralized on a single computing device or distributed over a network of multiple computing devices.
  • the device/function module/functional unit in the above embodiment When the device/function module/functional unit in the above embodiment is implemented in the form of a software function module and sold or used as a stand-alone product, it can be stored in a computer readable storage medium.
  • the above mentioned computer readable storage medium may be a read only memory, a magnetic disk or an optical disk or the like.
  • the embodiments of the present invention can implement fast backup and recovery of the physical resources of the virtualized network, which can not only improve the inherent shortage of the traditional backup and recovery methods, but also save the recovery time required for system operation interruption in a specific scenario, and reduce the operation caused by system hardware and software failures. Risk and operation and maintenance costs can also be used to quickly realize the replication and migration of telecommunication services across systems, and truly realize the flexible deployment of telecommunication services.

Landscapes

  • Data Exchanges In Wide-Area Networks (AREA)
  • Information Retrieval, Db Structures And Fs Structures Therefor (AREA)

Abstract

一种虚拟化网络的备份方法，包括：网络功能虚拟化调度器NFVO接收备份请求，备份请求包括VNF备份请求或VNFM备份请求或NFVO备份请求；当备份请求为VNF备份请求时，NFVO根据VNF备份请求进行VNF备份操作；当备份请求为VNFM备份请求时，NFVO根据VNFM备份请求进行VNFM备份操作，并在VNFM备份成功后进行VNFM管理的每个VNF的备份操作；当备份请求为NFVO备份请求时，NFVO根据NFVO备份请求进行NFVO备份操作，并在NFVO备份成功后，进行NFVO管理的每个VNFM的备份操作；以及在每个VNFM备份成功后进行每个VNFM管理的每个VNF的备份操作。

Description

一种虚拟化网络备份、恢复的方法和相应装置 技术领域
本文涉及备份和恢复领域，尤其涉及虚拟化网络下的备份、恢复方法及相应装置。
背景技术
随着IT技术的成熟，越来越多的电信运营型采用虚拟化技术来降低其CAPEX(Capital Expenditure，资本性支出)和OPEX(Operating Expense，运营成本)，基于NFV(Network Function Virtualization，网络功能虚拟化)协议标准的虚拟化技术解决方案能在很大程度上满足电信运营商的技术实现需求。因此，采用NFV标准架构来实现核心网虚拟化部署的解决方案成为越来越多运营商的必然选择。
所谓NFV，其核心思想就是实现电信设备的硬件和软件解耦分离。NFV标准中，将每个网元设备都作为一个独立应用功能VNF(虚拟网络功能)统一部署在采用标准接口的CMS(Content Management System，云管理系统)上，通过NFV-MANO(NFV Management and Orchestration，网络功能虚拟化管理与编排)域实现对核心网内所有网元及网络服务的编排和部署，从而实现电信网络的开放性、自动化、智能化。
但虚拟化技术的应用，最大的潜在风险是数据安全问题，电信核心网的虚拟化更是如此。相关技术中，虽然底层的CMS平台提供了较为全面的安全保证，譬如主备机制、异地容灾等，能够从硬件底层实现快速业务恢复。但对于跨CMS平台的系统，却无法通过这种底层备份来保证整个系统数据备份的一致性，也无法实现整个系统内每个VNF之间的网络拓扑关系备份恢复，存在一定的局限性。
我们也可以通过业务层面的功能实体来实现电信网络设备的数据备份，譬如通过业务域的EMS(Element Management Systems，网元管理系统)来实现对下级网元设备的数据备份恢复，网元自身的数据备份恢复功能也可以实 现，这些都是电信物理设备的传统备份恢复方式。但在虚拟化技术下，这种方式就会暴露出一个先天缺陷：不能实现对自身物理资源的快速备份、恢复，这种物理资源包括主机、网络等。
发明内容
本文提供一种虚拟化网络的备份、恢复的方法和相应装置，以实现对自身物理资源的快速备份、恢复。
一种虚拟化网络的备份方法，所述方法包括：
网络功能虚拟化调度器NFVO接收备份请求，所述备份请求包括VNF备份请求或VNFM备份请求或NFVO备份请求；
当备份请求为所述VNF备份请求时，所述NFVO根据所述VNF备份请求进行VNF备份操作；
当备份请求为所述VNFM备份请求时，所述NFVO根据所述VNFM备份请求进行VNFM备份操作，并在所述VNFM备份成功后进行所述VNFM管理的每个VNF的备份操作；
当备份请求为所述NFVO备份请求时，所述NFVO根据NFVO备份请求进行NFVO备份操作，并在NFVO备份成功后，进行所述NFVO管理的每个VNFM的备份操作；以及在每个VNFM备份成功后进行每个VNFM管理的每个VNF的备份操作。
可选地，
当备份请求为所述VNF备份请求时，所述NFVO根据所述VNF备份请求进行VNF备份操作包括：
VNFM根据所述VNF备份请求生成VNF备份数据包；所述VNF备份数据包包括所述VNF的备份数据信息以及所述VNF的配置信息；
通过云管理系统CMS上传所述VNF备份数据包。
可选地，
当备份请求为所述VNFM备份请求时，所述NFVO根据所述VNFM备份请求进行VNFM备份操作，并在所述VNFM备份成功后进行所述VNFM 管理的每个VNF的备份操作包括：
所述VNFM根据所述VNFM备份请求生成VNFM备份数据包，所述VNFM备份数据包包括所述VNFM管理的每个VNF的备份数据信息、所述VNFM的配置信息以及所述每个VNF的配置信息；
通过CMS上传所述VNFM备份数据包。
可选地，
当备份请求为所述NFVO备份请求时，所述NFVO根据NFVO备份请求进行NFVO备份操作，并在NFVO备份成功后，进行所述NFVO管理的每个VNFM的备份操作；以及在每个VNFM备份成功后进行每个VNFM管理的每个VNF的备份操作包括：
所述NFVO根据所述NFVO备份请求生成NFVO备份数据包，所述NFVO备份数据包包括所述NFVO管理的每个VNF的备份数据信息、所述NFVO的配置信息、所述NFVO管理的每个VNFM的配置信息以及所述每个VNF的配置信息；
通过CMS上传所述NFVO备份数据包。
可选地，
所述VNF的配置信息包括所述VNF系统配置信息和VNF-VNF拓扑关联信息；
所述VNFM的配置信息包括所述VNFM系统配置信息、VNFM-VNF拓扑关联信息以及NFVO-VNFM拓扑关联信息；
所述NFVO的配置信息包括虚拟机规格信息、每个VNFM和每个VNF的系统配置信息以及NFVO-VNFM-VNF的拓扑关联信息。
一种虚拟化网络的恢复方法，所述方法包括：
网络功能虚拟化调度器NFVO接收恢复请求，所述恢复请求包括VNF恢复请求或VNFM恢复请求或NFVO恢复请求；
当恢复请求为所述VNF恢复请求时，所述NFVO根据所述VNF恢复请 求进行VNF恢复操作；
当恢复请求为所述VNFM恢复请求时，所述NFVO根据所述VNFM恢复请求进行VNFM恢复操作；
当恢复请求为所述NFVO恢复请求时，所述NFVO根据所述NFVO恢复请求进行NFVO恢复操作。
可选地，
当恢复请求为所述VNF恢复请求时，所述NFVO根据所述VNF恢复请求进行VNF恢复操作包括：
VNFM接收所述VNF恢复请求，根据所述VNF恢复请求对所述VNF进行实例恢复；
所述VNF对所述VNF进行数据恢复；
通过所述VNFM向所述NFVO发送恢复成功响应消息。
可选地，
当恢复请求为所述VNFM恢复请求时，所述NFVO根据所述VNFM恢复请求进行VNFM恢复操作包括：
所述NFVO进行所述VNFM实例恢复，并在所述VNFM实例恢复成功后进行所述VNFM数据恢复，所述VNFM恢复的数据与所述VNFM管理的每个VNF的数据一致。
可选地，
当恢复请求为所述NFVO恢复请求时，所述NFVO根据所述NFVO恢复请求进行NFVO恢复操作包括：
所述NFVO进行所述NFVO实例恢复，并在所述NFVO实例恢复成功后进行所述NFVO数据恢复，所述NFVO恢复的数据与所述NFVO管理的每个VNFM以及每个VNF的数据一致。
一种虚拟化网络的备份装置，所述装置包括：
第一接收模块，设置为：接收备份请求，所述备份请求包括VNF备份 请求或VNFM备份请求或NFVO备份请求；
备份模块，设置为：当备份请求为所述VNF备份请求时，根据所述VNF备份请求进行VNF备份操作；当备份请求为所述VNFM备份请求时，根据所述VNFM备份请求进行VNFM备份操作，并在所述VNFM备份成功后进行所述VNFM管理的每个VNF的备份操作；当备份请求为所述NFVO备份请求时，根据NFVO备份请求进行NFVO备份操作，并在NFVO备份成功后，进行所述NFVO管理的每个VNFM的备份操作；以及在每个VNFM备份成功后进行每个VNFM管理的每个VNF的备份操作。
可选地，
所述备份模块包括：
第一生成单元，设置为：当备份请求为所述VNF备份请求时，根据所述VNF备份请求生成VNF备份数据包；所述VNF备份数据包包括所述VNF的备份数据信息以及所述VNF的配置信息；
第一上传单元，设置为：通过云管理系统CMS上传所述VNF备份数据包。
可选地，
所述备份模块包括：
第二生成单元，设置为：当备份请求为所述VNFM备份请求时，根据所述VNFM备份请求生成VNFM备份数据包，所述VNFM备份数据包包括所述VNFM管理的每个VNF的备份数据信息、所述VNFM的配置信息以及所述每个VNF的配置信息；
第二上传单元，设置为：通过CMS上传所述VNFM备份数据包。
可选地，
所述备份模块包括：
第三生成单元，设置为：当备份请求为所述NFVO备份请求时，根据所述NFVO备份请求生成NFVO备份数据包，所述NFVO备份数据包包括所述NFVO管理的每个VNF的备份数据信息、所述NFVO的配置信息、所述NFVO管理的每个VNFM的配置信息以及所述每个VNF的配置信息；
第三上传单元，设置为：通过CMS上传所述NFVO备份数据包。
可选地，
所述VNF的配置信息包括所述VNF系统配置信息和VNF-VNF拓扑关联信息；
所述VNFM的配置信息包括所述VNFM系统配置信息、VNFM-VNF拓扑关联信息以及NFVO-VNFM拓扑关联信息；
所述NFVO的配置信息包括虚拟机规格信息、每个VNFM和每个VNF的系统配置信息以及NFVO-VNFM-VNF的拓扑关联信息。
一种虚拟化网络的恢复装置，所述装置包括：
第二接收模块，设置为：接收恢复请求，所述恢复请求包括VNF恢复请求或VNFM恢复请求或NFVO恢复请求；
恢复模块，设置为：当恢复请求为所述VNF恢复请求时，根据所述VNF恢复请求进行VNF恢复操作；当恢复请求为所述VNFM恢复请求时，根据所述VNFM恢复请求进行VNFM恢复操作；当恢复请求为所述NFVO恢复请求时，根据所述NFVO恢复请求进行NFVO恢复操作。
可选地，
所述恢复模块包括：
第一实例恢复单元，设置为：当恢复请求为所述VNF恢复请求时，接收所述VNF恢复请求，根据所述VNF恢复请求对所述VNF进行实例恢复；
第一数据恢复单元，设置为：对所述VNF进行数据恢复；
响应单元，设置为：发送恢复成功响应消息。
可选地，
所述恢复装置包括：
第二实例恢复单元，设置为：当恢复请求为所述VNFM恢复请求时，进行所述VNFM实例恢复；
第二数据恢复单元，设置为：在所述VNFM实例恢复成功后进行所述 VNFM数据恢复，所述VNFM恢复的数据与所述VNFM管理的每个VNF的数据一致。
可选地，
所述恢复模块包括：
第三实例恢复单元，设置为：当恢复请求为所述NFVO恢复请求时，进行所述NFVO实例恢复；
第三数据恢复单元，设置为：在所述NFVO实例恢复成功后进行所述NFVO数据恢复，所述NFVO恢复的数据与所述NFVO管理的每个VNFM以及每个VNF的数据一致。
一种计算机可读存储介质，存储有计算机可执行指令，所述计算机可执行指令用于执行上述任一项的方法。
上述方案可以实现对自身物理资源的快速备份、恢复，不仅能够完善传统备份恢复方式的先天不足，节省特定场景下系统运营中断所需的恢复时间，降低系统软硬件故障引起的运营风险及运维成本，还可以用于快速实现跨系统的电信服务复制迁移，真正实现电信服务的灵活部署。
附图概述
图1是本发明实施例一中的虚拟化网络备份的方法流程图；
图2是本发明实施例一中的虚拟化网络恢复的方法流程图；
图3是本发明实施例一中的虚拟化网络备份的装置示意图；
图4是本发明实施例一中的虚拟化网络恢复的装置示意图；
图5是本发明实施例二中VNF备份的流程图；
图6是本发明实施例二中VNF恢复的流程图；
图7是本发明实施例二中VNFM备份的流程图；
图8是本发明实施例二中VNFM备份的流程图；
图9是本发明实施例二中NFVO备份的流程图。
本发明的实施方式
下文中将结合附图对本发明的实施方式进行详细说明。需要说明的是，在不冲突的情况下，本文中的实施例及实施例中的特征可以相互任意组合。
本发明实施例提出在NFV-MANO域中的Orchestrator模块(资源编排调度器，后文简称NFVO)上增加备份恢复功能，通过与VNFM(VNF管理)模块配合，实现对域内所管理的VNFs统一数据备份及恢复，包括：
1.域内单个或多个VNF的备份。
2.域内单个或多个VNFM的备份。
3.域内单个或多个VNF的恢复。
4.域内单个或多个VNFM的恢复。
备份的内容则包括虚机及网络规格数据、Guest OS镜像资源及系统配置数据、业务数据等，所有备份数据在保证一致性的前提下，可根据自身属性特点自定义相关备份粒度，备份数据可以存放到第三方网络共享存储，也可以直接通过CMS存放到云存储中，用户无需关心存放位置。
此备份方法实际可应用的场景包括如下：
1.VNF崩溃后的快速恢复，如虚机Guest OS系统损坏导致的VNF恢复。
2.VNF迁移，譬如底层VM的切换。
3.跨CMS的系统数据备份恢复等。
根据NFV-MANO系统架构定义,NFV-MANO域主要包括3个功能实体，按照层次范围依序分别为NFVO、VNFM、VNFs。本发明实施例中的备份、恢复方法主要围绕这3个功能实体进行。解决方法如下：
1)NFVO模块提供备份恢复功能总控接口，按照范围及其依赖关系，将备份对象分为三个层次，分别为NFVO层、VNFM层、VNFs层。每个层面的备份数据各自生成单独的package包，统一通过共享存储或云存储系统实现数据备份。
2)NFVO层需要备份的数据信息包括：
a.虚机规格信息，如CPU、内存、存储等规格信息。
b.VNF及VNFM的镜像、版本配置信息
c.NFVO-VNFM-VNFs的整个网络拓扑描述信息
3)VNFM层需要备份的数据信息包括：
a.VNFM自身的系统配置描述信息
b.VNFM-VNFs网络拓扑描述信息
c.VNFM-NFVO的网络拓扑描述信息
4)VNFs层需要备份的数据信息包括：
a.VNF系统配置数据信息
b.VNF业务运营数据信息
c.VNFs之间的网络拓扑信息
5)备份恢复方法：
a.NFVO层的数据备份恢复功能由NFVO模块自身完成，备份数据信息直接从NFVO自身获取，打包后可调用CMS接口实现云存储。
b.VNFM层与VNFs层的数据备份恢复功能主要由VNFM模块实现，其中VNFs的业务数据可通过VNFs自身备份恢复功能获取。
c.为保证系统运营的数据一致性，备份恢复功能要求三个层面的数据备份存在父子依赖关系。即NFVO与VNFM是父与子，VNFM与VNFs是父与子关系，子层的备份必须与父层保持一致，当父层数据备份完成，需连带触发子层数据备份,反之则不然。为实现这种约束关系，要求每层的备份数据包必须带有时间戳。
d.恢复支持单层单个VNF恢复，也支持多层多VNFs的系统级恢复。
e.准备多层数据恢复时，每层的备份数据准备首先从子层开始，根据备份数据时间戳获取最接近恢复时间点的子层备份数据，再以此获取最接近子层时间点的父层备份数据。
一个简单的备份恢复时间戳示例：
Figure PCTCN2015083087-appb-000001
Figure PCTCN2015083087-appb-000002
1)当NFVO层在2014.8.1进行备份时，连带触发VNFM及VNFs层的数据备份。
2)当VNFM在2014.8.9进行备份时，连带触发VNFs层的数据备份。
3)单层数据恢复：当要求恢复2014.8.13的VNFs的数据，备份恢复功能依据时间戳取获最靠近的VNFs备份数据(2014.8.13)进行恢复。
4)多层数据恢复：若要求恢复2014.8.13的VNFs及VNFM数据，备份恢复功能首先获取最接近2014.8.13的VNFs层备份数据(2014.8.13)，再获取最接近VNFs备份数据时间戳的VNFM备份数据(2014.8.11)准备恢复。
5)若要求恢复NFVO管理下的整个系统在2014.8.17的数据，备份恢复功能则依次选择VNFs的2014.8.17、VNFM的2014.8.15、O的2014.8.11的备份数据进行恢复。
6)NFVO提供备份恢复策略和备份数据清理功能，根据备份策略保留一段时期内的数据备份。数据清理时，每层的数据一致性需要保证。
7)NFVO支持不同VNFM间的VNF备份恢复并发操作，同一VNFM下的VNF备份恢复需按照彼此之间的拓扑依赖关系顺序进行。
实施例一
如图1所示，本发明实施例提供一种虚拟化网络的备份方法，所述方法包括：
步骤11：网络功能虚拟化调度器NFVO接收备份请求，所述备份请求包括VNF备份请求或VNFM备份请求或NFVO备份请求；
步骤12：当备份请求为所述VNF备份请求时，所述NFVO根据所述VNF备份请求进行VNF备份操作；
当备份请求为所述VNFM备份请求时，所述NFVO根据所述VNFM备份请求进行VNFM备份操作，并在所述VNFM备份成功后进行所述VNFM管理的每个VNF的备份操作；
当备份请求为所述NFVO备份请求时，所述NFVO根据NFVO备份请求进行NFVO备份操作，并在NFVO备份成功后，进行所述NFVO管理的每个VNFM的备份操作；以及在每个VNFM备份成功后进行每个VNFM管理的每个VNF的备份操作。
当备份请求为所述VNF备份请求时，所述NFVO根据所述VNF备份请求进行VNF备份操作包括：
VNFM根据所述VNF备份请求生成VNF备份数据包；所述VNF备份数据包包括所述VNF的备份数据信息以及所述VNF的配置信息；
通过云管理系统CMS上传所述VNF备份数据包。
当备份请求为所述VNFM备份请求时，所述NFVO根据所述VNFM备份请求进行VNFM备份操作，并在所述VNFM备份成功后进行所述VNFM管理的每个VNF的备份操作包括：
所述VNFM根据所述VNFM备份请求生成VNFM备份数据包，所述VNFM备份数据包包括所述VNFM管理的每个VNF的备份数据信息、所述VNFM的配置信息以及所述每个VNF的配置信息；
通过所述CMS上传所述VNFM备份数据包。
当备份请求为所述NFVO备份请求时，所述NFVO根据NFVO备份请求进行NFVO备份操作，并在NFVO备份成功后，进行所述NFVO管理的每个 VNFM的备份操作；以及在每个VNFM备份成功后进行每个VNFM管理的每个VNF的备份操作包括：
所述NFVO根据所述NFVO备份请求生成NFVO备份数据包，所述NFVO备份数据包包括所述NFVO管理的每个VNF的备份数据信息、所述NFVO的配置信息、所述NFVO管理的每个VNFM的配置信息以及所述每个VNF的配置信息；
通过所述CMS上传所述NFVO备份数据包。
所述VNF的配置信息包括所述VNF系统配置信息和VNF-VNF拓扑关联信息；
所述VNFM的配置信息包括所述VNFM系统配置信息、VNFM-VNF拓扑关联信息以及NFVO-VNFM拓扑关联信息；
所述NFVO的配置信息包括虚拟机规格信息、每个VNFM和每个VNF的系统配置信息以及NFVO-VNFM-VNF的拓扑关联信息。
在步骤11后，步骤12前，还可以有：
步骤13：NFVO检查是否具备备份条件；
当满足备份条件时，则所述NFVO根据所述备份请求进行相应的备份操作。
如图2所示，本发明实施例还提供一种虚拟化网络的恢复方法，与本发明实施例提供的备份方法相对应，所述方法包括：
步骤21：网络功能虚拟化调度器NFVO接收恢复请求，所述恢复请求包括VNF恢复请求或VNFM恢复请求或NFVO恢复请求；
步骤22：当恢复请求为所述VNF恢复请求时，所述NFVO根据所述VNF恢复请求进行VNF恢复操作；
当恢复请求为所述VNFM恢复请求时，所述NFVO根据所述VNFM恢复请求进行VNFM恢复操作；
当恢复请求为所述NFVO恢复请求时，所述NFVO根据所述NFVO恢复 请求进行NFVO恢复操作。
当恢复请求为所述VNF恢复请求时，所述NFVO根据所述VNF恢复请求进行VNF恢复操作包括：
VNFM接收所述VNF恢复请求，根据所述VNF恢复请求对所述VNF进行实例恢复；
所述VNF对所述VNF进行数据恢复；
通过所述VNFM向所述NFVO发送恢复成功响应消息。
当恢复请求为所述VNFM恢复请求时，所述NFVO根据所述VNFM恢复请求进行VNFM恢复操作包括：
所述NFVO进行所述VNFM实例恢复，并在该实例恢复成功后进行所述VNFM数据恢复，所述VNFM恢复的数据与所述VNFM管理的每个VNF的数据一致。
当恢复请求为所述NFVO恢复请求时，所述NFVO根据所述NFVO恢复请求进行NFVO恢复操作包括：
所述NFVO进行所述NFVO实例恢复，并在该实例恢复成功后进行所述NFVO数据恢复，所述NFVO恢复的数据与所述NFVO管理的每个VNFM以及每个VNF的数据一致。
在步骤21后，步骤22前，还可以有以下步骤：
步骤23：所述NFVO检查是否具备恢复条件；
当满足恢复条件时，则所述NFVO根据所述恢复请求进行相应的恢复操作。
如图3所示，本发明实施例还提供一种虚拟化网络的备份装置，所述装置包括：
第一接收模块31，设置为：接收备份请求，所述备份请求包括VNF备份请求或VNFM备份请求或NFVO备份请求；
备份模块32，设置为：当备份请求为所述VNF备份请求时，根据所述 VNF备份请求进行VNF备份操作；当备份请求为所述VNFM备份请求时，根据所述VNFM备份请求进行VNFM备份操作，并在所述VNFM备份成功后进行所述VNFM管理的每个VNF的备份操作；当备份请求为所述NFVO备份请求时，根据NFVO备份请求进行NFVO备份操作，并在NFVO备份成功后，进行所述NFVO管理的每个VNFM的备份操作；以及在每个VNFM备份成功后进行每个VNFM管理的每个VNF的备份操作。
可选地，
所述备份模块32包括：
第一生成单元，设置为：当备份请求为所述VNF备份请求时，VNFM根据所述VNF备份请求生成VNF备份数据包；所述VNF备份数据包包括所述VNF的备份数据信息以及所述VNF的配置信息；
第一上传单元，设置为：通过云管理系统CMS上传所述VNF备份数据包。
可选地，
所述备份模块32还包括：
第二生成单元，设置为：当备份请求为所述VNFM备份请求时，根据所述VNFM备份请求生成VNFM备份数据包，所述VNFM备份数据包包括所述VNFM管理的每个VNF的备份数据信息、所述VNFM的配置信息以及所述每个VNF的配置信息；
第二上传单元，设置为：通过所述CMS上传所述VNFM备份数据包。
可选地，
所述备份模块32还包括：
第三生成单元，设置为：当备份请求为所述NFVO备份请求时，根据所述NFVO备份请求生成NFVO备份数据包，所述NFVO备份数据包包括所述NFVO管理的每个VNF的备份数据信息、所述NFVO的配置信息、所述NFVO管理的每个VNFM的配置信息以及所述每个VNF的配置信息；
第三上传单元，设置为：通过所述CMS上传所述NFVO备份数据包。
可选地，
所述VNF的配置信息包括所述VNF系统配置信息和VNF-VNF拓扑关联信息；
所述VNFM的配置信息包括所述VNFM系统配置信息、VNFM-VNF拓扑关联信息以及NFVO-VNFM拓扑关联信息；
所述NFVO的配置信息包括虚拟机规格信息、每个VNFM和每个VNF的系统配置信息以及NFVO-VNFM-VNF的拓扑关联信息。
如图4所示，本发明实施例还提供一种虚拟化网络的恢复装置，与本发明实施例中虚拟化网络的备份装置相对应，所述装置包括：
第二接收模块41，设置为：接收恢复请求，所述恢复请求包括VNF恢复请求或VNFM恢复请求或NFVO恢复请求；
恢复模块42，设置为：当恢复请求为所述VNF恢复请求时，根据所述VNF恢复请求进行VNF恢复操作；当恢复请求为所述VNFM恢复请求时，根据所述VNFM恢复请求进行VNFM恢复操作；当恢复请求为所述NFVO恢复请求时，根据所述NFVO恢复请求进行NFVO恢复操作。
可选地，
所述恢复模块42包括：
第一实例恢复单元，设置为：当恢复请求为所述VNF恢复请求时，接收所述VNF恢复请求，根据所述VNF恢复请求对所述VNF进行实例恢复；
第一数据恢复单元，设置为：对所述VNF进行数据恢复；
响应单元，设置为：通过所述VNFM向所述NFVO发送恢复成功响应消息。
可选地，
所述恢复装置42还包括：
第二实例恢复单元，设置为：当恢复请求为所述VNFM恢复请求时，进行所述VNFM实例恢复；
第二数据恢复单元，设置为：在所述VNFM实例恢复成功后进行所述VNFM数据恢复，所述VNFM恢复的数据与所述VNFM管理的每个VNF的数据一致。
可选地，
所述恢复模块42还包括：
第三实例恢复单元，设置为：当恢复请求为所述NFVO恢复请求时，进行所述NFVO实例恢复；
第三数据恢复单元，设置为：在所述NFVO实例恢复成功后进行所述NFVO数据恢复，所述NFVO恢复的数据与所述NFVO管理的每个VNFM以及每个VNF的数据一致。
实施例二
如图5所示，本实施例中的VNF备份的流程如下：
步骤101：USER(用户)向NFVO发送VNF备份请求。
步骤102：NFVO收到请求后，首先进行命令信息校验，检查是否符合备份要求，若符合则下一步，不符合则返回。
步骤103：NFVO向VNFM发送VNF备份请求。
步骤104：VNFM收集并备份所管理的VNF系统配置信息及拓扑关联信息等备份数据。
步骤105：VNFM向VNF发送VNF数据备份请求。
步骤106：VNF接收VNFM的备份请求，开始业务数据备份。
步骤107：VNF备份成功后通知VNFM备份成功，准备统一打包生成备份数据包。
步骤108：VNFM打包成功后通知NFVO备份成功，准备数据上传。
步骤109：NFVO收到VNFM的响应，通知CMS准备上传备份数据。
步骤110：备份数据上传成功，CMS反馈NFVO数据备份成功。
步骤111：NFVO反馈USER数据备份成功。
如图6所示，本实施例中VNF恢复处理流程如下：
步骤201：USER向NFVO发送VNF恢复请求。
步骤202：NFVO收到请求后，首先进行校验，检查是否符合恢复要求，校验通过则进行下一步，否则返回失败。
步骤203：NFVO通知CMS准备VNF备份数据进行恢复。
步骤204：CMS收到NFVO的通知后，检查并准备相关资源，准备OK后通知NFVO。
步骤205：NFVO向VNFM发送恢复VNF请求。
步骤206：VNFM收到NFVO的请求后，首先开始VNF实例恢复。
步骤207：VNF实例恢复成功后，VNFM通知VNF进行业务数据恢复。
步骤208：VNF收到VNFM的数据恢复请求，开始数据恢复。
步骤209：VNF数据恢复成功后通知VNFM。
步骤210：VNFM通知NFVO数据恢复成功。
步骤211：NFVO通知USER数据恢复成功。
如图7所示，本实施例中的VNFM备份的流程如下：
步骤301：USER向NFVO发送VNFM数据备份请求。
步骤302：NFVO收到请求后进行校验，检查是否具备备份条件。
步骤303：NFVO校验通过后开始通知VNFM进行VNFM数据备份。
步骤304：VNFM收到备份请求后，开始进行VFNM数据备份，主要包括VNFM自身系统配置数据信息，VNFM-VNFs网络拓扑描述信息，NFVO–VNFM网络拓扑描述等数据。
步骤305：VNFM备份成功后打包，生成VNFM备份数据包，同时通知VNF进行数据备份。
步骤306：VNF收到VNFM的备份请，开始进行VNF数据备份，包括VNF系统配置数据新、VNF-VNF网络拓扑信息，VNF业务数据信息等数据。
步骤307：VNF备份成功后打包，生成VNF备份数据包，同时反馈VNFM备份成功，数据准备上传。
步骤308：VNFM收到VNF的备份成功信息，反馈NFVO备份成功，数据准备上传。
步骤309：NFVO收到VNFM的备份成功信息，通知CMS准备上传2个层面备份数据包。
步骤310：备份数据包上传成功，CMS反馈NFVO上传结束。
步骤311：NFVO反馈USER数据备份成功。
如图8所示，本实施例中VNFM恢复的流程如下：
步骤401：USER向NFVO发送VNFM恢复请求。
步骤402：NFVO收到请求后进行校验，检查是否具备VNFM恢复条件。
步骤403：校验通过后开始VNFM的数据恢复，首先进行VNFM实例恢复，恢复成功后再进行自身VFNM数据恢复。
步骤404：数据恢复成功后，NFVO返回USER恢复成功。
如图9所示，本实施例中NFVO备份的流程如下：
步骤501：USER向NFVO发送NFVO面数据备份请求。
步骤502：NFVO收到请求后进行校验，检查是否具备备份条件。
步骤503：校验通过后开始进行NFVO上数据备份，主要包括所有虚机规格信息、VNFM和VNFs的镜像、版本等配置描述信息及NFVO-VNFM-VNFs的网络拓扑信息。
步骤504：NFVO备份成功后打包，生成NFVO备份数据，同时通知 VNFM进行数据备份。
步骤505：VNFM收到NFVO的备份请求，开始进行VNFM数据备份，包括VNFM自身配置数据信息，VNFM-VNFs网络拓扑描述信息，NFVO-VNFM网络拓扑描述等数据。
步骤506：VNFM备份成功后打包，生成VNFM层备份数据，同时通知VNFs进行数据备份。
步骤507：VNF收到VNFM的备份请求，开始进行VNF数据备份，包括VNF系统配置数据新、VNF-VNF网络拓扑信息，VNF业务数据信息等数据。
步骤508：VNF备份成功后打包，生成VNF备份数据，同时反馈VNFM备份成功，数据准备上传。
步骤509：VNFM收到VNF的备份成功信息，反馈NFVO备份成功，数据准备上传。
步骤510：NFVO收到VNFM的备份成功信息，通知CMS准备上传3个层面备份数据。
步骤511：备份数据上传成功，CMS反馈NFVO数据上传结束。
步骤512：NFVO反馈USER备份恢复成功。
本领域普通技术人员可以理解上述实施例的全部或部分步骤可以使用计算机程序流程来实现，所述计算机程序可以存储于一计算机可读存储介质中，所述计算机程序在相应的硬件平台上(如系统、设备、装置、器件等)执行，在执行时，包括方法实施例的步骤之一或其组合。
可选地，上述实施例的全部或部分步骤也可以使用集成电路来实现，这些步骤可以被分别制作成一个个集成电路模块，或者将它们中的多个模块或步骤制作成单个集成电路模块来实现。
上述实施例中的装置/功能模块/功能单元可以采用通用的计算装置来实现，它们可以集中在单个的计算装置上，也可以分布在多个计算装置所组成的网络上。
上述实施例中的装置/功能模块/功能单元以软件功能模块的形式实现并作为独立的产品销售或使用时，可以存储在一个计算机可读取存储介质中。上述提到的计算机可读取存储介质可以是只读存储器，磁盘或光盘等。
工业实用性
本发明实施例可以实现虚拟化网络对自身物理资源的快速备份、恢复，不仅能够完善传统备份恢复方式的先天不足，节省特定场景下系统运营中断所需的恢复时间，降低系统软硬件故障引起的运营风险及运维成本，还可以用于快速实现跨系统的电信服务复制迁移，真正实现电信服务的灵活部署。

Claims (19)

  1. 一种虚拟化网络的备份方法，包括：
    网络功能虚拟化调度器NFVO接收备份请求，所述备份请求包括VNF备份请求或VNFM备份请求或NFVO备份请求；
    当备份请求为所述VNF备份请求时，所述NFVO根据所述VNF备份请求进行VNF备份操作；
    当备份请求为所述VNFM备份请求时，所述NFVO根据所述VNFM备份请求进行VNFM备份操作，并在所述VNFM备份成功后进行所述VNFM管理的每个VNF的备份操作；
    当备份请求为所述NFVO备份请求时，所述NFVO根据NFVO备份请求进行NFVO备份操作，并在NFVO备份成功后，进行所述NFVO管理的每个VNFM的备份操作；以及在每个VNFM备份成功后进行每个VNFM管理的每个VNF的备份操作。
  2. 如权利要求1所述的方法，其中：
    当备份请求为所述VNF备份请求时，所述NFVO根据所述VNF备份请求进行VNF备份操作包括：
    VNFM根据所述VNF备份请求生成VNF备份数据包；所述VNF备份数据包包括所述VNF的备份数据信息以及所述VNF的配置信息；
    通过云管理系统CMS上传所述VNF备份数据包。
  3. 如权利要求1所述的方法，其中：
    当备份请求为所述VNFM备份请求时，所述NFVO根据所述VNFM备份请求进行VNFM备份操作，并在所述VNFM备份成功后进行所述VNFM管理的每个VNF的备份操作包括：
    所述VNFM根据所述VNFM备份请求生成VNFM备份数据包，所述VNFM备份数据包包括所述VNFM管理的每个VNF的备份数据信息、所述VNFM的配置信息以及所述每个VNF的配置信息；
    通过CMS上传所述VNFM备份数据包。
  4. 如权利要求1所述的方法，其中：
    当备份请求为所述NFVO备份请求时，所述NFVO根据NFVO备份请求进行NFVO备份操作，并在NFVO备份成功后，进行所述NFVO管理的每个VNFM的备份操作；以及在每个VNFM备份成功后进行每个VNFM管理的每个VNF的备份操作包括：
    所述NFVO根据所述NFVO备份请求生成NFVO备份数据包，所述NFVO备份数据包包括所述NFVO管理的每个VNF的备份数据信息、所述NFVO的配置信息、所述NFVO管理的每个VNFM的配置信息以及所述每个VNF的配置信息；
    通过CMS上传所述NFVO备份数据包。
  5. 如权利要求2～4所述的方法，其中：
    所述VNF的配置信息包括所述VNF系统配置信息和VNF-VNF拓扑关联信息；
    所述VNFM的配置信息包括所述VNFM系统配置信息、VNFM-VNF拓扑关联信息以及NFVO-VNFM拓扑关联信息；
    所述NFVO的配置信息包括虚拟机规格信息、每个VNFM和每个VNF的系统配置信息以及NFVO-VNFM-VNF的拓扑关联信息。
  6. 一种虚拟化网络的恢复方法，包括：
    网络功能虚拟化调度器NFVO接收恢复请求，所述恢复请求包括VNF恢复请求或VNFM恢复请求或NFVO恢复请求；
    当恢复请求为所述VNF恢复请求时，所述NFVO根据所述VNF恢复请求进行VNF恢复操作；
    当恢复请求为所述VNFM恢复请求时，所述NFVO根据所述VNFM恢复请求进行VNFM恢复操作；
    当恢复请求为所述NFVO恢复请求时，所述NFVO根据所述NFVO恢复请求进行NFVO恢复操作。
  7. 如权利要求6所述的方法，其中：
    当恢复请求为所述VNF恢复请求时，所述NFVO根据所述VNF恢复请求进行VNF恢复操作包括：
    VNFM接收所述VNF恢复请求，根据所述VNF恢复请求对所述VNF进行实例恢复；
    所述VNF对所述VNF进行数据恢复；
    通过所述VNFM向所述NFVO发送恢复成功响应消息。
  8. 如权利要求6所述的方法，其中：
    当恢复请求为所述VNFM恢复请求时，所述NFVO根据所述VNFM恢复请求进行VNFM恢复操作包括：
    所述NFVO进行所述VNFM实例恢复，并在所述VNFM实例恢复成功后进行所述VNFM数据恢复，所述VNFM恢复的数据与所述VNFM管理的每个VNF的数据一致。
  9. 如权利要求6所述的方法，其中：
    当恢复请求为所述NFVO恢复请求时，所述NFVO根据所述NFVO恢复请求进行NFVO恢复操作包括：
    所述NFVO进行所述NFVO实例恢复，并在所述NFVO实例恢复成功后进行所述NFVO数据恢复，所述NFVO恢复的数据与所述NFVO管理的每个VNFM以及每个VNF的数据一致。
  10. 一种虚拟化网络的备份装置，包括：
    第一接收模块，设置为：接收备份请求，所述备份请求包括VNF备份请求或VNFM备份请求或NFVO备份请求；
    备份模块，设置为：当备份请求为所述VNF备份请求时，根据所述VNF备份请求进行VNF备份操作；当备份请求为所述VNFM备份请求时，根据所述VNFM备份请求进行VNFM备份操作，并在所述VNFM备份成功后进行所述VNFM管理的每个VNF的备份操作；当备份请求为所述NFVO备份请求时，根据NFVO备份请求进行NFVO备份操作，并在NFVO备份成功 后，进行所述NFVO管理的每个VNFM的备份操作；以及在每个VNFM备份成功后进行每个VNFM管理的每个VNF的备份操作。
  11. 如权利要求10所述的装置，其中：
    所述备份模块包括：
    第一生成单元，设置为：当备份请求为所述VNF备份请求时，根据所述VNF备份请求生成VNF备份数据包；所述VNF备份数据包包括所述VNF的备份数据信息以及所述VNF的配置信息；
    第一上传单元，设置为：通过云管理系统CMS上传所述VNF备份数据包。
  12. 如权利要求10所述的装置，其中：
    所述备份模块包括：
    第二生成单元，设置为：当备份请求为所述VNFM备份请求时，根据所述VNFM备份请求生成VNFM备份数据包，所述VNFM备份数据包包括所述VNFM管理的每个VNF的备份数据信息、所述VNFM的配置信息以及所述每个VNF的配置信息；
    第二上传单元，设置为：通过CMS上传所述VNFM备份数据包。
  13. 如权利要求10所述的装置，其中：
    所述备份模块包括：
    第三生成单元，设置为：当备份请求为所述NFVO备份请求时，根据所述NFVO备份请求生成NFVO备份数据包，所述NFVO备份数据包包括所述NFVO管理的每个VNF的备份数据信息、所述NFVO的配置信息、所述NFVO管理的每个VNFM的配置信息以及所述每个VNF的配置信息；
    第三上传单元，设置为：通过CMS上传所述NFVO备份数据包。
  14. 如权利要求11～13所述的装置，其中：
    所述VNF的配置信息包括所述VNF系统配置信息和VNF-VNF拓扑关联信息；
    所述VNFM的配置信息包括所述VNFM系统配置信息、VNFM-VNF拓 扑关联信息以及NFVO-VNFM拓扑关联信息；
    所述NFVO的配置信息包括虚拟机规格信息、每个VNFM和每个VNF的系统配置信息以及NFVO-VNFM-VNF的拓扑关联信息。
  15. 一种虚拟化网络的恢复装置，包括：
    第二接收模块，设置为：接收恢复请求，所述恢复请求包括VNF恢复请求或VNFM恢复请求或NFVO恢复请求；
    恢复模块，设置为：当恢复请求为所述VNF恢复请求时，根据所述VNF恢复请求进行VNF恢复操作；当恢复请求为所述VNFM恢复请求时，根据所述VNFM恢复请求进行VNFM恢复操作；当恢复请求为所述NFVO恢复请求时，根据所述NFVO恢复请求进行NFVO恢复操作。
  16. 如权利要求15所述的装置，其中：
    所述恢复模块包括：
    第一实例恢复单元，设置为：当恢复请求为所述VNF恢复请求时，接收所述VNF恢复请求，根据所述VNF恢复请求对所述VNF进行实例恢复；
    第一数据恢复单元，设置为：对所述VNF进行数据恢复；
    响应单元，设置为：发送恢复成功响应消息。
  17. 如权利要求15所述的装置，其中：
    所述恢复装置包括：
    第二实例恢复单元，设置为：当恢复请求为所述VNFM恢复请求时，进行所述VNFM实例恢复；
    第二数据恢复单元，设置为：在所述VNFM实例恢复成功后进行所述VNFM数据恢复，所述VNFM恢复的数据与所述VNFM管理的每个VNF的数据一致。
  18. 如权利要求15所述的装置，其中：
    所述恢复模块包括：
    第三实例恢复单元，设置为：当恢复请求为所述NFVO恢复请求时，进行所述NFVO实例恢复；
    第三数据恢复单元，设置为：在所述NFVO实例恢复成功后进行所述NFVO数据恢复，所述NFVO恢复的数据与所述NFVO管理的每个VNFM以及每个VNF的数据一致。
  19. 一种计算机可读存储介质，存储有计算机可执行指令，所述计算机可执行指令用于执行权利要求1-9任一项的方法。
PCT/CN2015/083087 2014-10-24 2015-07-01 一种虚拟化网络备份、恢复的方法和相应装置 WO2016062116A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201410579709.1A CN105530116B (zh) 2014-10-24 2014-10-24 一种虚拟化网络备份、恢复的方法和相应装置
CN201410579709.1 2014-10-24

Publications (1)

Publication Number Publication Date
WO2016062116A1 true WO2016062116A1 (zh) 2016-04-28

Family

ID=55760238

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2015/083087 WO2016062116A1 (zh) 2014-10-24 2015-07-01 一种虚拟化网络备份、恢复的方法和相应装置

Country Status (2)

Country Link
CN (1) CN105530116B (zh)
WO (1) WO2016062116A1 (zh)

Families Citing this family (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN107786361A (zh) * 2016-08-30 2018-03-09 中兴通讯股份有限公司 一种切换nfvo的方法、装置、vnfm/vim及nfvo
US10742532B2 (en) 2017-12-18 2020-08-11 Futurewei Technologies, Inc. Non-intrusive mechanism to measure network function packet processing delay
CN110545193B (zh) * 2018-05-28 2021-04-09 华为技术有限公司 一种虚拟资源的管理方法、虚拟资源管理设备及服务器
CN109522159A (zh) * 2018-11-26 2019-03-26 广州华商职业学院 一种工程管理信息备份系统及其方法
CN111352767B (zh) * 2018-12-24 2023-07-18 中国电信股份有限公司 网络功能虚拟化平台资源管理方法、备份平台和系统
CN111092744B (zh) * 2019-04-16 2023-08-01 中兴通讯股份有限公司 一种恢复vnf实例的方法、装置和设备

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN103843284A (zh) * 2013-10-23 2014-06-04 华为技术有限公司 一种云应用的容灾方法、系统和装置
CN104050045A (zh) * 2014-06-27 2014-09-17 华为技术有限公司 基于磁盘io的虚拟资源分配方法及装置
CN104115447A (zh) * 2014-04-14 2014-10-22 华为技术有限公司 一种云计算架构下的容灾方案配置方法及装置
CN104253866A (zh) * 2014-09-20 2014-12-31 华为技术有限公司 虚拟网络功能网元的软件部署方法、系统及相关设备

Family Cites Families (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN103973487B (zh) * 2014-04-29 2018-07-24 上海上讯信息技术股份有限公司 一种基于交互式脚本的配置备份系统及配置管理方法

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN103843284A (zh) * 2013-10-23 2014-06-04 华为技术有限公司 一种云应用的容灾方法、系统和装置
CN104115447A (zh) * 2014-04-14 2014-10-22 华为技术有限公司 一种云计算架构下的容灾方案配置方法及装置
CN104050045A (zh) * 2014-06-27 2014-09-17 华为技术有限公司 基于磁盘io的虚拟资源分配方法及装置
CN104253866A (zh) * 2014-09-20 2014-12-31 华为技术有限公司 虚拟网络功能网元的软件部署方法、系统及相关设备

Also Published As

Publication number Publication date
CN105530116A (zh) 2016-04-27
CN105530116B (zh) 2020-06-16

Similar Documents

Publication Publication Date Title
US10931599B2 (en) Automated failure recovery of subsystems in a management system
US11074143B2 (en) Data backup and disaster recovery between environments
WO2016062116A1 (zh) 一种虚拟化网络备份、恢复的方法和相应装置
US10169173B2 (en) Preserving management services with distributed metadata through the disaster recovery life cycle
Endo et al. High availability in clouds: systematic review and research challenges
US10574588B2 (en) System and method for reducing latency time with cloud services
Zhang et al. A survey on cloud interoperability: taxonomies, standards, and practice
WO2017071460A1 (zh) 一种容器监控方法和装置
Jhawar et al. A comprehensive conceptual system-level approach to fault tolerance in cloud computing
EP3588296A1 (en) Dynamically scaled hyperconverged system
Jhawar et al. Fault tolerance management in IaaS clouds
Koslovski et al. Reliability support in virtual infrastructures
US11119829B2 (en) On-demand provisioning of customized developer environments
US10061665B2 (en) Preserving management services with self-contained metadata through the disaster recovery life cycle
US9077613B2 (en) System and method for graph based K-redundant resiliency for IT cloud
EP2959387B1 (en) Method and system for providing high availability for state-aware applications
US10326655B1 (en) Infrastructure replication
WO2017041525A1 (zh) 重建虚拟网络功能的方法和装置
Heidari et al. Qos assurance with light virtualization-a survey
US9959157B1 (en) Computing instance migration
CN103973725A (zh) 一种分布式协同方法和协同器
US20230082186A1 (en) Container-Based Application Data Protection Method and System
US11533391B2 (en) State replication, allocation and failover in stream processing
Meroufel et al. Optimization of checkpointing/recovery strategy in cloud computing with adaptive storage management
WO2020015751A1 (zh) 容器服务快照的管理方法和装置

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: 15852351

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 15852351

Country of ref document: EP

Kind code of ref document: A1