WO2024001279A1 - 一种备份方法及装置 - Google Patents

一种备份方法及装置 Download PDF

Info

Publication number
WO2024001279A1
WO2024001279A1 PCT/CN2023/080062 CN2023080062W WO2024001279A1 WO 2024001279 A1 WO2024001279 A1 WO 2024001279A1 CN 2023080062 W CN2023080062 W CN 2023080062W WO 2024001279 A1 WO2024001279 A1 WO 2024001279A1
Authority
WO
WIPO (PCT)
Prior art keywords
storage
backup
data
information
backed
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.)
Ceased
Application number
PCT/CN2023/080062
Other languages
English (en)
French (fr)
Inventor
刘继朋
崔恒基
何晋斌
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Huawei Technologies Co Ltd
Original Assignee
Huawei Technologies Co Ltd
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 Huawei Technologies Co Ltd filed Critical Huawei Technologies Co Ltd
Priority to EP23829470.6A priority Critical patent/EP4528517A4/en
Publication of WO2024001279A1 publication Critical patent/WO2024001279A1/zh
Priority to US19/003,982 priority patent/US20250138949A1/en
Anticipated expiration legal-status Critical
Ceased legal-status Critical Current

Links

Classifications

    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; 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 operations
    • G06F11/1446—Point-in-time backing up or restoration of persistent data
    • G06F11/1458—Management of the backup or restore process
    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; 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 operations
    • 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 OR CALCULATING; 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 operations
    • G06F11/1402—Saving, restoring, recovering or retrying
    • G06F11/1415—Saving, restoring, recovering or retrying at system level
    • G06F11/1435—Saving, restoring, recovering or retrying at system level using file system or storage system metadata
    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; 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 operations
    • G06F11/1446—Point-in-time backing up or restoration of persistent data
    • G06F11/1448—Management of the data involved in backup or backup restore
    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; 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 operations
    • G06F11/1446—Point-in-time backing up or restoration of persistent data
    • G06F11/1458—Management of the backup or restore process
    • G06F11/1464—Management of the backup or restore process for networked environments
    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; 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 operations
    • G06F11/1446—Point-in-time backing up or restoration of persistent data
    • G06F11/1458—Management of the backup or restore process
    • G06F11/1469—Backup restoration techniques
    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; 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
    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; 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/0629—Configuration or reconfiguration of storage systems
    • G06F3/0631—Configuration or reconfiguration of storage systems by allocating resources to storage systems
    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; 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/0638—Organizing or formatting or addressing of data
    • G06F3/064—Management of blocks
    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; 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/0638—Organizing or formatting or addressing of data
    • G06F3/0644—Management of space entities, e.g. partitions, extents, pools
    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; 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 application relates to the field of computers, and in particular, to a backup method and device.
  • backup storage resources (storage, that is, backup media) are virtualized into a storage architecture as shown in Figure 1, which specifically includes storage unit (storage unit, SU), storage pool (storage pool, SP), and repository (Repository). Three floors. Among them, the storage unit is associated with the real backup medium and is used to store data. The capacity of the storage unit can be configured according to the user's needs.
  • the storage pool virtualizes the storage resources of the storage unit so that users no longer care about physical storage.
  • the repository provides logical isolation between protection sets, and a backup copy is generated for each backup of the backup target (disk, virtual machine, etc.).
  • a set of storage (such as a cluster) is usually configured as a storage unit as a storage pool, and a backup copy of a backup target is stored in the storage pool.
  • a storage pool capacity is limited and a new storage unit is expanded, how to perform incremental backup in the storage pool needs to be solved urgently.
  • This application provides a method and device for backing up and configuring a storage pool, so as to realize the storage of backup copies across storage units, thereby achieving incremental backup after the storage pool is expanded.
  • a backup method may include: obtaining backup task information including information of data to be backed up and a backup storage identification; obtaining list information of the first storage pool indicated by the backup storage identification, and the list information is used to indicate Information about the storage units in the first storage pool; the first storage pool includes multiple storage units, and the multiple storage units are located in at least two storage clusters; according to the information about the data to be backed up, read the data to be backed up from the production storage; according to the first The list information of the storage pool stores the data to be backed up in one or more storage units in the first storage pool.
  • This application provides a backup method and device.
  • the storage pool By configuring the storage pool with list information indicating the information of the storage units in the storage pool, multiple storage units included in a storage pool are configured to be located in multiple storage clusters.
  • each data block in the backup copy can be stored in multiple storage units according to actual needs, and the data to be backed up and the unmodified data can be stored in different storage clusters; since each storage unit has a unique identifier, according to The list information of the storage pool can accurately realize data recovery. Therefore, the backup method of this application realizes effective incremental backup after capacity expansion.
  • the new storage cluster can be added to the storage pool as a storage unit. You only need to update the list information of the storage pool to add the information of the new storage unit, and the expansion of the storage pool is completed, so that A storage pool spans multiple storages. Although backup copies can be stored across storage units, multiple backup copies are still in the same storage pool.
  • the backup objects are associated with the repository, and the repository is associated with the storage pool. Users do not need to be aware of the new hardware storage. Therefore, After the storage pool is expanded, there is no need to perform data migration, and incremental backups can still be performed to achieve effective expansion.
  • the backup method provided by this application may also include: generating metadata of the data to be backed up, where the metadata of the data to be backed up includes identification of one or more storage units that store the data to be backed up, so as to facilitate Restore the data to be backed up based on the metadata of the data to be backed up.
  • the backup task information may also include storage location information of the metadata of the previous copy, which is the previous backup copy of the backup object to which the data to be backed up belongs.
  • the metadata of the data to be backed up also includes the storage location information of the data in the previous copy that has not been modified by the data to be backed up.
  • the storage unit that stores the data to be backed up and the storage unit that stores data that has not been modified by the data to be backed up are located in different storage clusters. To achieve incremental backup across storage units, effective incremental backup can be achieved when the storage pool is expanded.
  • the data to be backed up belongs to the first backup file
  • the backup task information also includes information about data in the first backup file that has not been modified by the data to be backed up, so as to achieve full backup.
  • the backup method provided by this application may further include: storing metadata of the data to be backed up in a first storage unit; and reporting the information of the first storage unit.
  • the metadata of the data to be backed up will be regarded as the metadata of the pre-order copy to achieve effective incremental backup.
  • a storage unit that stores copy metadata of different backup targets can be pre-configured, so that the metadata of the backup copy can be quickly obtained when performing backup or recovery.
  • the backup storage identification includes: an identification of the first storage pool, or an identification of a storage repository corresponding to the first storage pool.
  • the method provided by this application may also include: obtaining configuration task information.
  • the configuration task is used to instruct the second storage unit to be configured as a resource of the second storage pool;
  • the second storage pool includes multiple storage units.
  • the second storage pool includes multiple storage units located in at least two storage clusters; the information of the second storage unit is recorded in the list information of the second storage pool.
  • the list information of the storage pool is updated in real time to ensure the accuracy of the backup process.
  • the method provided by this application may also include: obtaining recovery task information, which includes information about the data to be restored; obtaining list information of the third storage pool that stores the data to be restored; Information about the data, obtain the metadata of the data to be restored.
  • the metadata of the data to be restored includes the storage location information of the data to be restored; read the data to be restored according to the list information of the third storage pool and the storage location information of the data to be restored.
  • the backup system includes a backup control device, a backup storage device, and a production storage device.
  • the backup method may include: the backup control device sending backup task information to the backup storage device, where the backup task information includes information about data to be backed up and a backup storage identification.
  • the backup storage device obtains the list information of the first storage pool indicated by the backup storage identification.
  • the list information is used to indicate the information of the storage units in the first storage pool; the first storage pool includes multiple storage units, and the multiple storage units are located in at least two Storage cluster; the backup storage device reads the data to be backed up from the production storage device according to the information of the data to be backed up; the backup storage device stores the data to be backed up in one or more storage units in the first storage pool according to the list information.
  • a third aspect provides a backup device, which may include: a first acquisition unit, a second acquisition unit, a reading unit, and a backup unit. in:
  • the first acquisition unit is used to acquire backup task information.
  • the backup task information includes information about the data to be backed up and the backup storage identification.
  • the second obtaining unit is used to obtain the list information of the first storage pool indicated by the backup storage identification, and the list information is used to indicate the information of the storage unit in the first storage pool.
  • the first storage pool includes a plurality of storage units, and the plurality of storage units are located in at least two storage clusters.
  • a reading unit configured to read the data to be backed up from the production storage according to the information of the data to be backed up.
  • the backup unit is configured to store the data to be backed up in one or more storage units in the first storage pool according to the list information of the first storage pool.
  • the backup device may further include: a first processing unit, configured to generate metadata of the data to be backed up, where the metadata of the data to be backed up includes one or more storage units that store the data to be backed up. logo.
  • the backup task information may also include storage location information of the metadata of the previous copy, which is the previous backup copy of the backup object to which the data to be backed up belongs.
  • the metadata of the data to be backed up also includes the storage location information of the data in the previous copy that has not been modified by the data to be backed up; the storage unit that stores the data to be backed up and the storage unit that stores the data that has not been modified by the data to be backed up. Located in different storage clusters.
  • the data to be backed up belongs to the first backup file
  • the backup task information also includes information about data in the first backup file that has not been modified by the data to be backed up.
  • the backup unit is also used to store metadata of the data to be backed up in the first storage unit.
  • the backup device may also include a reporting unit configured to report information in the first storage unit.
  • the backup storage identification includes: an identification of the first storage pool, or an identification of a storage repository corresponding to the first storage pool.
  • the first obtaining unit is further configured to obtain configuration task information
  • the configuration task is used to instruct the second storage unit to be configured as a resource of the second storage pool.
  • the second storage pool includes a plurality of storage units, and the plurality of storage units included in the second storage pool are located in at least two storage clusters.
  • the backup device may further include a second processing unit configured to record the information of the second storage unit in the list information of the second storage pool.
  • the first acquisition unit is further configured to: acquire recovery task information, where the recovery task information includes information about data to be recovered.
  • the second obtaining unit is also used to obtain list information of a third storage pool that stores data to be restored.
  • the backup device also includes a third acquisition unit, configured to acquire metadata of the data to be restored based on the information of the data to be restored.
  • the metadata of the data to be restored includes the storage location information of the data to be restored; according to the list information of the third storage pool , and the storage location information of the data to be restored, read the data to be restored.
  • the fourth aspect provides a backup system, which includes a backup control device, a backup storage device, and a production storage device. in:
  • the backup control device is used to: send backup task information to the backup storage device, where the backup task information includes information about the data to be backed up and the backup storage identification.
  • the backup storage device is used to: obtain list information of the first storage pool indicated by the backup storage identifier, where the list information is used to indicate information about the storage units in the first storage pool.
  • the first storage pool includes a plurality of storage units, and the plurality of storage units are located in at least two storage clusters. According to the information of the data to be backed up, the data to be backed up is read from the production storage device; according to the list information, the data to be backed up is stored in one or more storage units in the first storage pool.
  • the present application provides a computing device that can implement the functions in the method examples described in the first aspect.
  • the functions can be implemented by hardware, or can be implemented by hardware executing corresponding software.
  • the hardware or software includes one or more modules corresponding to the above functions.
  • the computing device may exist in the form of a chip product.
  • the computing device may include a processor and a transmission interface.
  • the transmission interface is used to receive and send data.
  • the processor is configured to invoke program instructions stored in the memory, so that the computing device performs the functions in the method examples described in the first aspect above.
  • a computer-readable storage medium including instructions that, when run on a computer, cause the computer to execute the backup method described in any of the above aspects or any possible implementation manner.
  • a seventh aspect provides a computer program product that, when run on a computer, causes the computer to execute the backup method described in any of the above aspects or any possible implementation manner.
  • a chip system in an eighth aspect, includes a processor and may also include a memory for implementing the functions in the above method.
  • the chip system can be composed of chips or include chips and other discrete devices.
  • Figure 1 is a schematic diagram of backup storage resources
  • Figure 2 is a schematic architectural diagram of a storage backup system provided by an embodiment of the present application.
  • Figure 3 is a schematic structural diagram of a computing device provided by an embodiment of the present application.
  • Figure 4 is a schematic flowchart of a method for configuring a resource pool provided by an embodiment of the present application
  • Figure 5 is a schematic flowchart of another method for configuring a resource pool provided by an embodiment of the present application.
  • Figure 6 is a schematic flow chart of a backup method provided by an embodiment of the present application.
  • Figure 7 is a schematic flow chart of a data recovery method provided by an embodiment of the present application.
  • Figure 8 is a schematic structural diagram of a backup device provided by an embodiment of the present application.
  • Figure 9 is a schematic structural diagram of another backup device provided by an embodiment of the present application.
  • Figure 10 is a schematic structural diagram of another computing device provided by an embodiment of the present application.
  • words such as “exemplary” or “for example” are used to represent examples, illustrations or explanations. Any embodiment or design described as “exemplary” or “such as” in the embodiments of the present application is not to be construed as preferred or advantageous over other embodiments or designs. Rather, the use of words such as “exemplary” or “such as” is intended to present related concepts in a concrete manner that is easier to understand.
  • A/B can mean A or B; “and/or” in this application only means It is an association relationship that describes related objects. It means that there can be three relationships.
  • a and/or B can mean: A exists alone, A and B exist simultaneously, and B exists alone. Among them, A and B Can be singular or plural.
  • plural means two or more than two. “At least one of the following” or similar expressions thereof refers to any combination of these items, including any combination of a single item (items) or a plurality of items (items).
  • At least one of a, b, or c can mean: a, b, c, a-b, a-c, b-c, or a-b-c, where a, b, c can be single or multiple .
  • At least one can also be described as one or more, and the plurality can be two, three, four or more, which is not limited by this application.
  • the backup object refers to the source object in the backup operation, that is, the backup operation is to back up the data in the backup object.
  • the backup object can be a disk, virtual machine, or other form of device with storage capabilities.
  • a backup copy refers to the result of a backup operation on a backup object.
  • Backup copies include metadata and backup data.
  • the backup data is the backup of the data in the backup object.
  • Metadata is used to record information about backup objects. Metadata can also be used to record where the data in the backup data is stored in the storage unit.
  • the metadata of a backup copy can As shown in Table 1, this metadata records copy information, disk information, and data block information. Among them, the copy information is used to record the identification of the backup copy, the disk information is used to record the disk identification of the data block storage, and the data block information is used to record the identification of the data block.
  • a backup chain refers to the collection of all backup copies of a backup object.
  • the data structure of the backup chain of a backup object can be shown in Table 2.
  • the backup object corresponds to repository 1, that is, the backup copies of the backup object are all stored in the resources of repository 1.
  • a storage cluster also known as storage, refers to the physical hardware devices, such as disks or other forms, used to store data.
  • a storage unit refers to a collection of resources used for storage that are virtually composed of stored resources based on user needs.
  • a storage unit can be composed of one or more storages, and a storage unit can also be a part of the storage resources.
  • Storage pool is a concept derived from further virtualization of storage resources based on storage units.
  • One or more storage units constitute a storage pool.
  • Repository a collection of resources used to store all backup copies of a backup object.
  • the repository provides logical isolation between backup objects.
  • the resources of a repository can include one or more storage pools, and the repository corresponds to the storage pool to which the resources it includes belong.
  • This application provides a backup method and device.
  • the storage pool By configuring the storage pool with list information indicating the information of the storage units in the storage pool, multiple storage units included in a storage pool are configured to be located in multiple storage clusters.
  • each data block in the backup copy can be stored in multiple storage units according to actual needs, and the data to be backed up and the unmodified data can be stored in different storage clusters; since each storage unit has a unique identifier, according to The list information of the storage pool can accurately realize data recovery. Therefore, the backup method of this application realizes effective incremental backup after capacity expansion.
  • the new storage cluster can be added to the storage pool as a storage unit. You only need to update the list information of the storage pool to add the information of the new storage unit, and the expansion of the storage pool is completed, so that A storage pool spans multiple storages. Although backup copies can be stored across storage units, multiple backup copies are still in the same storage pool.
  • the backup objects are associated with the repository, and the repository is associated with the storage pool. Users do not need to be aware of the new hardware storage. Therefore, it is necessary to expand the storage pool. Afterwards, there is no need to perform data migration, and incremental backup can still be performed to achieve effective expansion.
  • the storage backup system 20 may include a backup control management device 201 , a backup storage management device 202 , a storage medium 203 and a production storage management device 204 .
  • the production storage management device 204 is used to manage the data of the backup object.
  • the storage medium 203 is actual physical storage and is used to provide storage resources.
  • the storage resources provided by it can be virtualized into storage units, storage pools, and storage libraries.
  • the backup control management device 201 is the control center of the storage backup system 20 .
  • the backup control management device 201 can interact with the user to obtain backup requirements or others.
  • the backup control management device 201 can also issue tasks to the backup storage management device 202 to perform storage resource configuration, data backup, data recovery, etc.
  • the backup storage management device 202 is the executor of backup operations in the storage backup system 20 .
  • the backup storage management device 202 can execute the tasks issued by the backup control management device 201, configure the resources in the storage medium 203, or back up the data provided by the production storage management device 204 and store the backup copy in the storage medium 203. , or restore the backup copy from the storage medium 203 to the production storage management device 204.
  • backup control management device 201 may be computing devices (such as servers) or other forms, and the embodiments of this application are not limited to their specific product forms.
  • Figure 2 is only used as an example to illustrate the architecture of the storage backup system, and does not limit the application scenarios of the solution of this application.
  • the architectural content of the storage backup system can be configured according to actual needs, which is not limited in the embodiments of the present application.
  • the storage backup system 20 may be a storage or cloud storage backup system, or the storage backup system 20 may be a backup system in other scenarios involving backup.
  • the embodiments of the present application are not limited to application scenarios.
  • embodiments of the present application provide a computing device for executing the solution provided by the present application.
  • the computing device may be the backup storage management device 202 illustrated in FIG. 2 .
  • FIG. 3 illustrates a structural diagram of a computing device 30 provided by an embodiment of the present application.
  • computing device 30 may include a processor 301 , a memory 302 , and a transceiver 303 .
  • the memory 302 may be a volatile memory (volatile memory), such as a random-access memory (RAM); or a non-volatile memory (non-volatile memory), such as a read-only memory (read-only memory, ROM), flash memory (flash memory), hard disk (harddisk drive, HDD) or solid-state drive (solid-state drive, SSD); or a combination of the above types of memory, used to store application code that can implement the method of the present application , configuration files, data information or other content.
  • the memory 302 may also be deployed in other devices independent of the computing device 30 .
  • the transceiver 303 is used for information interaction between the computing device 30 and other devices.
  • Processor 301 may be the control center of computing device 30 .
  • the processor 301 may be a central processing unit (CPU), an application specific integrated circuit (ASIC), or may be configured to implement one or more integrated circuits of the embodiments of the present application.
  • Circuits such as: one or more microprocessors (digital signal processor, DSP), or one or more field programmable gate arrays (field programmable gate array, FPGA).
  • the processor 301 can perform the following functions by running or executing software programs and/or modules stored in the memory 302:
  • the backup task information which includes the information of the data to be backed up and the backup storage identifier; obtain the backup The list information of the first storage pool indicated by the storage identifier, the list information is used to indicate the information of the storage units in the first storage pool; the first storage pool includes multiple storage units, and the multiple storage units are located in at least two storage clusters; according to For information about the data to be backed up, the data to be backed up is read from the production storage; and the data to be backed up is stored in one or more storage units in the first storage pool according to the list information of the first storage pool.
  • a unique identifier is configured for the storage unit, and list information is configured for the storage pool.
  • the list information of a storage pool is used to indicate the information of the storage unit in the storage pool.
  • a stored list information may include the identification and access path of the storage unit in the storage pool.
  • the identification of the storage unit/storage pool/repository is used to uniquely indicate the storage unit/storage pool/repository and is not repeated in the entire backup system.
  • the identification of the storage unit may be in an index or other form.
  • the access path of the storage unit is used to access the storage unit in the storage pool.
  • the embodiment of the present application does not limit the specific content of the access path of the storage unit.
  • the access path of the storage unit may be the mounting path of the storage unit in the backup server.
  • the list information of a storage pool may also include whether the storage units included in the storage pool are writable.
  • the list information of the storage pool can be stored in a dedicated storage unit in the storage pool.
  • the list information of the storage pool can be stored in each storage unit in the storage pool.
  • the list information recorded in SU_0 and SU_1 is the list information of storage pool SP_0.
  • the list information includes the identifiers and access paths of all storage units (SU_0 and SU_1) in storage pool SP_0.
  • the list information recorded in SU_0 and SU_1 is shown in Table 3 below.
  • SU_2 belongs to storage pool SP_1, and the list information recorded in SU_2 is the identification and access path of all storage units (SU_2) in storage pool SP_1.
  • the list information recorded in SU_2 is shown in Table 4 below.
  • the new storage cluster can be added to the storage pool as a storage unit. You only need to update the list information of the storage pool to add the information of the new storage unit, and the expansion of the storage pool is completed, so that A storage pool spans multiple storages. Although backup copies can be stored across storage units, multiple backup copies are still in the same storage pool.
  • the backup objects are associated with the repository, and the repository is associated with the storage pool. Users do not need to be aware of the new hardware storage. Therefore, it is necessary to expand the storage pool. Afterwards, there is no need to perform data migration, and incremental backup can still be performed to achieve effective expansion.
  • the list information of the storage pool includes the information of the storage units in the storage pool, when a new storage unit is added to the storage pool, the list information of the storage pool needs to be updated to add the information of the newly added storage unit. information.
  • the storage unit SU_1 is added to SP_1.
  • SU_0 belongs to storage pool SP_0.
  • the storage units included in storage pool SP_0 have not changed, and the list information of storage pool SP_0 remains unchanged.
  • Storage unit SU_1 is added to SP_1, and the list information of SP_1 needs to be updated to include the information of SU_1 and SU_2.
  • the list information recorded in SU_1 includes the list information of SP_0 and the list information of SP_1, and the list information recorded in SU_2 is the updated list information of SP_1.
  • the list information recorded in SU_1 will be changed as shown in Table 5.
  • the list information recorded in SU_2 will be changed as shown in Table 6.
  • Tables 3 to 6 are only illustrative descriptions of the list information of the storage unit in the form of examples, and do not specifically limit the content and form of the list information.
  • embodiments of the present application provide a backup method, which can be executed by a backup storage management device.
  • the backup storage management device is used to perform storage backup, which can be performed by the backup storage management device 202 illustrated in FIG. 2 .
  • This backup method can be used in combination with the aforementioned method of configuring a resource pool, or can be used alone, which is not limited in the embodiments of the present application.
  • the backup process is the same every time the backup task is executed.
  • the following embodiments of the present application take a backup process as an example to illustrate, and the rest will not be described one by one.
  • the embodiment of the present application provides a backup method that may include:
  • the backup storage management device obtains backup task information.
  • the backup task information includes information about the data to be backed up and the backup storage identification.
  • the data to be backed up is the modified data in the first backup object to which the data to be backed up is compared with the previous backup, the data to be backed up is.
  • the information of the data to be backed up is used to indicate the data to be backed up.
  • the information about the data to be backed up may be the identification of the first backup object.
  • the backup task information is used to instruct the data to be backed up to be stored in the storage pool indicated by the backup storage identifier.
  • the backup storage identifier is used to indicate the first storage pool
  • the first storage pool is used to store the backup copy of the first backup object to which the data to be backed up belongs.
  • the backup storage identification may be an identification of the first storage pool, or the backup storage identification may be an identification of a storage repository that stores a backup copy of the first backup object.
  • the backup storage identifier may be the identifier of the first backup object.
  • a storage pool is pre-configured to store backup copies of each backup object.
  • the backup storage management device obtains the backup task information in S401, it can determine the backup copy of the first backup object to be stored according to the identification of the first backup object.
  • the first storage pool is pre-configured to store backup copies of each backup object.
  • a repository for storing backup copies of each backup object is pre-configured.
  • the backup storage management device obtains the backup task information in S401, it can determine the backup copy of the first backup object to be stored according to the identification of the first backup object. storage pool, and determine the storage pool corresponding to the storage pool as the first storage pool.
  • the backup task may also include the storage location information of the metadata of the previous copy, which is the previous backup copy of the first backup object to which the data to be backed up belongs.
  • the storage location information may be the identification of the storage unit.
  • the data to be backed up belongs to the first backup file
  • the backup task information also includes information about the data in the first backup file that has not been modified by the data to be backed up, so as to achieve full backup of the first backup file.
  • the backup storage management device in S401 can receive the backup task information from the backup control management device, or the backup storage management device in S401 can receive the backup task input by the user.
  • the embodiment of the present application does not limit the source of the backup task information.
  • the backup storage management device reads the data to be backed up from the production storage according to the information of the data to be backed up.
  • the backup storage management device reads the data to be backed up based on the information of the data to be backed up through interaction with the production storage.
  • the backup storage management device stores the data to be backed up in one or more storage units in the first storage pool according to the list information of the first storage pool.
  • the list information of the first storage pool records the information of the storage units in the first storage pool.
  • the first storage pool can be used to store the data to be backed up. one or more storage units, and then store the data to be backed up in one or more storage units in the first storage pool.
  • the backup storage management device may store the data to be backed up in one or more writable storage units in the first storage pool according to the list information of the first storage pool.
  • the backup storage management device first determines the writable storage units in the first storage pool.
  • the backup storage management device records the writable storage units in the first storage pool, and in S403, the writable storage units in the first storage pool can be determined based on the recorded content.
  • the backup control management device records the writable storage units in the first storage pool.
  • the backup storage management device interacts with the backup control management device to determine the writable storage units in the first storage pool. Write storage unit.
  • the list information of the first storage pool includes whether the storage unit in the first storage unit is writable.
  • the backup storage management device may determine the writable storage unit in the first storage pool from the list information of the first storage pool. The storage location of the list information of the first storage pool is known to the backup storage management device.
  • the list information of the first storage pool is stored in each storage unit in the first storage pool.
  • the backup storage management device can obtain the list information of the first storage pool from any storage unit in the first storage pool. , and then determine the writable storage units in the first storage pool.
  • the backup storage management device may determine one or more storage units in the first storage pool that store the data to be backed up according to the backup policy.
  • the backup copy when performing storage backup, can be divided into data blocks for storage.
  • the size of the divided data blocks can be configured according to actual needs, which is not limited in the embodiments of the present application.
  • storing the data blocks in the first backup copy in several storage units can be set according to business requirements or functions of the backup system, which is not limited in the embodiments of the present application.
  • a data block can be stored in a storage unit.
  • the backup strategy may include selecting a storage unit with the largest remaining capacity. For example, when executing S403, each data block in the data to be backed up can be traversed, and the storage unit with the largest remaining capacity is selected for each data block for storage.
  • the backup strategy may include selecting a storage unit with the fastest read and write speed. For example, when executing S403, each data block in the data to be backed up can be traversed, and the storage unit with the fastest read and write speed can be selected for each data block for storage.
  • the capacity and read and write speed of the storage unit can be used as attribute parameters of the storage unit, which can be recorded and used by the backup storage management device, or recorded by the backup control management device, and the backup storage management device obtains them through interaction.
  • the storage unit There are no restrictions on how to obtain the capacity and read and write speed.
  • the backup storage management device stores the data to be backed up in one or more storage units determined in the first storage pool according to the access path of the storage unit indicated by the list information according to the list information of the first storage pool.
  • This application provides a backup method.
  • the storage pool By configuring the storage pool with list information indicating the information of the storage units in the storage pool, multiple storage units included in a storage pool are configured to be located in multiple storage clusters.
  • the backup Each data block in the copy can be stored in multiple storage units according to actual needs. Since multiple storage units in a storage pool come from at least two storage clusters, it is possible to combine the data to be backed up with the unmodified data. It can be stored in different storage clusters; since each storage unit has a unique identifier, data recovery can be accurately achieved based on the list information of the storage pool. Therefore, the backup method of this application realizes effective incremental backup after capacity expansion.
  • the new storage cluster can be added to the storage pool as a storage unit. You only need to update the list information of the storage pool to add the information of the new storage unit, and the expansion of the storage pool is completed, so that A storage pool spans multiple storages. Although backup copies can be stored across storage units, multiple backup copies are still in the same storage pool.
  • the backup objects are associated with the repository, and the repository is associated with the storage pool. Users do not need to be aware of the new hardware storage. Therefore, it is necessary to expand the storage pool. Afterwards, there is no need to perform data migration, and incremental backup can still be performed to achieve effective expansion.
  • the backup method provided by the embodiment of the present application may also include S404.
  • the backup storage management device generates metadata of the data to be backed up.
  • the metadata of the data to be backed up includes identifiers of one or more storage units that store the data to be backed up.
  • the metadata of a backup copy records the storage location information of each data block in the backup copy during this backup operation of the backup object.
  • the storage location information may be the identification of the storage unit.
  • the metadata of the data to be backed up also includes the storage location information of the data in the previous copy that has not been modified by the data to be backed up.
  • the storage unit that stores the data to be backed up and the storage unit that stores the data that has not been modified by the data to be backed up may be located in different storage clusters.
  • incremental backup is performed in S403. Since the storage location information of the data that has not been modified by the data to be backed up needs to be borrowed from the storage location information of the data that has not been modified by the data to be backed up in the metadata of the previous copy, S404.
  • the backup storage management device When generating the metadata of the data to be backed up, the backup storage management device first obtains the storage location information of the metadata of the previous copy to obtain the metadata of the previous copy, and then generates the metadata of the data to be backed up.
  • the backup task information obtained in S401 also includes the storage location information of the metadata of the previous copy.
  • the backup storage management device can obtain the storage location information of the metadata of the previous copy from the backup task information. Then, the metadata of the pre-order copy is obtained based on the storage location information, and it is parsed to obtain the storage location information of the data in the pre-order copy that has not been modified by the data to be backed up.
  • storage units that store copy metadata of different backup objects are pre-configured.
  • the backup storage management device obtains the previous data from the pre-configured storage unit that stores copy metadata of the first backup object.
  • the metadata of the pre-order copy is parsed to obtain the storage location information of the data in the pre-order copy that has not been modified by the data to be backed up.
  • the first backup object can be divided into three data blocks, which are recorded as data block 1, data block 2 and data block 3 respectively.
  • all backup copies were stored in storage unit a in the first storage pool, and the metadata is shown in Table 7.
  • data block 2 is modified during this backup.
  • data block 2 is stored in storage unit b.
  • the metadata can be shown in icon 8. .
  • Table 7 and Table 8 only illustrate metadata by way of examples and do not constitute specific limitations on the form and content of metadata.
  • the current backup metadata of the first backup copy may be as shown in Table 9.
  • the metadata shown in Table 9 adds a storage unit identifier to facilitate data recovery when the data blocks in the backup copy are distributed and stored in different storage units.
  • the backup chain of the first backup object may be as shown in Table 10.
  • the backup storage management device stores the metadata of the data to be backed up in the first storage unit.
  • storage units that store copy metadata of different backup objects are pre-configured, and the first storage unit is a pre-configured storage unit that stores copy metadata of the first backup object.
  • the first storage unit may be any storage unit in the first storage pool, and the embodiment of the present application does not limit the method of selecting the first storage unit.
  • the method provided by the embodiment of the present application further includes: reporting the identification of the first storage unit. Therefore, the backup task information for the next backup operation on the first backup object carries the identification of the first storage unit.
  • the above-mentioned data to be backed up belongs to the first backup file, and the backup task information also includes information about the data in the first backup file that has not been modified by the data to be backed up, so as to achieve full backup of the first backup file.
  • the data that has not been modified by the data to be backed up is also read from the production storage according to the information of the data that has not been modified by the data to be backed up; in S403, based on the list information of the first storage pool, the data that has not been modified by the data to be backed up is read.
  • the data is stored in one or more storage units in the first storage pool, and the storage location information is recorded in the metadata.
  • the backup method provided by the embodiment of the present application may also include a process of configuring a resource pool, which process may be shown in Figure 6 .
  • the method for configuring a storage pool may include:
  • the backup storage management device obtains configuration task information.
  • the configuration task information is used to indicate configuring the second storage unit as a resource of the second storage pool.
  • the second storage pool includes a plurality of storage units, and the plurality of storage units included in the second storage pool are located in at least two storage clusters.
  • the backup storage management device may receive the configuration task information from the backup control management device, or in S601, the backup storage management device may receive the configuration task information input by the user.
  • the embodiment of this application does not limit the source of configuration task information.
  • S601 when building a backup storage system, S601 can be executed to configure the storage pool of the system.
  • the second storage pool is a newly configured storage pool.
  • S601 when expanding the capacity of the second storage pool, S601 can be executed to configure the storage pool of the system.
  • the resources of the second storage unit may be resources in the storage newly added during capacity expansion, and the storage unit has been configured in the second storage pool.
  • the resources of the second storage unit and the configured storage unit in the second storage pool belong to the same storage cluster, or the resources of the second storage unit and the configured storage unit in the second storage pool belong to different storages. cluster.
  • the backup storage management device records the information of the second storage unit in the list information of the second storage pool.
  • the backup storage management device may obtain the identity of the second storage unit and the access path of the second storage unit in the second storage pool, and then record the identity of the second storage unit in the list information of the second storage pool. and access path.
  • the configuration task information obtained in S601 includes: the access path of the second storage unit in the second storage pool.
  • the backup storage management device in S602 will update the list information of the second storage pool (the list that records the information of the second storage unit). information) is stored in the second storage unit, and the list information stored in the storage unit other than the second storage unit in the second storage pool is updated to the updated list information of the second storage pool.
  • a possible implementation manner is to update the list information stored in a storage unit other than the second storage unit in the second storage pool to the updated list information of the second storage pool, which can be implemented as: in the second storage pool To the list information stored in a storage unit other than the second storage unit, the information of the second storage unit is added.
  • the backup storage management device can also record the mapping relationship between the storage unit and the storage pool to record the mapping relationship between the storage library, the storage pool and the storage unit, and achieve the purpose of recording multi-layer resource mapping.
  • the backup method provided by the embodiment of the present application may also include a data recovery process, which process may be shown in Figure 7 .
  • This data recovery process can be used in combination with the aforementioned backup method and/or the method of configuring a resource pool, or can be used alone, which is not limited in the embodiments of the present application.
  • the data recovery process can be performed by the backup storage management device.
  • the backup storage management device is used to perform storage backup recovery, and may be performed by the backup storage management device 202 illustrated in FIG. 2 .
  • the data recovery process provided by the embodiment of this application may include:
  • the backup storage management device obtains recovery task information.
  • the recovery task includes information about the data to be recovered.
  • the information of the data to be restored is used to indicate the latest backup copy of the second backup object.
  • the recovery task information is used to instruct the data to be recovered from the third storage pool.
  • the third storage pool is used to store the backup copy of the second backup object.
  • the information of the data to be restored may be an identifier of the second backup object, and the second backup copy is the latest backup copy of the second backup object.
  • the information of the data to be restored may be the identifier of the third storage pool, or the information of the data to be restored may be the identifier of the storage repository corresponding to the third storage pool.
  • the third storage pool can be determined based on the information of the data to be restored.
  • the backup storage management device may receive the recovery task information from the backup control management device, or in S701, the backup storage management device may receive the recovery task information input by the user.
  • the embodiment of the present application does not limit the source of the recovery task information.
  • the backup storage management device obtains the list information of the third storage pool.
  • the backup storage management device can obtain the list information of the third storage pool from any storage unit of the third storage pool.
  • the backup storage management device may obtain the list information of the third storage pool from a storage unit of the third storage pool that is dedicated to storing list information.
  • the backup storage management device obtains the metadata of the data to be restored based on the information of the data to be restored.
  • the metadata of the data to be restored includes the storage location information of the data to be restored.
  • the storage locations of metadata of different backup objects are pre-configured, and the metadata of the data to be restored can be obtained based on the storage location of the metadata of the second backup object indicated by the information about the restored data.
  • the recovery task information includes storage location information of the metadata of the data to be recovered, and based on the storage location information, the metadata of the data to be recovered can be obtained.
  • the storage location information described in this application may be the identification of the storage unit.
  • the backup storage management device reads the data to be restored based on the list information of the third storage pool and the storage location information of the data to be restored.
  • the list information of the third storage pool indicates the information of the storage units in the third storage pool. According to the identification and access path of each storage unit indicated by the information, and according to the storage location information of the data to be restored, the location of the data to be restored is obtained. The storage unit accesses the path, and then reads each data block of the data to be restored in the storage unit according to the access path to obtain the data to be restored.
  • the equipment includes hardware structures and/or software modules corresponding to each function.
  • the present invention can be implemented in the form of hardware or a combination of hardware and computer software. Whether a function is performed by hardware or computer software driving the hardware depends on the specific application and design constraints of the technical solution. Skilled artisans may implement the described functionality using different methods for each specific application, but such implementations should not be considered to be beyond the scope of the present invention.
  • Embodiments of the present application can divide the backup device provided by the present application into functional modules according to the above method examples.
  • functional modules can be divided into corresponding functional modules, or two or more functions can be integrated into one processing module.
  • the above integrated modules can be implemented in the form of hardware or software function modules.
  • the division of modules in the embodiments of this application is schematic and is only a logical function division. There may be other division methods in actual implementation.
  • FIG. 8 shows a possible structural diagram of the backup device deployed in the computing device involved in the above embodiment.
  • the backup device 80 may be a functional module or a chip.
  • the backup device 80 may include: a first acquisition unit 801 , a second acquisition unit 802 , a reading unit 803 , and a backup unit 804 .
  • the first acquisition unit 801 is used to execute the process S401 in Fig. 4 or Fig. 5, or execute the process S601 in Fig. 6, or execute the process S701 in Fig. 7;
  • the second acquisition unit 802 is used to execute the process S401 in Fig. 4 or Fig. 7. 5, or execute the process S702 in FIG.
  • the reading unit 803 is used to execute the process S403 in FIG. 4 or 5; the backup unit 804 is used to execute the process S404 in FIG. 4 or 5, or the process S404 in FIG. Process S405 in 5. All relevant content of each step involved in the above method embodiments can be quoted from the functional description of the corresponding functional module, and will not be described again here.
  • the backup device 80 may also include a first processing unit 805 for executing process S404 in FIG. 5 .
  • the backup device 80 may also include a reporting unit 806 for reporting information on the first storage unit that stores metadata of the data to be backed up.
  • the backup device 80 may also include a second processing unit 807 for executing process S602 in FIG. 6 .
  • FIG. 10 shows a possible structural diagram of the computing device involved in the above embodiment.
  • the computing device 100 may include: a processing module 1001 and a communication module 1002.
  • the processing module 1001 is used to control and manage the actions of the computing device 100, and the communication module 1002 is used to communicate with other devices.
  • the processing module 1001 is configured to perform any one of the processes S401 to S404 in FIG. 4 or FIG. 5 .
  • Computing device 100 may also include a storage module 1003 for storing program code and data for computing device 100 .
  • the processing module 1001 may be the processor 301 in the physical structure of the computing device 30 shown in FIG. 3 , and may be a processor or a controller. For example, it can be a CPU, a general-purpose processor, a DSP, an ASIC, an FPGA or other programmable logic devices, transistor logic devices, hardware components or any combination thereof. It may implement or execute the various illustrative logical blocks, modules, and circuits described in connection with this disclosure.
  • the processing module 1001 may also be a combination that implements computing functions, such as a combination of one or more microprocessors, a combination of a DSP and a microprocessor, and so on.
  • the communication module 1002 may be the transceiver 303 in the physical structure of the computing device 30 shown in FIG. 3.
  • the communication module 1002 may be a communication port, or may be a transceiver, a transceiver circuit, a communication interface, or the like. Alternatively, the above-mentioned communication interface can realize communication with other devices through the above-mentioned components with transceiver functions. The above-mentioned components with transceiver functions may be implemented by antennas and/or radio frequency devices.
  • the storage module 1003 may be the memory 302 in the physical structure of the computing device 30 shown in FIG. 3 .
  • the backup device 80 or the computing device 100 provided by the embodiments of the present application can be used to implement the corresponding functions in the methods implemented by the above embodiments of the present application.
  • the parts related to the embodiments of the present application are shown. , if the specific technical details are not disclosed, please refer to the embodiments of this application.
  • a computer-readable storage medium on which instructions are stored, and when the instructions are executed, the backup method in the above method embodiment is performed.
  • a computer program product containing instructions is provided.
  • the computer program product When the computer program product is run on a computer, it causes the computer to execute the backup method in the above method embodiment.
  • An embodiment of the present application further provides a chip system, which includes a processor and is used to implement the technical method of the embodiment of the present invention.
  • the chip system also includes a memory for storing necessary program instructions and/or data for embodiments of the present invention.
  • the chip system further includes a memory for the processor to call the application code stored in the memory.
  • the chip system may be composed of one or more chips, or may include chips and other Other discrete devices are not specifically limited in the embodiments of this application.
  • the disclosed devices and methods can be implemented in other ways.
  • the device embodiments described above are only illustrative.
  • the division of modules or units is only a logical function division.
  • there may be other division methods for example, multiple units or components may be The combination can either be integrated into another device, or some features can be omitted, or not implemented.
  • the coupling or direct coupling or communication connection between each other shown or discussed may be through some interfaces, and the indirect coupling or communication connection of the devices or units may be in electrical, mechanical or other forms.
  • the units described as separate components may or may not be physically separated.
  • the components shown as units may be one physical unit or multiple physical units, that is, they may be located in one place, or they may be distributed to multiple different places. . Some or all of the units can be selected according to actual needs to achieve the purpose of the solution of this embodiment.
  • each functional unit in each embodiment of the present application can be integrated into one processing unit, each unit can exist physically alone, or two or more units can be integrated into one unit.
  • the above integrated units can be implemented in the form of hardware or software functional units.
  • the integrated unit is implemented in the form of a software functional unit and sold or used as an independent product, it may be stored in a readable storage medium.
  • the technical solutions of the embodiments of the present application are essentially or contribute to the existing technology, or all or part of the technical solution can be embodied in the form of a software product, and the software product is stored in a storage medium , including several instructions to cause a device (which can be a microcontroller, a chip, etc.) or a processor to execute all or part of the steps of the methods described in various embodiments of this application.
  • the aforementioned storage media include: U disk, mobile hard disk, read-only memory (ROM), random access memory (Random Access Memory, RAM), magnetic disk or optical disk and other media that can store program code. .

Landscapes

  • Engineering & Computer Science (AREA)
  • Theoretical Computer Science (AREA)
  • Physics & Mathematics (AREA)
  • General Engineering & Computer Science (AREA)
  • General Physics & Mathematics (AREA)
  • Human Computer Interaction (AREA)
  • Quality & Reliability (AREA)
  • Library & Information Science (AREA)
  • Information Retrieval, Db Structures And Fs Structures Therefor (AREA)

Abstract

本申请公开了一种备份方法及装置，涉及计算机领域，以实现备份副本跨存储单元存储，进而达到存储池扩容后的增量备份。具体方案为：获取备份任务信息，备份任务信息包括待备份数据的信息、备份存储标识；获取备份存储标识指示的第一存储池的列表信息，列表信息用于指示第一存储池中存储单元的信息；第一存储池包括多个存储单元，多个存储单元位于至少两个存储集群；根据待备份数据的信息，从生产存储读取待备份数据；根据列表信息，将待备份数据存储在第一存储池中的一个或多个存储单元中。

Description

一种备份方法及装置 技术领域
本申请涉及计算机领域，尤其涉及一种备份方法及装置。
背景技术
随着服务器海量数据的不断增长，各种数据的安全性和重要程度也越来越被人们所重视。在系统运行过程中，存在各种各样导致数据丢失的原因，例如网络攻击、自然灾害、病毒侵入、电源故障、人为操作失误等等。一旦数据丢失，都会严重影响系统的正常运行。因此，对数据进行备份存储的意义重大。
当前，将备份存储的资源(存储，即备份介质)虚拟为如图1所示的存储架构，具体包括存储单元(storage unit，SU)、存储池(storage pool，SP)以及存储库(Repository)三层。其中，存储单元与真实的备份介质关联，用于存储数据，可以根据用户的需求配置存储单元的容量。而存储池将存储单元的存储资源虚拟化，使用户不再关心物理存储。存储库为保护集之间提供逻辑隔离，对于备份目标(磁盘、虚拟机等)每进行一次备份就会产生一个备份副本。
目前的存储备份方案中，通常将一套存储(例如一个集群)作为一个存储单元配置为一个存储池，在存储池内存储一个备份目标的备份副本。当存储池容量有限，扩容新的存储单元后，如何在存储池中进行增量备份亟待解决。
发明内容
本申请提供一种备份、配置存储池的方法及装置，以实现备份副本跨存储单元存储，进而达到存储池扩容后的增量备份。
为达到上述目的，本申请实施例采用如下技术方案：
第一方面，提供一种备份方法，该方法可以包括：获取包括待备份数据的信息、备份存储标识的备份任务信息；获取备份存储标识指示的第一存储池的列表信息，列表信息用于指示第一存储池中存储单元的信息；第一存储池包括多个存储单元，多个存储单元位于至少两个存储集群；根据待备份数据的信息，从生产存储读取待备份数据；根据第一存储池的列表信息，将待备份数据存储在第一存储池中的一个或多个存储单元中。
本申请提供一种备份方法及装置，通过对存储池配置用于指示存储池中存储单元的信息的列表信息，配置一个存储池包括的多个存储单元位于多个存储集群中，在进行备份时，备份副本中的各个数据块就可以按照实际需求分散存储在多个存储单元中，待备份数据与未被修改的数据可以存储于不同的存储集群中；由于各个存储单元有唯一的标识，根据存储池的列表信息就可以准确的实现数据恢复，因此，本申请的备份方法实现了扩容后有效的增量备份。
进一步的，当存储池扩容时，新增的存储集群可以作为存储单元加入存储池，只需要更新存储池的列表信息，以添加新增的存储单元的信息，就完成了存储池的扩容，使得存储池跨越了多个存储。虽然备份副本可以跨存储单元存储，但多个备份副本依然在同一个存储池内，备份对象与存储库关联，存储库与存储池关联，用户无需感知新增的硬件存储，因此， 对存储池扩容后，无需进行数据迁移，依然可以进行增量备份，实现有效扩容的目的。
一种可能的实现方式中，本申请提供的备份方法还可以包括：生成待备份数据的元数据，待备份数据的元数据中包括存储待备份数据的一个或多个存储单元的标识，以便于根据待备份数据的元数据恢复该待备份数据。
在一种可能的实现方式中，备份任务信息还可以包括前序副本的元数据的存储位置信息，前序副本为待备份数据所属的备份对象前一次备份的副本。待备份数据的元数据中还包括前序副本中未被待备份数据修改的数据的存储位置信息。存储待备份数据的存储单元与存储未被待备份数据修改的数据的存储单元位于不同的存储集群。以实现跨存储单元的增量备份，当存储池扩容时实现有效的增量备份。
在一种可能的实现方式中，待备份数据属于第一备份文件，备份任务信息还包括第一备份文件中未被待备份数据修改的数据的信息，以实现全量备份。
在一种可能的实现方式中，本申请提供的备份方法还可以包括：将待备份数据的元数据存储于第一存储单元；上报第一存储单元的信息。以便于下一次备份时，将待备份数据的元数据看作前序副本的元数据，实现有效的增量备份。
在一种可能的实现方式中，可以预先配置了存储不同备份目标的副本元数据的存储单元，在进行备份或恢复时，快速获取备份副本的元数据。
在一种可能的实现方式中，备份存储标识包括：第一存储池的标识，或者，第一存储池对应的存储库的标识。
在一种可能的实现方式中，本申请提供的方法还可以包括：获取配置任务信息，配置任务用于指示将第二存储单元配置为第二存储池的资源；第二存储池包括多个存储单元，第二存储池包括的多个存储单元位于至少两个存储集群；在第二存储池的列表信息中记录第二存储单元的信息。在存储池扩容时，实时更新存储池的列表信息，以保证备份过程的准确性。
在一种可能的实现方式中，本申请提供的方法还可以包括：获取恢复任务信息，恢复任务信息包括待恢复数据的信息；获取存储待恢复数据的第三存储池的列表信息；根据待恢复数据的信息，获取待恢复数据的元数据，待恢复数据的元数据包括待恢复数据的存储位置信息；根据第三存储池的列表信息，以及待恢复数据的存储位置信息，读取待恢复数据。
第二方面，提供另一种备份方法，应用于备份系统，该备份系统包括备份控制设备、备份存储设备以及生产存储设备。该备份方法可以包括：备份控制设备向备份存储设备发送备份任务信息，备份任务信息包括待备份数据的信息、备份存储标识。备份存储设备获取备份存储标识指示的第一存储池的列表信息，列表信息用于指示第一存储池中存储单元的信息；第一存储池包括多个存储单元，多个存储单元位于至少两个存储集群；备份存储设备根据待备份数据的信息，从生产存储设备读取待备份数据；备份存储设备根据列表信息，将待备份数据存储在第一存储池中的一个或多个存储单元中。
第三方面，提供一种备份装置，该装置可以包括：第一获取单元、第二获取单元、读取单元以及备份单元。其中：
第一获取单元，用于获取备份任务信息，备份任务信息包括待备份数据的信息、备份存储标识。
第二获取单元，用于获取备份存储标识指示的第一存储池的列表信息，列表信息用于指示第一存储池中存储单元的信息。第一存储池包括多个存储单元，多个存储单元位于至少两个存储集群。
读取单元，用于根据待备份数据的信息，从生产存储读取所述待备份数据。
备份单元，用于根据第一存储池的列表信息，将待备份数据存储在第一存储池中的一个或多个存储单元中。
在一种可能的实现方式中，该备份装置还可以包括：第一处理单元，用于生成待备份数据的元数据，待备份数据的元数据中包括存储待备份数据的一个或多个存储单元的标识。
在一种可能的实现方式中，备份任务信息还可以包括前序副本的元数据的存储位置信息，前序副本为待备份数据所属的备份对象前一次备份的副本。待备份数据的元数据中还包括前序副本中未被所述待备份数据修改的数据的存储位置信息；存储所述待备份数据的存储单元与存储未被待备份数据修改的数据的存储单元位于不同的存储集群。
在一种可能的实现方式中，待备份数据属于第一备份文件，备份任务信息还包括第一备份文件中未被待备份数据修改的数据的信息。
在一种可能的实现方式中，备份单元还用于：将待备份数据的元数据存储于第一存储单元。该备份装置还可以包括上报单元，用于上报第一存储单元的信息。
在一种可能的实现方式中，备份存储标识包括：第一存储池的标识，或者，第一存储池对应的存储库的标识。
在一种可能的实现方式中，第一获取单元还用于：获取配置任务信息，配置任务用于指示将第二存储单元配置为第二存储池的资源。第二存储池包括多个存储单元，所述第二存储池包括的多个存储单元位于至少两个存储集群。该备份装置还可以包括第二处理单元，用于在第二存储池的列表信息中记录第二存储单元的信息。
在一种可能的实现方式中，第一获取单元还用于：获取恢复任务信息，恢复任务信息包括待恢复数据的信息。第二获取单元还用于，获取存储待恢复数据的第三存储池的列表信息。该备份装置还包括第三获取单元，用于根据待恢复数据的信息，获取待恢复数据的元数据，待恢复数据的元数据包括待恢复数据的存储位置信息；根据第三存储池的列表信息，以及待恢复数据的存储位置信息，读取待恢复数据。
第四方面，提供一种备份系统，该备份系统包括备份控制设备、备份存储设备以及生产存储设备。其中：
备份控制设备用于：向备份存储设备发送备份任务信息，备份任务信息包括待备份数据的信息、备份存储标识。
备份存储设备用于：获取备份存储标识指示的第一存储池的列表信息，列表信息用于指示第一存储池中存储单元的信息。第一存储池包括多个存储单元，多个存储单元位于至少两个存储集群。根据待备份数据的信息，从生产存储设备读取待备份数据；根据列表信息，将待备份数据存储在第一存储池中的一个或多个存储单元中。
第五方面，本申请提供了一种计算设备，该计算设备可以实现上述第一方面描述的方法示例中的功能，所述功能可以通过硬件实现，也可以通过硬件执行相应的软件实现。所述硬件或软件包括一个或多个上述功能相应的模块。该计算设备可以以芯片的产品形态存在。
在一种可能的实现方式中，该计算设备可以包括处理器和传输接口。其中，传输接口用于接收和发送数据。处理器被配置为调用存储在存储器中的程序指令，以使得该计算设备执行上述第一方面描述的方法示例中的功能。
第六方面，提供一种计算机可读存储介质，包括指令，当其在计算机上运行时，使得计算机执行上述任一方面或任意一种可能的实现方式所述的备份方法。
第七方面，提供一种计算机程序产品，当其在计算机上运行时，使得计算机执行上述任一方面或任意一种可能的实现方式所述的备份方法。
第八方面，提供一种芯片系统，该芯片系统包括处理器，还可以包括存储器，用于实现上述方法中的功能。该芯片系统可以由芯片构成，也可以包含芯片和其他分立器件。
上述第二方面至第八方面提供的方案，用于实现上述第一方面提供的方法，因此可以与第一方面达到相同的有益效果，此处不再进行赘述。
需要说明的是，上述各个方面中的任意一个方面的各种可能的实现方式，在方案不矛盾的前提下，均可以进行组合。
附图说明
图1为备份存储资源示意图；
图2为本申请实施例提供的一种存储备份系统的架构示意图；
图3为本申请实施例提供的一种计算设备的结构示意图；
图4为本申请实施例提供的一种配置资源池的方法的流程示意图；
图5为本申请实施例提供的另一种配置资源池的方法的流程示意图；
图6为本申请实施例提供的一种备份方法的流程示意图；
图7为本申请实施例提供的一种数据恢复方法的流程示意图；
图8为本申请实施例提供的一种备份装置的结构示意图；
图9为本申请实施例提供的另一种备份装置的结构示意图；
图10为本申请实施例提供的另一种计算设备的结构示意图。
具体实施方式
本申请说明书和权利要求书及上述附图中的术语“第一”、“第二”和“第三”等是用于区别不同对象，而不是用于限定特定顺序。
在本申请实施例中，“示例性的”或者“例如”等词用于表示作例子、例证或说明。本申请实施例中被描述为“示例性的”或者“例如”的任何实施例或设计方案不应被解释为比其它实施例或设计方案更优选或更具优势。确切而言，使用“示例性的”或者“例如”等词旨在以具体方式呈现相关概念，便于理解。
在本申请的描述中，除非另有说明，“/”表示前后关联的对象是一种“或”的关系，例如，A/B可以表示A或B；本申请中的“和/或”仅仅是一种描述关联对象的关联关系，表示可以存在三种关系，例如，A和/或B，可以表示：单独存在A，同时存在A和B，单独存在B这三种情况，其中A,B可以是单数或者复数。并且，在本申请的描述中，除非另有说明，“多个”是指两个或多于两个。“以下至少一项(个)”或其类似表达，是指的这些项中的任意组合，包括单项(个)或复数项(个)的任意组合。例如，a，b，或c中的至少一项(个)，可以表示：a，b，c，a-b，a-c，b-c，或a-b-c，其中a，b，c可以是单个，也可以是多个。
在本申请实施例中，至少一个还可以描述为一个或多个，多个可以是两个、三个、四个或者更多个，本申请不做限制。
在描述本申请实施例之前，先对本申请实施例中涉及的名词进行解释。
备份对象，是指备份操作中源对象，即备份操作是将备份对象中的数据进行备份。备份对象可以为磁盘、虚拟机或其他形式的具有存储功能的设备。
备份副本，是指对一个备份对象的进行一次备份操作得到的结果。备份副本包括元数据和备份数据。备份数据为备份对象中的数据的备份。元数据用于记录备份对象的信息。元数据还可以用于记录备份数据中的数据在存储单元中的存储位置。一个备份副本的元数据可以 如表1所示，该元数据中记录了副本信息、磁盘信息以及数据块信息。其中，副本信息用于记录备份副本的标识，磁盘信息用于记录数据块存储的磁盘标识，数据块信息用于记录数据块的标识。
表1
备份链，是指一个备份对象的所有备份副本的集合。一个备份对象的备份链的数据结构可以如表2所示，该备份对象对应存储库1，即该备份对象的备份副本均存储于存储库1的资源中。
表2
存储集群，也可以称为存储，是指用于存储数据的实体硬件装置，例如磁盘或其他形式。
存储单元，是指根据用户需求，将存储的资源虚拟构成的用于存储的资源的集合。一个存储单元可以为一个或多个存储构成，一个存储单元也可以为存储的一部分资源。
存储池，是在存储单元的基础上，更进一步的存储资源虚拟化得到的概念。一个或多个存储单元构成存储池。
存储库，用于存储一个备份对象的全部备份副本的资源集合。存储库为备份对象之间提供逻辑隔离，一个存储库的资源可以包括一个或多个存储池，存储库与其包括的资源所属的存储池相对应。
本申请提供一种备份方法及装置，通过对存储池配置用于指示存储池中存储单元的信息的列表信息，配置一个存储池包括的多个存储单元位于多个存储集群中，在进行备份时，备份副本中的各个数据块就可以按照实际需求分散存储在多个存储单元中，待备份数据与未被修改的数据可以存储于不同的存储集群中；由于各个存储单元有唯一的标识，根据存储池的列表信息就可以准确的实现数据恢复，因此，本申请的备份方法实现了扩容后有效的增量备份。
进一步的，当存储池扩容时，新增的存储集群可以作为存储单元加入存储池，只需要更新存储池的列表信息，以添加新增的存储单元的信息，就完成了存储池的扩容，使得存储池跨越了多个存储。虽然备份副本可以跨存储单元存储，但多个备份副本依然在同一个存储池内，备份对象与存储库关联，存储库与存储池关联，用户无需感知新增的硬件存储，因此，对存储池扩容后，无需进行数据迁移，依然可以进行增量备份，实现有效扩容的目的。
下面将结合附图对本申请实施例的实施方式进行详细描述。
本申请提供的方案可以应用于图2示意的存储备份系统20中。如图2所示，存储备份系统20可以包括备份控制管理设备201、备份存储管理设备202、存储介质203以及生产存储管理设备204。
其中，生产存储管理设备204用于管理备份对象的数据。存储介质203为实际的物理存储，用于提供存储资源，其提供的存储资源可以虚拟化为存储单元、存储池以及存储库。
备份控制管理设备201为存储备份系统20的控制中心。备份控制管理设备201可以与用户交互获取备份需求或其他。备份控制管理设备201还可以向备份存储管理设备202下发任务，进行存储资源配置、数据备份、数据恢复等。
备份存储管理设备202是存储备份系统20中的备份操作的执行者。例如，备份存储管理设备202可以执行备份控制管理设备201下发的任务，配置存储介质203中的资源，或者，将生产存储管理设备204提供的数据进行备份，将备份副本存储至存储介质203中，或者，从存储介质203中恢复备份副本至生产存储管理设备204。
示例性的，上述备份控制管理设备201、备份存储管理设备202、生产存储管理设备204可以为计算设备(例如服务器)或其他形态，本申请实施例对于其具体产品形态不予限定。
需要说明的是，上述图2仅以举例的形式，示意存储备份系统的架构，并不是对本申请方案应用场景的限定。在实际应用中，可以根据实际需求配置存储备份系统的架构内容，本申请实施例对此不予限定。
示例性的，存储备份系统20可以为存储或云存储的备份系统，或者，存储备份系统20可以为其他涉及备份的场景中的备份系统，本申请实施例对于应用场景不予限定。
下面结合附图，对本申请的实施例提供的方案进行具体阐述。
一方面，本申请实施例提供一种计算设备，用于执行本申请提供的方案。例如，该计算设备可以为图2中示意的备份存储管理设备202。
图3示意了本申请实施例提供的计算设备30的结构图。如图3所示，计算设备30可以包括处理器301、存储器302、收发器303。
下面结合图3对计算设备30的各个构成部件进行具体的介绍：
存储器302可以是易失性存储器(volatile memory)，例如随机存取存储器(random-access memory，RAM)；或者非易失性存储器(non-volatile memory)，例如只读存储器(read-only memory，ROM)，快闪存储器(flash memory)，硬盘(harddisk drive，HDD)或固态硬盘(solid-state drive，SSD)；或者上述种类的存储器的组合，用于存储可实现本申请方法的应用程序代码、配置文件、数据信息或者其他内容。在其他可能的情形中，该存储器302也可以部署在独立于计算设备30的其他设备中。
收发器303用于计算设备30与其他设备的信息交互。
处理器301可以是计算设备30的控制中心。例如，处理器301可以是一个中央处理器(central processing unit，CPU)，也可以是特定集成电路(application specific integrated circuit，ASIC)，或者是被配置成实施本申请实施例的一个或多个集成电路，例如：一个或多个微处理器(digital signal processor，DSP)，或，一个或者多个现场可编程门阵列(field programmable gate array，FPGA)。
示例性的，处理器301通过运行或执行存储在存储器302内的软件程序和/或模块，可以执行如下功能：
获取备份任务信息，该备份任务信息包括待备份数据的信息、备份存储标识；获取备份 存储标识指示的第一存储池的列表信息，该列表信息用于指示第一存储池中存储单元的信息；第一存储池包括多个存储单元，多个存储单元位于至少两个存储集群；根据待备份数据的信息，从生产存储读取待备份数据；根据第一存储池的列表信息，将待备份数据存储在第一存储池中的一个或多个存储单元中。
本申请提供的方案中，对存储单元配置了唯一的标识，对存储池配置了列表信息，一个存储池的列表信息用于指示该存储池中存储单元的信息。
示例性的，一个存储的列表信息中可以包括该存储池中的存储单元的标识以及访问路径。
具体的，存储单元/存储池/存储库的标识用于唯一指示存储单元/存储池/存储库，在整个备份系统中无重复。示例性的，存储单元的标识可以为索引或其他形式。
其中，存储单元的访问路径用于在存储池中访问存储单元，本申请实施例对于存储单元的访问路径的具体内容不予限定。
示例性的，存储单元的访问路径可以为存储单元在备份服务器中的挂载路径。
一种可能的实现方式中，一个存储池的列表信息还可以包括该存储池包括的存储单元是否可写。
一种可能的实现方式中，存储池的列表信息可以存储于存储池中某一个专用的存储单元中。
另一种可能的实现方式中，存储池的列表信息可以存储于存储池中每一个存储单元中。
示例性的，假设在存储池SP_0中配置了两个存储单元：SU_0和SU_1，在存储池SP_1中配置了一个存储单元SU_2。
SU_0、SU_1均属于存储池SP_0，SU_0、SU_1中记录的列表信息为存储池SP_0的列表信息，列表信息中包括存储池SP_0中所有存储单元(SU_0和SU_1)的标识以及访问路径。SU_0、SU_1中记录的列表信息如下表3所示。
表3
SU_2属于存储池SP_1，SU_2中记录的列表信息为存储池SP_1中所有存储单元(SU_2)的标识以及访问路径。SU_2中记录的列表信息如下表4所示。
表4

进一步的，当存储池扩容时，新增的存储集群可以作为存储单元加入存储池，只需要更新存储池的列表信息，以添加新增的存储单元的信息，就完成了存储池的扩容，使得存储池跨越了多个存储。虽然备份副本可以跨存储单元存储，但多个备份副本依然在同一个存储池内，备份对象与存储库关联，存储库与存储池关联，用户无需感知新增的硬件存储，因此，对存储池扩容后，无需进行数据迁移，依然可以进行增量备份，实现有效扩容的目的。
进一步的，由于存储池的列表信息中包括了该存储池中的存储单元的信息，当存储池中新增加了存储单元后，存储池的列表信息则需更新，以添加新增加的存储单元的信息。
示例性的，基于上述表3和表4的示例，假设将存储单元SU_1添加至SP_1中。SU_0、属于存储池SP_0，存储池SP_0包括的存储单元未变化，存储池SP_0的列表信息保持不变。SP_1中新增了存储单元SU_1，SP_1的列表信息需更新，以包括SU_1和SU_2的信息。SU_1中记录的列表信息则包括SP_0的列表信息和SP_1的列表信息，SU_2中记录的列表信息则为更新后的SP_1的列表信息。
SU_1中记录的列表信息将变更为表5所示。SU_2中记录的列表信息将变更为表6所示。
表5
由于SU_1存在于SP_0和SP_1中，其记录的列表信息内记录了SU_1在的两个存储池的访问路径，由于存储池SP_0、SP_1创建于不同的备份服务器，存储单元SU_1需同时挂载在两个备份服务器上，访问路径虽然不相同但访问的是同一个存储单元。
表6

需要说明的是，上述表3至表6只是以举例的形式对存储单元的列表信息进行示例描述，并不是对列表信息的内容以及形式的具体限定。
另一方面，本申请实施例提供一种备份方法，该备份方法可以由备份存储管理设备执行。该备份存储管理设备用于执行存储备份，可以为图2中示意的备份存储管理设备202执行。该备份方法可以与前述配置资源池的方法结合使用，也可以单独使用，本申请实施例对此不予限定。
需要说明的是，每一次执行备份任务进行备份的过程相同，本申请下述实施例以一次备份的过程为例进行说明，其他不再一一赘述。
如图4所示，本申请实施例提供一种备份方法可以包括：
S401、备份存储管理设备获取备份任务信息。
其中，备份任务信息包括待备份数据的信息、备份存储标识。
具体的，待备份数据为本次备份时，相比于前一次备份，待备份数据所属的第一备份对象中被修改的数据。待备份数据的信息用于指示待备份数据。
示例性的，待备份数据的信息可以为第一备份对象的标识。
该备份任务信息用于指示将待备份数据存储于备份存储标识指示的存储池。
具体的，备份存储标识用于指示第一存储池，第一存储池用于存储待备份数据所属的第一备份对象的备份副本。第一存储池可以为一个或多个。
一种可能的实现方式中，备份存储标识可以为第一存储池的标识，或者，备份存储标识可以为存储第一备份对象的备份副本的存储库的标识。
另一种可能的实现方式中，备份存储标识可以为第一备份对象的标识。
示例性的，预先配置了存储各个备份对象的备份副本的存储池，S401中备份存储管理设备获取到备份任务信息时，根据第一备份对象的标识，就可以确定存储第一备份对象的备份副本的第一存储池。
示例性的，预先配置了存储各个备份对象的备份副本的存储库，S401中备份存储管理设备获取到备份任务信息时，根据第一备份对象的标识，就可以确定存储第一备份对象的备份副本的存储库，将该存储库对应的存储池，确定为第一存储池。
进一步的，该备份任务还可以包括前序副本的元数据的存储位置信息，该前序副本为待备份数据所属的第一备份对象前一次备份的副本。
其中，存储位置信息可以为存储单元的标识。
进一步的，该待备份数据属于第一备份文件，备份任务信息还包括第一备份文件中未被待备份数据修改的数据的信息，以实现对第一备份文件进行全量备份。
一种可能的实现方式中，S401中备份存储管理设备可以从备份控制管理设备接收该备份任务信息，或者，S401中备份存储管理设备可以接收用户输入的该备份任务。本申请实施例对于备份任务信息的来源不予限定。
S402、备份存储管理设备根据待备份数据的信息，从生产存储读取待备份数据。
具体的，S402中备份存储管理设备通过与生产存储的交互，根据待备份数据的信息，读取待备份数据。
S403、备份存储管理设备根据第一存储池的列表信息，将待备份数据存储在第一存储池中的一个或多个存储单元中。
具体的，第一存储池的列表信息中记录了第一存储池中的存储单元的信息，S403中根据第一存储池的列表信息，可以确定第一存储池中可以用于存储待备份数据的一个或多个存储单元，然后将待备份数据存储在第一存储池中的一个或多个存储单元中。
示例性的，可以备份存储管理设备根据第一存储池的列表信息，将待备份数据存储在第一存储池中的一个或多个可写的存储单元中。
具体的，在S403中备份存储管理设备先确定第一存储池中可写的存储单元。
一种可能的实现方式中，备份存储管理设备中记录了第一存储池中可写的存储单元，S403中可以根据记录的内容确定第一存储池中可写的存储单元。
另一种可能的实现方式中，备份控制管理设备中记录了第一存储池中可写的存储单元，S403中备份存储管理设备通过与备份控制管理设备的交互，以确定第一存储池中可写的存储单元。
再一种可能的实现方式中，第一存储池的列表信息包括第一存储单元中的存储单元是否可写。S403中备份存储管理设备可以从第一存储池的列表信息中，确定第一存储池中可写的存储单元。第一存储池的列表信息的存储位置，对于备份存储管理设备已知。
示例性的，第一存储池的列表信息存储于第一存储池中每一个存储单元中，S403中备份存储管理设备可以从第一存储池中任一个存储单元中获取第一存储池的列表信息，然后确定第一存储池中可写的存储单元。
进一步的，S403中备份存储管理设备可以根据备份策略，确定第一存储池中存储待备份数据的一个或多个存储单元。
具体的，在进行存储备份时，可以将备份副本切分成数据块存储，对于切分的数据块的大小，可以根据实际需求配置，本申请实施例对此不予限定。
进一步的，将第一备份副本中的数据块存储于几个存储单元，可以根据业务需求或者备份系统的功能设定，本申请实施例对此不予限定。
示例性的，可以将一个数据块存储于一个存储单元。
示例性的，备份策略可以包括选择剩余容量最大的存储单元。例如，可以在执行S403时，遍历待备份数据中各个数据块，为每个数据块选择剩余容量最大的存储单元进行存储。
示例性的，备份策略可以包括选择读写速度最快的存储单元。例如，可以在执行S403时，遍历待备份数据中各个数据块，为每个数据块选择读写速度最快的存储单元进行存储。
其中，可以存储单元的容量、读写速度作为存储单元的属性参数，可以由备份存储管理设备记录使用，或者由备份控制管理设备记录，备份存储管理设备通过交互获取，本申请实施例对于存储单元的容量、读写速度的获取方式不予限定。
进一步的，备份存储管理设备根据第一存储池的列表信息，按照列表信息指示的存储单元的访问路径，将待备份数据存储在第一存储池中确定的的一个或多个存储单元中。
本申请提供一种备份方法，通过对存储池配置用于指示存储池中存储单元的信息的列表信息，配置一个存储池包括的多个存储单元位于多个存储集群中，在进行备份时，备份副本中的各个数据块就可以按照实际需求分散存储在多个存储单元中，由于一个存储池中的多个存储单元来自至少两个存储集群，就可以实现将待备份数据与未被修改的数据可以存储于不同的存储集群中；由于各个存储单元有唯一的标识，根据存储池的列表信息就可以准确的实现数据恢复，因此，本申请的备份方法实现了扩容后有效的增量备份。
进一步的，当存储池扩容时，新增的存储集群可以作为存储单元加入存储池，只需要更新存储池的列表信息，以添加新增的存储单元的信息，就完成了存储池的扩容，使得存储池跨越了多个存储。虽然备份副本可以跨存储单元存储，但多个备份副本依然在同一个存储池内，备份对象与存储库关联，存储库与存储池关联，用户无需感知新增的硬件存储，因此，对存储池扩容后，无需进行数据迁移，依然可以进行增量备份，实现有效扩容的目的。
进一步的，如图5所示，本申请实施例提供的备份方法还可以包括S404。
S404、备份存储管理设备生成待备份数据的元数据。
其中，待备份数据的元数据中包括存储待备份数据的一个或多个存储单元的标识。
应理解，一个备份副本的元数据记录了备份对象本次备份操作时，备份副本中各个数据块的存储位置信息。其中，存储位置信息可以为存储单元的标识。
进一步的，S403中进行增量备份，待备份数据的元数据中还包括前序副本中未被待备份数据修改的数据的存储位置信息。存储待备份数据的存储单元，与存储未被该待备份数据修改的数据的存储单元，可以位于不同的存储集群。
具体的，在S403中进行了增量备份，由于未被该待备份数据修改的数据的存储位置信息，需借用前序副本的元数据中未被待备份数据修改的数据的存储位置信息，S404中生成待备份数据的元数据时，备份存储管理设备先获取前序副本的元数据的存储位置信息，以获取前序副本的元数据，再生成待备份数据的元数据。
一种可能的实现方式中，S401中获取的备份任务信息还包括前序副本的元数据的存储位置信息，备份存储管理设备可以从备份任务信息中获取前序副本的元数据的存储位置信息，进而根据该存储位置信息获取前序副本的元数据，对其解析以获取前序副本中未被待备份数据修改的数据的存储位置信息。
另一种可能的实现方式中，预先配置了存储不同备份对象的副本元数据的存储单元，S404中备份存储管理设备从预先配置的存储第一备份对象的副本元数据的存储单元中，获取前序副本的元数据，对其解析以获取前序副本中未被待备份数据修改的数据的存储位置信息。
例如，第一备份对象可以切分为3个数据块，分别记录为数据块1、数据块2以及数据块3。在前一次备份时，备份副本全部存储于第一存储池中的存储单元a，元数据如表7所示。
表7
对第一存储池扩容存储单元b之后，本次备份时，数据块2进行了修改，通过执行上述S401至S403的过程，将数据块2存储于存储单元b中，元数据可以图标8所示。
表8

需要说明的是，表7和表8仅通过举例的方式对于元数据进行说明，并不构成对元数据的形式以及内容的具体限定。
示例性的，第一备份副本的本次备份元数据可以如表9所示。
表9
与前述表1示意的元数据相比，表9示意的元数据中新增了存储单元的标识，以便于备份副本中的数据块分散存储与不同存储单元时数据的恢复。
示例性的，第一备份对象的备份链可以如表10所示。
表10
S405、备份存储管理设备将待备份数据的元数据存储于第一存储单元。
一种可能的实现方式中，预先配置了存储不同备份对象的副本元数据的存储单元，第一存储单元则为预先配置的存储第一备份对象的副本元数据的存储单元。
另一种可能的实现方式中，第一存储单元可以为第一存储池中任一存储单元，本申请实施例对于选取第一存储单元的方式不予限定。相应的，本申请实施例提供的方法还包括：上报第一存储单元的标识。以使得在下一次对第一备份对象进行备份操作的备份任务信息中，携带该第一存储单元的标识。
进一步的，上述待备份数据属于第一备份文件，备份任务信息还包括第一备份文件中未被待备份数据修改的数据的信息，以实现对第一备份文件进行全量备份。相应的，S402中还根据未被待备份数据修改的数据的信息，从生产存储读取未被待备份数据修改的数据；S403中根据第一存储池的列表信息，将未被待备份数据修改的数据存储在第一存储池中的一个或多个存储单元中，并在元数据中记录存储位置信息。
进一步的，本申请实施例提供的备份方法还可以包括配置资源池的过程，该过程可以如图6所示。
需要说明的是，每一次配置资源池的过程相同，本申请下述实施例以一次配置资源池的 过程为例进行说明，其他不再一一赘述。
如图6所示，本申请实施例提供的配置存储池的方法可以包括：
S601、备份存储管理设备获取配置任务信息。
其中，配置任务信息用于指示将第二存储单元配置为第二存储池的资源。第二存储池包括多个存储单元，第二存储池包括的多个存储单元位于至少两个存储集群。
一种可能的实现方式中，S601中备份存储管理设备可以从备份控制管理设备接收该配置任务信息，或者，S601中备份存储管理设备可以接收用户输入的该配置任务信息。本申请实施例对于配置任务信息的来源不予限定。
具体的，第二存储池为一个或多个。例如，第二存储池为多个，实现存储单元对多个存储池共享。
一种可能的实现方式中，可以在搭建备份存储系统时，执行S601以配置系统的存储池。第二存储池为新配置的存储池。
另一种可能的实现方式中，可以在对第二存储池进行扩容时，执行S601以配置系统的存储池。此时，第二存储单元的资源可以为扩容时新增加的存储中的资源，第二存储池已配置了存储单元。
示例性的，第二存储单元与第二存储池中已配置的存储单元的资源属于同一个存储集群，或者，第二存储单元与第二存储池中已配置的存储单元的资源属于不同的存储集群。
S602、备份存储管理设备在第二存储池的列表信息中记录第二存储单元的信息。
存储池的列表信息已经在前述内容中进行了详细说明，此处不再赘述。
示例性的，S602中备份存储管理设备可以获取第二存储单元的标识，以及第二存储单元在第二存储池的访问路径，然后在第二存储池的列表信息中记录第二存储单元的标识以及访问路径。
一种可能的实现方式中，S601中获取的配置任务信息中包括：第二存储单元在第二存储池的访问路径。
示例性的，当存储池的列表信息存储于存储池中每个存储单元中时，S602中备份存储管理设备将更新后的第二存储池的列表信息(记录了第二存储单元的信息的列表信息)存储于第二存储单元，将第二存储池中第二存储单元之外的存储单元中存储的列表信息，更新为第二存储池更新后的列表信息。
一种可能的实现方式，将第二存储池中第二存储单元之外的存储单元中存储的列表信息，更新为第二存储池更新后的列表信息，可以实现为：在第二存储池中第二存储单元之外的存储单元中存储的列表信息中，添加第二存储单元的信息。
进一步的，在S602之后，备份存储管理设备还可以记录存储单元与存储池的映射关系，以记录存储库、存储池与存储单元的映射关系，实现记录多层资源映射的目的。
进一步的，本申请实施例提供的备份方法还可以包括数据恢复的过程，该过程可以如图7所示。该数据恢复过程可以与前述备份方法和/或配置资源池的方法结合使用，也可以单独使用，本申请实施例对此不予限定。该数据恢复的过程可以由备份存储管理设备执行。该备份存储管理设备用于执行存储备份的回复，可以为图2中示意的备份存储管理设备202执行。
需要说明的是，每一次进行数据恢复的过程相同，本申请下述实施例以一次数据恢复的过程为例进行说明，其他不再一一赘述。
如图7所示，本申请实施例提供的数据恢复过程可以包括：
S701、备份存储管理设备获取恢复任务信息。
其中，恢复任务包括待恢复数据的信息。待恢复数据的信息用于指示第二备份对象的最新的备份副本。
具体的，该恢复任务信息用于指示从第三存储池中恢复待恢复数据。第三存储池用于存储第二备份对象的备份副本。
一种可能的实现方式中，待恢复数据的信息可以为第二备份对象的标识，第二备份副本为第二备份对象的最新的备份副本。
另一种可能的实现方式中，待恢复数据的信息可以为第三存储池的标识，或者，待恢复数据的信息可以为第三存储池对应的存储库的标识。
具体的，可以根据待恢复数据的信息，确定第三存储池。
示例性的，第三存储池可以为一个或多个。
一种可能的实现方式中，S701中备份存储管理设备可以从备份控制管理设备接收该恢复任务信息，或者，S701中备份存储管理设备可以接收用户输入的该恢复任务信息。本申请实施例对于恢复任务信息的来源不予限定。
S702、备份存储管理设备获取第三存储池的列表信息。
一种可能的实现方式中，备份存储管理设备可以从第三存储池的任一存储单元中，获取第三存储池的列表信息。
另一种可能的实现方式中，备份存储管理设备可以从第三存储池专用于存储列表信息的存储单元中，获取第三存储池的列表信息。
S703、备份存储管理设备根据待恢复数据的信息，获取待恢复数据的元数据。
其中，待恢复数据的元数据包括待恢复数据的存储位置信息。
一种可能的实现方式中，预先配置了不同备份对象的元数据的存储位置，根据恢复数据的信息指示的第二备份对象的元数据的存储位置，就可以获取待恢复数据的元数据。
另一种可能的实现方式中，恢复任务信息中包括待恢复数据的的元数据的存储位置信息，根据该存储位置信息，就可以获取待恢复数据的元数据。
其中，本申请所描述的存储位置信息，可以为存储单元的标识。
S704、备份存储管理设备根据第三存储池的列表信息，以及待恢复数据的存储位置信息，读取待恢复数据。
其中，第三存储池的列表信息指示了第三存储池中存储单元的信息，根据该信息指示的各个存储单元的标识以及访问路径，根据待恢复数据的存储位置信息，获取存储待恢复数据的存储单元访问路径，然后按照访问路径在存储单元中读取待恢复数据的各个数据块，得到待恢复数据。
上述主要从设备的工作原理的角度对本发明实施例提供的方案进行了介绍。可以理解的是，设备等为了实现上述功能，其包含了执行各个功能相应的硬件结构和/或软件模块。本领域技术人员应该很容易意识到，结合本文中所公开的实施例描述的各示例的单元及算法步骤，本发明能够以硬件或硬件和计算机软件的结合形式来实现。某个功能究竟以硬件还是计算机软件驱动硬件的方式来执行，取决于技术方案的特定应用和设计约束条件。专业技术人员可以对每个特定的应用来使用不同方法来实现所描述的功能，但是这种实现不应认为超出本发明的范围。
本申请实施例可以根据上述方法示例对本申请提供的备份装置进行功能模块的划分，例如，可以对应各个功能划分各个功能模块，也可以将两个或两个以上的功能集成在一个处理模块中。上述集成的模块既可以采用硬件的形式实现，也可以采用软件功能模块的形式实现。 本申请实施例中对模块的划分是示意性的，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式。
在采用对应各个功能划分各个功能模块的情况下，图8示出了上述实施例中所涉及的计算设备中部署的备份装置的一种可能的结构示意图。该备份装置80可以为功能模块或者芯片。如图8所示，备份装置80可以包括：第一获取单元801、第二获取单元802、读取单元803、备份单元804。其中，第一获取单元801用于执行图4或图5中的过程S401，或者执行图6中的过程S601，或者执行图7中的过程S701；第二获取单元802用于执行图4或图5中的过程S402，或者执行图7中的过程S702；读取单元803用于执行图4或图5中的过程S403；备份单元804用于执行图4或图5中的过程S404，或者图5中的过程S405。其中，上述方法实施例涉及的各步骤的所有相关内容均可以援引到对应功能模块的功能描述，在此不再赘述。
进一步的，如图9所示，备份装置80还可以包括第一处理单元805，用于执行图5中的过程S404。
进一步的，如图9所示，备份装置80还可以包括上报单元806，用于上报存储待备份数据的元数据的第一存储单元的信息。
进一步的，如图9所示，备份装置80还可以包括第二处理单元807，用于执行图6中的过程S602。
在采用集成的单元的情况下，图10示出了上述实施例中所涉及的计算设备的一种可能的结构示意图。计算设备100可以包括：处理模块1001、通信模块1002。处理模块1001用于对计算设备100的动作进行控制管理，通信模块1002用于与其他设备通信。例如，处理模块1001用于执行图4或图5中的过程S401至S404中任一项。计算设备100还可以包括存储模块1003，用于存储计算设备100的程序代码和数据。
其中，处理模块1001可以为图3所示的计算设备30的实体结构中的处理器301，可以是处理器或控制器。例如可以是CPU，通用处理器，DSP，ASIC，FPGA或者其他可编程逻辑器件、晶体管逻辑器件、硬件部件或者其任意组合。其可以实现或执行结合本申请公开内容所描述的各种示例性的逻辑方框，模块和电路。处理模块1001也可以是实现计算功能的组合，例如包含一个或多个微处理器组合，DSP和微处理器的组合等等。通信模块1002可以为图3所示的计算设备30的实体结构中的收发器303，通信模块1002可以是通信端口，或者可以是收发器、收发电路或通信接口等。或者，上述通信接口可以通过上述具有收发功能的元件，实现与其他设备的通信。上述具有收发功能的元件可以由天线和/或射频装置实现。存储模块1003可以是图3所示的计算设备30的实体结构中的存储器302。
如前述，本申请实施例提供的备份装置80或计算设备100可以用于实施上述本申请各实施例实现的方法中相应的功能，为了便于说明，仅示出了与本申请实施例相关的部分，具体技术细节未揭示的，请参照本申请各实施例。
作为本实施例的另一种形式，提供一种计算机可读存储介质，其上存储有指令，该指令被执行时执行上述方法实施例中的备份方法。
作为本实施例的另一种形式，提供一种包含指令的计算机程序产品，当该计算机程序产品在计算机上运行时，使得该计算机执行时执行上述方法实施例中的备份方法。
本申请实施例再提供一种芯片系统，该芯片系统包括处理器，用于实现本发明实施例的技术方法。在一种可能的设计中，该芯片系统还包括存储器，用于保存本发明实施例必要的程序指令和/或数据。在一种可能的设计中，该芯片系统还包括存储器，用于处理器调用存储器中存储的应用程序代码。该芯片系统，可以由一个或多个芯片构成，也可以包含芯片和其 他分立器件，本申请实施例对此不作具体限定。
通过以上的实施方式的描述，所属领域的技术人员可以清楚地了解到，为描述的方便和简洁，仅以上述各功能模块的划分进行举例说明，实际应用中，可以根据需要而将上述功能分配由不同的功能模块完成，即将装置的内部结构划分成不同的功能模块，以完成以上描述的全部或者部分功能。
在本申请所提供的几个实施例中，应该理解到，所揭露的装置和方法，可以通过其它的方式实现。例如，以上所描述的装置实施例仅仅是示意性的，例如，所述模块或单元的划分，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式，例如多个单元或组件可以结合或者可以集成到另一个装置，或一些特征可以忽略，或不执行。另一点，所显示或讨论的相互之间的耦合或直接耦合或通信连接可以是通过一些接口，装置或单元的间接耦合或通信连接，可以是电性，机械或其它的形式。
所述作为分离部件说明的单元可以是或者也可以不是物理上分开的，作为单元显示的部件可以是一个物理单元或多个物理单元，即可以位于一个地方，或者也可以分布到多个不同地方。可以根据实际的需要选择其中的部分或者全部单元来实现本实施例方案的目的。
另外，在本申请各个实施例中的各功能单元可以集成在一个处理单元中，也可以是各个单元单独物理存在，也可以两个或两个以上单元集成在一个单元中。上述集成的单元既可以采用硬件的形式实现，也可以采用软件功能单元的形式实现。
所述集成的单元如果以软件功能单元的形式实现并作为独立的产品销售或使用时，可以存储在一个可读取存储介质中。基于这样的理解，本申请实施例的技术方案本质上或者说对现有技术做出贡献的部分或者该技术方案的全部或部分可以以软件产品的形式体现出来，该软件产品存储在一个存储介质中，包括若干指令用以使得一个设备(可以是单片机，芯片等)或处理器(processor)执行本申请各个实施例所述方法的全部或部分步骤。而前述的存储介质包括：U盘、移动硬盘、只读存储器(Read-Only Memory，ROM)、随机存取存储器(Random Access Memory，RAM)、磁碟或者光盘等各种可以存储程序代码的介质。
以上所述，仅为本申请的具体实施方式，但本申请的保护范围并不局限于此，任何在本申请揭露的技术范围内的变化或替换，都应涵盖在本申请的保护范围之内。因此，本申请的保护范围应以所述权利要求的保护范围为准。

Claims (19)

  1. 一种备份方法，其特征在于，所述方法包括：
    获取备份任务信息，所述备份任务信息包括待备份数据的信息、备份存储标识；
    获取所述备份存储标识指示的第一存储池的列表信息，所述列表信息用于指示所述第一存储池中存储单元的信息；所述第一存储池包括多个存储单元，所述多个存储单元位于至少两个存储集群；
    根据所述待备份数据的信息，从生产存储读取所述待备份数据；
    根据所述列表信息，将所述待备份数据存储在所述第一存储池中的一个或多个存储单元中。
  2. 根据权利要求1所述的方法，其特征在于，所述方法还包括：
    生成所述待备份数据的元数据，所述待备份数据的元数据中包括存储所述待备份数据的一个或多个存储单元的标识。
  3. 根据权利要求2所述的方法，其特征在于，所述备份任务信息还包括前序副本的元数据的存储位置信息，所述前序副本为所述待备份数据所属的备份对象前一次备份的副本；
    所述待备份数据的元数据中还包括所述前序副本中未被所述待备份数据修改的数据的存储位置信息；
    其中，存储所述待备份数据的存储单元与存储所述未被所述待备份数据修改的数据的存储单元位于不同的存储集群。
  4. 根据权利要求1-3任一项所述的方法，其特征在于，所述待备份数据属于第一备份文件，
    所述备份任务信息还包括所述第一备份文件中未被所述待备份数据修改的数据的信息。
  5. 根据权利要求2或3所述的方法，其特征在于，所述方法还包括：
    将所述待备份数据的元数据存储于第一存储单元；
    上报所述第一存储单元的信息。
  6. 根据权利要求1-5任一项所述的方法，其特征在于，所述备份存储标识包括：所述第一存储池的标识，或者，所述第一存储池对应的存储库的标识。
  7. 根据权利要求1-6任一项所述的方法，其特征在于，所述方法还包括：
    获取配置任务信息，所述配置任务用于指示将第二存储单元配置为第二存储池的资源；第二存储池包括多个存储单元，所述第二存储池包括的多个存储单元位于至少两个存储集群；
    在所述第二存储池的列表信息中记录所述第二存储单元的信息。
  8. 根据权利要求1-7任一项所述的方法，其特征在于，所述方法还包括：
    获取恢复任务信息，所述恢复任务信息包括待恢复数据的信息；
    获取存储所述待恢复数据的第三存储池的列表信息；
    根据所述待恢复数据的信息，获取所述待恢复数据的元数据，所述待恢复数据的元数据包括所述待恢复数据的存储位置信息；
    根据所述第三存储池的列表信息，以及所述待恢复数据的存储位置信息，读取所述待恢复数据。
  9. 一种备份方法，其特征在于，应用于备份系统，所述备份系统包括备份控制设备、备份存储设备以及生产存储设备；所述方法包括：
    所述备份控制设备向所述备份存储设备发送备份任务信息，所述备份任务信息包括待备份数据的信息、备份存储标识；
    所述备份存储设备获取所述备份存储标识指示的第一存储池的列表信息，所述列表信息用于指示所述第一存储池中存储单元的信息；所述第一存储池包括多个存储单元，所述多个存储单元位于至少两个存储集群；
    所述备份存储设备根据所述待备份数据的信息，从所述生产存储设备读取所述待备份数据；
    所述备份存储设备根据所述列表信息，将所述待备份数据存储在所述第一存储池中的一个或多个存储单元中。
  10. 一种备份装置，其特征在于，所述装置包括：
    第一获取单元，用于获取备份任务信息，所述备份任务信息包括待备份数据的信息、备份存储标识；
    第二获取单元，用于获取所述备份存储标识指示的第一存储池的列表信息，所述列表信息用于指示所述第一存储池中存储单元的信息；所述第一存储池包括多个存储单元，所述多个存储单元位于至少两个存储集群；
    读取单元，用于根据所述待备份数据的信息，从生产存储读取所述待备份数据；
    备份单元，用于根据所述列表信息，将所述待备份数据存储在所述第一存储池中的一个或多个存储单元中。
  11. 根据权利要求10所述的装置，其特征在于，所述装置还包括：
    第一处理单元，用于生成所述待备份数据的元数据，所述待备份数据的元数据中包括存储所述待备份数据的一个或多个存储单元的标识。
  12. 根据权利要求11所述的装置，其特征在于，所述备份任务信息还包括前序副本的元数据的存储位置信息，所述前序副本为所述待备份数据所属的备份对象前一次备份的副本；
    所述待备份数据的元数据中还包括所述前序副本中未被所述待备份数据修改的数据的存储位置信息；存储所述待备份数据的存储单元与存储所述未被所述待备份数据修改的数据的存储单元位于不同的存储集群。
  13. 根据权利要求10-12任一项所述的装置，其特征在于，所述待备份数据属于第一备份文件，所述备份任务信息还包括所述第一备份文件中未被所述待备份数据修改的数据的信息。
  14. 根据权利要求11或12所述的装置，其特征在于，
    所述备份单元还用于：将所述待备份数据的元数据存储于第一存储单元；
    所述装置还包括上报单元，用于上报所述第一存储单元的信息。
  15. 根据权利要求10-14任一项所述的装置，其特征在于，所述备份存储标识包括：所述第一存储池的标识，或者，所述第一存储池对应的存储库的标识。
  16. 一种备份系统，其特征在于，所述备份系统包括备份控制设备、备份存储设备以及生产存储设备；其中：
    所述备份控制设备用于：向所述备份存储设备发送备份任务信息，所述备份任务信息包括待备份数据的信息、备份存储标识；
    所述备份存储设备用于：获取所述备份存储标识指示的第一存储池的列表信息，所述列表信息用于指示所述第一存储池中存储单元的信息；所述第一存储池包括多个存储单元，所述多个存储单元位于至少两个存储集群；根据所述待备份数据的信息，从所述生产存储设备读取所述待备份数据；根据所述列表信息，将所述待备份数据存储在所述第一存储池中的一个或多个存储单元中。
  17. 一种计算设备，其特征在于，所述计算设备包括：处理器和存储器；
    所述存储器与所述处理器连接；所述存储器用于存储计算机指令，当所述处理器执行所述计算机指令时，使得所述计算设备执行如权利要求1-8中任一项所述的备份方法。
  18. 一种计算机可读存储介质，其特征在于，包括指令，当其在计算机上运行时，使得计算机执行权利要求1-8中任一项所述的备份方法。
  19. 一种计算机程序产品，其特征在于，当其在计算机上运行时，使得计算机执行权利要求1-8中任一项所述的备份方法。
PCT/CN2023/080062 2022-06-28 2023-03-07 一种备份方法及装置 Ceased WO2024001279A1 (zh)

Priority Applications (2)

Application Number Priority Date Filing Date Title
EP23829470.6A EP4528517A4 (en) 2022-06-28 2023-03-07 SAFETY METHOD AND DEVICE
US19/003,982 US20250138949A1 (en) 2022-06-28 2024-12-27 Backup method and apparatus

Applications Claiming Priority (4)

Application Number Priority Date Filing Date Title
CN202210749821 2022-06-28
CN202210749821.X 2022-06-28
CN202211080338.3 2022-09-05
CN202211080338.3A CN117312044A (zh) 2022-06-28 2022-09-05 一种备份方法及装置

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US19/003,982 Continuation US20250138949A1 (en) 2022-06-28 2024-12-27 Backup method and apparatus

Publications (1)

Publication Number Publication Date
WO2024001279A1 true WO2024001279A1 (zh) 2024-01-04

Family

ID=89248659

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2023/080062 Ceased WO2024001279A1 (zh) 2022-06-28 2023-03-07 一种备份方法及装置

Country Status (4)

Country Link
US (1) US20250138949A1 (zh)
EP (1) EP4528517A4 (zh)
CN (1) CN117312044A (zh)
WO (1) WO2024001279A1 (zh)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN117707857A (zh) * 2024-02-06 2024-03-15 合芯科技(苏州)有限公司 芯片研发数据备份方法、装置、计算机设备和存储介质

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN104424052A (zh) * 2013-09-11 2015-03-18 杭州信核数据科技有限公司 一种自动冗余的分布式存储系统及方法
CN106843773A (zh) * 2017-02-16 2017-06-13 天津书生云科技有限公司 存储方法和分布式存储系统
US20180101308A1 (en) * 2015-03-31 2018-04-12 International Business Machines Corporation Storing data utilizing a maximum accessibility approach in a dispersed storage network
CN110858124A (zh) * 2018-08-24 2020-03-03 华为技术有限公司 数据迁移方法及装置
CN114328029A (zh) * 2022-03-02 2022-04-12 苏州浪潮智能科技有限公司 一种应用资源的备份方法、装置、电子设备及存储介质

Family Cites Families (8)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP4267420B2 (ja) * 2003-10-20 2009-05-27 株式会社日立製作所 ストレージ装置及びバックアップ取得方法
US7529785B1 (en) * 2006-02-28 2009-05-05 Symantec Corporation Efficient backups using dynamically shared storage pools in peer-to-peer networks
US7606845B2 (en) * 2006-07-13 2009-10-20 International Business Machines Corporation Apparatus, systems, and method for concurrent storage to an active data file storage pool, copy pool, and next pool
US20080016390A1 (en) * 2006-07-13 2008-01-17 David Maxwell Cannon Apparatus, system, and method for concurrent storage pool migration and backup
US7953945B2 (en) * 2008-03-27 2011-05-31 International Business Machines Corporation System and method for providing a backup/restore interface for third party HSM clients
US9904603B2 (en) * 2013-11-18 2018-02-27 Actifio, Inc. Successive data fingerprinting for copy accuracy assurance
US9940377B1 (en) * 2014-09-16 2018-04-10 Amazon Technologies, Inc. Instant copies of storage volumes
CN114356650B (zh) * 2021-11-19 2025-05-02 科大讯飞股份有限公司 数据备份方法、装置、设备、系统及存储介质

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN104424052A (zh) * 2013-09-11 2015-03-18 杭州信核数据科技有限公司 一种自动冗余的分布式存储系统及方法
US20180101308A1 (en) * 2015-03-31 2018-04-12 International Business Machines Corporation Storing data utilizing a maximum accessibility approach in a dispersed storage network
CN106843773A (zh) * 2017-02-16 2017-06-13 天津书生云科技有限公司 存储方法和分布式存储系统
CN110858124A (zh) * 2018-08-24 2020-03-03 华为技术有限公司 数据迁移方法及装置
CN114328029A (zh) * 2022-03-02 2022-04-12 苏州浪潮智能科技有限公司 一种应用资源的备份方法、装置、电子设备及存储介质

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
See also references of EP4528517A4 *

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN117707857A (zh) * 2024-02-06 2024-03-15 合芯科技(苏州)有限公司 芯片研发数据备份方法、装置、计算机设备和存储介质
CN117707857B (zh) * 2024-02-06 2024-05-24 合芯科技(苏州)有限公司 芯片研发数据备份方法、装置、计算机设备和存储介质

Also Published As

Publication number Publication date
EP4528517A1 (en) 2025-03-26
US20250138949A1 (en) 2025-05-01
EP4528517A4 (en) 2025-12-17
CN117312044A (zh) 2023-12-29

Similar Documents

Publication Publication Date Title
US11734306B2 (en) Data replication method and storage system
US11455277B2 (en) Verifying snapshot integrity
CN107111533B (zh) 虚拟机集群备份
US8473462B1 (en) Change tracking for shared disks
US8756598B1 (en) Diskless virtual machine cloning by separately cloning a virtual drive and configuration data of a source virtual machine for combination into a cloned virtual machine
JP5461216B2 (ja) 論理ボリューム管理の為の方法と装置
US20260072606A1 (en) Container-based application processing
CN111949210B (zh) 分布式存储系统中元数据存储方法、系统及存储介质
CN110413444B (zh) 实现存储卷的一致性组的快照集
US10635547B2 (en) Global naming for inter-cluster replication
US11513914B2 (en) Computing an unbroken snapshot sequence
WO2012109876A1 (zh) 虚拟化数据备份方法、虚拟化数据重组方法、装置及系统
US10613947B2 (en) Saving and restoring storage devices using application-consistent snapshots
JP2014044553A (ja) プログラム、情報処理装置および情報処理システム
CN105988901A (zh) 数据复制方法及存储系统
CN115657969B (zh) 一种获取文件系统差异数据的方法、装置、设备及介质
CN114564339A (zh) 一种磁盘镜像文件跨平台迁移方法及系统
WO2024001279A1 (zh) 一种备份方法及装置
US8560577B1 (en) Method for coordinating stats collection and analysis among multiple hosts
CN118626432A (zh) 数据处理方法、存储系统、网络接口设备及存储介质
US20250252118A1 (en) Writeable partitions within read-only replicated records
US20250061216A1 (en) User indexing for identifying access to sensitive data
US20250061217A1 (en) User indexing for identifying access to sensitive data
EP4597334A1 (en) Writeable partitions within read-only replicated records
Andreas Böhm Igor Praher Jakob 0155477 0056228 igor@ bytelabs. org jp@ hapra. at

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

Country of ref document: EP

Kind code of ref document: A1

WWE Wipo information: entry into national phase

Ref document number: 2023829470

Country of ref document: EP

ENP Entry into the national phase

Ref document number: 2023829470

Country of ref document: EP

Effective date: 20241219

NENP Non-entry into the national phase

Ref country code: DE