CN112583868A

CN112583868A - Backup method, device, equipment and medium for cloud storage data

Info

Publication number: CN112583868A
Application number: CN201910927942.7A
Authority: CN
Inventors: 姚婷
Original assignee: Zhejiang Uniview Technologies Co Ltd
Current assignee: Zhejiang Uniview Technologies Co Ltd
Priority date: 2019-09-27
Filing date: 2019-09-27
Publication date: 2021-03-30
Anticipated expiration: 2039-09-27
Also published as: CN112583868B

Abstract

The invention discloses a backup method, a backup device, equipment and a backup medium for cloud storage data. Determining the file size and the file name of a file to be backed up matched with the backup parameters in at least two source end cloud direct storage virtual nodes, and a source end cloud direct storage virtual node and a source end data block to which the file to be backed up belongs according to the backup parameters; locking each source end data block storing a file to be backed up, instructing target end cloud storage equipment to create files with the same name and the same size according to the file size and the file name, and distributing target cloud direct storage virtual nodes and target data blocks; and sending each source end data block to the target end cloud storage device in parallel so as to write each source end data block into the target data block. The invention simplifies the backup structure when backing up the file data, can realize parallel backup based on the cloud direct storage virtual node, improves the performance and efficiency of file data backup, and can lock the file to ensure the consistency of the file and optimize the file backup process.

Description

Backup method, device, equipment and medium for cloud storage data

Technical Field

The embodiment of the invention relates to the technical field of data backup, in particular to a method, a device, equipment and a medium for backing up cloud storage data.

Background

When the video monitoring system is combined with the Cloud storage system, a monitoring device (such as a front-end camera and a rear-end hard disk video recorder) in the video monitoring system stores a generated multimedia file (such as a video file or a picture file) to a Cloud Direct Virtual (CDV) node in the Cloud storage system.

In an actual application process, in order to prevent a multimedia file from being lost due to an operation error of a system or a system failure, a file stored in one cloud storage system (i.e., a source cloud storage system) is usually copied to another storage medium (e.g., another cloud storage system, i.e., a target cloud storage system, etc.) to implement backup of the multimedia file. In the related art, when a file in a source cloud storage system is copied to a target cloud storage system, a data stream is read from the source cloud storage system through a Real Time Streaming Protocol (RTSP) mode based on a backup server, and then the data stream is written into the target cloud storage system, as shown in fig. 1.

However, in the above manner, since the multimedia file has the time sequence attribute, the backup server can only read data from one CDV node in the source cloud storage system at each time, so that the speed of file backup is slow and the time is long, and the file consistency is ensured by using the snapshot during the conventional file backup, while the multimedia file has the time sequence attribute, so that the file is fully covered during the file backup process, so that the file is inconsistent.

Disclosure of Invention

Embodiments of the present invention provide a method, an apparatus, a device, and a medium for backing up cloud storage data, which simplify a backup structure when backing up file data, and can implement parallel backup based on a cloud direct storage virtual node, thereby improving performance and efficiency of file data backup.

In a first aspect, an embodiment of the present invention provides a method for backing up cloud storage data, which is applied to a source cloud storage device including at least two source cloud direct storage virtual nodes, where the method includes:

determining the file size and the file name of a file to be backed up, which is matched with the backup parameters, in the at least two source end cloud direct storage virtual nodes according to the backup parameters, and at least one source end data block in the at least two source end cloud direct storage virtual nodes to which the file to be backed up belongs and each source end cloud direct storage virtual node, wherein the backup parameters at least comprise a monitoring equipment identifier and a backup time range of the monitoring equipment;

locking each source end data block storing the file to be backed up, sending the file size and the file name to target end cloud storage equipment to indicate the target end cloud storage equipment to create files with the same name and the same size in the target end cloud storage equipment according to the file size and the file name, and allocating at least two target cloud direct storage virtual nodes and at least one target data block in each target cloud direct storage virtual node to the files;

and sending each source end data block storing the file to be backed up to the target end cloud storage device in parallel to instruct the target end cloud storage device to write each source end data block storing the file to be backed up into the at least one target data block respectively.

In a second aspect, an embodiment of the present invention provides a backup method for cloud storage data, which is applied to a target cloud storage device including at least two target cloud direct storage virtual nodes, where the method includes:

creating files with the same name and the same size according to file sizes and file names received from a source end cloud storage device, and allocating at least two target cloud direct storage virtual nodes and at least one target data block in each target cloud direct storage virtual node for the files, wherein the file sizes are the file sizes of files to be backed up, the file names are the file names of the files to be backed up, the files to be backed up are stored in at least one source end data block respectively, and the source end data blocks are data blocks in the at least two source end cloud direct storage virtual nodes of the source end cloud storage device;

receiving each source data block which is transmitted by the source cloud storage device in parallel and stores the file to be backed up;

and respectively writing each source data block storing the file to be backed up into the at least one target data block.

In a third aspect, an embodiment of the present invention further provides a backup apparatus for cloud storage data, configured in a source cloud storage device including at least two source cloud direct storage virtual nodes, where the apparatus includes:

a first determining module, configured to determine, according to backup parameters, a file size and a file name of a file to be backed up in the at least two source-end cloud direct memory virtual nodes, where the file to be backed up matches the backup parameters, and at least one source-end data block in the at least two source-end cloud direct memory virtual nodes and each source-end cloud direct memory virtual node to which the file to be backed up belongs, where the backup parameters at least include a monitoring device identifier and a backup time range of the monitoring device;

the sending module is used for locking each source end data block storing the file to be backed up, sending the file size and the file name to target end cloud storage equipment so as to instruct the target end cloud storage equipment to create files with the same name and the same size in the target end cloud storage equipment according to the file size and the file name, and distributing at least two target cloud direct storage virtual nodes and at least one target data block in each target cloud direct storage virtual node for the files;

and the control module is configured to send each source end data block in which the file to be backed up is stored to the target end cloud storage device in parallel, so as to instruct the target end cloud storage device to write each source end data block in which the file to be backed up is stored into the at least one target data block respectively.

In a fourth aspect, an embodiment of the present invention further provides a backup apparatus for cloud storage data, configured to a target cloud storage device including at least two target cloud direct storage virtual nodes, where the apparatus includes:

the second determining module is configured to create files with the same name and the same size according to the file size and the file name received from the source-end cloud storage device, and allocate at least two target cloud direct storage virtual nodes and at least one target data block in each target cloud direct storage virtual node to the files, where the file size is a file size of a file to be backed up, the file name is a file name of the file to be backed up, the file to be backed up is stored in at least one source-end data block, and the source-end data blocks are data blocks in the at least two source-end cloud direct storage virtual nodes of the source-end cloud storage device;

the receiving module is used for receiving each source data block which is transmitted by the source cloud storage device in parallel and stores the file to be backed up;

and the writing module is used for respectively writing each source data block storing the file to be backed up into the at least one target data block.

In a fifth aspect, an embodiment of the present invention further provides a source cloud storage device, including:

one or more processors;

a storage device for storing one or more programs,

when the one or more programs are executed by the one or more processors, the one or more processors implement the method for backing up cloud storage data of a source cloud storage device including at least two source cloud direct storage virtual nodes according to any one of the embodiments of the present invention.

In a sixth aspect, an embodiment of the present invention further provides a target cloud storage device, including:

one or more processors;

a storage device for storing one or more programs,

when the one or more programs are executed by the one or more processors, the one or more processors implement the method for backing up cloud storage data, which is applied to a target cloud storage device including at least two target cloud direct storage virtual nodes, in any of the embodiments of the present invention.

In a seventh aspect, an embodiment of the present invention further provides a computer-readable storage medium, where a computer program is stored on the computer-readable storage medium, and when the computer program is executed by a processor, the computer program implements a backup method of cloud storage data applied to a source cloud storage device including at least two source cloud direct storage virtual nodes in any of the embodiments of the present invention.

In an eighth aspect, an embodiment of the present invention further provides a computer-readable storage medium, on which a computer program is stored, where the computer program, when executed by a processor, implements a method for backing up cloud storage data, where the method is applied to a target cloud storage device that includes at least two target cloud direct storage virtual nodes.

The technical scheme disclosed by the embodiment of the invention has the following beneficial effects:

the method comprises the steps of determining the file size and the file name of a file to be backed up, which are matched with backup parameters, in at least two source end cloud direct storage virtual nodes, and at least one source end data block in the source end cloud direct storage virtual nodes, wherein the file to be backed up belongs to the at least two source end cloud direct storage virtual nodes, locking each source end data block storing the file to be backed up, sending the file size and the file name of the file to be backed up to a target end cloud direct storage device, indicating the target end cloud storage device to create files with the same name and the same size in the target end cloud storage device according to the file size and the file name, allocating at least two target cloud direct storage virtual nodes and at least one target data block in each target cloud direct storage virtual node to the files, and then sending each source end data block storing the file to be backed up to the target end cloud storage device in parallel, and instructing the target end cloud storage device to write each source end data block storing the file to be backed up into at least one target data block respectively. Therefore, the backup structure during file data backup is simplified, parallel backup can be realized based on the cloud direct storage virtual nodes, the performance and the efficiency of file data backup are improved, files can be locked based on the time attribute of the file data, the consistency during file backup is determined, and the file backup process is optimized.

Drawings

Fig. 1 is a schematic diagram of an embodiment of backing up a file in a source end storage system to a target end cloud storage system by using a backup server in the related art;

FIG. 2 is a schematic structural diagram of a block resource provided in the present invention;

fig. 3 is a schematic flowchart of an embodiment of a backup method for cloud storage data according to the present invention;

fig. 4 is a schematic flowchart of another embodiment of a method for backing up cloud storage data according to the present invention;

fig. 5 is a flowchart of another embodiment of a method for backing up cloud storage data according to the present invention;

fig. 6 is a schematic diagram of a backup process when a file type to be backed up is a video according to the present invention;

fig. 7 is a schematic diagram of a backup process when a file type to be backed up is a picture according to the present invention;

fig. 8 is a schematic structural diagram of a cloud storage data backup device provided in the present invention;

fig. 9 is a schematic structural diagram of another embodiment of a cloud storage data backup device provided in the present invention;

fig. 10 is a schematic structural diagram of an embodiment of a source cloud storage device provided in the present invention.

Detailed Description

The embodiments of the present invention will be described in further detail with reference to the drawings and examples. It is to be understood that the specific embodiments described herein are merely illustrative of and not restrictive on the broad invention. It should be further noted that, for convenience of description, only some structures, not all structures, relating to the embodiments of the present invention are shown in the drawings.

The embodiment of the invention provides a cloud storage data backup method aiming at the problems that in the related art, when a backup server is used for reading a data stream from a source end cloud storage system based on an RTSP (real time streaming protocol) mode and then writing the data stream into a target end cloud storage system, the backup server can only read material data from a cloud direct storage virtual node in the source end cloud storage system at each moment due to the fact that a multimedia file has a time sequence attribute, so that the file backup speed is low, the time is long, file consistency is guaranteed by adopting a snapshot in the traditional file backup process, and the multimedia file has the time sequence attribute, so that the files are covered fully in the file backup process, and the files are inconsistent.

In the embodiment of the invention, the file size and the file name of a file to be backed up which are matched with backup parameters in at least two source end cloud direct storage virtual nodes are determined, at least one source end data block in the source end cloud direct storage virtual nodes and each source end cloud direct storage virtual node to which the file to be backed up belongs is determined, each source end data block storing the file to be backed up is locked, the file size and the file name of the file to be backed up are sent to a target end cloud direct storage device, the target end cloud storage device is instructed to create files with the same name and the same size in the target end cloud storage device according to the file size and the file name, at least two target cloud direct storage virtual nodes and at least one target data block in each target cloud direct storage virtual node are distributed to the files, and then each source end data block storing the file to be backed up is sent to the target end cloud storage device in parallel, and instructing the target end cloud storage device to write each source end data block storing the file to be backed up into at least one target data block respectively. Therefore, the backup structure during file data backup is simplified, parallel backup can be realized based on the cloud direct storage virtual nodes, the performance and the efficiency of file data backup are improved, files can be locked based on the time attribute of the file data, the consistency during file backup is determined, and the file backup process is optimized.

In order to clearly describe the cloud storage data backup method provided in the embodiment of the present invention, a cloud storage system in the embodiment of the present invention is first described below.

The Cloud Storage system in the embodiment of the present invention is also called a Cloud Direct Storage system (CDS), and is a distributed Cloud Storage system, which includes a Cloud Direct Storage Management (CDM) server and at least two Cloud Direct Virtual (CDV) nodes.

The CDV node may be an actual physical device, or may also be a virtual machine configured on the physical device, and is configured to store a file generated by the monitoring device. In this embodiment, the monitoring device may be, but is not limited to: a front-end camera, a network camera, a rear-end hard disk video recorder and the like.

It should be noted that each CDV node may include at least one data block, and the data block may store data, so that when the CDV node stores the file generated by the monitoring device, the file generated by the monitoring device is stored in the data block of the CDV node.

The CDM server is a storage management node in a CDS management solution, provides a storage virtualization management function, combines all CDV node spaces into a storage virtual pool, and provides mass storage space for the outside.

In actual use, the monitoring system may send a file generated by a certain monitoring device to the CDS, and the CDS may obtain at least two target CDV nodes from all CDV nodes based on a load balancing policy, and allocate at least one free data block in the at least two target CDV nodes based on a CDS-defined block-level space allocation algorithm, so as to store the file generated by the monitoring device in a distributed manner in at least one data block of the at least two target CDV nodes.

The method includes that at least one idle data block is automatically allocated to a file generated by the monitoring device based on a CDS (compact disc system) by a block-level space allocation algorithm, and specifically, space allocation on the block device can be directly managed by introducing a uniform allocation layer. And managing and distributing the block resources provided by the bottom layer according to the data blocks (slices) with the same size. As shown in fig. 2, there is formatting information and slice index before the chunk resource, and there is a file name index area after the chunk resource. And the slice indexes slice block information corresponding to the video or the picture. When video or pictures are written, the CDS self-defined block-level space allocation algorithm automatically allocates free slices, writes the video or pictures into the slices, and records the allocated slice addresses and offsets in slice indexes. When the file type is a video, recording the name of a video file, the slice address of the file and the offset in a file name index area; when the file type is a picture, the slice address, offset and length of the picture are recorded in a Uniform Resource Locator (URL) of the picture, and then a specific physical location can be accessed according to the URL.

The following describes in detail a backup method of cloud storage data according to an embodiment of the present invention with reference to fig. 3.

Fig. 3 is a schematic flowchart of an embodiment of a method for backing up cloud storage data according to the present invention, where the embodiment of the present invention is applicable to a scenario in which file data in a source cloud storage device is backed up, and the method may be executed by a backup apparatus configured to cloud storage data according to the embodiment of the present invention, where the apparatus may be implemented by software and/or hardware and may be applied to the source cloud storage device, where the source cloud storage device has a cloud storage system, and the cloud storage system includes at least two source cloud direct storage virtual nodes. The method specifically comprises the following steps:

s301, determining the file size and the file name of a file to be backed up in the at least two source end cloud direct memory virtual nodes, which are matched with the backup parameters, and at least one source end data block in the at least two source end cloud direct memory virtual nodes and each source end cloud direct memory virtual node to which the file to be backed up belongs according to the backup parameters, wherein the backup parameters at least include a monitoring device identifier and a backup time range of the monitoring device.

Wherein the monitoring device may be, but is not limited to: a front-end camera, a rear-end hard disk video recorder and the like. The monitoring device identifier refers to information that uniquely identifies the monitoring device, and may be, for example, a number, a serial number, and the like, and is not specifically limited herein.

The backup time range of the monitoring device may be set according to the actual application requirement, and is not specifically limited herein. For example, it is set by the week, or by the month, etc., and is not particularly limited herein.

Generally, a Video Management server (VM) is provided in a monitoring system, and the VM can centrally manage all devices in the monitoring system and schedule various Video monitoring services. That is to say, the embodiment may send the file backup trigger instruction to the source cloud storage device through the VM, so that the source cloud storage device executes the file backup operation according to the file backup trigger instruction.

When the file backup triggering instruction is sent by the VM, the file backup triggering instruction may be automatically triggered based on a predefined triggering period, or manually triggered on a VM display interface, which is not specifically limited herein.

In the embodiment of the invention, when the VM sends the file backup triggering instruction, the backup parameter can be carried in the instruction, so that the source cloud storage device obtains the backup parameter by analyzing the file backup triggering instruction. And then, determining whether the file name index area recorded by the source end CDV node comprises the backup parameter in all source end CDV nodes according to the backup parameter, if so, determining the file corresponding to the file name index area as a file to be backed up, inquiring the file size and the file name of the file to be backed up, and determining all the source end CDV nodes to which the file to be backed up belongs and at least one source end data block on each source end CDV node.

In this embodiment, the final file to be backed up may be formed by splicing files to be backed up in at least one source end data block on each source end CDV node. That is to say, the file to be backed up in at least one source end data block is the file segment of the file to be backed up finally.

The backup parameters in the embodiment of the present invention may further include: and the file type to be backed up comprises a video or a picture.

Because the types of the files to be backed up are different, the storage modes of the files to be backed up are different, and therefore, when determining the file size and the file name of the file to be backed up, and the source-end cloud directly-stored virtual node to which the file to be backed up belongs and at least one source-end data block in each source-end cloud directly-stored virtual node according to the type of the file to be backed up, the identifier of the monitoring device, and the backup time range of the monitoring device, which are included in the backup parameters, the method may include:

if the type of the file to be backed up is a video, scanning a file name index area stored by each source end cloud direct storage virtual node, determining the file to be backed up which comprises a monitoring equipment identifier and a backup time range of the monitoring equipment, determining the file size and the file name of the file, at least two source end cloud direct storage virtual nodes which store the file to be backed up and at least one source end data block in each source end cloud direct storage virtual node;

if the type of the file to be backed up is a picture, an initial uniform resource locator which comprises the monitoring equipment identification and the backup time range of the monitoring equipment is obtained from a database of a monitoring system, the file corresponding to the initial uniform resource locator is determined as the file to be backed up, and at least two source end cloud direct storage virtual nodes which store the file to be backed up and at least one source end data block in each source end cloud direct storage virtual node are determined.

In this embodiment, the initial Uniform Resource Locator (URL) can be represented by the following format:

monitoring system identification/YY/MM/DD/HH/monitoring device identification @0001.jpgdev ═ source cloud storage device identification & fid

The system comprises a monitoring device, a source cloud storage device, a storage system, a monitoring system and a monitoring device, wherein YY represents the year, MM represents the month, DD represents the date, HH represents the hour, fid represents the specific physical position of picture storage, and fid + sliceid + sliceops + len, wherein resid represents the resource ID, sliceod represents the data block ID, sliceops represents the offset of the picture in the data block, len represents the length of the picture file size, the monitoring system identification represents the identity information of the monitoring system, the monitoring device identification represents the identity information of the monitoring device, and the source cloud storage device identification represents the. For example, the monitoring system identification may refer to a name, number, or the like; the monitoring equipment identification can be a number, a serial number and the like; the source cloud storage device identifier may be a name, a number, and the like, and is not particularly limited herein.

That is, when the type of the file to be backed up is a picture, the source cloud storage device may store the picture to be backed up in a plurality of cloud direct storage virtual nodes of the source cloud storage device by hours based on the HH field in the uniform resource locator of the picture.

For example, if the type of the file to be backed up is a picture, the identifier of the monitoring device is number 99, and the backup time range is: when the number of the source cloud storage device is 23, the name of the monitoring system, 99, 13 hours in 1 month and 1 day in 2019, and 14 days in 1 month and 1 day in 2019, the source cloud storage device may obtain the number of the monitoring device from 99,2019 hours in 1 month and 1 day in 13 years in a database in the corresponding monitoring system to 14 hours in 1 month and 1 day in 2019, and the corresponding URL is the name of the monitoring system/2019/1/1/13-14/99 @0001.jpgdev ═ 23& fid. And then searching source end cloud direct memory virtual nodes storing the URL as the node 1 and the node 5, source data blocks 11 and 12 in the node 1 and source data blocks 9 and 12 in the node 5 according to the URL as the monitoring system name/2019/1/1/13-14/99 @0001.jpgdev ═ 23& fid, and determining that the source end cloud direct memory virtual nodes are the node 1 and the node 5, and at least one source end data block is the source data blocks 11 and 12 in the node 1 and the nodes 9 and 12 in the node 5.

For another example, if the type of the file to be backed up is a video, the identifier of the monitoring device is number 99, and the backup time range is: the source cloud storage device may scan file name index areas recorded by all source CDV nodes of the source cloud storage device according to numbers 99, 1/2019-1/31/2019, and if videos to be backed up matched with backup parameters are stored in data blocks 1 and 2 in the node 1, data blocks 3 in the node 3, data blocks 9 and 10 in the node 6, data blocks 2 in the node 8, and data blocks 10 in the node 9, it is determined that the videos to be backed up are stored in data blocks 1 and 2 in the node 1, data blocks 3 in the node 3, data blocks 9 and 10 in the node 6, and data blocks 2 in the node 8 and data blocks 10 in the node 9, respectively.

In an embodiment of the present invention, when the file type to be backed up is a video in this embodiment, before performing S201, the CDM server in the source cloud storage device may further record the obtained backup parameter, so that the source cloud storage device may continue to perform the file data backup operation according to the backup parameter recorded by the CDM server when an abnormality (for example, power failure) occurs in the file data backup process.

Further, when the CDM server records the obtained backup parameters, the backup parameters may also be synchronized into the memory of the load balancing policy, so that the source cloud storage device determines, according to the backup parameters in the memory of the load balancing policy, the file size and the file name of the file to be backed up, all source cloud directly-stored virtual nodes to which the file to be backed up belongs, and at least one source data block in each source cloud directly-stored virtual node.

In another embodiment of the present invention, when the type of the file to be backed up is a picture, and when the backup parameter is recorded, the obtained backup parameter is recorded by using the database in the monitoring system, so that when an abnormal condition (for example, power failure) occurs in a subsequent file data backup process, the source cloud storage device may continue to execute the file data backup operation according to the backup parameter recorded in the database.

Correspondingly, when the database in the monitoring system records the obtained backup parameters, the backup parameters can be synchronized into the memory of the load balancing strategy, so that the source cloud storage device determines the file size and the file name of the file to be backed up, all source cloud directly-stored virtual nodes to which the file to be backed up belongs and at least one source data block in each source cloud directly-stored virtual node according to the backup parameters in the memory of the load balancing strategy.

Optionally, in order to facilitate subsequent source cloud storage devices, each source data block storing a file to be backed up is accurately and unmistakably sent to the target cloud storage device, and the backup parameters in this embodiment may further include: and identifying the target cloud storage device. And the source end cloud storage device can determine the corresponding target end cloud storage device according to the target end cloud storage device identification.

The target cloud storage device identifier may be any information capable of uniquely identifying the identity of the target cloud storage device. Such as names, numbers, etc., which are not specifically limited herein.

S302, locking each source end data block storing the file to be backed up, sending the file size and the file name to a target end cloud storage device, instructing the target end cloud storage device to create files with the same name and the same size in the target end cloud storage device according to the file size and the file name, and allocating at least two target cloud direct storage virtual nodes and at least one target data block in each target cloud direct storage virtual node for the files.

In an actual application process, the monitoring device generates a new file in real time, so that the source cloud storage device needs to continuously store the new file into its source CDV node. However, the space of the source cloud storage device is limited, and in order to have enough space to store a new file, the source cloud storage device may predefine a file storage period for the stored file, for example, two weeks, one month, 6 months, and the like. And when the file storage period reaches a preset period, the stored old file can be covered by the new file so as to effectively store the new file.

In this embodiment, after determining at least two source-end cloud direct storage virtual nodes storing a file to be backed up and at least one source-end data block in each source-end cloud direct storage virtual node according to a file backup trigger instruction sent by a video management server, the file to be backed up is prevented from being fully covered by a new file. In this embodiment, each source end data block in which the file to be backed up is stored may also be locked based on the storage period of the file to be backed up, so as to ensure consistency of the file data to be backed up stored in the source end data block in the subsequent backup process, and avoid that the new file fully covers the file to be backed up, so that the data of the file to be backed up is lost, and the file data to be backed up cannot be normally backed up.

That is to say, when a source cloud storage device receives a new file, it is first determined whether a file to be backed up in each source data block in a source cloud direct storage virtual node is in a locked state. If the file to be backed up in any source end data block is in a locked state, it indicates that the file to be backed up in the data block cannot be covered by a new file; if the file to be backed up in any data block is in an unlocked state, it indicates that the file to be backed up in the data block can be fully covered by the new file, and at this time, the new file can be stored in the data block, so that the old file in the data block is fully covered by the new file.

Further, after each source end data block storing the file to be backed up is locked, the embodiment may send the file size and the file name of the file to be backed up in the source end data block to the target end cloud storage device through the source end cloud direct storage virtual node corresponding to the source end data block, so that the target cloud storage device allocates at least two target cloud direct storage virtual nodes and at least one target data block according to the same load balancing policy as the source end cloud storage device, so as to ensure that the source end cloud storage device and the target end cloud storage device can maintain the same data structure.

That is to say, in this embodiment, the target cloud live storage virtual nodes allocated by the target cloud storage device correspond to the source cloud live storage virtual nodes of the source cloud storage device one to one. Similarly, the allocated at least one target data block is also in one-to-one correspondence with at least one source data block of the source cloud storage device.

After the target cloud storage device determines at least two target cloud direct memory virtual nodes and at least one target data block in each target cloud direct memory virtual node, the target cloud direct memory virtual node address, the target data block start address and the resource ID may be sent to the source cloud storage device. The source end cloud storage device lays a foundation for the source end cloud storage device to backup the file to be backed up by acquiring at least two target cloud direct storage virtual node addresses, at least one target data block starting address and the resource ID sent by the target end cloud storage device.

And S303, sending each source end data block storing the file to be backed up to the target end cloud storage device in parallel, so as to instruct the target end cloud storage device to write each source end data block storing the file to be backed up into the at least one target data block respectively.

For example, the source cloud storage device may send each source data block storing the file to be backed up to the target cloud storage device in parallel, so that the target cloud storage device writes each source data block storing the file to be backed up into at least one target data block respectively.

In an optional implementation manner of the present invention, the source-side cloud direct memory virtual node to which each source-side data block belongs may be divided into a plurality of queues, and a multithread backup operation is performed according to a number of concurrent threads preset in the queues. The preset number of concurrent threads can be adaptively adjusted according to actual application. For example, 10 are transmitted in parallel at the same time, or 15 are transmitted in parallel at the same time, etc., and this is not particularly limited herein.

And sending each source end data block storing the file to be backed up to a target end cloud storage device in parallel based on a write Input Output (IO) interface of the source end cloud direct storage virtual node corresponding to each source end data block.

The method for backing up cloud storage data provided by the embodiment of the invention determines the file size and the file name of a file to be backed up in at least two source end cloud direct storage virtual nodes matched with backup parameters according to the backup parameters, at least two source end cloud direct storage virtual nodes to which the file to be backed up belongs and at least one source end data block in each source end cloud direct storage virtual node, locks each source end data block storing the file to be backed up, sends the file size and the file name of the file to be backed up to a target end cloud direct storage device to instruct the target end cloud storage device to create files with the same name and the same size in the target end cloud storage device according to the file size and the file name, allocates at least two target cloud direct storage virtual nodes and at least one target data block in each target cloud direct storage virtual node for the file, and then sends each source end data block storing the file to be backed up to the target end cloud storage device in parallel, and instructing the target end cloud storage device to write each source end data block storing the file to be backed up into at least one target data block respectively. Therefore, the backup structure during file data backup is simplified, parallel backup can be realized based on the cloud direct storage virtual nodes, the performance and the efficiency of file data backup are improved, files can be locked based on the time attribute of the file data, the consistency during file backup is determined, and the file backup process is optimized.

On the basis of the above embodiment, S303 is followed by: receiving a response message sent by the target end cloud storage device, wherein the response message indicates that each source end data block storing a file to be backed up has been written into at least one target data block by the target end cloud storage device; and based on the response message, unlocking each source end data block storing the file to be backed up.

That is to say, in this embodiment, by receiving a response message sent by the target cloud storage device, it is determined that the file to be backed up has completed the backup operation, and based on the response message, each source data block in which the file to be backed up is stored is unlocked, so that a subsequent new file can fully cover the file stored in the source data block. And after receiving the response message, the CDM server in the source cloud storage device, or a database in the monitoring system, may also delete the recorded backup parameters to provide a storage space for the subsequent new backup parameters.

On the basis of the above embodiment, S303 is followed by: the response message includes: backing up a uniform resource locator;

after receiving the response message sent by the target cloud storage device, the method further includes:

and sending the backup uniform resource locator to a database in a monitoring system so that the database records the backup uniform resource locator.

That is to say, when the type of the file to be backed up is a picture, the target cloud storage device sends the backup uniform resource locator to the source cloud storage device to send the backup uniform resource locator to the database in the monitoring system, and records the backup uniform resource locator through the database, so that the backed-up file data can be acquired by using the backup uniform resource locator after the subsequent initial backup uniform resource locator is deleted.

Fig. 4 is a schematic flowchart of another embodiment of a cloud storage data backup method provided by the present invention. The embodiment provides a specific implementation manner for the first embodiment, and as shown in fig. 4, the method for backing up cloud storage data may include the following steps:

s401, determining the file size and the file name of a file to be backed up in the at least two source end cloud direct memory virtual nodes, which are matched with the backup parameters, and at least one source end data block in the at least two source end cloud direct memory virtual nodes and each source end cloud direct memory virtual node to which the file to be backed up belongs according to the backup parameters, wherein the backup parameters at least include a monitoring device identification and a backup time range of the monitoring device.

S402, locking each source end data block storing the file to be backed up, sending the file size and the file name to a target end cloud storage device, instructing the target end cloud storage device to create files with the same name and the same size in the target end cloud storage device according to the file size and the file name, and allocating at least two target cloud direct storage virtual nodes and at least one target data block in each target cloud direct storage virtual node for the files.

And S403, based on a write input/output interface of a source cloud direct storage virtual node, sending each source data block storing the file to be backed up to the target cloud storage device in parallel, so as to instruct the target cloud storage device to write each source data block storing the file to be backed up into at least one target data block respectively.

Generally, a write input/output interface (IO interface) of a cloud direct memory virtual node is affected by the performance of processing data by a disk. Because the IO performance of the disk processing data is limited, the data is processed untimely when the IO performance exceeds the IO performance threshold. At this time, if a cache memory (cache) exists, data accumulation may occur, and if the cache does not exist, data loss may occur, for example, a service with a time-consuming requirement, such as a video.

To this end, the present embodiment may divide the cache memory of the write traffic of the cloud direct memory virtual node into a main cache memory and a backup cache memory. Therefore, when each source end data block storing the file to be backed up is sent to the target end cloud storage device in parallel, the write service and the read service can be realized by using the main cache memory of the source end cloud direct storage virtual node corresponding to each source end data block. When the total number of the source-side cloud direct memory virtual nodes executing the write service and the read service exceeds the number threshold of the main cache memory, it indicates that data processing influences the normal write service of the source-side cloud direct memory virtual nodes at this time, and data cannot be processed in time, so that data is lost in the main cache memory.

Therefore, the source-end cloud direct memory virtual node can utilize the backup cache memory to continuously execute the writing service and the reading service through the backup cache memory, and simultaneously monitor the data processing capacity of the backup cache memory. When the data processing amount of the backup cache memory reaches a preset threshold value, the backup cache memory is monitored to have the conditions that the data cannot be processed in time, the data accumulation is easy to occur and the like.

In order to ensure that the write service of the source cloud direct memory virtual node operates normally, the embodiment may reduce the ratio of the read service by adjusting the ratio of the read service to the write service of the source cloud direct memory virtual node, so as to ensure the normal operation of the write service.

For example, when the source cloud direct memory virtual node 12 simultaneously processes 50 write services and 50 read services, and the amount of data processed by the backup cache exceeds the preset threshold, the source cloud direct memory virtual node 12 is adjusted to have a write service of 60 and a read service of 40, so as to ensure that the write service of the source cloud direct memory virtual node can normally operate.

That is to say, the sending, in parallel, each source end data block storing the file to be backed up to the target end cloud storage device in this embodiment includes:

based on a write input/output interface of a source cloud direct storage virtual node, sending each source data block storing the file to be backed up to the target cloud storage device in parallel;

if the total data volume of the write service and the read service executed by any source-end cloud direct memory virtual node exceeds the data volume threshold value of the distributed main cache memory, the write service and the read service are executed by using the backup cache memory;

and if the data volume processed by the backup cache memory reaches a preset threshold value, reducing the read service proportion executed by the source-end cloud direct memory virtual node.

Further, in the embodiment of the present invention, the file type to be backed up includes a video or a picture. When the type of the file to be backed up is a picture and a plurality of pictures to be backed up are stored in one source end data block, based on a write input/output interface of a source end cloud direct storage virtual node, when each source end data block storing the file to be backed up is sent to a target end cloud storage device in parallel, the method comprises the steps of

And if at least two pictures to be backed up are stored in any source end data block, merging the at least two pictures to be backed up.

That is to say, when at least two pictures to be backed up are stored in any source end data block, in order to save the usage amount of the write input output interface of the source end cloud direct storage virtual node, by combining a plurality of pictures to be backed up to send the pictures through one write input output interface, all the pictures to be backed up in the source end data block can be read out by calling once.

According to the cloud storage data backup method provided by the embodiment of the invention, each source end data block storing a file to be backed up is sent to the target end cloud storage equipment in parallel through the write input/output interface based on the source end cloud direct storage virtual node, if the total data volume of write service and read service executed by any source end cloud direct storage virtual node exceeds the data volume threshold value of the distributed main cache memory, the write service and the read service are executed by using the backup cache memory, and if the processing data volume of the backup cache memory reaches the preset threshold value, the read service executed by the source end cloud direct storage virtual node is reduced. Therefore, the backup IO is dynamically adjusted to ensure normal writing of online video monitoring services in the file backup process, and a plurality of pictures to be backed up in the same source data block are combined to be read through an IO interface so as to improve the file data backup performance.

The method for backing up cloud storage data provided by the embodiment of the invention is described in detail below by taking a target cloud storage device as an example.

Fig. 5 is a flowchart of another embodiment of a method for backing up cloud storage data according to the present invention. The method can be executed by the backup device configured to the cloud storage data provided by the embodiment of the invention, and the device can be realized in a software and/or hardware manner and can be applied to the target cloud storage equipment, wherein the target cloud storage equipment is provided with a cloud storage system, and the cloud storage system comprises at least two target cloud direct storage virtual nodes. As shown in fig. 5, the method may include:

s501, files with the same name and the same size are created according to the file size and the file name received from a source end cloud storage device, at least two target cloud direct storage virtual nodes and at least one target data block in each target cloud direct storage virtual node are distributed to the files, wherein the file size is the file size of a file to be backed up, the file name is the file name of the file to be backed up, the file to be backed up is stored in at least one source end data block respectively, and the source end data blocks are data blocks in the at least two source end cloud direct storage virtual nodes of the source end cloud storage device.

The target cloud storage device and the source cloud storage device have the same data structure, namely the target cloud storage device distributes at least two target cloud direct storage virtual nodes and at least one target data block according to the same load balancing strategy as the source cloud storage device.

During specific implementation, the target cloud storage device may first create a file with the same file name and the same file size as the file name according to the file size and the file name, then allocate at least two target cloud direct memory virtual nodes according to the same load balancing policy as the source cloud storage device, and allocate at least one target data block in each target cloud direct memory virtual node.

The created file may include formatting information, a data block index, a data block data area, and a file name index area, as shown in fig. 2. In this embodiment, the file name index area stores identification information of files to be backed up. The identification information may refer to a name, a number, etc., and is not particularly limited herein.

That is to say, after the target cloud storage device allocates the target cloud direct storage virtual node and the target data block to the created file, information such as a target cloud direct storage virtual node address, a target data block start address, and a resource ID may be sent to the source cloud storage device, so that the source cloud storage device may send each source data block storing the file to be backed up to the target cloud storage device in parallel according to information such as at least two target cloud direct storage virtual node addresses, at least one target data block start address, and a resource ID.

S502, receiving each source data block, which is sent by the source cloud storage device in parallel and stores the file to be backed up.

S503, writing each source data block storing the file to be backed up into the at least one target data block respectively.

Optionally, in this embodiment, the files to be backed up in each source data block may be sequentially written into the corresponding target data block, so as to implement the backup of the files to be backed up.

In specific implementation, the target data block including the file with the same size and the same file name as the file to be backed up is determined according to the file size and the file name of the file to be backed up, and then the source data block storing the file to be backed up is written into the determined target data block.

According to the method for backing up the cloud storage data, files with the same name and the same size are created according to file size and file name received from a source end cloud storage device, at least two target cloud direct storage virtual nodes and at least one target data block in each target cloud direct storage virtual node are distributed for the files, each source data block of the files to be backed up is received and stored in the source end cloud storage device in parallel, and then each source data block of the files to be backed up is stored and written into at least one target data block. Therefore, the backup structure during file data backup is simplified, parallel backup can be realized based on the cloud direct storage virtual nodes, the performance and the efficiency of file data backup are improved, files can be locked based on the time attribute of the file data, the consistency during file backup is determined, and the file backup process is optimized.

On the basis of the above embodiment, S503 is followed by: updating an index area of a target file in the at least one target data block, and sending a response message to the source cloud storage device, where the response message indicates that each source data block storing a file to be backed up has been written into the at least one target data block by the target cloud storage device, respectively.

The index area comprises a data block index area and a file name index area.

In this embodiment, after the index region of the target file in at least one target data block is updated, the updated index information may be sent to the CDM server located in the target cloud storage device, so that when a subsequent technical user performs polling, the index data recorded in the data block in the CDM server is queried, thereby avoiding querying on a specific cloud direct-storage virtual node, simplifying a data checking mode, and improving a checking speed.

On the basis of the above embodiment, S503 is followed by: if the file type to be backed up is a picture, after writing each source end data block storing the file to be backed up into the at least one target data block, the method further includes:

and generating a backup uniform resource locator of the picture to be backed up, carrying the backup uniform resource locator in the response message, and sending the backup uniform resource locator to the source cloud storage device.

For more clearly explaining the embodiment of the present invention, a process of backing up a file to be backed up from a source cloud storage device to a target cloud storage device when the file to be backed up is a video or a picture in the embodiment of the present invention is specifically described below with reference to fig. 6 and 7.

First, as shown in fig. 6, when the type of the file to be backed up is a video, a CDM server in the source cloud storage device records acquired backup parameters, and synchronizes the backup parameters to the content of the load balancing policy, so that the source cloud storage device queries all source cloud direct storage virtual nodes (specifically, 610 marked in fig. 6) of itself through the backup parameters stored in the memory of the load balancing policy, to determine which source cloud direct storage virtual nodes store the video to be backed up (specifically, 620 marked in fig. 6) that matches the backup parameters, and further determine a plurality of source data blocks (specifically, 612 marked in fig. 6) that specifically store the file video to be backed up in the source cloud direct storage virtual nodes that store the video to be backed up. After the source end data blocks are determined, the source end data blocks storing the video to be backed up are locked, and according to a target cloud direct storage virtual node (specifically, 614 marked in fig. 6) determined by the target cloud storage device and at least one target data block (specifically, 616 marked in fig. 6), the source end data blocks storing the video to be backed up are sent to the target cloud storage device in parallel through the corresponding source end cloud direct storage virtual node for backup.

Furthermore, with reference to fig. 7, when the type of the file to be backed up is a picture, the obtained backup parameters are recorded by a database (e.g., 710 marked in fig. 7) in the monitoring system, and the backup parameters are synchronized into the content of the load balancing policy, so that the source cloud storage device queries all source cloud direct storage virtual nodes (e.g., 712 marked in fig. 7) of itself through the backup parameters stored in the memory of the load balancing policy, to determine which cloud direct storage virtual nodes store the picture to be backed up (e.g., 720 marked in fig. 7) that is matched with the backup parameters, and further determine a plurality of source data blocks (e.g., 712 marked in fig. 7) that store the data of the picture to be backed up in the source cloud direct storage virtual nodes that store the picture to be backed up. After the plurality of source end data blocks are determined, the plurality of source end data blocks storing the picture to be backed up are locked, a target cloud direct memory virtual node (specifically 714 marked in fig. 7) and at least one target data block (specifically 716 marked in fig. 7) are determined according to the target cloud storage device, and the plurality of source end data blocks storing the picture to be backed up are sent to the target cloud storage device in parallel through the corresponding source end cloud direct memory virtual node for backup. When at least two pictures to be backed up are stored in any source end data block, the read requests of the at least two pictures to be backed up are combined, so that the usage amount of a write input/output interface of a source end cloud direct storage virtual node is saved. In addition, after the target-side source storage device writes the picture to be backed up into at least one target data block, a backup uniform resource locator (specifically, 718 marked in fig. 7) of the picture to be backed up is also generated, and the backup uniform resource locator is sent to the database of the monitoring system, so as to record through the database, thereby facilitating the subsequent acquisition of the backed up picture based on the backup uniform resource locator.

In order to achieve the above object, an embodiment of the present invention provides a backup device for cloud storage data, where the backup device for cloud storage data is configured in a source cloud storage device including at least two source cloud direct storage virtual nodes.

Fig. 8 is a schematic structural diagram of a cloud storage data backup device provided in the present invention.

As shown in fig. 8, the backup apparatus for cloud storage data according to the embodiment of the present invention includes: a first determination module 810, a sending module 820, and a control module 830.

The first determining module 810 is configured to determine, according to backup parameters, a file size and a file name of a file to be backed up in the at least two source-end cloud direct storage virtual nodes, where the file to be backed up is matched with the backup parameters, and at least one source-end data block in the at least two source-end cloud direct storage virtual nodes and each source-end cloud direct storage virtual node to which the file to be backed up belongs, where the backup parameters at least include a monitoring device identifier and a backup time range of the monitoring device;

a sending module 820, configured to lock each source data block storing the file to be backed up, send the file size and the file name to a target cloud storage device, so as to instruct the target cloud storage device to create files with the same name and the same size in the target cloud storage device according to the file size and the file name, and allocate at least two target cloud direct storage virtual nodes and at least one target data block in each target cloud direct storage virtual node to the file;

a control module 830, configured to send each source end data block storing the file to be backed up to the target end cloud storage device in parallel, so as to instruct the target end cloud storage device to write each source end data block storing the file to be backed up into the at least one target data block respectively.

As an optional implementation manner of the embodiment of the present invention, the backup parameter further includes: the file type to be backed up comprises a video or a picture;

correspondingly, the first determining module 810 is specifically configured to:

if the type of the file to be backed up is a video, scanning a file name index area stored by each source end cloud direct memory virtual node, determining the file to be backed up which comprises a monitoring equipment identifier and a backup time range of the monitoring equipment, determining the file size and the file name of the file, at least two source end cloud direct memory virtual nodes which store the file to be backed up and at least one source end data block in each source end cloud direct memory virtual node;

As an optional implementation manner of the embodiment of the present invention, the sending module 820 is specifically configured to:

As an optional implementation manner of the embodiment of the present invention, if the type of the file to be backed up is a picture, the control module 830 is specifically configured to:

and based on the storage period of the file to be backed up, locking each source end data block in which the file to be backed up is stored.

As an optional implementation manner of the embodiment of the present invention, the method further includes: and a third determining module.

The first determining module is used for allocating at least two target cloud direct storage virtual nodes and at least one target data block to the target cloud storage device according to a load balancing strategy which is the same as that of the source cloud storage device.

As an optional implementation manner of the embodiment of the present invention, the backup apparatus for cloud storage data further includes: a receiving module and an unlocking module.

The receiving module is configured to receive a response message sent by the target cloud storage device, where the response message indicates that each source data block storing a file to be backed up has been written into at least one target data block by the target cloud storage device;

and the unlocking module is used for unlocking each source end data block storing the file to be backed up based on the response message.

As an optional implementation manner of the embodiment of the present invention, the response message includes: backing up a uniform resource locator;

the backup device of the cloud storage data further comprises: and a recording module.

The recording module is used for sending the backup uniform resource locator to a database in a monitoring system so that the database records the backup uniform resource locator.

It should be noted that the foregoing explanation of the embodiment of the cloud storage data backup method is also applicable to the cloud storage data backup apparatus of the embodiment, and the implementation principle is similar, and is not described herein again.

The cloud storage data backup device provided by the embodiment of the invention simplifies the backup structure during file data backup, can realize parallel backup based on the cloud direct storage virtual nodes, thereby improving the performance and efficiency of file data backup, and can lock files based on the time attribute of the file data to determine the consistency during file backup and optimize the file backup process.

Fig. 9 is a schematic structural diagram of another embodiment of a cloud storage data backup apparatus according to the present invention, wherein the cloud storage data backup apparatus is configured to a target cloud storage device including at least two target cloud direct storage virtual nodes.

As shown in fig. 9, the backup apparatus for cloud storage data according to the embodiment of the present invention includes: a second determining module 910, a receiving module 920, and a writing module 930.

The second determining module 910 is configured to create a file with the same name and the same size according to the size and the file name of a file received from a source cloud storage device, and allocate at least two target cloud direct storage virtual nodes and at least one target data block in each target cloud direct storage virtual node to the file, where the size of the file is the size of the file to be backed up, the file name is the file name of the file to be backed up, the file to be backed up is stored in at least one source data block, and the source data block is a data block in at least two source cloud direct storage virtual nodes of the source cloud storage device;

the receiving module 920 is configured to receive each source data block, which is sent by the source cloud storage device in parallel and stores the file to be backed up;

the file writing module 930 is configured to write each source data block storing the file to be backed up into the at least one target data block respectively.

As an optional implementation manner of the embodiment of the present invention, the apparatus further includes: and a fourth determination module.

The fourth determining module is configured to allocate, by the target cloud storage device, at least two target cloud direct storage virtual nodes and at least one target data block according to a load balancing policy that is the same as that of the source cloud storage device.

As an optional implementation manner of the embodiment of the present invention, the apparatus further includes: and updating the module.

The updating module is configured to update an index area of a target file in the at least one target data block, and send a response message to the source cloud storage device, where the response message indicates that each source data block storing a file to be backed up has been written into the at least one target data block by the target cloud storage device, respectively.

As an optional implementation manner of the embodiment of the present invention, if the file type to be backed up is a picture, the apparatus further includes: and a sending module.

The sending module is configured to generate a backup uniform resource locator of the picture to be backed up, carry the backup uniform resource locator in the response message, and send the response message to the source cloud storage device.

In order to achieve the above object, an embodiment of the present invention further provides a source cloud storage device.

Referring to fig. 10, an embodiment of the present invention provides a source cloud storage device 12, which includes: one or more processors 16; the storage device 28 is configured to store one or more programs, and when the one or more programs are executed by the one or more processors 16, the one or more processors 16 implement the backup method for cloud storage data applied to a source cloud storage device including at least two source cloud direct storage virtual nodes according to the embodiment of the present invention, including:

Of course, those skilled in the art will understand that the processor 16 may also implement the technical solution of the backup method applied to the cloud storage data of the source cloud storage device including at least two source cloud direct storage virtual nodes according to any embodiment of the present invention.

The source cloud storage device 12 shown in fig. 10 is only an example, and should not bring any limitation to the functions and the scope of use of the embodiment of the present invention.

As shown in fig. 10, the source cloud storage device 12 is in the form of a general purpose computing device. The components of the source cloud storage device 12 may include, but are not limited to: one or more processors or processors 16, a memory device 28, and a bus 18 that connects the various system components (including the memory device 28 and the processors 16).

Bus 18 represents one or more of any of several types of bus structures, including a memory bus or memory controller, a peripheral bus, an accelerated graphics port, and a processor or local bus using any of a variety of bus architectures. By way of example, such architectures include, but are not limited to, Industry Standard Architecture (ISA) bus, micro-channel architecture (MAC) bus, enhanced ISA bus, Video Electronics Standards Association (VESA) local bus, and Peripheral Component Interconnect (PCI) bus.

The source cloud storage device 12 typically includes a variety of computer system readable media. These media may be any available media that can be accessed by the source cloud storage 12 and includes both volatile and nonvolatile media, removable and non-removable media.

Storage 28 may include computer system readable media in the form of volatile memory, such as Random Access Memory (RAM)30 and/or cache memory 32. The source cloud storage 12 may further include other removable/non-removable, volatile/nonvolatile computer system storage media. By way of example only, storage system 34 may be used to read from and write to non-removable, nonvolatile magnetic media (not shown in FIG. 10, and commonly referred to as a "hard drive"). Although not shown in FIG. 10, a magnetic disk drive for reading from and writing to a removable, nonvolatile magnetic disk (e.g., a "floppy disk") and an optical disk drive for reading from or writing to a removable, nonvolatile optical disk (e.g., a CD-ROM, DVD-ROM, or other optical media) may be provided. In these cases, each drive may be connected to bus 18 by one or more data media interfaces. Storage 28 may include at least one program product having a set (e.g., at least one) of program modules that are configured to carry out the functions of embodiments of the invention.

A program/utility 40 having a set (at least one) of program modules 42 may be stored, for example, in storage 28, such program modules 42 including, but not limited to, an operating system, one or more application programs, other program modules, and program data, each of which examples or some combination thereof may comprise an implementation of a network environment. Program modules 42 generally carry out the functions and/or methodologies of the described embodiments of the invention.

The source cloud storage device 12 may also communicate with one or more external devices 14 (e.g., keyboard, pointing device, display 24, etc.), with one or more devices that enable a user to interact with the source cloud storage device 12, and/or with any device (e.g., network card, modem, etc.) that enables the source cloud storage device 12 to communicate with one or more other computing devices. Such communication may be through an input/output (I/O) interface 22. Also, the source cloud storage device 12 may also communicate with one or more networks (e.g., a Local Area Network (LAN), a Wide Area Network (WAN), and/or a public network, such as the internet) via the network adapter 20. As shown, the network adapter 20 communicates with the other modules of the source cloud storage device 12 over the bus 18. It should be appreciated that although not shown in the figures, other hardware and/or software modules may be used in conjunction with the source cloud storage device 12, including but not limited to: microcode, device drivers, redundant processing units, external disk drive arrays, RAID systems, tape drives, and data backup storage systems, among others.

The processing unit 16 executes various functional applications and data processing by running programs stored in the system storage 28, for example, implementing a backup method of cloud storage data applied to a source cloud storage device including at least two source cloud direct storage virtual nodes.

An embodiment of the present invention further provides a target cloud storage device, which includes: one or more processors; the storage device is used for storing one or more programs, and when the one or more programs are executed by the one or more processors, the one or more processors implement the backup method for cloud storage data applied to a target cloud storage device comprising at least two target cloud direct storage virtual nodes, which is provided by the embodiment of the invention, and the method comprises the following steps:

Of course, those skilled in the art can understand that the processor may also implement the technical solution of the backup method for cloud storage data applied to a target cloud storage device including at least two target cloud direct storage virtual nodes, which is provided by any embodiment of the present invention. The hardware structure and functions of the electronic device can be referred to the content explanation of the source cloud storage device.

An embodiment of the present invention further provides a computer-readable storage medium, on which a computer program is stored, where the computer program, when executed by a processor, is configured to perform a backup method applied to cloud storage data of a source cloud storage device including at least two source cloud direct storage virtual nodes, where the method includes:

Of course, the computer-readable storage medium provided in the embodiment of the present invention has computer-executable instructions that are not limited to the method operations described above, and may also perform related operations provided in any embodiment of the present invention for performing a backup method applied to cloud storage data of a source cloud storage device including at least two cloud direct storage virtual nodes.

Computer storage media for embodiments of the invention may employ any combination of one or more computer-readable media. The computer readable medium may be a computer readable signal medium or a computer readable storage medium. A computer readable storage medium may be, for example, but not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any combination of the foregoing. More specific examples (a non-exhaustive list) of the computer readable storage medium would include the following: an electrical connection having one or more wires, a portable computer diskette, a hard disk, a Random Access Memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing. In the context of this document, a computer readable storage medium may be any tangible medium that can contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device.

A computer readable signal medium may include a propagated data signal with computer readable program code embodied therein, for example, in baseband or as part of a carrier wave. Such a propagated data signal may take many forms, including, but not limited to, electro-magnetic, optical, or any suitable combination thereof. A computer readable signal medium may also be any computer readable medium that is not a computer readable storage medium and that can communicate, propagate, or transport a program for use by or in connection with an instruction execution system, apparatus, or device.

Program code embodied on a computer readable medium may be transmitted using any appropriate medium, including but not limited to wireless, wireline, optical fiber cable, RF, etc., or any suitable combination of the foregoing.

Computer program code for carrying out operations for aspects of the present invention may be written in any combination of one or more programming languages, including an object oriented programming language such as Java, Smalltalk, C + + or the like and conventional procedural programming languages, such as the "C" programming language or similar programming languages. The program code may execute entirely on the user's computer, partly on the user's computer, as a stand-alone software package, partly on the user's computer and partly on a remote computer or entirely on the remote computer or server. In the case of a remote computer, the remote computer may be connected to the user's computer through any type of network, including a Local Area Network (LAN) or a Wide Area Network (WAN), or the connection may be made to an external computer (for example, through the Internet using an Internet service provider).

An embodiment of the present invention further provides another computer-readable storage medium, on which a computer program is stored, where the computer program, when executed by a processor, implements a method for backing up cloud storage data of a target cloud storage device that includes at least two target cloud direct storage virtual nodes, where the method includes:

Of course, the computer-readable storage medium provided in the embodiment of the present invention has computer-executable instructions that are not limited to the method operations described above, and may also perform related operations in the backup method of cloud storage data applied to a target cloud storage device including at least two target cloud direct storage virtual nodes provided in any embodiment of the present invention. The description of the storage medium is explained with reference to the contents of the computer-readable storage medium in the above embodiments.

It is to be noted that the foregoing is only illustrative of the preferred embodiments of the present invention and the technical principles employed. It will be understood by those skilled in the art that the present invention is not limited to the particular embodiments described herein, but is capable of various obvious changes, rearrangements and substitutions as will now become apparent to those skilled in the art without departing from the scope of the invention. Therefore, although the present invention has been described in greater detail by the above embodiments, the present invention is not limited to the above embodiments, and may include other equivalent embodiments without departing from the spirit of the present invention, and the scope of the present invention is determined by the scope of the appended claims.

Claims

1. A backup method of cloud storage data is applied to a source cloud storage device comprising at least two source cloud direct storage virtual nodes, wherein the method comprises the following steps:

2. The method of claim 1, wherein the backup parameters further comprise: the file type to be backed up comprises a video or a picture;

correspondingly, determining the file size and the file name of the file to be backed up in the at least two source end cloud direct memory virtual nodes, which are matched with the backup parameters, and at least one source end data block in the at least two source end cloud direct memory virtual nodes and each source end cloud direct memory virtual node to which the file to be backed up belongs according to the backup parameters, includes:

3. The method of claim 2, wherein sending each source-side data block storing the file to be backed up to the target-side cloud storage device in parallel comprises:

4. The method according to claim 3, if the file type to be backed up is a picture, sending each source data block storing the file to be backed up to the target cloud storage device in parallel, including:

5. The method of claim 1, wherein locking each source data block storing the file to be backed up comprises: and based on the storage period of the file to be backed up, locking each source end data block in which the file to be backed up is stored.

6. The method of claim 1, wherein the target cloud storage device allocates at least two target cloud direct storage virtual nodes and at least one target data block according to a same load balancing policy as the source cloud storage device.

7. The method according to any one of claims 1-6, further comprising:

receiving a response message sent by the target end cloud storage device, wherein the response message indicates that each source end data block storing a file to be backed up has been written into at least one target data block by the target end cloud storage device;

and based on the response message, unlocking each source end data block storing the file to be backed up.

8. The method of claim 7, wherein the response message comprises: backing up a uniform resource locator;

9. The method for backing up cloud storage data is applied to a target cloud storage device comprising at least two target cloud direct storage virtual nodes, and comprises the following steps:

10. The method of claim 9, wherein the target cloud storage device allocates at least two target cloud direct storage virtual nodes and at least one target data block according to the same load balancing policy as the source cloud storage device.

11. The method according to claim 9, after writing each source data block storing the file to be backed up into the at least one target data block, further comprising:

updating an index area of a target file in the at least one target data block, and sending a response message to the source cloud storage device, where the response message indicates that each source data block storing a file to be backed up has been written into the at least one target data block by the target cloud storage device, respectively.

12. The method of claim 11, wherein if the type of the file to be backed up is a picture, after writing each source data block storing the file to be backed up into the at least one target data block, respectively, the method further comprises:

13. A backup apparatus for cloud storage data, configured to a source cloud storage device including at least two source cloud direct storage virtual nodes, wherein the apparatus includes:

14. The backup device of cloud storage data is configured to a target cloud storage device including at least two target cloud direct storage virtual nodes, wherein the device includes:

15. A source cloud storage device, comprising:

one or more processors;

a storage device for storing one or more programs,

when executed by the one or more processors, cause the one or more processors to implement the method of backing up cloud storage data as recited in any of claims 1-8.

16. A target cloud storage device, comprising:

one or more processors;

a storage device for storing one or more programs,

when executed by the one or more processors, cause the one or more processors to implement or perform the method for backing up cloud storage data as recited in any of claims 9-12.

17. A computer-readable storage medium on which a computer program is stored, the program, when executed by a processor, implementing the method for backing up cloud-stored data according to any one of claims 1 to 8.

18. A computer-readable storage medium on which a computer program is stored, the program, when executed by a processor, implementing the method for backing up cloud-stored data according to any one of claims 9 to 12.