CN113127258A - Data backup method, device, equipment and medium - Google Patents
Data backup method, device, equipment and medium Download PDFInfo
- Publication number
- CN113127258A CN113127258A CN201911398370.4A CN201911398370A CN113127258A CN 113127258 A CN113127258 A CN 113127258A CN 201911398370 A CN201911398370 A CN 201911398370A CN 113127258 A CN113127258 A CN 113127258A
- Authority
- CN
- China
- Prior art keywords
- instance
- data
- backup
- storage system
- storage
- Prior art date
- Legal status (The legal status 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 status listed.)
- Pending
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/07—Responding to the occurrence of a fault, e.g. fault tolerance
- G06F11/14—Error detection or correction of the data by redundancy in operation
- G06F11/1402—Saving, restoring, recovering or retrying
- G06F11/1446—Point-in-time backing up or restoration of persistent data
- G06F11/1448—Management of the data involved in backup or backup restore
- G06F11/1451—Management of the data involved in backup or backup restore by selection of backup contents
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/07—Responding to the occurrence of a fault, e.g. fault tolerance
- G06F11/14—Error detection or correction of the data by redundancy in operation
-
- 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
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Quality & Reliability (AREA)
- Human Computer Interaction (AREA)
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
Abstract
The application provides a data backup method, which is applied to a storage system, wherein the storage system is preset with a default backup quantity, the default backup quantity is used for generating N data copies for first to-be-written data included in a first data writing request generated by a first example, the N data copies are stored in the storage system, and N is an integer greater than 1, and the method comprises the following steps: and acquiring adjustment setting of the default backup quantity, acquiring a second data writing request generated by a second instance, and generating M data copies for second data to be written in a storage layer of the storage system according to the adjustment setting of the default backup quantity, wherein M is a positive integer smaller than N. Therefore, the number of data copies can be reduced, the waste of storage resources is avoided, and the writing rate is improved.
Description
Technical Field
The present application relates to the field of storage technologies, and in particular, to a data backup method, apparatus, device, and medium.
Background
Cloud storage is being adopted by more and more enterprises due to the characteristics of flexibility, simplicity, high availability and the like. The cloud storage is a technology based on storage virtualization, which maps dispersed and heterogeneous storage devices in a storage network into a virtual storage resource pool, and provides an access interface of the storage resource pool for an application program, so that the application program accesses the storage resource pool through the access interface to realize data reading and writing.
In order to ensure data security and service continuity, when a storage system allocates storage resources, additional storage resources are often allocated to perform redundant backup on data. In some cases, the redundant backup of the storage system obtains more copies, which results in a waste of storage resources and further increases the application operation cost. In addition, the writing rate of the application is reduced due to more copies, so that the running efficiency of the application is influenced, and the user experience is reduced.
Disclosure of Invention
The application provides a data backup method, which supports adjustment of the default backup quantity preset by a storage system, so that the quantity of backup data copies is reduced under the condition of meeting data safety, the waste of storage resources is reduced, and the application and operation cost is reduced. The method can improve the data writing speed of the application and improve the running efficiency of the application, thereby improving the user experience.
In a first aspect, the present application provides a data backup method, which may be applied to a storage system. The storage system is preset with a default backup number, the default backup number is used for generating N data copies for first data to be written included in a first data writing request generated by a first instance, the N data copies are stored in the storage system, and N is an integer greater than 1. The storage system may obtain adjustment settings for the default backup number, and obtain a second data writing request generated by a second instance, where the second data writing request includes second data to be written, and the storage system may generate M data copies for the second data to be written in a storage layer of the storage system according to the adjustment settings for the default backup number. Wherein M is a positive integer less than N.
The method supports adjustment of the default backup quantity, for example, under the condition that an application layer backs up data, the default backup quantity can be adjusted at any time from instance creation to instance writing of the data generated by the instance into a storage system, and the data to be written is backed up based on the adjustment setting of the default backup quantity, so that the backup quantity is reduced on the premise of meeting data safety, the waste of storage resources is reduced, and the data writing rate of application is improved.
With reference to the first aspect, in a first implementation manner of the first aspect, the storage system may obtain the adjustment setting of the default backup number according to the service type by obtaining the service type of the second instance, and a user does not need to manually adjust the backup number, so that waste of storage resources due to human errors may be avoided.
With reference to the first aspect, in a second implementation manner of the first aspect, the storage system includes a console, and the console is provided with a backup number adjustment control. Correspondingly, the storage system can obtain the adjustment setting of the default backup quantity according to the storage layer backup cancellation operation triggered by the user through the backup quantity adjustment control. Therefore, the backup quantity can be adjusted according to the user requirements, and the balance between data safety and storage resources is realized.
With reference to the first aspect, in a third implementation manner of the first aspect, the storage system includes a console, and the console is provided with a security level selection control, where different security levels correspond to different backup numbers. Correspondingly, the storage system can obtain the adjustment setting of the default backup quantity according to the security level selection operation triggered by the user through the security level selection control. Therefore, the backup quantity can be adjusted in a personalized manner according to the user requirements, and the balance between data safety and storage resources is realized.
With reference to the first aspect or the first implementation manner to the third implementation manner of the first aspect, in a fourth implementation manner of the first aspect, the storage system may further obtain a service invocation request, where the service invocation request includes a service identifier of a target service, and the storage system may generate an instance of the target service according to the service invocation request, where the instance may be the first instance or the second instance.
With reference to the first aspect or the first implementation manner to the third implementation manner of the first aspect, in a fifth implementation manner of the first aspect, the storage system may further obtain an instance creation request, and then generate an instance according to the instance creation request, where the instance includes the first instance or the second instance.
In a second aspect, the present application provides a data backup apparatus, which is applied to a storage system, where a default backup number is preset in the storage system, where the default backup number is used to generate N data copies for first data to be written included in a first data writing request generated by a first instance, where the N data copies are stored in the storage system, and N is an integer greater than 1; the device comprises:
the communication module is used for acquiring the adjustment setting of the default backup number;
the communication module is further configured to obtain a second write data request generated by a second instance, where the second write data request includes second data to be written;
and the backup module is used for generating M data copies for the second data to be written in the storage layer of the storage system according to the adjustment setting of the default backup quantity, wherein M is a positive integer smaller than N.
With reference to the second aspect, in a first implementation manner of the second aspect, the communication module is specifically configured to:
acquiring the service type of the second instance;
the device further comprises:
and the determining module is used for acquiring the adjustment setting of the default backup quantity according to the service type.
With reference to the second aspect, in a second implementation manner of the second aspect, the storage system includes a console, and the console is provided with a backup number adjusting control;
the communication module is specifically configured to:
and obtaining the adjustment setting of the default backup quantity according to the storage layer backup cancellation operation triggered by the user through the backup quantity adjustment control.
With reference to the second aspect, in a third implementation manner of the second aspect, the storage system includes a console, the console is provided with a security level selection control, and different security levels correspond to different backup numbers;
the communication module is specifically configured to:
and obtaining the adjustment setting of the default backup quantity according to the security level selection operation triggered by the user through the security level selection control.
With reference to the second aspect or the first implementation manner to the third implementation manner of the second aspect, in a fourth implementation manner of the second aspect, the communication module is further configured to:
acquiring a service calling request, wherein the service calling request comprises a service identifier of a target service;
the device further comprises:
and the instance generation module is used for generating an instance of the target service according to the service calling request, wherein the instance comprises the first instance or the second instance.
With reference to the second aspect or the first implementation manner to the third implementation manner of the second aspect, the communication module is further configured to:
acquiring an instance creation request;
the device further comprises:
an instance generation module, configured to generate an instance according to the instance creation request, where the instance includes the first instance or the second instance.
In a third aspect, the present application provides a computer cluster comprising at least one computer, each computer comprising a processor and a memory. The processor of the at least one computer is configured to execute instructions stored in the memory of the at least one computer to perform the method as in the first aspect or any implementation manner of the first aspect.
In a fourth aspect, the present application provides a computer-readable storage medium having stored therein instructions, which, when run on a cluster of computers, cause the cluster of computers to perform the method of the first aspect or any one of the implementations of the first aspect.
In a fifth aspect, the present application provides a computer program product comprising instructions which, when run on a cluster of computers, cause the cluster of computers to perform the method of the first aspect or any one of the implementations of the first aspect.
Drawings
FIG. 1 is a block diagram of a storage system in an embodiment of the present application;
FIG. 2A is a schematic diagram of a storage system for data backup in an embodiment of the present application;
FIG. 2B is a schematic diagram of a storage system for data backup in an embodiment of the present application;
FIG. 3 is a flowchart of a data backup method in an embodiment of the present application;
FIG. 4 is an interface diagram of an example creation configuration interface in an embodiment of the present application;
FIG. 5 is an interface diagram of an example creation configuration interface in an embodiment of the present application;
FIG. 6 is a schematic interface diagram of a service invocation configuration interface in an embodiment of the present application;
fig. 7 is a schematic structural diagram of a computer cluster according to an embodiment of the present application.
Detailed Description
Cloud storage is a network-based storage model. A cloud storage service provider may map storage devices scattered in a network, such as computers located around the world, into a virtual storage resource pool and provide storage services based on the storage resource pool. Users such as businesses or individuals, etc. that require data storage hosting may use the storage service by purchasing or leasing storage space from a cloud storage service provider.
The storage service is implemented based on a storage system. Fig. 1 shows a model architecture diagram of a storage system. As shown in FIG. 1, a storage system may include a storage tier 102, an underlying management tier 104, and a console (Console) 106. Wherein the storage tier 102 comprises at least one storage device. The storage device may be a homogeneous or heterogeneous storage device. For example, the storage device may be a Fibre Channel (FC) storage device, an Internet Protocol (IP) storage device such as a Network Attached Storage (NAS), an Internet small computer system interface (iSCSI), or a direct-attached-storage (DAS) storage device such as a SCSI (SCSI) or a Serial Attached SCSI (SAS). These storage devices may be connected through a wide area network or a FC fibre channel network.
The underlying management layer 104 located above the storage layer 102 may map the storage device, implement logical virtualization of the storage device, and form a storage resource pool. The base management layer 104 may also create a storage volume (volume) for the storage resource pool. The storage resource pool may be logically partitioned into at least one storage volume. At least one storage node may be included in each storage volume. The storage node is a node formed by the storage device. The underlying management layer 102 may allocate storage volumes as needed. Correspondingly, the base management layer 104 may also delete storage volumes when their use is not needed. In some cases, the base management layer 104 also supports mounting storage volumes and dismounting storage volumes. It should be noted that the basic management layer 104 may perform multi-link redundancy management on the storage nodes, monitor the states of the storage nodes, and perform fault maintenance when the storage nodes fail, so as to ensure the reliability of the storage system.
The data backup apparatus 1040 includes a communication module 1042 and a backup module 1044. The communication module 1042 is specifically configured to obtain a data write request generated by an instance, and the backup module 1044 is specifically configured to generate at least one data copy in the storage tier 102 of the storage system for data to be written in the data write request.
It should be noted that, for an example (referred to as a first example in this application) in which the default backup number is not adjusted, the backup module 1044 generates N data copies for the data to be written (referred to as a first data to be written in this application) included in the write data request generated by the backup module. In an example (referred to as a second example in this application) in which the default backup number is adjusted and set, the backup module 1044 generates M data copies for the data to be written (referred to as second data to be written in this application) included in the write data request generated by the backup module. Wherein M is a positive integer less than N.
The console 106 is a user interface that enables a user to customize the storage services he or she desires. The user interface may be a Graphical User Interface (GUI) or a command-line interface (CLI). The command line interface is also called a Character User Interface (CUI), among others. Through the user interface, a user can configure the needed storage service. For example, the user may provide information such as the storage resource type and storage resource size required by the user interface configuration. Of course, the user may also manually adjust the default backup number by using the backup number adjustment control provided by the console 106 based on the service type of the instance.
In this application, an instance may be an instance running on the user side. Referring to the schematic diagram of data backup in the storage system shown in fig. 2A, as shown in fig. 2A, an instance, which may be a process of an application, runs on the user side 200, and the instance may generate a write data request and send the write data request to the storage system. The data writing request comprises data to be written. If the default backup number is adjusted in this example, the base management layer 104 in the storage system generates M data copies for the data to be written in the storage layer 102 of the storage system according to the adjustment setting of the default backup number. If the default backup number is not adjusted in this example, the base management layer 104 generates N data copies for the data to be written in the storage layer 102 of the storage system according to the default backup number.
In some possible implementations, the instance may also be an instance running in a storage system. Referring to the data backup diagram in the storage system shown in fig. 2B, as shown in fig. 2B, the storage system further includes a computing resource pool 108. Similar to the storage resource pool, the computing resource pool 108 may be virtualized by at least one computing device. In particular, decentralized computing devices may be connected over a network, and these computing devices are mapped as a pool of computing resources for the unified provision of computing services. Where each computing device may be considered a compute node in a computing resource pool.
In the embodiment shown in fig. 2B, the base management layer 104 is further configured to implement a cooperative work among a plurality of computing nodes, and the console 106 further supports a user to create instance-related information or service invocation-related information through a user interface configuration. In this embodiment, when creating an instance, the base management layer 104 may mount the storage volume to an instance of a compute node, such as a virtual machine (vm), so that, when performing data backup, data to be written may be directly written into the storage volume mounted by the instance without addressing through the data management layer 104, and a corresponding data copy is obtained.
In the embodiment shown in fig. 1 or fig. 2A, 2B, the base management layer 104 and the console 106 may be deployed on a computer cluster, which may include at least one computer. It should be noted that base management layer 104 and console 106 may be deployed on the same computer cluster or on different computer clusters. In addition, the user terminal 200 in fig. 2A may be any user device with computing capability, for example, wearable devices such as a smart phone, a computer, a smart band, and a smart watch.
In view of data security and service continuity, a storage system generally defaults to backup data in a storage layer, for example, three backups are performed on data to obtain three data copies. However, in some application scenarios, the application layer itself already backs up the data, and backing up the data in the storage layer will result in more copies being stored in the storage system, which results in waste of storage resources and increases application operation cost. Moreover, writing more copies also causes the application writing rate to decrease, thereby affecting the application running efficiency and reducing the user experience.
Based on this, the application provides a data backup method. The method supports adjustment of the number of the default backups, and performs data backup based on adjustment setting of the number of the default backups, so that the number of copies written into a storage layer is reduced on the premise that data safety meets requirements, storage resource waste is avoided, and application and operation cost is reduced. In addition, the application writing rate can be improved by reducing the number of copies written into the storage layer, so that the application running efficiency is improved, and the user experience is improved.
Embodiments of the present application are described below with reference to the accompanying drawings.
The terms "first," "second," and the like in the description and in the claims of the present application and in the above-described drawings are used for distinguishing between similar elements and not necessarily for describing a particular sequential or chronological order. It is to be understood that the terms so used are interchangeable under appropriate circumstances and are merely descriptive of the various embodiments of the application and how objects of the same nature can be distinguished.
Referring to the flowchart of the data backup method shown in fig. 3, the method may be applied to the data backup apparatus 1040 as shown above, and specifically includes the following steps:
s302: the data backup device 1040 obtains the first write data request generated by the first instance.
In this application, the first instance refers to an instance in which the default number of backups is not adjusted. The first instance may be generated by data backup appliance 1040 in response to an instance creation request, or may be generated by data backup appliance 1040 in response to a service invocation request.
In actual application, a user may create an instance or invoke a service by accessing the console 106 of the storage system. Specifically, a user may access the console 106 of the storage system through any user device such as a mobile phone and a computer, the console 106 is provided with an instance creation interface and/or a service invocation interface, and the user may enter an instance creation procedure through the instance creation interface and enter a service invocation procedure through the service invocation interface.
In the instance creation flow, the user device may display an instance creation configuration interface. As shown in FIG. 4, an instance creation configuration interface includes an instance configuration component and a storage configuration component. The instance configuration component comprises an instance type configuration control, an instance quantity configuration control and a duration configuration control. The storage configuration component comprises a storage resource type configuration control and a storage resource size configuration control.
The instance type configuration control may specifically be a selection control corresponding to each instance type in the instance type list. The example type list shows at least one of information such as a specification family, a specification name, a virtual central processing unit (vCPU) number, a memory size, a processor model, an intranet bandwidth, a reference price and the like corresponding to each example type. And the user selects the instance type through the selection control based on the information displayed by the instance type list, so that the instance type configuration is realized. In some cases, the instance type configuration component may further include an instance type filtering control, and a user may filter the instance types of the specified number of vcpus, the specified size of memory, and/or the specified specification name through the filtering control. Of course, the instance type screening control can also support the user to screen the instance types based on the architecture or the function classification, so that the selection range is narrowed, and the configuration efficiency is improved.
The storage resource type configuration control is specifically used for configuring the storage resource type. The storage resource type refers to the type of a cloud storage disk (cloud disk for short). In one example, the storage resource type may be a Hard Disk Drive (HDD) type or a Solid State Drive (SSD) type. The mechanical hard disk type corresponds to a common cloud disk, and the solid state hard disk type corresponds to a high-efficiency cloud disk. The storage resource size configuration control is specifically used for configuring the size of the storage resource. The storage resource size refers to the size of the space of the storage resource. In one example, a user may configure a storage resource size of 20 Gigabytes (GiB).
It should be noted that the data backup apparatus 1040 is provided with a default backup number, that is, the number of default backups of the storage layer for data security. Considering that some applications themselves are backed up at the application layer, such as applications of a Distributed database, a Distributed File System (HDFS), a Distributed message component, and the like, the instance creation configuration interface may further provide a backup number adjustment component 40 so that a user can adjust the backup number to reduce the data backup number.
Wherein adjusting the number of storage tier backups comprises cancelling the storage tier backups or reducing the number of storage tier backups.
In some possible implementations, as shown in fig. 4, the backup number adjustment component 40 includes a backup number adjustment control 402. When the backup quantity adjusting control is not selected, the storage layer backup cancellation operation is not triggered by the representation. For the instance that the application layer is not backed up, the user can not select the backup number adjusting control, so that the storage system can subsequently perform data backup according to the default backup number, and the data safety is guaranteed.
In other possible implementations, as shown in FIG. 5, the backup number adjustment component 40 includes a security level selection control 404 for configuring security levels, with different security levels corresponding to different storage tier backup numbers. In the example of fig. 5, the security levels include a normal level and a high level, where the high level may correspond to a default number of backups and the normal level may correspond to a number of backups less than the default number of backups. For example, when the default number of the backups is 3, the high-level representation storage tier performs 3 backups, and the common-level representation storage tier performs 2 backups or 1 backups. In other possible implementations, the security level selection control 404 may also provide more security levels for the user to select. For the application layer non-backup example, the user can select a high level, so that the storage system performs data backup according to the default backup quantity, and the data safety is guaranteed.
An instance creation confirmation control is further included in the instance creation configuration interface and is used for triggering instance creation operation. After the user completes the instance configuration and the storage configuration, the instance creation operation can be triggered through the instance creation confirmation control. The user equipment generates an instance creation request in response to the above-described instance creation operation, and sends the instance creation request to the data backup apparatus 1040 in the storage system. It should be noted that the user equipment may generate an instance creation request, where all parameters are carried in the instance creation request. In some cases, the user equipment may also generate a plurality of instance creation requests, where each instance creation request carries part of parameters, for example, one instance creation request carries parameters such as an instance type, an instance number, and a use duration, and another instance creation request carries parameters such as a storage resource type and a storage resource size.
The data backup device 1040 creates an instance, such as a virtual machine, on the compute node in response to the instance creation request. The user may deploy the application in the virtual machine to provide the corresponding service. The first instance is the instance whose default backup number is not adjusted during and after the instance is created.
In the service invocation flow, the user equipment may display a service invocation configuration interface. As shown in FIG. 6, the service invocation configuration interface may include a service selection component. Wherein the service selection component provides at least one service for selection by the user. The service invocation configuration interface may also include a node configuration component. The node configuration component is for configuring a node that provides a service. In the example shown in FIG. 6, the node configuration component may be used to configure the control node master and the analysis core nodes needed to provide the service, the instance specification of the analysis task node, the number of instances, etc.
Similar to the instance creation flow, the service call configuration interface may also include a service call validation control. The user may trigger the service invocation operation through the service invocation control, and the user equipment may generate a service invocation request in response to the service invocation operation, and send the service invocation request to the data backup apparatus 1040 in the storage system.
The service invocation request includes the service identification of the target service. The target service refers to a service selected and called by a user. The data backup device 1040 generates an instance of the target service in response to the service invocation request. Wherein an instance of a target service may be a process running on one or more compute nodes. The compute node running the process may also be referred to as a task node. In some cases, when the parameter of the node is carried in the service invocation request, the data backup device may further create nodes required for providing the service, including a control node, an analysis core node, and an analysis task node, based on the parameter. When the target service does not perform data backup at the application layer, the data backup apparatus 1040 may generate the first instance.
The time period from creation to deletion of the first instance is referred to as the lifecycle of the first instance. In the lifecycle, the first instance may generate a first write data request, where the first write data request carries first data to be written. And then, sending a first write data request to a data backup device 1040 in the storage system, so as to generate a data backup for the first data to be written in the storage system, thereby ensuring data security.
S304: the data backup apparatus 1040 generates N data copies for the first data to be written included in the first data write request generated by the first instance, according to the default backup number.
Specifically, the first instance does not adjust the default backup number, so the data backup apparatus 1040 generates N data copies for the first to-be-written data included in the first write data request generated by the first instance according to the default backup number, so as to ensure data security.
S306: the data backup apparatus 1040 obtains the adjustment setting of the default backup number.
Considering that some applications, such as a distributed file system, a distributed object storage system, a distributed message component, and the like, perform data backup in an application layer, as shown in fig. 4, a user may trigger a storage tier backup cancellation operation through a backup number adjustment control when creating an instance or after creating an instance. The data backup apparatus 1040 may obtain adjustment settings for the default number of backups based on the storage tier backup cancellation operation. For example, the number of backups is adjusted from a default number of backups to one.
It should be noted that the backup number adjustment control may be in other forms. For example, the number of backups may be increased and decreased by decreasing the child control, based on which the adjustment setting for the number of backups may be decreased by decreasing the child control. The setting of the adjustment of the backup number may be the backup number directly edited by the editing control.
Of course, as shown in fig. 5, the user may also trigger the security level selection operation based on the security level selection control, and correspondingly, the data backup apparatus 1040 may obtain the adjustment setting of the default backup number according to the security level selection operation triggered by the user through the security level selection control.
In some possible implementations, for example, when the instance is generated by using a service invocation manner, the data backup apparatus 1040 may also obtain a service type of the instance, and automatically determine an adjustment setting for the default backup number according to the service type. The service types can be classified into distributed service types and non-distributed service types. For the distributed service type, backup is generally performed in the application layer, and based on this, when the service type of the instance is the distributed service type, the data backup apparatus 1040 may automatically adjust the default backup number to reduce the data backup number.
In case of instance creation or service call, the data backup apparatus 1040 may also generate a bill based on the type of storage resource required, the size of the storage resource, and the adjustment setting of the default backup number. The data backup apparatus 1040 may return a bill to the user equipment, and the user equipment may display the bill on a corresponding user interface, such as an example creation configuration interface or a service call configuration interface, so that the user determines whether to trigger a corresponding operation or adjust a configuration parameter based on the bill. In some cases, data backup 1040 also generates the above-described bill based on information including the instance type and number of instances.
S308, the data backup device 1040 obtains the second write data request generated by the second instance.
In this application, the second example refers to an example in which the default backup number is adjusted. Similar to the first instance, the second instance may be generated by the data backup apparatus 1040 in response to the instance creation request, or may be generated by the data backup apparatus 1040 in response to the service invocation request.
When instance creation or service calling is performed, a user can trigger storage tier backup cancellation operation through the backup quantity adjusting control so as to adjust the default backup quantity. The user may also select a security level via a security level selection control to adjust the default number of backups. Thus, the instance creation request or the service invocation request may also carry adjustment settings for the default backup number. Correspondingly, the instance generated by the data backup device 1040 in response to the instance creation request or the service invocation request is the second instance.
For the service invocation scenario, when the service type of the invoked target service is a distributed service type, the data backup apparatus 1040 may also automatically obtain an adjustment setting for the default backup number based on the service type, and the generated instance is the second instance.
The time period from creation to deletion of the second instance is referred to as the lifecycle of the second instance. In the lifetime, the second instance may generate a second write data request, where the second write data request carries second data to be written, and then send the second write data request to the data backup apparatus 1040, so that the data backup apparatus 1040 performs persistent storage on the second write data.
S310: the data backup apparatus 1040 generates M data copies for the second data to be written in the storage layer 102 of the storage system according to the adjustment setting of the default backup quantity.
Specifically, when the instance is an instance running on a user side, the data backup apparatus 1040 may generate M data copies for the second data to be written in the storage layer of the storage system based on the correspondence between the logical address and the physical address of the storage volume in the storage resource pool according to the adjustment setting of the default backup number. Wherein M is a positive integer less than N. Therefore, on the premise of meeting data security, the problems of storage resource waste and low writing rate caused by excessive data copies are solved.
When the instance is an instance running on a compute node in a compute resource pool of the storage system, for example, a virtual machine on the compute node, the data backup apparatus 1040 may directly write the second data to be written into the storage volume based on the correspondence between the compute node and the mounted storage volume thereof according to the adjustment setting of the default backup number, and generate M data copies.
It should be noted that the order of creation of the first instance and the second instance may be arbitrary. In some possible implementation manners, the first instance and the second instance may be created in parallel, or may be created according to a set sequence. Therefore, the execution sequence of S302, S304 and S306 to S308 may be parallel, or S302, S304 may be executed first and then S306 to S308, or S306 to S308 may be executed first and then S302 to S304. In some cases, the data backup device 1040 may not create the first instance, that is, S302 and S304 are optional steps in the embodiment of the present application, and whether to execute the first instance or not may be selected according to actual needs.
For ease of understanding, the data backup method is described below with reference to specific examples.
This example includes application a and application B, where application a is a non-distributed application and application B is a distributed application. An example 1 is created for the application A, three examples 2 are created for the application B, and when the example is created for the application B, a user adjusts the default backup number preset by the storage system, specifically, three are adjusted to one.
For the write data request generated in example 1, the data backup device 1040 generates 1 × 3 data copies in the storage tier 102 for the data to be written in the write data request according to the default backup number.
For the data write requests generated by the three instances 2, the data backup device 1040 generates 3 × 1 data copies for the data to be written in the data write request in the storage tier 102 according to the adjustment setting of the default backup number. If the backup is performed according to the default backup number, 3 x 3 copies of the data are generated.
Therefore, the data backup method provided by the embodiment of the application can greatly reduce the number of backed-up data copies for the backed-up instance of the application layer, reduce the waste of storage resources and reduce the application operation cost. In addition, by reducing the number of copies of data to be written, the data writing efficiency can be improved, so that the application is smoother, and the user experience is improved.
The data backup method provided by the embodiment of the present application is described in detail above with reference to fig. 1 to 6, and the apparatus and device provided by the present application will be described below with reference to the accompanying drawings.
Referring to the schematic structural diagram of the data backup apparatus 1040 shown in fig. 1, the apparatus 1040 is applied to a storage system, and the storage system is preset with a default backup number, where the default backup number is used to generate N data copies for first data to be written included in a first data write request generated by a first example, where the N data copies are stored in the storage system, and N is an integer greater than 1. The apparatus 1040 includes:
a communication module 1042 for obtaining adjustment setting of default backup number;
the communication module 1042 is further configured to obtain a second write data request generated by a second instance, where the second write data request includes second data to be written;
and the backup module 1044 is configured to generate M data copies for the second data to be written in the storage layer of the storage system according to the adjustment setting of the default backup number, where M is a positive integer smaller than N.
For a specific implementation of the communication module 1042, reference may be made to the description of the relevant contents in steps S306 and S308 in the embodiment shown in fig. 3, and for a specific implementation of the backup module 1044, reference may be made to the description of the relevant contents in step S310 in the embodiment shown in fig. 3, which is not described herein again.
Optionally, the communication module 1042 is specifically configured to:
acquiring the service type of the second instance;
the apparatus 1040 further comprises:
and the determining module is used for acquiring the adjustment setting of the default backup quantity according to the service type.
Optionally, the storage system includes a console, and the console is provided with a backup number adjustment control;
the communication module 1042 is specifically configured to:
and obtaining the adjustment setting of the default backup quantity according to the storage layer backup cancellation operation triggered by the user through the backup quantity adjustment control.
Optionally, the storage system includes a console, the console is provided with a security level selection control, and different security levels correspond to different backup numbers;
the communication module 1042 is specifically configured to:
and obtaining the adjustment setting of the default backup quantity according to the security level selection operation triggered by the user through the security level selection control.
Optionally, the communication module 1042 is further configured to:
acquiring a service calling request, wherein the service calling request comprises a service identifier of a target service;
the apparatus 1040 further comprises:
and the instance generation module is used for generating an instance of the target service according to the service calling request, wherein the instance comprises the first instance or the second instance.
Optionally, the communication module 1042 is further configured to:
acquiring an instance creation request;
the apparatus 1040 further comprises:
an instance generation module, configured to generate an instance according to the instance creation request, where the instance includes the first instance or the second instance.
The data backup apparatus 1040 according to the embodiment of the present application may correspond to performing the method described in the embodiment of the present application, and the above and other operations and/or functions of each module of the data backup apparatus 1040 are respectively to implement the corresponding flow of each method in fig. 3, and for brevity, are not described again here.
The data backup apparatus 1040 may be implemented by a computer cluster. FIG. 7 provides a computer cluster, the computer cluster shown in FIG. 7 being illustrated as including one computer. As shown in fig. 7, the computer cluster 500 may be specifically used to implement the functions of the data backup apparatus 1040 in the above embodiments. The computer cluster 500 includes a bus 501, a processor 502, a communication interface 503, and a memory 504. The processor 502, memory 504 and communication interface 503 communicate via the bus 501. The bus 501 may be a Peripheral Component Interconnect (PCI) bus, an Extended Industry Standard Architecture (EISA) bus, or the like. The bus may be divided into an address bus, a data bus, a control bus, etc. For ease of illustration, only one thick line is shown in FIG. 7, but this is not intended to represent only one bus or type of bus. The communication interface 503 is used for communication with the outside. For example, the communication interface 503 may be used to obtain an adjustment setting for the default number of backups, or to obtain a first write data request generated by a first instance, a second write data request generated by a second instance, and so on.
The processor 502 may be a Central Processing Unit (CPU). The memory 504 may include volatile memory (volatile memory), such as Random Access Memory (RAM). The memory 504 may also include a non-volatile memory (non-volatile memory), such as a read-only memory (ROM), a flash memory, a Hard Disk Drive (HDD), or a Solid State Drive (SSD).
The memory 504 has stored therein executable code that the processor 502 executes to perform the aforementioned data backup method. Specifically, in the case of implementing the data backup apparatus 1040 and the modules described in the embodiments are implemented by software, software or program codes required for executing the functions of the backup module 1044, the determination module and the instance creation module are stored in the memory 504, the function of the communication module 1042 is implemented by the communication interface 503, and the processor is configured to execute the instructions in the memory 504 and execute the data backup method applied to the data backup apparatus 1040.
Specifically, the computer cluster 500 obtains the adjustment setting for the default backup number through the communication interface 503, obtains the second write data request generated by the second instance through the communication interface 503, and then the processor 502 performs the following operations based on the instructions in the memory 504:
and according to the adjustment setting of the default backup quantity, generating M data copies for the second data to be written in a storage layer of the storage system, wherein M is a positive integer smaller than N.
Optionally, the computer cluster 500 may obtain the service type of the second instance through the communication interface 503;
the following operations are then performed based on the instructions in the memory 504:
and acquiring the adjustment setting of the default backup quantity according to the service type.
Optionally, the storage system includes a console, and the console is provided with a backup number adjustment control; the computing cluster may obtain the adjustment setting for the default backup number based on the storage tier backup cancellation operation triggered by the user through the backup number adjustment control through the communication interface 503.
Optionally, the storage system comprises a console, the console being provided with a security level selection control, the different security levels corresponding to different backup numbers; the computing cluster may obtain the adjustment setting for the default backup number based on the storage tier backup cancellation operation triggered by the user through the backup number adjustment control through the communication interface 503.
Optionally, the computer cluster 500 further obtains a service invocation request through the communication interface 503, the service invocation request including the service identification of the target service, and the processor 502 further performs the following operations based on the instructions in the memory 504:
and generating an instance of the target service according to the service calling request, wherein the instance comprises the first instance or the second instance.
Optionally, the computer cluster 500 further obtains an instance creation request through the communication interface 503, and the processor 502 further performs the following operations based on the instructions in the memory 504:
generating an instance according to the instance creation request, the instance including the first instance or the second instance.
Fig. 7 illustrates functions of the data backup apparatus 1040 implemented by the computer cluster 500 including one computer. In other possible implementations of the present application, the functions of the service apparatus 1040 may also be implemented by a computer cluster formed by a plurality of computers.
In some possible implementations, a computer cluster may include multiple computers, each capable of performing all of the functions of data backup appliance 1040. That is, the memory 504 of each computer in the computer cluster stores the software or program code needed to implement the functions of the backup module 1044, the determination module, and the instance generation module.
In other possible implementations, a computer cluster may include multiple computers, at least one of which implements some of the functionality of data backup appliance 1040, and multiple computers that cooperate to implement all of the functionality of data backup appliance 104. In one example, the computers in the computer cluster may be divided into groups, where one group of computers has stored in its memory the software or program code needed to implement the functions of the backup module 1044, another group of computers has stored in its memory the software or program code needed to implement the functions of the identified modules, and a group of computers has stored in its memory the software or program code needed to implement the functions of the instance generating module, such that all of the functions of the data backup apparatus 1040 are implemented by a plurality of computers.
It should be noted that the computers in the computer cluster may also be combined in other manners to implement all functions of the data backup apparatus 1040. For example, one set of computers may implement the functionality of the backup module 1044 and another set of computers implement the functionality of the determination module and the instance generation module. This is not a limitation of the present application.
Embodiments of the present application further provide a computer-readable storage medium, which includes instructions that, when executed on a computer cluster, cause the computer cluster to execute the data backup method applied to the data backup apparatus 1040.
An embodiment of the present application further provides a computer program product, where when the computer program product is executed by a computer cluster, the computer cluster executes any one of the foregoing data backup methods. The computer program product may be a software installation package which may be downloaded and executed on a cluster of computers in the event that any of the aforementioned data backup methods are required.
It should be noted that the above-described embodiments of the apparatus are merely schematic, where the units described as separate parts may or may not be physically separate, and the parts displayed as units may or may not be physical units, may be located in one place, or may be distributed on multiple network units. Some or all of the modules may be selected according to actual needs to achieve the purpose of the solution of the present embodiment. In addition, in the drawings of the embodiments of the apparatus provided in the present application, the connection relationship between the modules indicates that there is a communication connection therebetween, and may be implemented as one or more communication buses or signal lines.
Through the above description of the embodiments, those skilled in the art will clearly understand that the present application can be implemented by software plus necessary general-purpose hardware, and certainly can also be implemented by special-purpose hardware including special-purpose integrated circuits, special-purpose CPUs, special-purpose memories, special-purpose components and the like. Generally, functions performed by computer programs can be easily implemented by corresponding hardware, and specific hardware structures for implementing the same functions may be various, such as analog circuits, digital circuits, or dedicated circuits. However, for the present application, the implementation of a software program is more preferable. Based on such understanding, the technical solutions of the present application may be substantially embodied in the form of a software product, which is stored in a readable storage medium, such as a floppy disk, a usb disk, a removable hard disk, a ROM, a RAM, a magnetic disk, or an optical disk of a computer, and includes several instructions for enabling a computer device (which may be a personal computer, an exercise device, or a network device) to execute the method according to the embodiments of the present application.
In the above embodiments, the implementation may be wholly or partially realized by software, hardware, firmware, or any combination thereof. When implemented in software, may be implemented in whole or in part in the form of a computer program product.
The computer program product includes one or more computer instructions. When loaded and executed on a computer, cause the processes or functions described in accordance with the embodiments of the application to occur, in whole or in part. The computer may be a general purpose computer, a special purpose computer, a network of computers, or other programmable device. The computer instructions may be stored in a computer readable storage medium or transmitted from one computer readable storage medium to another, for example, from one website site, computer, training device, or data center to another website site, computer, training device, or data center via wired (e.g., coaxial cable, fiber optic, Digital Subscriber Line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.). The computer-readable storage medium can be any available medium that a computer can store or a data storage device, such as a training device, a data center, etc., that incorporates one or more available media. The usable medium may be a magnetic medium (e.g., floppy Disk, hard Disk, magnetic tape), an optical medium (e.g., DVD), or a semiconductor medium (e.g., Solid State Disk (SSD)), among others.
Claims (14)
1. A data backup method is characterized by being applied to a storage system, wherein the storage system is preset with a default backup quantity, the default backup quantity is used for generating N data copies for first to-be-written data included in a first data writing request generated by a first instance, the N data copies are stored in the storage system, and N is an integer greater than 1;
acquiring adjustment setting of the default backup quantity;
acquiring a second data writing request generated by a second instance, wherein the second data writing request comprises second data to be written;
and according to the adjustment setting of the default backup quantity, generating M data copies for the second data to be written in a storage layer of the storage system, wherein M is a positive integer smaller than N.
2. The method of claim 1, wherein obtaining the adjustment setting for the default number of backups comprises:
acquiring the service type of the second instance;
and acquiring the adjustment setting of the default backup quantity according to the service type.
3. The method of claim 1, wherein the storage system comprises a console provided with a backup number adjustment control;
the obtaining of the adjustment setting of the default backup number includes:
and obtaining the adjustment setting of the default backup quantity according to the storage layer backup cancellation operation triggered by the user through the backup quantity adjustment control.
4. The method of claim 1, wherein the storage system comprises a console provided with a security level selection control, different security levels corresponding to different backup numbers;
the obtaining of the adjustment setting of the default backup number includes:
and obtaining the adjustment setting of the default backup quantity according to the security level selection operation triggered by the user through the security level selection control.
5. The method of any one of claims 1 to 4, further comprising:
acquiring a service calling request, wherein the service calling request comprises a service identifier of a target service;
and generating an instance of the target service according to the service calling request, wherein the instance comprises the first instance or the second instance.
6. The method of any one of claims 1 to 4, further comprising:
acquiring an instance creation request;
generating an instance according to the instance creation request, the instance including the first instance or the second instance.
7. A data backup device is characterized by being applied to a storage system, wherein the storage system is preset with a default backup number, the default backup number is used for generating N data copies for first to-be-written data included in a first data writing request generated by a first instance, the N data copies are stored in the storage system, and N is an integer greater than 1; the device comprises:
the communication module is used for acquiring the adjustment setting of the default backup number;
the communication module is further configured to obtain a second write data request generated by a second instance, where the second write data request includes second data to be written;
and the backup module is used for generating M data copies for the second data to be written in the storage layer of the storage system according to the adjustment setting of the default backup quantity, wherein M is a positive integer smaller than N.
8. The apparatus of claim 7, wherein the communication module is specifically configured to:
acquiring the service type of the second instance;
the device further comprises:
and the determining module is used for acquiring the adjustment setting of the default backup quantity according to the service type.
9. The apparatus of claim 7, wherein the storage system comprises a console, the console being provided with a backup number adjustment control;
the communication module is specifically configured to:
and obtaining the adjustment setting of the default backup quantity according to the storage layer backup cancellation operation triggered by the user through the backup quantity adjustment control.
10. The apparatus of claim 7, wherein the storage system comprises a console provided with security level selection controls, different security levels corresponding to different numbers of backups;
the communication module is specifically configured to:
and obtaining the adjustment setting of the default backup quantity according to the security level selection operation triggered by the user through the security level selection control.
11. The apparatus of any one of claims 7 to 10, wherein the communication module is further configured to:
acquiring a service calling request, wherein the service calling request comprises a service identifier of a target service;
the device further comprises:
and the instance generation module is used for generating an instance of the target service according to the service calling request, wherein the instance comprises the first instance or the second instance.
12. The apparatus of any one of claims 7 to 10, wherein the communication module is further configured to:
acquiring an instance creation request;
the device further comprises:
an instance generation module, configured to generate an instance according to the instance creation request, where the instance includes the first instance or the second instance.
13. A cluster of computers comprising at least one computer, each computer comprising a processor and a memory;
the processor of the at least one computer is configured to execute instructions stored in the memory of the at least one computer to perform the method of any of claims 1 to 6.
14. A computer-readable storage medium comprising instructions that, when executed on a computer cluster, cause the computer cluster to perform the method of any of claims 1 to 6.
Priority Applications (2)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201911398370.4A CN113127258A (en) | 2019-12-30 | 2019-12-30 | Data backup method, device, equipment and medium |
| PCT/CN2020/111987 WO2021135326A1 (en) | 2019-12-30 | 2020-08-28 | Data backup method, apparatus and device, and medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201911398370.4A CN113127258A (en) | 2019-12-30 | 2019-12-30 | Data backup method, device, equipment and medium |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN113127258A true CN113127258A (en) | 2021-07-16 |
Family
ID=76687071
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201911398370.4A Pending CN113127258A (en) | 2019-12-30 | 2019-12-30 | Data backup method, device, equipment and medium |
Country Status (2)
| Country | Link |
|---|---|
| CN (1) | CN113127258A (en) |
| WO (1) | WO2021135326A1 (en) |
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN115562911A (en) * | 2022-12-07 | 2023-01-03 | 中科方德软件有限公司 | Virtual machine data backup method, device, system, electronic equipment and storage medium |
| WO2023151547A1 (en) * | 2022-02-14 | 2023-08-17 | 华为技术有限公司 | Data processing system and method, and device |
Family Cites Families (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101902498B (en) * | 2010-07-02 | 2013-03-27 | 广州鼎甲计算机科技有限公司 | Network technology based storage cloud backup method |
| CN110362422A (en) * | 2018-04-11 | 2019-10-22 | 武汉海康存储技术有限公司 | A kind of data back up method, apparatus and system |
| CN110389715B (en) * | 2018-04-23 | 2021-07-09 | 杭州海康威视系统技术有限公司 | Data storage method, storage server and cloud storage system |
| CN110096388A (en) * | 2019-04-28 | 2019-08-06 | 平安科技（深圳）有限公司 | A kind of method, apparatus and computer storage medium of data backup |
| CN110597659A (en) * | 2019-08-28 | 2019-12-20 | 华为技术有限公司 | Backup processing method and server |
-
2019
- 2019-12-30 CN CN201911398370.4A patent/CN113127258A/en active Pending
-
2020
- 2020-08-28 WO PCT/CN2020/111987 patent/WO2021135326A1/en active Application Filing
Cited By (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2023151547A1 (en) * | 2022-02-14 | 2023-08-17 | 华为技术有限公司 | Data processing system and method, and device |
| CN115562911A (en) * | 2022-12-07 | 2023-01-03 | 中科方德软件有限公司 | Virtual machine data backup method, device, system, electronic equipment and storage medium |
| CN115562911B (en) * | 2022-12-07 | 2023-04-25 | 中科方德软件有限公司 | Virtual machine data backup method, device, system, electronic equipment and storage medium |
Also Published As
| Publication number | Publication date |
|---|---|
| WO2021135326A1 (en) | 2021-07-08 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| JP6928055B2 (en) | Dynamic configuration of data volume | |
| US11068361B2 (en) | Cluster file system support for extended network service addresses | |
| JP6005706B2 (en) | Virtual machine morphing for heterogeneous mobile environments | |
| US10067940B2 (en) | Enhanced storage quota management for cloud computing systems | |
| EP3469478B1 (en) | Server computer management system for supporting highly available virtual desktops of multiple different tenants | |
| US10936553B2 (en) | Intelligent file system with transparent storage tiering | |
| US9417870B2 (en) | Managing user access to alternative versions of a particular function of a software product from within a current version of the software product | |
| US10210054B1 (en) | Backup optimization in hybrid storage environment | |
| US9614931B2 (en) | Identifying a resource set require for a requested application and launching the resource set in a container for execution in a host operating system | |
| US20150186064A1 (en) | Managing operational parameters for electronic resources | |
| CN111488241A (en) | Method and system for realizing agent-free backup and recovery operation on container arrangement platform | |
| US11924117B2 (en) | Automated local scaling of compute instances | |
| Collier et al. | Microsoft azure essentials-fundamentals of azure | |
| CN106331075B (en) | Method for storing file, metadata server and manager | |
| US11379290B2 (en) | Prioritizing and parallelizing the capture of data for debugging computer programs | |
| US20160371102A1 (en) | System and method for supporting execution of application based on multi-platform using virtual platform service | |
| JP2013524343A (en) | Manage certification request rates for shared resources | |
| CN111061432A (en) | Service migration method, device, equipment and readable storage medium | |
| WO2021135326A1 (en) | Data backup method, apparatus and device, and medium | |
| US10884818B2 (en) | Increasing processing capacity of virtual machines | |
| US10884845B2 (en) | Increasing processing capacity of processor cores during initial program load processing | |
| CN113296891B (en) | Platform-based multi-scene knowledge graph processing method and device | |
| US20220206836A1 (en) | Method and Apparatus for Processing Virtual Machine Migration, Method and Apparatus for Generating Virtual Machine Migration Strategy, Device and Storage Medium | |
| Shahan | Microsoft Azure Essentials-Fundamentals of Azure | |
| US11263053B2 (en) | Tag assisted cloud resource identification for onboarding and application blueprint construction |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| TA01 | Transfer of patent application right |
Effective date of registration: 20220215 Address after: 550025 Huawei cloud data center, jiaoxinggong Road, Qianzhong Avenue, Gui'an New District, Guiyang City, Guizhou Province Applicant after: Huawei Cloud Computing Technology Co.,Ltd. Address before: 518129 Bantian HUAWEI headquarters office building, Longgang District, Guangdong, Shenzhen Applicant before: HUAWEI TECHNOLOGIES Co.,Ltd. |
|
| TA01 | Transfer of patent application right |