WO2014086150A1 - Procédé d'instantané, nœud de service, nœud de commande principal et système - Google Patents

Procédé d'instantané, nœud de service, nœud de commande principal et système Download PDF

Info

Publication number
WO2014086150A1
WO2014086150A1 PCT/CN2013/079568 CN2013079568W WO2014086150A1 WO 2014086150 A1 WO2014086150 A1 WO 2014086150A1 CN 2013079568 W CN2013079568 W CN 2013079568W WO 2014086150 A1 WO2014086150 A1 WO 2014086150A1
Authority
WO
WIPO (PCT)
Prior art keywords
snapshot
post
node
application
function
Prior art date
Application number
PCT/CN2013/079568
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 WO2014086150A1 publication Critical patent/WO2014086150A1/fr

Links

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F3/00—Input arrangements for transferring data to be processed into a form capable of being handled by the computer; Output arrangements for transferring data from processing unit to output unit, e.g. interface arrangements
    • G06F3/06—Digital input from, or digital output to, record carriers, e.g. RAID, emulated record carriers or networked record carriers
    • G06F3/0601—Interfaces specially adapted for storage systems
    • G06F3/0602—Interfaces specially adapted for storage systems specifically adapted to achieve a particular effect
    • G06F3/0604—Improving or facilitating administration, e.g. storage management
    • G06F3/0605—Improving or facilitating administration, e.g. storage management by facilitating the interaction with a user or administrator
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F3/00—Input arrangements for transferring data to be processed into a form capable of being handled by the computer; Output arrangements for transferring data from processing unit to output unit, e.g. interface arrangements
    • G06F3/06—Digital input from, or digital output to, record carriers, e.g. RAID, emulated record carriers or networked record carriers
    • G06F3/0601—Interfaces specially adapted for storage systems
    • G06F3/0628—Interfaces specially adapted for storage systems making use of a particular technique
    • G06F3/0646—Horizontal data movement in storage systems, i.e. moving data in between storage devices or systems
    • G06F3/065—Replication mechanisms
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F3/00—Input arrangements for transferring data to be processed into a form capable of being handled by the computer; Output arrangements for transferring data from processing unit to output unit, e.g. interface arrangements
    • G06F3/06—Digital input from, or digital output to, record carriers, e.g. RAID, emulated record carriers or networked record carriers
    • G06F3/0601—Interfaces specially adapted for storage systems
    • G06F3/0668—Interfaces specially adapted for storage systems adopting a particular infrastructure
    • G06F3/067—Distributed or networked storage systems, e.g. storage area networks [SAN], network attached storage [NAS]

Definitions

  • the present invention relates to computer technologies, and in particular, to a snapshot method, a service node, a master node, and a system. Background technique
  • the virtualization platform includes a hypervisor (hypervisor), a master virtual machine ( DomainO ), and a business virtual machine ( DomainU ).
  • Hypervisor is the core of the virtualization platform. It is between the hardware and the operating system. It is responsible for providing virtualized hardware resources for the operating system running on the upper layer, managing and allocating these resources, and ensuring the isolation between virtual machines.
  • Hypervisor Provides an abstraction layer to DomainO that contains the Application Programming Interface (API) for management and virtual hardware. DomainO internally contains real device drivers, native device drivers, direct access to hardware, and is responsible for interacting with the management API provided by Hypervisor, receiving hypervisor management commands, and managing the business virtual machine (DomainU).
  • API Application Programming Interface
  • the specific processes of the two implementation methods include: 1) Preparation before the snapshot: Before the cloud platform administrator or storage administrator makes a snapshot, the virtual machine administrator needs to be notified, the application is suspended, and the data in the memory is refreshed to the disk. 2) Create a snapshot: Before the virtual machine administrator prepares for work, notify the cloud platform administrator or storage administrator to create a snapshot. 3) After the snapshot, work: The cloud platform administrator or storage administrator notifies the virtual machine administrator to restore the application.
  • the virtual machine administrator needs to suspend or resume the application before and after the snapshot, and basically use scripts to complete, but the applications on each virtual machine are different.
  • the application scripts are different, and there is no unified interface management, which leads to high complexity of snapshots, and the same problem exists in snapshots of physical machines. Summary of the invention
  • the embodiment of the invention provides a snapshot method, a service node, a main control node and a system, which are used to solve The problem of realizing the complexity of snapshots in the prior art.
  • an embodiment of the present invention provides a snapshot method, including:
  • the pre-snapshot function includes a pre-snapshot interface parameter corresponding to each application or database saved in the local configuration file and a call before the snapshot pause script;
  • a pre-snap operation completion notification is sent to the main control node to enable the creation of the snapshot.
  • the performing a pre-snapshot function includes:
  • a post-snapshot function is executed, and the post-snapshot function includes a call to the post-snapshot interface parameter and the post-snapshot recovery script corresponding to each application or database saved in the local configuration file;
  • a post-snapshot operation completion notification is sent to the main control node, so that the confirmation snapshot is completed.
  • the performing the post-snapshot function includes:
  • an embodiment of the present invention provides a snapshot method, including:
  • the method further includes: confirming the snapshot creation The snapshot completion notification is sent to each service node, so that each service node performs a locally configured post-snapshot function according to the snapshot completion notification, and the post-snapshot function includes a snapshot corresponding to each application or database saved in the local configuration file. Post-interface parameters and calls to the recovery script after the snapshot;
  • the sending the snapshot creation notification to each service node includes:
  • the method further includes:
  • the sending the snapshot creation notification to each service node includes:
  • the method further includes:
  • the method further includes:
  • an embodiment of the present invention provides a service node, including: a receiving module, configured to receive a snapshot creation notification sent by the master node;
  • the pre-snapshot interface is configured to perform a pre-snapshot function according to the snapshot creation notification, where the pre-snapshot function includes a pre-snapshot interface parameter corresponding to each application or database saved in the local configuration file and a call before the snapshot pause script;
  • a sending module configured to send a pre-snap operation completion notification to the main control node after the execution of the function before the snapshot is completed, so that the snapshot is started.
  • the pre-snapshot interface is configured to configure a pre-snapshot running environment of the application or database according to an interface pre-snapshot interface parameter corresponding to an application or a database. ; Pause the script before executing the snapshot corresponding to the application or database.
  • the receiving module is further configured to receive a snapshot completion notification sent by the master control node;
  • the service node further includes:
  • the post-snapshot interface is configured to perform a post-snapshot function according to the snapshot completion notification, and the post-snapshot function includes a call to the post-snapshot interface parameter and the post-snapshot recovery script corresponding to each application or database saved in the local configuration file;
  • the sending module is further configured to send a post-snapshot operation completion notification to the main control node after the execution of the function is completed, so that the confirmation snapshot is completed.
  • the post-snapshot interface is specifically configured to configure, according to the post-snapshot interface parameter corresponding to the application or the database, Run the environment after the snapshot of the application or database; execute the snapshot after the snapshot of the application or database.
  • an embodiment of the present invention provides a master control node, including:
  • a sending module configured to send a snapshot creation notification to each service node, so that each service node performs a locally configured pre-snapshot function according to the snapshot creation notification, where the pre-snapshot function includes each application or database saved in the local configuration file.
  • the receiving module is configured to receive a pre-snapshot operation completion notification sent by each service node after the execution of the pre-snapshot function is completed.
  • the sending module is further configured to: after confirming the snapshot creation, send a snapshot completion notification to each service node, so that each service node is configured according to the The snapshot completion notification performs a locally configured post-snapshot function, and the post-snapshot function includes a call to the post-snapshot interface parameter and the post-snapshot recovery script corresponding to each application or database saved in the local configuration file;
  • the receiving module is further configured to receive an operation completion notification after each snapshot of the snapshot returned by each service node after the function is completed.
  • the master node further includes: an confirming module, configured to confirm that the snapshot is completed according to the post-snapshot operation completion notification returned by each service node.
  • the sending module is specifically configured to: according to a pre-configured snapshot policy, to each service node Send a snapshot creation notification;
  • the method further includes: a creating module, configured to start creating a snapshot after the receiving module receives the operation completion notification before the snapshot sent by each service node.
  • the sending module is specifically configured to: receive a snapshot creation notification sent by a cloud platform or a storage layer, A snapshot creation notification is sent to each service node;
  • the main control node further includes: a notification module, configured to notify the cloud platform or the storage layer to start creating a snapshot after the receiving module receives the pre-snap operation completion notification sent by each service node; and confirm the snapshot in the confirmation module After completion, notify the cloud platform or storage tier snapshot to complete.
  • a notification module configured to notify the cloud platform or the storage layer to start creating a snapshot after the receiving module receives the pre-snap operation completion notification sent by each service node; and confirm the snapshot in the confirmation module After completion, notify the cloud platform or storage tier snapshot to complete.
  • the fifth aspect provides a snapshot system, including: the master node according to the fourth aspect, and at least one service node as described in the third aspect.
  • the embodiment of the present invention performs a pre-snapshot function after receiving the snapshot creation notification sent by the main control node, where the pre-snapshot function includes a pre-snapshot interface parameter corresponding to each application or database saved in the local configuration file and a pause before the snapshot.
  • the script is called to make different applications or databases follow the standard processes and interfaces, and the scripts that call different applications or databases only need to modify the corresponding interface parameters and scripts, which reduces the complexity of implementing snapshots.
  • FIG. 1 is a schematic flowchart diagram of a snapshot method according to Embodiment 1 of the present invention
  • FIG. 2 is a schematic flowchart of a snapshot method according to Embodiment 2 of the present invention.
  • FIG. 3 is a schematic flowchart of a snapshot method according to Embodiment 3 of the present invention.
  • FIG. 4 is a schematic flowchart of a snapshot method according to Embodiment 4 of the present invention.
  • FIG. 5 is a schematic structural diagram of a service node 500 according to Embodiment 5 of the present invention.
  • FIG. 6 is a schematic structural diagram of a service node 600 according to Embodiment 6 of the present invention.
  • FIG. 7 is a schematic structural diagram of a main control node 700 according to Embodiment 7 of the present invention.
  • FIG. 8 is a schematic structural diagram of a main control node 800 according to Embodiment 8 of the present invention.
  • FIG. 9 is a schematic structural diagram of a snapshot system 900 according to Embodiment 9 of the present invention.
  • the technical solutions in the embodiments of the present invention are clearly and completely described in the following with reference to the accompanying drawings in the embodiments of the present invention.
  • the embodiments are a part of the embodiments of the invention, and not all of the embodiments. All other embodiments obtained by those skilled in the art based on the embodiments of the present invention without creative efforts are within the scope of the present invention.
  • FIG. 1 is a schematic flowchart diagram of a snapshot method according to Embodiment 1 of the present invention. As shown in Figure 1, it includes:
  • the service node receives a snapshot creation notification sent by the master node.
  • the master node may be a master virtual machine, and the service node may be a service virtual machine.
  • the master node may be a master server, and the service node may be a service server.
  • the master node can also act as a service node.
  • the pre-snapshot function includes The pre-snapshot interface parameters and the pre-snapshot pause scripts corresponding to each application or database saved in the local configuration file.
  • the pre-snapshot function and the local configuration file may be pre-written to the service node.
  • Each application or database is a respective application or database installed on a service node.
  • the pre-flash interface parameters corresponding to the application or database include the running permissions, environment configuration parameters, etc. required by the application or database to perform pre-snapshot operations.
  • a suspend command or a hold command provided by the application or database is encapsulated in the pre-snapshot pause script corresponding to the application or database.
  • 102 can include:
  • the application or database is frozen, and the cached data of the application or database is refreshed.
  • the pre-snapshot function may further include an underlying API function for the operating system of the service node, which is used to refresh the cache data of the operating system file system of the service node after the script is suspended before executing the snapshot corresponding to the application or the database.
  • the pre-snap operation completion notification is sent to the main control node, so that the snapshot is started.
  • the execution of the pre-snapshot function may be monitored by a listener in the service node, and the pre-snap operation completion notification is sent to the main control node after the function execution is completed before the snapshot is monitored.
  • the master node can confirm that the preparation work before the snapshot of the service node is completed, thereby starting to create a snapshot.
  • the embodiment of the present invention performs a pre-snapshot function after receiving the snapshot creation notification sent by the main control node, where the pre-snapshot function includes a pre-snapshot interface parameter corresponding to each application or database saved in the local configuration file and a pause before the snapshot.
  • the script is called to make different applications or databases follow the standard processes and interfaces, and the scripts that call different applications or databases only need to modify the corresponding interface parameters and scripts, which reduces the complexity of implementing snapshots.
  • FIG. 2 is a schematic flowchart diagram of a snapshot method according to Embodiment 2 of the present invention. As shown in Figure 2, in After 101 ⁇ 103 as shown, it also includes:
  • the master node After confirming that the snapshot is created, the master node sends the snapshot completion notification to the service node, so that the service node performs a snapshot recovery operation.
  • post-snapshot function includes a call to the post-snapshot interface parameter and the post-snapshot recovery script corresponding to each application or database saved in the local configuration file.
  • the post-snapshot function may also be written into the service node in advance.
  • Each of the applications or databases is an application or database installed on a service node.
  • the post-snapshot interface parameters corresponding to the application or database include the running permissions, environment configuration parameters, etc. required by the application or database to perform post-snapshot operations.
  • the recovery or resume command provided by the application or database is encapsulated in the post-snapshot recovery script corresponding to the application or database.
  • 105 can include:
  • the application or database is thawed during the execution of the post-snapshot recovery script corresponding to the application or database.
  • the post-snap operation completion notification is sent to the main control node, so that the confirmation snapshot is completed.
  • the execution of the post-snapshot function may be monitored by a listener in the service node, and after the function is completed after the snapshot is monitored, the post-snapshot operation completion notification is sent to the main control node.
  • the master node can confirm the completion of the snapshot after the snapshot of the service node, thereby confirming that the snapshot is completed.
  • the embodiment of the present invention performs a pre-snapshot function after receiving the snapshot creation notification sent by the main control node, where the pre-snapshot function includes a pre-snapshot interface parameter corresponding to each application or database saved in the local configuration file and a pause before the snapshot.
  • the post-snapshot function is executed, and the post-snapshot function includes the respective functions saved in the local configuration file.
  • Use the post-snapshot interface parameters corresponding to the database or the callback recovery script to make the different applications or databases follow the standard processes and interfaces, and the scripts that call different applications or databases only need to modify the corresponding interface parameters and scripts. Yes, the complexity of implementing snapshots is reduced.
  • FIG. 3 is a schematic flowchart diagram of a snapshot method according to Embodiment 3 of the present invention. As shown in Figure 3, it includes:
  • the master node sends a snapshot creation notification to each service node.
  • a master node may be a master virtual machine, and a service node may be a service virtual machine; in a physical machine platform, a master node may be a master server, and a service node may be a service server.
  • the master node can also act as a service node.
  • the pre-snapshot function and the local configuration file may be pre-written to the service node.
  • Each application or database is a respective application or database installed on a service node.
  • the pre-flash interface parameters corresponding to the application or database include the running permissions, environment configuration parameters, etc. required by the application or database to perform pre-snapshot operations.
  • the suspend command or the hold command provided by the application or database is encapsulated in the pre-snapshot pause script corresponding to the application or database.
  • the master node can confirm that the pre-snap preparation work of each service node is completed, thereby starting to create a snapshot.
  • the master node triggers the snapshot according to the pre-configured snapshot policy, and initiates the snapshot creation after the preparation of the snapshot of each service node is completed.
  • the method 301 may include: sending a snapshot creation notification to each service node according to the pre-configured snapshot policy; and correspondingly, after 302, further comprising: starting to create a snapshot.
  • a snapshot policy can be to create a snapshot every hour.
  • the master node triggers the snapshot according to the command of the cloud platform or the storage layer, and notifies the cloud platform or the storage layer to start creating a snapshot after the preparation work is completed before the snapshot of each service node is confirmed.
  • the method 301 includes: receiving a snapshot creation notification sent by the cloud platform or the storage layer, The snapshot creation notification is sent to each service node.
  • the method further includes: notifying the cloud platform or the storage layer to initiate creation of a snapshot.
  • the master node can trigger a snapshot according to a command of the cloud platform or the storage layer.
  • the master node can trigger the snapshot according to the command of the storage layer.
  • the embodiment of the present invention performs a pre-snapshot function after receiving the snapshot creation notification sent by the main control node, where the pre-snapshot function includes a pre-snapshot interface parameter corresponding to each application or database saved in the local configuration file and a pause before the snapshot.
  • the script is called to make different applications or databases follow the standard processes and interfaces, and the scripts that call different applications or databases only need to modify the corresponding interface parameters and scripts, which reduces the complexity of implementing snapshots.
  • FIG. 4 is a schematic flowchart diagram of a snapshot method according to Embodiment 4 of the present invention. As shown in Figure 4, after 301 ⁇ 302 shown in Figure 3, it also includes:
  • the post-snapshot function may also be written into the service node in advance.
  • Each of the applications or databases is an application or database installed on a service node.
  • the post-snapshot interface parameters corresponding to the application or database include the running permissions, environment configuration parameters, etc. required by the application or database to perform post-snapshot operations.
  • the recovery or resume command provided by the application or database is encapsulated in the post-snapshot recovery script corresponding to the application or database.
  • the confirmation snapshot is created to confirm that the snapshot of the master node is completed.
  • the confirmation snapshot is created to confirm that the cloud platform or the storage layer snapshot is created.
  • the master node can also mark the snapshot success and record the snapshot completion time point.
  • the method further includes: notifying the cloud platform or the storage layer Photo is complete.
  • the cloud platform or storage tier can mark the snapshot success and record the snapshot completion time point.
  • the embodiment of the present invention performs a pre-snapshot function after receiving the snapshot creation notification sent by the main control node, where the pre-snapshot function includes a pre-snapshot interface parameter corresponding to each application or database saved in the local configuration file and a pause before the snapshot.
  • the post-snapshot function includes restoring the post-snapshot interface parameters and snapshots corresponding to each application or database saved in the local configuration file.
  • the script is called to make different applications or databases follow the standard processes and interfaces, and the scripts that call different applications or databases only need to modify the corresponding interface parameters and scripts, which reduces the complexity of implementing snapshots.
  • the aforementioned program can be stored in a computer readable storage medium.
  • the program when executed, performs the steps including the foregoing method embodiments; and the foregoing storage medium includes: a medium that can store program codes, such as a ROM, a RAM, a magnetic disk, or an optical disk.
  • FIG. 5 is a schematic structural diagram of a service node 500 according to Embodiment 5 of the present invention. As shown in Figure 5, it includes:
  • the receiving module 51 is configured to receive a snapshot creation notification sent by the master node
  • the pre-snapshot interface 52 is configured to perform a pre-snapshot function according to the snapshot creation notification, where the pre-snapshot function includes a pre-snapshot interface parameter and a pre-snapshot pause script corresponding to each application or database saved in the local configuration file;
  • the sending module 53 is configured to send a pre-snapshot operation completion notification to the main control node after the execution of the pre-snapshot function is completed, so that the snapshot is started.
  • pre-snapshot interface 52 is specifically configured to configure a pre-snapshot running environment of the application or the database according to the pre-snapshot interface parameter corresponding to the application or the database; and execute the pause script before the snapshot corresponding to the application or the database.
  • the receiving module 51 is further configured to receive a snapshot completion notification sent by the master node; the service node 500 further includes:
  • the post-snapshot interface 54 is configured to perform a post-snapshot function according to the snapshot completion notification, where the post-snapshot function includes a call to the post-snapshot interface parameter and the post-snapshot recovery script corresponding to each application or database saved in the local configuration file;
  • the sending module 53 is further configured to: after the function is completed after the snapshot, complete the operation after the snapshot Knowing to send to the master node, so that the confirmation snapshot is completed.
  • post-snapshot interface 54 is specifically configured to configure a running environment of the application or the snapshot of the database according to the post-snapshot interface parameter corresponding to the application or the database; and execute the snapshot corresponding to the application or the database to restore the script.
  • the foregoing function module may be included in a snapshot proxy client, and the snapshot proxy client is deployed in the service node 500. Further, the pre-snapshot function, the post-snapshot function, and the configuration file are all set in the Snapshot Agent client.
  • a specific implementation of this embodiment refers to a snapshot method provided by Embodiment 1 or Embodiment 2 of the present invention.
  • the embodiment of the present invention performs a pre-snapshot function after receiving the snapshot creation notification sent by the main control node, where the pre-snapshot function includes a pre-snapshot interface parameter corresponding to each application or database saved in the local configuration file and a pause before the snapshot.
  • the script is called to make different applications or databases follow the standard processes and interfaces, and the scripts that call different applications or databases only need to modify the corresponding interface parameters and scripts, which reduces the complexity of implementing snapshots.
  • FIG. 6 is a schematic structural diagram of a service node 600 according to Embodiment 6 of the present invention.
  • the service node 600 generally includes at least one processor 610, such as a central processing unit (CPU), a digital signal processor (DSP), at least one port 620, a memory 630, and at least one communication.
  • Communication bus 640 is used to implement connection communication between these devices.
  • the processor 610 is configured to execute an executable module, such as a computer program, stored in the memory 630; optionally, the service node 600 can include a user interface 650 including, but not limited to, a display, a keyboard, and a pointing device, such as a mouse, a track Trackball, touchpad or tactile display.
  • the memory 630 may include a random access memory (RAM), and may also include a non-volatile memory such as at least one disk storage.
  • memory 630 stores the following elements, executable modules or data structures, or a subset thereof, or their extension set:
  • Operating system 632 which contains various system programs for implementing various basic services and handling hardware-based tasks
  • Application Module 634 includes a variety of applications for implementing various application services.
  • the application module 634 includes but is not limited to the receiving module 51, the pre-snapshot interface 52, and the transmitting module 53. Further, the application module 634 further includes: a post-snapshot interface 54, a pre-snapshot function, a post-snapshot function, and a configuration file.
  • each module in the application module 634 refers to the corresponding module in the service node 500, and details are not described herein.
  • the embodiment of the present invention performs a pre-snapshot function after receiving the snapshot creation notification sent by the main control node, where the pre-snapshot function includes a pre-snapshot interface parameter corresponding to each application or database saved in the local configuration file and a pause before the snapshot.
  • the script is called to make different applications or databases follow the standard processes and interfaces, and the scripts that call different applications or databases only need to modify the corresponding interface parameters and scripts, which reduces the complexity of implementing snapshots.
  • FIG. 7 is a schematic structural diagram of a main control node 700 according to Embodiment 7 of the present invention. As shown in Figure 7, it includes:
  • the sending module 71 is configured to send a snapshot creation notification to each service node, so that each service node performs a locally configured pre-snapshot function according to the snapshot creation notification, where the pre-snapshot function includes each application saved in the local configuration file or The interface parameters before the snapshot corresponding to the database and the call of the pause script before the snapshot;
  • the receiving module 72 is configured to receive a pre-flash operation completion notification sent by each service node after the execution of the pre-snapshot function is completed.
  • the sending module 71 is further configured to: after confirming the snapshot creation, send a snapshot completion notification to each service node, so that each service node performs a locally configured post-snapshot function according to the snapshot completion notification, where the post-snapshot function includes Calls to the post-snapshot interface parameters and post-snapshot recovery scripts for each application or database saved in the local configuration file;
  • the receiving module 72 is further configured to receive, after each snapshot, a snapshot completion operation completion notification returned by each service node after the function is completed.
  • the master node 700 further includes: an confirming module 73, configured to confirm that the snapshot is completed according to the post-snapshot operation completion notification returned by each service node.
  • the sending module 71 is specifically configured to send a snapshot creation notification to each service node according to the pre-configured snapshot policy.
  • the master node 700 further includes: a creating module, configured to start creating a snapshot after the receiving module 72 receives the operation completion notification before the snapshot sent by each service node.
  • the sending module 71 is specifically configured to: receive a snapshot creation notification sent by the cloud platform or the storage layer, and send the snapshot creation notification to each service node;
  • the main control node 700 further includes: a notification module, configured to notify the cloud platform or the storage layer to start creating a snapshot after the receiving module 72 receives the pre-snap operation completion notification sent by each service node; after the confirmation module confirms that the snapshot is completed , notify the cloud platform or storage layer snapshot to complete.
  • a notification module configured to notify the cloud platform or the storage layer to start creating a snapshot after the receiving module 72 receives the pre-snap operation completion notification sent by each service node; after the confirmation module confirms that the snapshot is completed , notify the cloud platform or storage layer snapshot to complete.
  • the foregoing function module may be included in the snapshot proxy server, and the snapshot proxy server is deployed in the master node 700.
  • a specific implementation of this embodiment refers to a snapshot method provided by Embodiment 3 or Embodiment 4 of the present invention.
  • the embodiment of the present invention performs a pre-snapshot function after receiving the snapshot creation notification sent by the main control node, where the pre-snapshot function includes a pre-snapshot interface parameter corresponding to each application or database saved in the local configuration file and a pause before the snapshot.
  • the script is called to make different applications or databases follow the standard processes and interfaces, and the scripts that call different applications or databases only need to modify the corresponding interface parameters and scripts, which reduces the complexity of implementing snapshots.
  • FIG. 8 is a schematic structural diagram of a master control node 800 according to Embodiment 6 of the present invention.
  • the master node 800 generally includes at least one processor 810, such as a central processing unit (CPU), a digital signal processor (DSP), at least one port 820, a memory 830, and at least one Communication bus 840.
  • Communication bus 840 is used to implement connection communication between these devices.
  • the processor 810 is configured to execute an executable module, such as a computer program, stored in the memory 830; alternatively, the master node 800 can include a user interface 850 including, but not limited to, a display, a keyboard, and a pointing device, such as a mouse, Trackball, touchpad or tactile display.
  • the memory 830 may include a random access memory (RAM), and may also include a non-volatile memory such as at least one disk storage.
  • RAM random access memory
  • memory 830 stores the following elements, executable modules or data structures, or a subset thereof, or their extension set:
  • Operating system 832 which contains various system programs for implementing various basic services and handling hardware-based tasks
  • Application module 834 which contains various applications for implementing various application services.
  • the application module 834 includes, but is not limited to, a transmitting module 71 and a receiving module 72. Further, application The module 834 further includes: a confirmation module 73, a creation module, and a notification module.
  • each module in the application module 834 refers to the corresponding module in the master node 700, and details are not described herein.
  • the embodiment of the present invention performs a pre-snapshot function after receiving the snapshot creation notification sent by the main control node, where the pre-snapshot function includes a pre-snapshot interface parameter corresponding to each application or database saved in the local configuration file and a pause before the snapshot.
  • the script is called to make different applications or databases follow the standard processes and interfaces, and the scripts that call different applications or databases only need to modify the corresponding interface parameters and scripts, which reduces the complexity of implementing snapshots.
  • FIG. 9 is a schematic structural diagram of a snapshot system 900 according to Embodiment 9 of the present invention.
  • the system 900 includes: a master node 91 and at least one service node 92; the master node 91 is a master node provided in Embodiment 7 of the present invention, and each service node 92 is an embodiment of the present invention. Five provided business nodes.
  • a snapshot proxy server (Snapshot Agent Server) is deployed in the main control node 91, and each of the main control nodes provided in Embodiment 7 of the present invention is disposed in the snapshot proxy server.
  • a function module; a Snapshot Agent Client is deployed in each of the service nodes 92, and each function module in the service node provided by the fifth embodiment of the present invention and a pre-snapshot function and a snapshot are disposed in the snapshot proxy client.
  • a snapshot agent control management module (Snapshot Agent Control Manager) is further disposed in the master control node 91, and a snapshot policy and related configuration information of the snapshot proxy server and the snapshot proxy client are configured on the snapshot proxy control management module.
  • the configuration information of the snapshot proxy server includes the default installation directory of the snapshot proxy server and the communication port.
  • the communication port of the snapshot proxy server needs to be fixed; the configuration information of the snapshot proxy client includes the default installation directory of the snapshot proxy client, and the IP address.
  • the address and communication port, the client's communication port can use a fixed port, or can use a dynamic port.
  • the server and the client exchange information through the respective configured communication ports.
  • the interface between the cloud platform or the storage layer may be configured on the Snapshot Agent Control Management Module, and the cloud platform or the storage layer may be used to create a snapshot, delete a snapshot, and query a snapshot. Accordingly, the master node and the cloud The interaction between the platform or the storage tier is performed by the Snapshot Agent Control Management Module. In addition, if there is a firewall between the master node and the service node, you need to open the snapshot. Proxy server to client firewall policy.
  • the embodiment of the present invention performs a pre-snapshot function after receiving the snapshot creation notification sent by the main control node, where the pre-snapshot function includes a pre-snapshot interface parameter corresponding to each application or database saved in the local configuration file and a pause before the snapshot.
  • the script is called to make different applications or databases follow the standard processes and interfaces, and the scripts that call different applications or databases only need to modify the corresponding interface parameters and scripts, which reduces the complexity of implementing snapshots.

Landscapes

  • Engineering & Computer Science (AREA)
  • Theoretical Computer Science (AREA)
  • Human Computer Interaction (AREA)
  • Physics & Mathematics (AREA)
  • General Engineering & Computer Science (AREA)
  • General Physics & Mathematics (AREA)
  • Telephonic Communication Services (AREA)

Abstract

L'invention porte sur un procédé d'instantanée, un nœud de service, un nœud de commande principal et un système. Le procédé consiste à : recevoir une notification de création d'instantané envoyée par un nœud de commande principal; conformément à la notification de création d'instantané, exécuter une fonction pré-instantané, la fonction pré-instantané consistant à appeler des paramètres d'interface et des scripts de pause pré-instantané correspondant à chaque application ou base de données stockée dans des fichiers de configuration locaux; et après achèvement de l'exécution de la fonction pré-instantané, envoyer une notification d'achèvement d'opération pré-instantané au nœud de commande principal, de manière à commencer à créer un instantané. La présente invention réalise que différentes applications ou bases de données se conforment toutes à un flux et une interface standards, et elle nécessite seulement de modifier des paramètres d'interface et des scripts correspondants pour appeler des scripts de différentes applications ou bases de données, réduisant la complexité pour réaliser un instantané.
PCT/CN2013/079568 2012-12-07 2013-07-18 Procédé d'instantané, nœud de service, nœud de commande principal et système WO2014086150A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201210523981.9A CN103853632B (zh) 2012-12-07 2012-12-07 快照方法、业务节点、主控节点及系统
CN201210523981.9 2012-12-07

Publications (1)

Publication Number Publication Date
WO2014086150A1 true WO2014086150A1 (fr) 2014-06-12

Family

ID=50861315

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2013/079568 WO2014086150A1 (fr) 2012-12-07 2013-07-18 Procédé d'instantané, nœud de service, nœud de commande principal et système

Country Status (2)

Country Link
CN (1) CN103853632B (fr)
WO (1) WO2014086150A1 (fr)

Families Citing this family (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN106547926A (zh) * 2016-12-14 2017-03-29 北京华云网际科技有限公司 分布式块存储的快照树的根节点的优化方法和装置
CN108347467A (zh) * 2017-01-24 2018-07-31 华为技术有限公司 一种在分布式集群中组件包的安装方法及相关设备
WO2019178839A1 (fr) * 2018-03-23 2019-09-26 华为技术有限公司 Procédé et dispositif de création d'un instantané de cohérence pour une application distribuée et un système distribué
CN113515437B (zh) * 2020-04-10 2024-07-16 北京沃东天骏信息技术有限公司 调试接口的方法和装置
CN112286869A (zh) * 2020-10-29 2021-01-29 杭州宏杉科技股份有限公司 一种快照创建方法及装置

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102053876A (zh) * 2009-11-06 2011-05-11 杭州华三通信技术有限公司 快照建立方法、系统及应用服务器
CN102103530A (zh) * 2009-12-16 2011-06-22 成都市华为赛门铁克科技有限公司 快照方法、设备及系统
CN102520881A (zh) * 2011-12-02 2012-06-27 中标软件有限公司 一种云计算平台的虚拟机快照管理方法和系统

Family Cites Families (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US7370164B1 (en) * 2006-03-21 2008-05-06 Symantec Operating Corporation Backup of virtual machines from the base machine

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102053876A (zh) * 2009-11-06 2011-05-11 杭州华三通信技术有限公司 快照建立方法、系统及应用服务器
CN102103530A (zh) * 2009-12-16 2011-06-22 成都市华为赛门铁克科技有限公司 快照方法、设备及系统
CN102520881A (zh) * 2011-12-02 2012-06-27 中标软件有限公司 一种云计算平台的虚拟机快照管理方法和系统

Also Published As

Publication number Publication date
CN103853632B (zh) 2016-08-10
CN103853632A (zh) 2014-06-11

Similar Documents

Publication Publication Date Title
US10776215B2 (en) Snapshot generating method, system, and apparatus
US10169173B2 (en) Preserving management services with distributed metadata through the disaster recovery life cycle
CN112035293B (zh) 确定虚拟机节点所有权的方法、计算机系统和程序产品
US9871851B2 (en) Migrating private infrastructure services to a cloud
US10445186B1 (en) Associating a guest application within a virtual machine to create dependencies in backup/restore policy
US9304705B2 (en) Virtual machine cloning
US8458419B2 (en) Method for application backup in the VMware consolidated backup framework
EP3750066B1 (fr) Protection de charges de travail d'une infrastructure en tant que service dans un nuage public
KR101970839B1 (ko) 서비스의 2차 위치에서의 작업의 재생 기법
US10754741B1 (en) Event-driven replication for migrating computing resources
US10061665B2 (en) Preserving management services with self-contained metadata through the disaster recovery life cycle
US20140380411A1 (en) Techniques for workload spawning
WO2016045439A1 (fr) Procédé et dispositif de protection tolérant aux catastrophes de vnfm, nfvo et support de stockage
WO2012163245A1 (fr) Système de commande de services reposant sur des transactions et procédé de commande s'y rapportant
WO2014086150A1 (fr) Procédé d'instantané, nœud de service, nœud de commande principal et système
Agarwal et al. Live migration of virtual machines in cloud
WO2016106756A1 (fr) Procédé, système et appareil de reprise après sinistre
US9805038B2 (en) Efficient conflict resolution among stateless processes
US20210117330A1 (en) Provisioning Virtual Machines with a Single Identity and Cache Virtual Disk
CN117311627A (zh) 容器卷热扩容系统、方法及介质
US20240168853A1 (en) Techniques for providing data backup configurations as a service
US9483326B2 (en) Non-invasive upgrades of server components in cloud deployments
CN112241293A (zh) 工业互联网云平台的应用管理方法、装置、设备及介质
US12093151B2 (en) Managing reference snapshots across multiple sites for efficient failover/failback
US20240232387A1 (en) Intercepting and securing backup traffic

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

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

Country of ref document: EP

Kind code of ref document: A1