CN116662077A - Method, device, equipment and storage medium for adjusting backup cycle - Google Patents

Abstract

The invention discloses a method, a device, equipment and a storage medium for adjusting a backup period, wherein the method comprises the following steps: judging whether a target service host has service fault risks or not; when the service fault risk exists, determining the fault type generated by the service fault risk; identifying each service host of a service system corresponding to the target service host; and adjusting the backup period of each service host according to the fault type. Because the invention judges whether the target service host has service fault risk, then when the service fault risk exists, the fault type generated by the service fault risk is determined, then each service host of the service system corresponding to the target host is identified, and the backup period of each service host is adjusted.

Description

Method, device, equipment and storage medium for adjusting backup cycle

technical field

The invention relates to the technical field of data backup, in particular to a method, device, equipment and storage medium for adjusting a backup cycle.

Background technique

When the business system of the existing data center is doing data disaster recovery backup, the backup cycle of the business system is fixed. However, if the backup cycle of the business system is too long, when a business failure occurs, more business data will be lost; if the backup cycle of the business system is too short, the amount of backup data will be too large, and the investment cost will be too high.

Therefore, there is an urgent need for a method for adjusting the backup cycle, which can automatically adjust the backup cycle of the business system, reduce the loss of business data, and reduce input costs.

The above content is only used to assist in understanding the technical solution of the present invention, and does not mean that the above content is admitted as prior art.

Contents of the invention

The main purpose of the present invention is to provide a method, device, equipment and storage medium for adjusting the backup cycle, aiming to solve the technical problems in the prior art that the fixed backup cycle of the business system leads to excessive data loss or excessive investment in the business system .

To achieve the above object, the invention provides a method for adjusting backup cycle, said method may further comprise the steps:

Determine whether the target business host has a business failure risk;

When there is a risk of business failure, determine the type of failure caused by the risk of business failure;

identifying each service host of the service system corresponding to the target service host;

The backup period of each service host is adjusted according to the failure type.

Optionally, before the step of determining the type of failure caused by the risk of business failure when there is a risk of business failure, it may further include:

Carry out cluster analysis on business crash accidents to determine the type of failure;

Analyzing the fault logs of the fault types in turn to obtain analysis results;

According to the analysis result, determine the backup cycle corresponding to the fault type;

A preset fault type-backup cycle mapping table is established based on the fault type and the backup cycle corresponding to the fault type.

Optionally, the step of adjusting the backup period of each service host according to the failure type includes:

Obtain the target backup cycle according to the default fault type-backup cycle correspondence mapping table;

The backup period of each service host in the service system is adjusted according to the target backup period.

Optionally, the step of analyzing the fault logs of the fault types in sequence to obtain the analysis results includes:

Acquiring fault logs of the fault types in sequence;

determining the risk level corresponding to the fault type according to the fault log;

Based on the preset risk level table and the risk level, the analysis result is obtained.

Optionally, the step of judging whether the target service host has a service failure risk includes:

Conduct behavior detection on the behavior of the target business host, and obtain the behavior detection results;

According to the behavior detection result, it is judged whether the target service host has a service failure risk.

Optionally, the step of identifying each service host of the service system corresponding to the target service host includes:

Obtain the service configuration of the target service host;

Obtain a connection record in the service system corresponding to the target service host according to the service configuration;

determining the occurrence frequency of host information according to the connection record;

Each service host in the service system is identified according to the occurrence frequency of the host information.

Optionally, the method also includes:

When the target service host has no risk of service failure within the preset time range, the backup period corresponding to the service system is adjusted to a default backup period.

In addition, in order to achieve the above purpose, the present invention also proposes a device for adjusting the backup cycle, which includes:

The risk judgment module is used to judge whether there is a business failure risk in the target business host;

A type determination module, configured to determine the type of failure caused by the business failure risk when there is a business failure risk;

A host identification module, configured to identify each service host of the service system corresponding to the target service host;

A cycle adjustment module, configured to adjust the backup cycle of each service host according to the type of failure.

In addition, in order to achieve the above object, the present invention also proposes a device for adjusting the backup cycle, which includes: a memory, a processor, and a program for adjusting the backup cycle that is stored in the memory and can run on the processor. The program for adjusting the backup cycle is configured to implement the steps of the method for adjusting the backup cycle as described above.

In addition, in order to achieve the above object, the present invention also proposes a storage medium, the storage medium stores a program for adjusting the backup period, and when the program for adjusting the backup period is executed by the processor, the method for adjusting the backup period as described above is realized. step.

The present invention judges whether the target business host has a business failure risk; when there is a business failure risk, determines the type of failure caused by the business failure risk; identifies each business host of the business system corresponding to the target business host; according to the fault The type adjusts the backup period of each service host. Because the present invention judges whether there is a business failure risk in the target business host, and then when there is a business failure risk, determines the type of failure caused by the business failure risk, identifies each business host of the business system corresponding to the target host, and adjusts each business host. Backup period, compared with the business system in the prior art when doing data disaster recovery backup, the backup period of the business system is fixed, the invention realizes the automatic adjustment of the backup period of the business system, reduces the loss of business data, Reduced input costs.

Description of drawings

Fig. 1 is a schematic structural diagram of a device for adjusting the backup period of the hardware operating environment involved in the solution of the embodiment of the present invention;

Fig. 2 is a schematic flow chart of the first embodiment of the method for adjusting the backup cycle in the present invention;

Fig. 3 is a schematic flow chart of the second embodiment of the method for adjusting the backup cycle in the present invention;

Fig. 4 is a schematic flow chart of the third embodiment of the method for adjusting the backup cycle according to the present invention;

Fig. 5 is a structural block diagram of the first embodiment of the device for adjusting the backup period according to the present invention.

The realization of the purpose of the present invention, functional characteristics and advantages will be further described in conjunction with the embodiments and with reference to the accompanying drawings.

Detailed ways

It should be understood that the specific embodiments described here are only used to explain the present invention, not to limit the present invention.

Referring to FIG. 1 , FIG. 1 is a schematic structural diagram of equipment for adjusting the backup period of the hardware operating environment involved in the solution of the embodiment of the present invention.

As shown in FIG. 1 , the device for adjusting the backup period may include: a processor 1001 , such as a central processing unit (Central Processing Unit, CPU), a communication bus 1002 , a user interface 1003 , a network interface 1004 , and a memory 1005 . Wherein, the communication bus 1002 is used to realize connection and communication between these components. The user interface 1003 may include a display screen (Display), an input unit such as a keyboard (Keyboard), and the optional user interface 1003 may also include a standard wired interface and a wireless interface. The network interface 1004 may optionally include a standard wired interface and a wireless interface (such as a Wireless-Fidelity (Wireless-Fidelity, WI-FI) interface). The memory 1005 may be a high-speed random access memory (Random Access Memory, RAM), or a stable non-volatile memory (Non-Volatile Memory, NVM), such as a disk memory. Optionally, the memory 1005 may also be a storage device independent of the aforementioned processor 1001 .

Those skilled in the art can understand that the structure shown in FIG. 1 is not limited to the device for adjusting the backup cycle, and may include more or less components than shown in the figure, or combine some components, or arrange different components.

As shown in FIG. 1 , the memory 1005 as a storage medium may include an operating system, a network communication module, a user interface module, and a program for adjusting a backup cycle.

In the device for adjusting the backup cycle shown in Figure 1, the network interface 1004 is mainly used for data communication with the network server; the user interface 1003 is mainly used for data interaction with the user; the processor 1001, memory 1005 may be set in the device for adjusting the backup cycle, and the device for adjusting the backup cycle calls the program for adjusting the backup cycle stored in the memory 1005 through the processor 1001, and executes the method for adjusting the backup cycle provided by the embodiment of the present invention.

An embodiment of the present invention provides a method for adjusting a backup period. Referring to FIG. 2 , FIG. 2 is a schematic flowchart of a first embodiment of a method for adjusting a backup period according to the present invention.

In this embodiment, the method for adjusting the backup cycle includes the following steps:

Step S10: Determine whether the target service host has a service failure risk.

It should be noted that the execution subject of this embodiment may be a computing service device with data processing, network communication and program running functions, such as a server, tablet computer, personal computer, mobile phone, etc., or a computer that can realize the above functions electronic equipment, adjust backup cycle equipment, etc. In the following, the device for adjusting the backup cycle is taken as an example to illustrate this embodiment and the following embodiments.

It is understandable that this embodiment can be used in the process of data disaster recovery for the business system of the data center. Since the existing business system is performing data disaster recovery backup, the backup period is fixed. If the business If the backup cycle of the system is too long, when a business failure occurs, more business data will be lost; if the backup cycle of the business system is too short, it will cause too much backup data, resulting in excessive cost investment. This embodiment realizes the automatic adjustment of the backup period of the service system, reduces the loss of service data, and reduces the investment cost.

It should be understood that the service system may be a single service system or multiple service systems, which is not limited in this embodiment.

Furthermore, the above service system may be composed of multiple interrelated service hosts, and the service hosts may be computers, data terminals, or other devices with the same or similar functions, which is not limited in this embodiment.

It is understandable that the existing business system is composed of multiple hosts. When a business failure occurs (for example, when encountering a ransomware virus), data recovery needs to be performed on multiple hosts. Therefore, when adjusting the data backup cycle, It is necessary to adjust the data backup cycle of all associated hosts in the entire business system to ensure that in the event of a business failure, all hosts in the business system will lose as little data as possible. For example, the OA system is composed of hosts A, B, and C. When host A discovers potential risks of business failures (hosts B and C have not yet discovered risks), it is necessary to analyze and identify the business configuration and business behavior of host A to obtain business The hosts associated with the system (host B, host C), and then adjust the backup cycle of hosts A, B, and C at the same time to ensure that the entire business system will lose as little business data as possible in the event of a failure.

Further, behavior detection may be performed on the behavior of the target service host to obtain a behavior detection result; according to the behavior detection result, it is judged whether the target service host has a risk of service failure.

It should be noted that the behavior of the business host can be detected through a preset program, or can be detected through software related to business fault risk detection, or can be detected in other ways. There is no restriction on this.

Step S20: When there is a business failure risk, determine the failure type caused by the business failure risk.

It should be noted that when the target business host does not have the risk of business failure within the preset time range, the backup cycle corresponding to the business system where the target business host is located is adjusted to the default backup cycle to save resources. The preset time may be 24 hours, 48 hours, or other time ranges, which is not limited in this embodiment.

It is understandable that when the business failure risk exists in the business host, the type of failure caused by the business failure risk can be determined by analyzing the log files in the business host.

Further, the fault type may be set in advance, or may be obtained after analyzing a large number of business crash events and classifying the fault types generated by business fault risks.

Step S30: Identify each service host of the service system corresponding to the target service host.

What needs to be explained is that since most of the existing business systems are composed of multiple business hosts, when a business failure occurs (for example: encountering a ransomware virus), it is necessary to recover data from multiple business hosts, so when adjusting During the backup cycle of the business system, it is necessary to adjust the backup cycle of all associated business hosts of the business system to ensure that each business host of the business system loses as little data as possible in the event of a business failure. Therefore, when adjusting the backup cycle Before, each business host of the business system needs to be identified.

It should be explained that by enumerating all the business processes of the current host, identifying the business type according to the business process, finding all the configuration file information through the business process, and obtaining which hosts the current business is associated with according to the configuration file. If a host runs the ceph-osd process, which belongs to the ceph cluster, then read the configuration file of the cluster to obtain which business hosts the current business system consists of.

Further, by obtaining the host name-IP address correspondence mapping table of the business system, it is possible to know which business hosts the business system consists of according to the host name and ip address in the mapping table (usually , the business hosts involved in the mapping table all belong to the same business system). This is because many of the network communications between business hosts in the business system initiate connection requests through host names instead of directly using ip addresses. Therefore, by analyzing the "host name-IP address" mapping list of the system, we can also know which business hosts the business system consists of. For example, the /etc/hosts file of the Linux system stores the hostnames, virtual IP names, and private network names of all business hosts in the oraclerac cluster. Through this information, you can also know which business hosts the business system consists of.

Step S40: Adjust the backup period of each service host according to the failure type.

It is understandable that the backup frequency corresponding to different fault types is also different. For example, if the fault type of the business system belongs to the low-risk type, the backup cycle of the above business system can be set to be backed up every two days; If the failure type of the above-mentioned business system belongs to high risk, the backup period of the above-mentioned business system can be set to CDP backup, that is, real-time backup.

In a specific implementation, the target backup period may be obtained according to the preset fault type-backup period correspondence mapping table; and then the backup period of each service host in the service system is adjusted according to the target backup period.

In this embodiment, by judging whether the target business host has a business failure risk; when there is a business failure risk, determining the type of failure caused by the business failure risk; identifying each business host of the business system corresponding to the target business host; according to the The fault type adjusts the backup period of each service host. Because the present invention judges whether there is a business failure risk in the target business host, and then when there is a business failure risk, determines the type of failure caused by the business failure risk, identifies each business host of the business system corresponding to the target host, and adjusts each business host. Backup period, compared with the business system in the prior art when doing data disaster recovery backup, the backup period of the business system is fixed, the invention realizes the automatic adjustment of the backup period of the business system, reduces the loss of business data, Reduced input costs.

Referring to FIG. 3 , FIG. 3 is a schematic flowchart of a second embodiment of a method for adjusting a backup period according to the present invention.

Based on the first embodiment above, in this embodiment, before the step S20, it also includes:

Step S201: Carry out cluster analysis on business crash accidents to determine the type of failure.

It is understandable that a business crash event refers to an event in which an unpredictable error occurs in a business system due to various reasons, causing it to fail to operate normally or to stop working.

It should be understood that cluster analysis refers to the analytical process of grouping a collection of physical or abstract objects into classes of similar objects.

In the specific implementation, by clustering and analyzing the log files and files of various business hosts in a large number of business crash events, the fault types are divided into four categories, namely hardware faults, system faults, host attacks, and runtime risks.

What needs to be explained is that hardware failures include memory failures, disk failures, and raid card failures. When these hardware fails, the operating system or the underlying hardware system (such as the motherboard, raid card) will detect it first, and generate an alarm or error log.

System failures include system upgrades, software installations, file system errors, business application failures, etc., which can be determined by analyzing software upgrade logs (including operating system upgrades, application software upgrades), installation logs, system logs, and application runtime logs. Whether there is a system failure on the host.

If the business host is attacked, there will be a large number of abnormalities in the audit log, security log, and login log of the host. For example, remote login services such as mstsc and ssh will generate a large number of failed login logs, and the frequency of occurrence is very high. Generally speaking, these high-frequency abnormal log logs are a sign that the host is under attack. If the host is breached, the next step is likely to be to perform destructive actions, such as encrypting data for extortion. Therefore, if an attack risk is found in the audit log, security log, and login log, it is necessary to adjust the backup cycle of data backup to ensure that in the event of a blackmail event, business data can be restored through the backup point.

Runtime risks include the startup of malicious programs, abnormal changes of a large number of files (such as a large number of creation, deletion, and renaming), modification of data in key areas of the disk (such as disk boot sector, super block, metadata), etc., such behaviors In many cases, it means that the system is likely to encounter damage, and the frequency of data backup needs to be increased.

Step S202: Analyze the fault logs of the fault types in sequence to obtain the analysis results.

It should be noted that the fault logs corresponding to different types are also different. For example, the fault logs corresponding to hardware faults can be raid card logs, message logs, and operating system logs, etc.; the fault logs corresponding to operating system faults can be software upgrade logs, Installation logs, system logs, and application runtime logs, etc.; fault logs corresponding to host attacks can be host audit logs, security logs, login logs, etc.; fault logs of runtime risks can be the startup of malicious programs, abnormalities of a large number of files A log of changes and modifications to data in critical regions of the disk.

In a specific implementation, the fault log of the fault type can be obtained in sequence; then according to the fault log, the risk level corresponding to the fault type is determined; and then based on the preset risk level table and the risk level, the analysis is obtained result.

What needs to be explained is that the frequency of the backup cycle is adjusted by analyzing the fault log, and the risk level corresponding to the fault type is determined by analyzing the content of the fault log.

It should be noted that the above-mentioned preset risk level table may be preset, and the preset risk level table represents a mapping relationship between a risk level and a backup cycle. For example, when the risk level is low risk, the corresponding backup cycle is every 2 days; when the risk level is medium risk, the backup cycle is once a day; when the risk level is high risk, CDP backup is required, that is Real-time backup.

Step S203: Determine the backup period corresponding to the failure type according to the analysis result.

It should be noted that the above analysis result is the risk level corresponding to the failure type, by determining the risk classification level of the failure type, and then according to the preset risk level table, determine the backup period corresponding to the failure type.

Step S204: Establishing a default fault type-backup cycle mapping table based on the fault type and the backup cycle corresponding to the fault type.

In this embodiment, by judging whether there is a business failure risk in the target business host; performing cluster analysis on business crash accidents to determine the failure type; analyzing the failure logs of the failure types in turn to obtain analysis results; according to the analysis results, determining The backup cycle corresponding to the fault type; establishing a preset fault type-backup cycle correspondence mapping table based on the fault type and the backup cycle corresponding to the fault type; when there is a business fault risk, determine that the business fault risk occurs the fault type; identify each service host of the service system corresponding to the target service host; adjust the backup period of each service host according to the fault type. Because the present invention judges whether there is a business failure risk in the target business host, and then when there is a business failure risk, determines the type of failure caused by the business failure risk, identifies each business host of the business system corresponding to the target host, and adjusts each business host. Backup period, compared with the business system in the prior art when doing data disaster recovery backup, the backup period of the business system is fixed, the present invention divides the fault types by performing cluster analysis on a large number of business crash accidents, and in the target When the business host has a business failure risk, determine the type of failure caused by the business failure risk, and then adjust the backup cycle of each business host in the current business system according to the preset fault type-backup cycle correspondence mapping table, which not only realizes the recovery of business crash accidents The division of fault types also automatically adjusts the backup cycle of the business system, reducing the loss of business data and reducing investment costs.

Referring to FIG. 4 , FIG. 4 is a schematic flowchart of a third embodiment of a method for adjusting a backup period according to the present invention.

Based on the above-mentioned embodiments, in this embodiment, the step S30 includes:

Step S301: Obtain the service configuration of the target service host.

Step S302: Obtain the connection record in the service system corresponding to the target service host according to the service configuration.

It can be understood that the above-mentioned connection record of the business system may be a connection record between computers obtained through the corresponding business configuration on the target business host in the business system.

Step S303: Determine the occurrence frequency of host information according to the connection record.

It should be noted that the closer the computer business is, the more frequent the network communication between them is, and these network connections are all in the same subnet and do not need to be forwarded by routers. Like rac clusters, distributed file systems, and failover clusters, basically there are long tcp connections. Among them, there may be at least one tcp connection, and there may be multiple tcp connections. This embodiment does not limit this, so as to track each business host on the business system working status. Therefore, by analyzing the tcp network connections on each computing node, we can know which computing nodes the business system consists of.

Step S304: Identify each service host in the service system according to the occurrence frequency of the host information.

In the specific implementation, you can use the netstat command, ss command or call the system programming interface to enumerate all the tcp connections of the target business host at regular intervals, and then save the enumerated information, which includes: local ip, local port, external ip, external port and process name, the tcp connection in the current service host can be obtained through the above information, and the peer computer connected with the tcp is the service host of the above service system.

In this embodiment, by judging whether there is a business failure risk in the target business host; performing cluster analysis on business crash accidents to determine the failure type; analyzing the failure logs of the failure types in turn to obtain analysis results; according to the analysis results, determining The backup cycle corresponding to the fault type; establishing a preset fault type-backup cycle correspondence mapping table based on the fault type and the backup cycle corresponding to the fault type; when there is a business fault risk, determine that the business fault risk occurs fault type; obtain the service configuration of the target service host; obtain the connection record in the service system corresponding to the target service host according to the service configuration; determine the occurrence frequency of the host information according to the connection record; The occurrence frequency identifies each service host in the service system; adjusts the backup period of each service host according to the fault type. Because the present invention judges whether there is a business failure risk in the target business host, and then when there is a business failure risk, determines the type of failure caused by the business failure risk, identifies each business host of the business system corresponding to the target host, and adjusts each business host. Backup period, compared with the business system in the prior art when doing data disaster recovery backup, the backup period of the business system is fixed, the present invention divides the fault types by performing cluster analysis on a large number of business crash accidents, and in the target When the business host has a business failure risk, determine the type of failure caused by the business failure risk, and then adjust the backup cycle of each business host in the current business system according to the preset fault type-backup cycle correspondence mapping table, which not only realizes the recovery of business crash accidents The division of fault types also automatically adjusts the backup cycle of the business system, reducing the loss of business data and reducing investment costs.

In addition, the embodiment of the present invention also proposes a storage medium, on which a program for adjusting the backup period is stored, and when the program for adjusting the backup period is executed by a processor, the steps of the method for adjusting the backup period as described above are implemented.

Referring to FIG. 5 , FIG. 5 is a structural block diagram of the first embodiment of the device for adjusting the backup cycle according to the present invention.

As shown in FIG. 5 , the device for adjusting the backup cycle proposed by the embodiment of the present invention includes: a risk judgment module 501 , a type determination module 502 , a host identification module 503 and a cycle adjustment module 504 .

The risk judging module 501 is configured to judge whether there is a business failure risk in the target business host.

The type determination module 502 is configured to determine the type of failure caused by the business failure risk when there is a business failure risk.

The host identification module 503 is configured to identify each service host of the service system corresponding to the target service host.

The period adjustment module 504 is configured to adjust the backup period of each service host according to the failure type.

The risk judging module 501 is further configured to conduct behavior detection on the behavior of the target service host to obtain a behavior detection result; according to the behavior detection result, determine whether the target service host has a business failure risk.

The risk judging module 501 is further configured to adjust the backup cycle corresponding to the business system to a default backup cycle when the target business host does not have a business failure risk within a preset time range.

The period adjustment module 504 is further configured to obtain a target backup period according to the preset fault type-backup period correspondence mapping table; adjust the backup period of each service host in the service system according to the target backup period.

In this embodiment, by judging whether the target business host has a business failure risk; when there is a business failure risk, determining the type of failure caused by the business failure risk; identifying each business host of the business system corresponding to the target business host; according to the The fault type adjusts the backup period of each service host. Because the present invention judges whether there is a business failure risk in the target business host, and then when there is a business failure risk, determines the type of failure caused by the business failure risk, identifies each business host of the business system corresponding to the target host, and adjusts each business host. Backup period, compared with the business system in the prior art when doing data disaster recovery backup, the backup period of the business system is fixed, the invention realizes the automatic adjustment of the backup period of the business system, reduces the loss of business data, Reduced input costs.

Based on the first embodiment of the device for adjusting the backup cycle of the present invention, a second embodiment of the device for adjusting the backup cycle of the present invention is proposed.

In this embodiment, the type determination module 502 is also used to perform cluster analysis on business crash accidents to determine the type of failure; analyze the failure logs of the type of failure in turn to obtain analysis results; according to the analysis results , determining a backup cycle corresponding to the fault type; establishing a preset fault type-backup cycle mapping table based on the fault type and the backup cycle corresponding to the fault type.

For other embodiments or specific implementations of the device for adjusting the backup cycle of the present invention, reference may be made to the above-mentioned method embodiments, which will not be repeated here.

It should be noted that, as used herein, the term "comprises", "comprises" or any other variation thereof is intended to cover a non-exclusive inclusion such that a process, method, article or system comprising a set of elements includes not only those elements, It also includes other elements not expressly listed, or elements inherent in the process, method, article, or system. Without further limitations, an element defined by the phrase "comprising a..." does not preclude the presence of additional identical elements in the process, method, article or system comprising that element.

The serial numbers of the above embodiments of the present invention are for description only, and do not represent the advantages and disadvantages of the embodiments.

Through the description of the above embodiments, those skilled in the art can clearly understand that the methods of the above embodiments can be implemented by means of software plus a necessary general-purpose hardware platform, and of course also by hardware, but in many cases the former is better implementation. Based on this understanding, the essence of the technical solution of the present invention or the part that contributes to the prior art can be embodied in the form of software products, and the computer software products are stored in a storage medium (such as read-only memory/random access Memory, magnetic disk, optical disk), including several instructions to make a terminal device (which can be a mobile phone, computer, server, air conditioner, or network device, etc.) execute the methods described in various embodiments of the present invention.

The above are only preferred embodiments of the present invention, and are not intended to limit the patent scope of the present invention. Any equivalent structure or equivalent process conversion made by using the description of the present invention and the contents of the accompanying drawings, or directly or indirectly used in other related technical fields , are all included in the scope of patent protection of the present invention in the same way.

Claims (10)

1. a method for adjusting the backup cycle, characterized in that, the method for adjusting the backup cycle comprises the following steps: Determine whether the target business host has a business failure risk; When there is a risk of business failure, determine the type of failure caused by the risk of business failure; identifying each service host of the service system corresponding to the target service host; The backup period of each service host is adjusted according to the failure type. 2. The method for adjusting the backup period according to claim 1, wherein, before the step of determining the type of failure caused by the risk of business failure when there is a risk of business failure, further comprising: Carry out cluster analysis on business crash accidents to determine the type of failure; Analyzing the fault logs of the fault types in turn to obtain analysis results; According to the analysis result, determine the backup cycle corresponding to the fault type; A preset fault type-backup cycle mapping table is established based on the fault type and the backup cycle corresponding to the fault type. 3. The method for adjusting the backup period according to claim 2, wherein the step of adjusting the backup period of each service host according to the type of failure comprises: Obtain the target backup cycle according to the default fault type-backup cycle correspondence mapping table; The backup period of each service host in the service system is adjusted according to the target backup period. 4. The method for adjusting the backup period according to claim 2, wherein the step of analyzing the failure log of the failure type in turn to obtain the analysis result comprises: Acquiring fault logs of the fault types in sequence; According to the fault log, determine the risk level corresponding to the fault type; Based on the preset risk level table and the risk level, the analysis result is obtained. 5. The method for adjusting the backup period according to claim 1, wherein the step of judging whether the target service host has a risk of service failure comprises: Conduct behavior detection on the behavior of the target business host, and obtain the behavior detection results; According to the behavior detection result, it is judged whether the target service host has a service failure risk. 6. The method for adjusting the backup period according to claim 1, wherein the step of identifying each service host of the service system corresponding to the target service host comprises: Obtain the service configuration of the target service host; Obtain a connection record in the service system corresponding to the target service host according to the service configuration; determining the occurrence frequency of host information according to the connection record; Each service host in the service system is identified according to the occurrence frequency of the host information. 7. The method for adjusting the backup cycle according to any one of claims 1-6, wherein the method further comprises: When the target service host has no risk of service failure within the preset time range, the backup period corresponding to the service system is adjusted to a default backup period. 8. A device for adjusting the backup cycle, characterized in that the device comprises: The risk judgment module is used to judge whether there is a business failure risk in the target business host; A type determination module, configured to determine the type of failure caused by the business failure risk when there is a business failure risk; A host identification module, configured to identify each service host of the service system corresponding to the target service host; A cycle adjustment module, configured to adjust the backup cycle of each service host according to the type of failure. 9. A device for adjusting a backup cycle, characterized in that the device includes: a memory, a processor, and a backup cycle adjustment program stored on the memory and operable on the processor, the backup cycle adjustment program It is configured to realize the steps of the method for adjusting the backup period according to any one of claims 1-7. 10. A storage medium, characterized in that a program for adjusting the backup cycle is stored on the storage medium, and when the program for adjusting the backup cycle is executed by a processor, the adjusted backup cycle as described in any one of claims 1 to 7 is realized method steps.