CMS remote incremental backup method, device and system and storage medium

Abstract

The invention discloses a CMS remote incremental backup method, device and system and a storage medium, and relates to the technical field of incremental data processing. The method comprises the steps of running a CMS on a CMS server, deploying a backup management end, backing up a local database, forming a backup list file, calculating and packaging a backup file watermark of the backup list file, forming a backup list file compression package, establishing connection with the CMS server through a remote backup machine, and carrying out CMS remote incremental backup. Informing the remote backup machine of downloading and providing a file downloading interface through the backup management end; and deploying a backup client on the remote backup machine, receiving a downloading notification sent by the backup management end, checking the integrity of the backup list file, traversing the backup list file after downloading and decompression, and carrying out CMS remote incremental backup. According to the embodiment of the invention, the risk that the backup data is tampered or damaged is reduced, the backup time is shortened, and the accuracy and integrity of the backup data are ensured.

Description

Technical Field

[0001] The present application belongs to the technical field of incremental data processing, and in particular, relates to a CMS remote incremental backup method, device, system and storage medium. Background Art

[0002] During the deployment and operation of CMS (Content Management System), in addition to its own program files and configuration files, a large number of template files, static resources and data are generated. These files and data files are generally saved locally. Once the database is damaged or the local machine is damaged, it cannot be restored, which will cause system paralysis, data loss and other problems, thus causing immeasurable losses to users.

[0003] Currently, a large number of CMS system backups are mainly implemented by dumping data from the database and using the scheduled task corntab of the operating system. CMS data is exported and stored locally at regular intervals. If there is a need for off-site backup, the operating system's rsync or scp is used to synchronize data files to the remote backup machine, thereby achieving remote backup.

[0004] However, the current CMS backup mainly backs up the database files, and does not back up the template files, static resource files, and program files of the CMS system. It can only deal with the rapid recovery of data damage. Once the environment is damaged (such as the damage of the server running CMS), it cannot be restored; the backup operation mainly relies on the command execution of the operating system. Once the command fails (such as network jitter), there is no retry mechanism, resulting in backup failure. Secondly, there is a lack of file integrity verification during the copying process, resulting in the unusable damaged backup package; each export and copy is a complete data package, and incremental backup cannot be achieved, which is inefficient and occupies a large amount of disk space. Summary of the invention

[0005] The purpose of this application is to provide a CMS remote incremental backup method, device, system and storage medium, which ensures the integrity and reliability of backup data based on the settings of the backup plan, the download, verification, recovery and backup integrity check of backup files, and further enhances the security and stability of the backup process.

[0006] In order to achieve the above objectives, the solution of this application is:

[0007] In a first aspect, an embodiment of the present application provides a CMS remote incremental backup method, including:

[0008] CMS runs on the CMS server. The backup management terminal is deployed on the CMS server. The local database is backed up through the backup management terminal to form a backup list file. The backup file watermark of the backup list file is calculated and the backup list file is packaged to form a backup list file compression package. A connection is established between the remote backup machine and the CMS server to perform CMS remote incremental backup. The CMS remote incremental backup method includes:

[0009] Notify the remote backup machine through the backup management end to download the backup list file compression package and provide a file download interface; deploy the backup client on the remote backup machine, receive the download notification sent by the backup management end through the backup client, download and decompress the backup list file compression package, traverse the backup list file, and detect whether the backup list file exists in the local file. If so, calculate the local file watermark and the backup file watermark, and compare the local file watermark with the backup file watermark. If the local file watermark is the same as the backup file watermark, there is no need to download and continue the detection; if the local file watermark is different from the backup file watermark, download the backup list file and perform CMS remote incremental backup.

[0010] According to the above method of the embodiment of the present application, the following additional technical features may also be provided:

[0011] Furthermore, the CMS remote incremental backup method includes:

[0012] Set up a scheduled backup plan in CMS and determine the execution time for the backup. Define the table structure in the local database through XML metadata, and store the business data in the table structure in the backup list file in the form of an XML file. The backup list file includes a data file list, a template file list, a static resource list, and a program file list. Record the file name, file size, file generation time, and backup file watermark of each backup list file.

[0013] Furthermore, the backup file watermark of the backup list file is calculated, including:

[0014] A verification file is generated during packaging, and the backup list file is processed through the MD5 algorithm and the CRC32 algorithm to generate an MD5 value and a CRC32 value. The MD5 value and the CRC32 value are directly concatenated to obtain a backup file watermark.

[0015] Furthermore, a connection is established between the remote backup machine and the CMS server, including:

[0016] Check whether the remote backup machine can be connected. If it can be connected, call the remote backup machine interface, notify the remote backup machine through the backup management end to download the backup list file compression package and provide a file download interface; if it cannot be connected, configure the preset time interval and the preset number of connections, start the thread to initiate a connection request every preset time interval, and continue the preset number of connections. If it still cannot be connected, interrupt the connection and make an interruption notification.

[0017] Furthermore, the backup list file compressed package is downloaded and decompressed, including:

[0018] Verify whether the backup list file is complete based on the backup file watermark and the verification file. If the backup file watermark is consistent with the verification file, the backup list file is complete; if the backup file watermark is inconsistent with the verification file, the backup list file is incomplete and an alarm notification is issued.

[0019] Furthermore, the file download address is spliced ​​according to the file name, and multiple threads are started through the thread pool to download the file and save it to a temporary directory. If the file download fails, the preset retry step and the preset number of retries are configured, and the download is repeated according to the preset retry step and the preset number of retries. After the download is completed, the download file watermark is calculated and compared with the backup file watermark. If the download file watermark is the same as the backup file watermark, the download file is moved to the backup path and the download continues; if the download file watermark is different from the backup file watermark, the file is determined to be damaged and a failure log is recorded.

[0020] Furthermore, the CMS remote incremental backup method includes:

[0021] After traversing and downloading the backup list file, a backup snapshot file is generated, and the backup integrity is checked and the failure log is read. If the failure log is empty, the backup is complete; if the number of failure log records is less than the preset failure threshold, the backup is partially complete; otherwise, the backup is considered incomplete;

[0022] Perform a self-check on the remote backup machine to detect the disk usage of the remote backup machine. If the disk usage exceeds the preset usage threshold, an alarm notification will be issued.

[0023] In a second aspect, an embodiment of the present application provides a CMS remote incremental backup device, including:

[0024] The CMS server module is configured to run the CMS, deploy a backup management terminal on the CMS server, back up the local database through the backup management terminal, form a backup list file, calculate the backup file watermark of the backup list file, and pack the backup list file to form a backup list file compression package, establish a connection with a remote backup machine, notify the remote backup machine to download the backup list file compression package through the backup management terminal, and provide a file download interface;

[0025] The remote backup machine module is configured to deploy a backup client on a remote backup machine, receive a download notification sent by the backup management end through the backup client, download and decompress the backup list file compression package, traverse the backup list file, and detect whether the backup list file exists in the local file. If so, the local file watermark and the backup file watermark are calculated, and the local file watermark is compared with the backup file watermark. If the local file watermark is the same as the backup file watermark, there is no need to download and continue the detection; if the local file watermark is different from the backup file watermark, the backup list file is downloaded to perform CMS remote incremental backup.

[0026] In a third aspect, an embodiment of the present application provides a CMS remote incremental backup system, the system including a processor and a memory, the memory storing a computer program, the computer program being loaded and executed by the processor to implement the CMS remote incremental backup method provided in the first aspect of the embodiment of the present application.

[0027] In a fourth aspect, an embodiment of the present application provides a computer-readable storage medium, in which a computer program is stored. When the computer program is executed by a processor, it is used to implement the CMS remote incremental backup method as described in the first aspect of the embodiment of the present application.

[0028] Compared with the prior art, the CMS remote incremental backup method provided by the embodiment of the present application has the following beneficial technical effects:

[0029] The embodiment of the present application verifies the backup list file through MD5 and CRC32 algorithms, generates and records the backup file watermark, and effectively ensures the integrity and security of the backup data during transmission and storage. This method can significantly reduce the risk of data being tampered with or damaged during the backup process.

[0030] The embodiment of the present application adopts multi-thread download technology, and downloads multiple files simultaneously through the thread pool, thereby improving the efficiency of the backup operation. This parallel processing method significantly shortens the time required for backup, especially when processing large amounts of data.

[0031] The embodiment of the present application supports remote incremental backup, that is, only backing up the data that has changed since the last backup. This avoids repeated backup of unchanged data, saving storage space and backup time. At the same time, by detecting the consistency of the local file watermark and the backup file watermark, it intelligently determines which files need to be downloaded, further improving the accuracy and efficiency of the backup.

[0032] The embodiment of the present application provides multiple protection mechanisms to ensure the reliability of backup. This includes performing connectivity detection when the remote backup machine establishes a connection with the CMS server, and automatically retrying when the connection fails; when downloading a file fails, re-downloading it according to the preset retry step and number; after the backup is completed, a backup snapshot file is generated and the backup integrity is checked to ensure the accuracy and integrity of the backup data.

[0033] The embodiment of the present application supports a scheduled backup plan, and the execution time of the backup can be flexibly set according to actual needs. At the same time, the database table structure and business data are defined in the form of XML metadata, making the backup process more flexible and customizable.

[0034] The backup list file of the embodiment of the present application contains detailed file information (such as file name, size, generation time and watermark, etc.), which is convenient for administrators to query, manage and maintain backup data. In addition, through recording failure logs and alarm notification mechanisms, problems that may arise during the backup process can be discovered and solved in a timely manner. BRIEF DESCRIPTION OF THE DRAWINGS

[0035] Figure 1 A schematic diagram showing a flow chart of a CMS remote incremental backup method according to an embodiment of the present application is shown;

[0036] Figure 2 A structural block diagram of a CMS remote incremental backup device according to an embodiment of the present application is shown;

[0037] Figure 3 A structural block diagram of a computer device according to an embodiment of the present application is shown. DETAILED DESCRIPTION

[0038] In order to make the above-mentioned purposes, features and advantages of the present application more obvious and easy to understand, the specific implementation methods of the present application are described in detail below in conjunction with the accompanying drawings. It is to be understood that the specific embodiments described herein are only used to explain the present application, rather than to limit the present application. It should also be noted that, for ease of description, only some structures related to the present application are shown in the accompanying drawings, rather than all structures. Based on the embodiments in the present application, all other embodiments obtained by ordinary technicians in this field without making creative work are within the scope of protection of this application.

[0039] The terms "including" and "having" and any variations thereof in this application are intended to cover non-exclusive inclusions. For example, a process, method, system, product or device comprising a series of steps or units is not limited to the listed steps or units, but may optionally include steps or units not listed, or may optionally include other steps or units inherent to these processes, methods, products or devices.

[0040] Reference to "embodiments" in this application means that a particular feature, structure, or characteristic described in conjunction with the embodiments may be included in at least one embodiment of the present application. The appearance of the phrase in various locations in the specification does not necessarily refer to the same embodiment, nor is it an independent or alternative embodiment that is mutually exclusive with other embodiments. It is explicitly and implicitly understood by those skilled in the art that the embodiments described in this application may be combined with other embodiments.

[0041] CMS (Content Management System): A content management system is an application used to manage, publish and edit website content. It provides an intuitive and easy-to-use interface that allows users to create, edit, manage and publish content, including text, images, videos and other multimedia files. The core advantage of CMS is that it simplifies the content update process of websites and applications without requiring users to have professional programming or technical knowledge.

[0042] CMS server: CMS server is short for content management system server, which refers to the server used to run and host CMS software. CMS server helps website administrators easily create, edit and publish various contents of the website by providing a set of fully functional management interfaces. It is one of the basic infrastructures for the normal operation of CMS.

[0043] Remote backup machine: Remote backup machine usually refers to a device or system used to remotely store and back up data. In the data protection strategy of a website or system, remote backup machine plays a vital role. It can ensure that data can be restored in the event of an unexpected situation, thereby ensuring business continuity and data integrity.

[0044] The data file watermark (MD5+CRC32 value) is obtained by calculating the hash value of the data file. The embodiment of the present application combines the two algorithms of MD5 and CRC32 to enhance the verification capability of the data file. MD5 (Message-DigestAlgorithm 5) is a widely used cryptographic hash function that can generate a 128-bit (16-byte) hash value (usually represented by a 32-bit hexadecimal number). The MD5 algorithm is widely used in data integrity verification due to its high hashing and irreversibility. Applying the MD5 algorithm to the data file can generate the MD5 hash value of the file as a "fingerprint" of the file content. CRC32 (Cyclic Redundancy Check 32) is a verification algorithm for detecting errors that may occur after data transmission or storage. It generates a 32-bit checksum to check whether an error occurs during data transmission or storage. The CRC32 algorithm is faster in calculation speed than MD5, but its verification capability is slightly weaker.

[0045] In the embodiment of the present application, in order to more comprehensively verify the integrity of the data file, both MD5 and CRC32 algorithms are used. First, the MD5 and CRC32 hash values ​​are calculated for the data file respectively, and then these two values ​​are combined in some way (such as direct splicing) to form a data file watermark (MD5+CRC32 value). The advantage of this is that even if one of the algorithms is bypassed or cracked in some way, the other algorithm can still provide a certain degree of verification capability.

[0046] like Figure 1 As shown, the embodiment of the present application provides a CMS remote incremental backup method, including the following steps:

[0047] Step 101, run CMS on the CMS server, deploy the backup management terminal, back up the local database through the backup management terminal, form a backup list file, calculate the backup file watermark of the backup list file, and package the backup list file to form a backup list file compression package, establish a connection with the remote backup machine, notify the remote backup machine through the backup management terminal to download the backup list file compression package and provide a file download interface.

[0048] Running CMS on the CMS server and deploying the backup management client to perform a series of backup tasks involves multiple steps.

[0049] The backup management terminal of the embodiment of the present application will trigger the database backup task regularly or according to preset conditions to back up the structure and data of the database. During the backup process, one or more backup list files will be generated, which record the detailed information of all files involved in the backup process (such as data files, template files, static resources, program files, etc.), including file name, size, generation time, etc. In addition, the backup file watermark of each file will be recorded for subsequent data integrity verification.

[0050] In order to save storage space and facilitate transmission, the backup management terminal will package the backup list file and its related files into a compressed package. During the packaging process, a verification file will be generated, and the backup list file will be processed through the MD5 algorithm and CRC32 algorithm to generate the MD5 value and CRC32 value, and these two values ​​will be directly spliced ​​to obtain the backup file watermark. This watermark is used to verify the integrity and correctness of the backup file later.

[0051] The backup management end will establish a network connection with the remote backup machine, usually using FTP, SFTP, SCP and other protocols for data transmission. Before establishing the connection, a connectivity check will be performed to ensure that the remote backup machine is reachable. Once the backup list file compression package is ready, the backup management end will send a download notification to the remote backup machine through the established connection. The backup management end will provide one or more file download interfaces (such as HTTP download links, FTP server addresses, etc.) for the remote backup machine to use to download the backup list file compression package.

[0052] In order to automate the backup process, a scheduled backup plan can be set in the CMS. This includes specifying the execution time of the backup (such as 1 a.m. every day), the frequency of the backup (such as once a day, once a week, etc.), etc. In order to more flexibly define and store the database table structure and business data, the embodiment of the present application uses XML format to describe this information. During the backup process, the business data in the table structure will be stored in the backup list file in the form of an XML file to facilitate subsequent recovery and migration.

[0053] For each backup list file, detailed information such as its file name, file size, and file generation time will be recorded for easy management and query. As mentioned earlier, the backup file watermark generated by the MD5 and CRC32 algorithms will also be recorded to verify the integrity and correctness of the backup data. This process ensures that the CMS data can be regularly and securely backed up to the remote backup machine and can be quickly restored when needed, thereby ensuring the stability of the system and the security of the data.

[0054] Step 102, deploy a backup client on the remote backup machine, receive the download notification sent by the backup management end through the backup client, download and decompress the backup list file compression package, traverse the backup list file, and detect whether the backup list file exists in the local file. If so, calculate the local file watermark and the backup file watermark, and compare the local file watermark with the backup file watermark. If the local file watermark is the same as the backup file watermark, there is no need to download and continue the detection; if the local file watermark is different from the backup file watermark, download the backup list file and perform CMS remote incremental backup.

[0055] The embodiment of the present application uses the backup client to traverse each item in the backup list file and check one by one whether the corresponding file already exists locally. For existing files, the local file watermark is calculated (also using MD5 and CRC32 algorithms) and compared with the backup file watermark. The backup client software is installed and configured on the remote backup machine so that it can communicate and collaborate with the backup management terminal on the CMS server.

[0056] Select the appropriate backup client software and ensure its compatibility with the CMS server. Install the backup client software on the remote backup machine and configure it according to the requirements of the CMS server. Configure the network settings of the backup client, including the IP address, port number, authentication information, etc., to ensure that it can successfully connect to the CMS server. Verify whether the backup client is successfully installed and configured, and perform necessary debugging and optimization.

[0057] The backup client receives the download notification from the backup management terminal on the CMS server and downloads the backup list file compressed package. The backup client continuously listens for notifications from the CMS server. Once a download notification is received, the backup client parses the notification content, obtains the download link and related information of the backup list file compressed package, and uses HTTP, FTP and other protocols to download the backup list file compressed package from the CMS server. During the download process, you may need to verify the validity of the download link and handle network fluctuations.

[0058] Ensure that the downloaded backup list file has not been tampered with or damaged during transmission. Read the verification file provided with the compressed package to obtain the MD5, CRC32 and other verification values ​​of the backup list file. Use appropriate tools to calculate the MD5, CRC32 and other verification values ​​of the downloaded backup list file. Compare the calculated verification value with the value in the verification file. If the two are consistent, the backup list file is complete; if they are inconsistent, an alarm notification is issued and it may be necessary to download it again.

[0059] Decompress the compressed backup list file to a specified directory for subsequent processing. Use a compression tool (such as tar, zip, etc.) to decompress the compressed package of the backup list file to a specified directory. Ensure the security of the decompression path to avoid overwriting important files or leaking sensitive information.

[0060] Perform CMS remote incremental backup based on the contents of the backup list file. Traverse each entry in the backup list file and check whether the corresponding backup file exists locally. If the file exists, calculate the MD5, CRC32 and other check values ​​of the local file and compare them with the check values ​​in the backup list file. If the two are consistent, there is no need to download again; if they are inconsistent, download the latest backup file from the CMS server. Use multi-threading or thread pool technology to improve download efficiency and handle download failures, including retry mechanisms. After the download is complete, verify the integrity of the downloaded file again. Move the verified files to the backup path to complete the incremental backup.

[0061] If the local file watermark is different from the backup file watermark, it means that the file has changed since the last backup, so you need to download the latest version of the file from the CMS server for incremental backup. If the file watermarks are the same, you don't need to download it again, saving bandwidth and time.

[0062] To improve download efficiency, the backup client will splice the download address according to the file name, and start multiple threads through the thread pool to download multiple files at the same time. These files are temporarily stored in a temporary directory for subsequent processing. If the download fails due to network fluctuations or other reasons during the download process, the backup client will configure the preset retry step size and retry times to automatically retry the download. After each retry, the watermark of the downloaded file will be recalculated and compared with the watermark of the backup file to ensure file integrity.

[0063] After traversing and downloading all backup manifest files, the backup client generates a backup snapshot file for quick recovery and checks the integrity of the entire backup process. After traversing and downloading all backup manifest files, a backup snapshot file is generated. Read the failure log to check whether there are any file download failures or verification failures. Determine the integrity of the backup based on the content of the failure log: if the failure log is empty, the backup is complete; if the number of failure log records is less than the preset failure threshold, the backup is partially complete; otherwise, the backup is considered incomplete.

[0064] Specifically, the backup snapshot is prompted based on the actual verification situation to better judge the validity of the backup, as shown in the following table:

[0065] Table 1

[0066]

[0067] To determine the number of damaged and missing files, you can read the damaged file list and failed file list. The snapshot package marked with a green check mark is completely credible and can be used directly for recovery; the snapshot package marked with a yellow exclamation mark has some missing files, but can be used in an emergency, and the missing files can be uploaded in other ways; the snapshot package marked with a red cross is untrustworthy and cannot be directly restored. It is only used to backup a file. The number 50 can be modified in the configuration file serVerbackup.properties and configured according to the actual situation.

[0068] By reading the failure log, you can determine whether there is file corruption or download failure during the backup process. Based on the number of records in the failure log, you can evaluate the completeness of the backup. In order to prevent backup failures due to insufficient disk space, the backup client will also perform self-checks on the disk usage of the remote backup machine and check key indicators such as disk usage. If the disk usage exceeds the preset usage threshold, an alarm will be issued immediately so that the administrator can take timely measures, as shown in the following table:

[0069] Table 2

[0070]

[0071]

[0072] like Figure 2 As shown, the embodiment of the present application provides a CMS remote incremental backup device, including a CMS server module 201 and a remote backup machine module 202, wherein:

[0073] The CMS server module 201 is configured to run the CMS, deploy a backup management terminal on the CMS server, back up the local database through the backup management terminal, form a backup list file, calculate the backup file watermark of the backup list file, and pack the backup list file to form a backup list file compression package, establish a connection with a remote backup machine, notify the remote backup machine to download the backup list file compression package through the backup management terminal, and provide a file download interface;

[0074] The remote backup machine module 202 is configured to deploy a backup client on a remote backup machine, receive a download notification sent by the backup management end through the backup client, download and decompress the backup list file compression package, traverse the backup list file, and detect whether the backup list file exists in the local file. If so, the local file watermark and the backup file watermark are calculated, and the local file watermark is compared with the backup file watermark. If the local file watermark is the same as the backup file watermark, there is no need to download and continue the detection; if the local file watermark is different from the backup file watermark, the backup list file is downloaded to perform CMS remote incremental backup.

[0075] The CMS remote incremental backup device of the embodiment of the present application can be a computer device, or a component in the computer device, such as an integrated circuit or a chip. The computer device can be a terminal, or other devices other than a terminal. Exemplarily, the computer device can be a mobile phone, a tablet computer, a laptop computer, a PDA, a vehicle-mounted computer device, a mobile Internet device (Mobile Internet Device, MID), an ultra-mobile personal computer (Ultra-Mobile Personal Computer, UMPC), a netbook or a personal digital assistant (Personal Digital Assistant, PDA), etc. It can also be a server, a network attached storage (Network Attached Storage, NAS), a personal computer (Personal Computer, PC), etc., and the embodiment of the present application does not make specific limitations.

[0076] The CMS remote incremental backup device provided in the embodiment of the present application can achieve Figure 1 To avoid repetition, the various processes implemented in the CMS remote incremental backup method embodiment are not described here.

[0077] The present application also provides a computer device, such as Figure 3 As shown, the computer device includes a processor 301 and a memory 302. The memory 302 stores programs or instructions that can be run on the processor 301. When the program or instruction is executed by the processor 301, the various steps of the above-mentioned CMS remote incremental backup method are implemented, and the same technical effect can be achieved. To avoid repetition, it will not be repeated here.

[0078] It should be noted that the computer device in the embodiment of the present application includes the above-mentioned mobile computer device and non-mobile computer device.

[0079] The memory 302 can be used to store software programs and various data. The memory 302 may mainly include a first storage area for storing programs or instructions and a second storage area for storing data, wherein the first storage area may store an operating system, an application program or instructions required for at least one function (such as a sound playback function, an image playback function, etc.), etc. In addition, the memory 302 may include a volatile memory or a non-volatile memory, or the memory 302 may include both volatile and non-volatile memories. Among them, the non-volatile memory may be a read-only memory (ROM), a programmable read-only memory (PROM), an erasable programmable read-only memory (EPROM), an electrically erasable programmable read-only memory (EEPROM), or a flash memory. The volatile memory may be a random access memory (RAM), a static random access memory (SRAM), a dynamic random access memory (DRAM), a synchronous dynamic random access memory (SDRAM), a double data rate synchronous dynamic random access memory (DDRSDRAM), an enhanced synchronous dynamic random access memory (ESDRAM), a synchronous link dynamic random access memory (SLDRAM) and a direct memory bus random access memory (DRRAM). The memory 302 of the embodiment of the present application includes but is not limited to these and any other suitable types of memory.

[0080] The processor 301 may include one or more processing units; optionally, the processor 301 integrates an application processor and a modem processor, wherein the application processor mainly processes operations related to an operating system, a user interface, and application programs, and the modem processor mainly processes wireless communication signals, such as a baseband processor. It is understandable that the modem processor may not be integrated into the processor 301.

[0081] An embodiment of the present application also provides a readable storage medium, on which a program or instruction is stored. When the program or instruction is executed by a processor, each process of the above-mentioned CMS remote incremental backup method embodiment is implemented, and the same technical effect can be achieved. To avoid repetition, it will not be repeated here.

[0082] An embodiment of the present application also provides a chip, which includes a processor and a communication interface, the communication interface and the processor are coupled, and the processor is used to run programs or instructions to implement the various processes of the above-mentioned CMS remote incremental backup method embodiment, and can achieve the same technical effect. To avoid repetition, it will not be repeated here.

[0083] It should be understood that the chip mentioned in the embodiments of the present application can also be called a system-level chip, a system chip, a chip system or a system-on-chip chip, etc.

[0084] An embodiment of the present application also provides a computer program product, which is stored in a storage medium. The program product is executed by at least one processor to implement the various processes of the above-mentioned CMS remote incremental backup method embodiment, and can achieve the same technical effect. To avoid repetition, it will not be repeated here.

[0085] It should be noted that, in the present application, the terms "comprise", "include" or any other variant thereof are intended to cover non-exclusive inclusion, so that a process, method, article or device including a series of elements includes not only those elements, but also other elements not explicitly listed, or also includes elements inherent to such process, method, article or device. In the absence of further restrictions, an element defined by the sentence "comprises one..." does not exclude the presence of other identical elements in the process, method, article or device including the element. In addition, it should be noted that the scope of the method and device in the embodiment of the present application is not limited to performing functions in the order shown or discussed, and may also include performing functions in a substantially simultaneous manner or in reverse order according to the functions involved, for example, the described method may be performed in an order different from that described, and various steps may also be added, omitted, or combined. In addition, the features described with reference to certain examples may be combined in other examples.

[0086] The embodiments of the present application are described above in conjunction with the accompanying drawings, but the present application is not limited to the above-mentioned specific implementation methods. The above-mentioned specific implementation methods are merely illustrative and not restrictive. Under the guidance of the present application, ordinary technicians in this field can also make many forms without departing from the purpose of the present application and the scope of protection of the claims, all of which are within the protection of the present application.

Claims

1. A CMS remote incremental backup method, characterized in that: The CMS runs on a CMS server, a backup management terminal is deployed on the CMS server, a local database is backed up by the backup management terminal to form a backup list file, a backup file watermark of the backup list file is calculated, and the backup list file is packaged to form a backup list file compression package, and a connection is established with the CMS server through a remote backup machine to perform CMS remote incremental backup. The CMS remote incremental backup method includes: The backup management terminal notifies the remote backup machine to download the compressed package of the backup list file and provides a file download interface; the backup client is deployed on the remote backup machine, and the download notification sent by the backup management terminal is received through the backup client. The compressed package of the backup list file is downloaded and decompressed, the backup list file is traversed, and it is detected whether the backup list file exists in the local file. If so, the local file watermark and the backup file watermark are calculated, and the local file watermark is compared with the backup file watermark. If the local file watermark is the same as the backup file watermark, there is no need to download and the detection continues; if the local file watermark is different from the backup file watermark, the backup list file is downloaded to perform CMS remote incremental backup.

2. The CMS remote incremental backup method according to claim 1, characterized in that: The CMS remote incremental backup method includes: Set up a scheduled backup plan in CMS and set the backup execution time; define the table structure in the local database through XML metadata, and store the business data in the table structure in the backup list file in the form of an XML file; The backup list file includes a data file list, a template file list, a static resource list and a program file list; Record the file name and backup file watermark of each backup list file.

3. The CMS remote incremental backup method according to claim 1, characterized in that: The step of calculating the backup file watermark of the backup list file includes: When packaging, a verification file is generated, and the backup list file is processed by the MD5 algorithm and the CRC32 algorithm to generate an MD5 value and a CRC32 value, and the MD5 value and the CRC32 value are directly concatenated to obtain the backup file watermark.

4. The CMS remote incremental backup method according to claim 1, characterized in that: The step of establishing a connection with the CMS server through a remote backup machine includes: Check whether the remote backup machine can be connected. If it can be connected, call the remote backup machine interface, notify the remote backup machine through the backup management end to download the backup list file compression package and provide a file download interface; if it cannot be connected, configure the preset time interval and the preset number of connections, start the thread to initiate a connection request every preset time interval, and continue the preset number of connections. If it still cannot be connected, interrupt the connection and make an interruption notification.

5. The CMS remote incremental backup method according to claim 2, characterized in that: The downloading and decompressing the compressed package of the backup list file includes: The backup list file is verified to be complete based on the backup file watermark and the verification file. If the backup file watermark is consistent with the verification file, the backup list file is complete; if the backup file watermark is inconsistent with the verification file, the backup list file is incomplete, and an alarm notification is issued.

6. The CMS remote incremental backup method according to claim 2, characterized in that: The file download address is spliced ​​according to the file name, and multiple threads are started through the thread pool to download the file and saved to a temporary directory. If the file download fails, a preset retry step and a preset number of retries are configured, and the download is repeated according to the preset retry step and the preset number of retries. After the download is completed, the download file watermark is calculated and compared with the backup file watermark. If the download file watermark is the same as the backup file watermark, the download file is moved to the backup path and the download continues; if the download file watermark is different from the backup file watermark, the file is determined to be damaged and a failure log is recorded.

7. The CMS remote incremental backup method according to claim 6, characterized in that: The CMS remote incremental backup method includes: After traversing and downloading the backup list file, a backup snapshot file is generated, and the backup integrity is checked and the failure log is read. If the failure log is empty, the backup is complete; if the number of failure log records is less than the preset failure threshold, the backup is partially complete; otherwise, the backup is considered incomplete; The remote backup machine is self-checked to detect the disk usage of the remote backup machine. If the disk usage exceeds a preset usage threshold, an alarm notification is issued.

8. A CMS remote incremental backup device, characterized in that: The device comprises: The CMS server module is configured to run the CMS, deploy a backup management terminal on the CMS server, back up a local database through the backup management terminal, form a backup list file, calculate a backup file watermark of the backup list file, and pack the backup list file to form a backup list file compression package, establish a connection with a remote backup machine, notify the remote backup machine through the backup management terminal to download the backup list file compression package and provide a file download interface; The remote backup machine module is configured to deploy a backup client on the remote backup machine, receive a download notification sent by the backup management terminal through the backup client, download and decompress the backup list file compression package, traverse the backup list file, and detect whether the backup list file exists in the local file. If so, calculate the local file watermark and the backup file watermark, compare the local file watermark with the backup file watermark. If the local file watermark is the same as the backup file watermark, there is no need to download and continue to detect; if the local file watermark is different from the backup file watermark, download the backup list file and perform CMS remote incremental backup.

9. A CMS remote incremental backup system, the system comprising a processor and a memory, wherein the memory stores a computer program, characterized in that: The computer program is loaded and executed by the processor to implement the CMS remote incremental backup method according to any one of claims 1 to 7.

10. A computer-readable storage medium, wherein a computer program is stored in the storage medium, characterized in that: When the computer program is executed by a processor, it is used to implement the CMS remote incremental backup method according to any one of claims 1 to 7.

Images