TWI711288B - Remote backup method - Google Patents

Abstract

The disclosure provides a remote backup method, comprising: in response to a remote backup procedure corresponding to a block storage of a cloud service being triggered, obtaining metadata related to the block storage in a local database of the cloud service; determining whether the block storage has a backup history; in response to the block storage having no backup history, performing an incremental backup operation on the block storage to generate an incremental backup file; in response to the block storage having the backup history, performing a full backup operation on the block storage to generate a full backup file; compressing the incremental backup file or the full backup file into a compressed file, and sending the compressed file and the metadata to a remote backup storage space for remote backup.

Description

Remote backup method

The present invention relates to a data backup technology, and particularly relates to a remote backup method.

Since block storage is often large files of GB (gigabyte) or even TB (terabyte) level, if the block storage of all customers in the cloud storage service is regularly backed up to a remote location, it will not only occupy the storage space of the remote location. Moreover, because the network bandwidth across computer rooms is usually small, it is difficult to effectively back up the backup files to a remote location within a limited time.

In view of this, the present invention provides a remote backup method, which can be used to solve the above technical problems.

The present invention provides an offsite backup method, including: responding to triggering of an offsite backup procedure corresponding to a block storage in a cloud service, obtaining metadata associated with the block storage in a local database of the cloud service; and determining; Whether the block storage has a backup history; reflecting that the block storage has a backup history, perform an incremental backup operation on the block storage to generate an incremental backup file; reflecting that the block storage does not have a backup history, the block storage Storage Perform a full backup operation to generate a full backup file; export incremental backup files or full backup files as a backup file stored in blocks; compress the backup file into a compressed file, and compress the file and metadata Send to a remote backup storage space for remote backup.

Based on the above, the method of the present invention can back up the block storage in the cloud storage service to a remote storage environment. Moreover, in order to prevent the cloud service from losing the database and related metadata due to disasters, the method of the present invention can back up important database and metadata in the cloud service to a remote backup storage space. In addition, the present invention adopts incremental backup (Incremental backup) technology when storing the backup blocks. This technology can first complete the full backup and if data is added or deleted, the subsequent backup can only back up the difference from the previous backup. Therefore, the present invention can greatly reduce the bandwidth and backup time required for backup, and can also save the space for storing services in different places.

In order to make the above-mentioned features and advantages of the present invention more comprehensible, the following specific embodiments are described in detail in conjunction with the accompanying drawings.

Please refer to FIG. 1, which is a schematic diagram of a remote backup system according to an embodiment of the present invention. As shown in FIG. 1, the system 10 includes a user interface module 400, a remote backup service module 500 and a remote backup storage space 300.

In FIG. 1, the user interface module 400 may include a backup data management module 410, a backup setting module 420 and a backup restore trigger module 430. The remote backup service module 500 may include a scheduled backup module 510, a backup restore module 520, a remote mount module 530, a database 540, and a monitoring module 550.

The backup data management module 410 can present all the backed up metadata and block storage backup data history records, wherein the metadata source is provided by the metadata backup module 512 in the remote backup service module 500, and the backup The data history record is taken from the database 540 in the remote backup service module 500.

The backup setting module 420 can set the configuration file 501 in the remote backup service module 500, and all modules in the remote backup service module 500 are executed with reference to this configuration file 501. The remote mount module 530 can read the configuration file 501 and mount the remote backup storage space 300 by itself.

The schedule backup module 510 includes a backup rotation module 511, a metadata backup module 512, a backup module 513, and a backup recording module 514. The schedule backup module 510 can determine the schedule backup period and the backup time point according to the settings in the configuration file 501. In addition, the schedule backup module 510 can also control the backup module 513 and the metadata backup module 512 to perform backup.

In the embodiment of the present invention, the scheduled backup module 510 can periodically execute the offsite backup mechanism proposed by the present invention, which will be further described below.

Please refer to FIG. 2, which is a flowchart of a remote backup method according to an embodiment of the present invention. First, in step S210, in response to the offsite backup procedure corresponding to the block storage in the cloud service being triggered, the metadata backup module 512 can obtain the metadata associated with the block storage in the local database 101 of the cloud service 100 . In one embodiment, the maintenance personnel can fill in the backup service settings in the user interface module 400 and click Start backup to trigger the above remote backup procedure, but it is not limited to this. Correspondingly, the metadata backup module 512 can start to perform metadata backup. Specifically, the metadata backup module 512 can back up the metadata related to the block storage in the database 101 of the cloud service 100 to the remote mount module 530, but it is not limited to this. In different embodiments, the block storage described above may correspond to a virtual machine or a disk in the cloud storage service 200, but it may not be limited thereto.

In one embodiment, the metadata can be associated with the association between the block storage and the virtual host. For example, it can be found from the metadata that the block storage of virtual host A is B. When the backed-up block storage needs to be restored, this metadata can be used to install block B device into a virtual host of specification A, but The present invention may not be limited to this.

In addition, in some embodiments, the cloud service 100 may include multiple block storages belonging to different customers, and the scheduled backup module 510 can perform the same offsite backup operation for all block storages. In one embodiment, since it may not be necessary for every block storage to be backed up, the present invention can also set up a blacklist mechanism to allow maintenance personnel to store certain blocks that do not need to be backed up (for example, , Test data) added to the blacklist. In this way, the schedule backup module 510 may not perform the offsite backup mechanism proposed by the present invention for the block storage belonging to the blacklist, but it is not limited to this. Based on this, in one embodiment, after the offsite backup procedure corresponding to the block storage is triggered, the metadata backup module 512 can first determine whether the block storage belongs to the blacklist. If so, the scheduled backup module 510 can stop performing the offsite backup process of the block storage, otherwise, it can obtain the metadata associated with the block storage according to step S210, but it is not limited to this.

For the convenience of description, the following description will be based only on a single block storage, and a person with ordinary knowledge in the art should be able to deduce the operations performed on other block storage accordingly.

In one embodiment, after step S210 is performed, the schedule backup module 510 can perform steps S220 to S260 to perform the offsite backup procedure for the block storage. Specifically, in step S220, the backup module 513 can determine whether the block storage has a backup history. In one embodiment, if the block storage has been backed up previously, it means that it has a backup history. Correspondingly, one or more historical compressed files will be stored in the remote backup storage space 300. On the contrary, if the block storage has not been backed up before, it means that it does not have a backup history, but the invention is not limited to this.

In one embodiment, if the block storage has a backup history, in step S230, the backup module 513 can perform an incremental backup operation on the block storage to generate an incremental backup file. For example, when performing an incremental backup operation, if the considered block storage corresponds to a virtual machine, the backup module 513 can perform a snapshot operation on this virtual machine to retrieve the current system state of the virtual machine as Take a snapshot right now. After that, the backup module 513 can export the difference data between the current snapshot and a previous snapshot as the aforementioned incremental backup file, but it is not limited to this. In one embodiment, the aforementioned previous snapshot is, for example, the system state of the virtual machine captured during the previous backup, so it can be roughly understood as the last current snapshot, but the invention is not limited to this.

In different embodiments, the above-mentioned current snapshot is, for example, at least one of a crash-consistent snapshot, a file system consistent snapshot, and an application consistent snapshot, but may not be limited to this. In some embodiments, in the present invention, the customer can select one of the above three snapshot methods by himself, so as to control the backup module 513 to use the method selected by the customer to retrieve the snapshot.

Specifically, if the current snapshot is a crash-consistent snapshot, the snapshot will be restored when the customer's virtual machine or elastic block store (EBS) is busy I/O to the block store. The later file system may be damaged. Therefore, the present invention can also generate the current snapshot based on the principles of file system consistency and application program consistency.

Because the above functions can issue system calls to freeze I/O (ie, fsfreeze()) through the guest operating system (guest operating system) of the guest virtual machine when taking a snapshot or issue a system call to the application in the virtual machine The suspend instruction can ensure that the backup data is consistent no matter how frequently the I/O of the virtual machine is. And because the snapshot speed is very fast, the I/O suspend time in the virtual machine is very short, but the present invention is not limited to this.

In addition, in one embodiment, after the current snapshot is generated, the backup module 513 may further delete the current snapshot generated during the previous backup (ie, the previous snapshot). That is, the present invention can replace the current snapshot generated last time with the current snapshot generated this time.

Conversely, in another embodiment, if the block storage does not have a backup history, then in step S240, the backup module 513 can perform a full backup operation on the block storage to generate a full backup file. In this embodiment, if the block storage does not have a backup history, it means that the previous snapshot does not exist. In this case, the backup module 513 can directly export the captured current snapshot as a full backup file. For example, when performing a full backup operation, if the considered block storage corresponds to a virtual machine, the backup module 513 can perform a snapshot operation on the virtual machine to retrieve the current system state of the virtual machine as the current Snapshot. After that, the backup module 513 can export the difference data between the current snapshot and the (non-existent) previous snapshot as the aforementioned full backup file. Since the previous snapshot does not exist, the aforementioned difference data is the current snapshot itself, and the backup module 513 can directly export the current snapshot as the aforementioned full backup file, but the invention is not limited to this.

After generating the incremental backup file or the full backup file, in step S250, the backup module 513 can compress the incremental backup file or the full backup file into a compressed file, and send the compressed file and metadata to the remote backup storage space 300 For remote backup.

In one embodiment, the backup module 513 can use a multi-process method to compress the incremental backup file or the full backup file into a compressed file. For example, the backup module 513 can first divide the incremental backup file or the full backup file into multiple sub-compressed files, and then compress these sub-compressed files separately, and then synthesize them into one file as the above-mentioned compressed file. The invention may not be limited to this. In this way, in addition to speeding up the compression speed, the average compression rate of block storage can reach about 60%. In this way, not only can it reduce 40% of the storage space in the backup area, but it can also increase the backup speed and reduce the network bandwidth usage.

In an embodiment, the backup recording module 514 may record the storage path of the compressed file, the time when the backup is completed, the backup time point, and the name of the snapshot, etc., in the database 540. In this case, the backup data management module 410 can provide a corresponding user interface (for example, but not limited to a RESTful application interface) for the user to query the above data in the database 540, but it is not limited thereto.

In addition, after the backup module 513 stores the compressed files and metadata in the off-site backup storage space 300 to complete the off-site backup process, the backup rotation module 511 can also execute a rotation mechanism to adjust the off-site backup storage space 300 Storage situation. Specifically, in one embodiment, as time evolves, multiple historical compressed files can be stored in the remote backup storage space 300, which can be regarded as the backup module 513 previously performing the remote backup process and storing them in the remote backup. Previously compressed files in storage space 300.

In this case, after the compressed files and metadata are stored in the remote backup storage space 300, the backup rotation module 511 can determine whether the total number of the aforementioned historical compressed files and compressed files exceeds the file days limit of the remote backup storage space 300 (It can be set in the configuration file 501 by the maintenance personnel). In one embodiment, the file days limit is, for example, how many days of files can be kept in the remote backup storage space 300. Therefore, if the total number of the above-mentioned historical compressed files and compressed files exceeds the limit of 300 file days in the remote backup storage space, the backup rotation module 511 can remove the first historical compressed file (for example, the earliest historical compressed file) among the above-mentioned historical compressed files. Compressed file) and the second historical compressed file (for example, the second earliest historical compressed file) to replace the original first historical compressed file. In one embodiment, after performing the above merge operation, the backup rotation module 511 can update the database 540 to change the merged backup status to merged, so that the maintenance personnel will not see it from the user interface This backup process, but not limited to this.

In this embodiment, the first historical compressed file can be regarded as a full backup file. In this case, the storage space occupied by the remote backup storage space 300 can be reduced, and when backup and restoration are to be performed, because the number of file days is limited, the number of files that need to be merged during restoration will not exceed the number of days set by the rotation, so the restoration speed It is also faster, and the rotation mechanism can avoid the problem of inability to restore due to file damage. Because incremental backups need to be restored from the first backup in order to restore all incremental backup files, when there are dozens of incremental backups One of the incremental backup files is damaged, and the damaged backup and subsequent backups cannot be restored normally. In one embodiment, the above-mentioned rotation mechanism merges files every day. If a file error message appears during the merge, the backup rotation module 511 may send a warning message to notify the maintenance personnel for processing.

In one embodiment, the backup module 513 may first store the compressed files and metadata in the high-speed storage pool 310 of the off-site backup storage space 300 (for example, a small-space and fast storage pool constructed by a solid state drive). In this way, the storage speed of compressed files and metadata can be accelerated. In addition, after a period of time, the data in the high-speed storage pool 310 (for example, the above-mentioned compressed files and metadata) can be moved to the low-speed storage pool 320 of the off-site backup storage space 300 (for example, from a large and low-cost storage pool). A storage pool constructed by ordinary hard disks or tapes), but the invention is not limited to this.

In one embodiment, in addition, if a block storage cannot be snapshot, merged, or exported, it means that the block storage has been damaged. Therefore, the present invention can add the block storage to the blacklist And send an alarm to avoid backing up this block storage again.

In one embodiment, the maintenance personnel can find the backup data that needs to be restored through the backup data management module 410, and use the backup restoration trigger module 430 to select the backup data to be restored to the specified project in the specified customer.

In one embodiment, the backup restore module 520 is triggered by the backup restore trigger module 430 in the user interface module 400 to execute the restore process of the present invention. The details are as follows.

Please refer to FIG. 3, which is a flowchart of restoring block storage according to an embodiment of the present invention. In step S701, the maintenance personnel can select the block storage and backup history to be restored in the user interface. In step S702, the maintenance personnel can select designated customers and projects in the user interface. Correspondingly, the backup restoration module 520 can find the storage locations of the multiple historical compressed files corresponding to the block to be restored in the database 540 according to the information in steps S701 and S702.

After that, in step S703, the backup and restoration module 520 can decompress the required historical compressed files into multiple files to be merged. In one embodiment, if the maintenance personnel designate to store and restore the block to a specific point in time, the backup and restore module 520 can decompress all the historical compressed files between this specific point in time to obtain the aforementioned pending merge file. In addition, the aforementioned files to be merged may include, for example, one full backup and multiple incremental backups.

Then, in step S704, the backup and restoration module 520 can merge the above-mentioned files to be combined into a restoration file (for example, an image file). That is, the backup restoration module 520 can combine the aforementioned full backup and other incremental backups into a single file, that is, the aforementioned restoration file.

After that, in step S705, the backup and restoration module 520 can manage the restoration file to the cloud service image file space. For example, the backup and restoration module 520 can manage the restoration files through a virtualized infrastructure management (Virtualised Infrastructure Manager, vim) such as OpenStack or vCenter, but is not limited to this. In step S706, the backup and restoration module 520 can assign the aforementioned image file to the project of the designated customer. In step S707, the maintenance personnel can notify the customer to provide the installation service based on the above image file by themselves, and then complete the backup and restoration process.

In one embodiment, the monitoring module 550 can monitor the operating status of each module in the remote backup service module 500. If the remote mounting module 530 mounts the backup storage space 300 abnormally, or the backup module 513 If the snapshot creation fails, the monitoring module 550 will send an alarm through the cloud service 100 to notify the maintenance personnel to repair, but the present invention is not limited to this.

In an embodiment, the cloud service 100 may be provided by multiple microservices deployed on multiple physical servers in coordination, and the aforementioned microservices may provide a high availability active-active architecture. In the embodiment of the present invention, the above-mentioned microservices can cooperate to execute the remote backup program of the present invention. This not only speeds up the backup speed, but also when one physical server unexpectedly suspends or fails, the microservices in the other physical server can take over the offsite backup process that is being processed.

In one embodiment, the microservice on one physical server can monitor whether the microservice of another physical server has abnormal status, so as to determine whether other physical servers are suspended or malfunctioning. Specifically, the remote backup program of the present invention can have a database shared by each microservice, which can store the IP locations of all physical servers. In this case, each microservice can periodically obtain the IP locations of all physical servers from this database, and then obtain each other's status information through the RESTful application program interface that each microservice provides to check the status, but the invention is not limited to this.

In summary, the method of the present invention can regularly back up and manage user block storage in an efficient manner. Each block of storage is backed up by incremental backup and multi-process compression, and then moved to a remote storage space to reduce network bandwidth and storage space usage. In order to reduce the space occupation of the backup data and the efficiency of backup restoration, the backup technology of the present invention rotates the backup data, merges the old backup data, and maintains the number of backup data. And in the remote backup storage space to construct a hierarchical cache structure to accelerate the speed of data storage in the remote computer room and reduce the cost of large amounts of data storage.

In order to allow maintenance personnel to rebuild customer data into corresponding virtual hosts and disks in a new computer room (such as a remote computer room) after a disaster, the present invention will back up the metadata in the cloud service to the remote backup storage space. In this way, the reconstructed cloud service can associate the virtual machine with the block storage through metadata, build back to the cloud service, and restore the customer's virtual machine and disk, and then continue to provide services in the remote computer room.

In addition, the present invention provides a user interface module to allow maintenance personnel to manage the backups stored in all blocks in the cloud service. Maintenance personnel can browse all backup intermediate data and backup history through this interface, and can select specific backups Process, restore the specified backup file in an automated way. This backup restoration process includes file decompression, file merging to the specified backup process, file management, etc. All are restored in an automated manner. Maintenance personnel only need to select the specified backup file and process, and select Specify the user to trigger the automatic restore function. Relevant information will be recorded for each restoration, so as to prevent the maintenance personnel from restoring the data to the wrong user but not remembering which user to restore to.

Although the present invention has been disclosed in the above embodiments, it is not intended to limit the present invention. Anyone with ordinary knowledge in the technical field can make some changes and modifications without departing from the spirit and scope of the present invention. The scope of protection of the present invention shall be determined by the scope of the attached patent application.

10: System 100: cloud service 101: local database 200: Cloud storage service 300: Remote backup storage space 310: High-speed storage pool 320: Low-speed storage pool 400: User interface module 410: Backup data management module 420: Backup setting module 430: Backup and Restore Trigger Module 500: Remote backup service module 501: profile 510: Scheduled backup module 511: Backup Rotation Module 512: Metadata Backup Module 513: Backup Module 514: Backup record module 520: Backup and Restore Module 530: remote mount module 540: database 550: Monitoring module S210~S250, S701~S707: steps

Fig. 1 is a schematic diagram of a remote backup system according to an embodiment of the present invention. Fig. 2 is a flowchart of a remote backup method according to an embodiment of the present invention. FIG. 3 is a flow chart of the restoration of block storage according to an embodiment of the present invention.

S210~S250: steps

Claims (9)

An off-site backup method includes: responding to triggering of an off-site backup procedure corresponding to a block storage in a cloud service, obtaining metadata associated with the block storage in a local database of the cloud service, wherein the Cloud services are collaboratively provided by multiple microservices deployed on multiple physical servers. The microservices provide a high-availability active-active architecture. The microservices collaborate to execute the remote backup process, which is reflected in the physical servers If one of the physical servers fails, the microservices located in the other of the physical servers continue to execute the remote backup process; determine whether the block storage has a backup history; reflect that the block storage has the backup history , Perform an incremental backup operation on the block storage to generate an incremental backup file; reflect that the block storage does not have the backup history, perform a full backup operation on the block storage to generate a full backup file ; Compress the incremental backup file or the full backup file into a compressed file, and send the compressed file and the metadata to a remote backup storage space for remote backup, where the incremental backup file or the full backup file The step of compressing the compressed file includes: compressing the incremental backup file or the full backup file into the compressed file in a multi-process manner, wherein the remote backup storage space stores a plurality of historical compressed files, and the remote backup storage space has A file days limit, and the method further includes: reflecting that the compressed file is received in the remote backup storage space, and the calendars The total number of historical compressed files and the compressed file exceeds the limit of the number of days of the file, and the first historical compressed file and the second historical compressed file in the historical compressed files are merged to replace the first historical compressed file. The method described in item 1 of the scope of patent application, wherein the block storage corresponds to a single virtual machine or a single disk. For the method described in claim 1, wherein the step of performing the incremental backup operation on the block storage to generate the incremental backup file includes: taking a current snapshot of the block storage and storing the current snapshot The difference data between the next snapshot and a previous snapshot is exported as the incremental backup file, where the previous snapshot is included in the backup history. Such as the method described in item 3 of the scope of patent application, the method further includes deleting the previous snapshot. According to the method described in item 3 of the scope of patent application, the current snapshot is at least one of a crash-consistent snapshot, a file-consistent snapshot, and an application-consistent snapshot. For the method described in claim 1, wherein the step of performing the full backup operation on the block storage to generate the full backup file includes: taking a current snapshot of the block storage, and taking the current snapshot Export as the full backup file. The method described in item 1 of the scope of patent application, wherein it is reflected that an error occurred in a merging process of the first historical compressed file and the second historical compressed file, and the method further includes issuing a warning message . For example, the method described in item 1 of the scope of patent application further includes: recording the storage path of the compressed file, the backup completion time, the backup time point and the snapshot name in the local database, and accordingly provide an application program interface to For inquiries. For example, the method described in item 1 of the scope of patent application, wherein after the offsite backup procedure corresponding to the block storage is triggered, the method further includes: determining whether the block storage belongs to a blacklist; Block storage belongs to the blacklist, and the offsite backup procedure is not executed; in response to the block storage does not belong to the blacklist, the metadata associated with the block storage is obtained from the local database of the cloud service.

Images