Apparatus and method for consolidating backup policies

Abstract

The present invention relates to the field of storage systems, in particular to the field of backup systems. More specifically, a scheme is provided that allows to automatically merge backup policies assigned to the same backup object, e.g. in case of a backup policy conflict. Thus, the present invention provides an apparatus for merging backup policies. The apparatus is configured to determine whether a first backup policy comprising a first set of rules and a second backup policy comprising a second set of rules are assigned to a backup object. The apparatus is further configured to generate a merged backup policy comprising a merged set of rules based on the first backup policy and the second backup policy, if the first backup policy and the second backup policy are assigned to the backup object. A resource consumption of a backup created according to the merged backup policy is below a predefined threshold.

Description

Technical Field

[0001] This invention relates to the field of storage systems, and more particularly to the field of backup systems. More specifically, it provides an apparatus and a method that allow the automatic merging of backup policies assigned to the same backup object, for example, in the event of backup policy conflicts. Background Technology

[0002] In the field of backup systems, backups of protected objects (also known as backup objects) are typically created based on backup strategies.

[0003] For example, a backup is a copy of the protected object, or more specifically, a point-in-time copy of the protected data.

[0004] For example, a protected object is an entity containing data that needs to be protected, such as a virtual machine, database, file system, or file. A protected object can be part of an object hierarchy. For example, a virtual machine can be contained within a folder or cluster; files can be stored in a file system or folder.

[0005] A backup policy defines the parameters upon which backups are created, and may include at least one of the following: backup frequency rules, backup data format rules, backup activity rules, backup archiving rules (also known as retention periods), or backup replication rules. For example, a backup frequency rule defines the time interval for creating backups. A backup data format rule defines the data format used to store backups. A backup activity rule defines the time window in which backups can be created. For example, a backup archiving rule defines whether backups are stored locally or in an archive. A backup replication rule defines how backup copies are organized.

[0006] The association between backup policies and protected objects defines the rules of backup policies applied to protected objects.

[0007] To automate protection management, the backup system allows for automatic policy allocation:

[0008] Taking a virtual machine scenario as an example, in a virtual environment, a backup policy can be automatically assigned to the entire directory, that is, the same backup policy can be assigned to all virtual machines under that directory.

[0009] Alternatively, backup policies can be automatically assigned to virtual machines based on their characteristics, as shown in the following example rules:

[0010] - Assign policy A to all virtual machines running operating system 1.

[0011] - Assign policy B to all virtual machines running operating system 2.

[0012] - Assign policy C to all virtual machines whose names begin with "special".

[0013] - Assign policy D to all virtual machines with the database system installed.

[0014] This can cause problems if multiple rules are met by a virtual machine. For example, if a virtual machine running OS1 has a database system installed and its name is "special-VM-OS1-DB", then policies A, C, and D will be assigned to that virtual machine.

[0015] Currently, there are two methods to resolve this conflict: if the assigned backup policies conflict, users can manually intervene to select the relevant backup policy. Alternatively, multiple policies can be assigned simultaneously, and backups can be created separately based on each policy.

[0016] The problem with these methods is that either user involvement in the decision-making process is required, which prevents full automation and causes delays until the user resolves the issue; or if multiple backups of the protected object are performed (due to the allocation of multiple backup policies), the required storage space and CPU processing time become excessive, resulting in high resource consumption and cost. Summary of the Invention

[0017] In view of the above problems, the purpose of the various embodiments of the present invention is to improve the automatic generation of backup strategies.

[0018] This or other objectives can be achieved by various embodiments of the invention as described in the appended independent claims. Advantageous implementations of the embodiments of the invention are further defined in the dependent claims.

[0019] A first aspect of the present invention provides an apparatus for merging backup strategies, wherein the apparatus is configured to determine whether a first backup strategy including a first set of rules and a second backup strategy including a second set of rules are assigned to a backup object; if the first backup strategy and the second backup strategy are assigned to the backup object, a merged backup strategy including a merged set of rules is generated based on the first backup strategy and the second backup strategy; wherein the resource consumption of the backup created according to the merged backup strategy is lower than a predefined threshold.

[0020] This ensures that a single, unified backup strategy can be provided, thereby enabling efficient backup creation.

[0021] Specifically, backup objects can also be called protected objects or backup data.

[0022] Specifically, a backup policy defines the parameters and / or rules upon which backups are created. Specifically, a backup policy includes at least one of the following: backup frequency parameters, backup activity parameters, retention period, backup replication rules, and backup data format rules.

[0023] In one implementation of the first aspect, the resource consumption of the backup created according to the merged backup strategy is less than the sum of the resource consumption of the backup created according to the first backup strategy and the resource consumption of the backup created according to the second backup strategy.

[0024] This ensures that a single, unified backup strategy can be provided, which enables more efficient backup creation compared to creating backups based on two separate backup strategies.

[0025] Specifically, resource consumption includes at least one of the following: CPU processing power used to create backups, memory used to create backups, storage capacity (e.g., local storage or archive storage) used to store backups, network traffic used to create backups, network bandwidth used to create backups, and multiple backup processes executed.

[0026] In another implementation of the first aspect, the merge rule set is the union of the first rule set and the second rule set.

[0027] This ensures that no rules are lost when merging the first rule set and the second rule set, and that there are no duplicate rules in the merged rule set.

[0028] Specifically, if the second backup strategy does not contain an element that corresponds to an element in the first backup strategy (for example, if the first backup strategy includes a backup frequency rule, but the second backup strategy does not include that rule), then the second rule set will be considered an empty set.

[0029] In another implementation of the first aspect, the merge backup strategy further defines the creation of the backup based on predefined rules in the merge rule set.

[0030] This allows for flexible selection of rules to be used to generate the backup within the merge rule set.

[0031] Specifically, the merge strategy also defines creating the backup based on only one rule in the merge rule set.

[0032] In another implementation of the first aspect, the merge backup strategy further defines creating the backup based on each rule in the merge rule set.

[0033] This ensures that backups created based on the merge rule set meet all the requirements of the rules in the first rule set and the second rule set.

[0034] In another implementation of the first aspect, the merge backup strategy further defines creating the backup based on the maximum and / or minimum elements in the merge rule set.

[0035] This ensures that if there are multiple parameters with the same backup attributes in the merged backup strategy, the backup can be created based on the largest or smallest element, thereby satisfying the requirements of the remaining parameters simultaneously.

[0036] In another implementation of the first aspect, the first rule set includes a first backup frequency rule, the second rule set includes a second backup frequency rule, and the merge rule set includes the first backup frequency rule and the second backup frequency rule; and the merge backup strategy further defines creating the backup according to each backup frequency rule in the merge rule set.

[0037] This ensures that when the first rule set and the second rule set have two different backup frequencies, backups will be created at all times according to the first rule set, and backups will also be created at all times according to the second rule set. In other words, the backup frequency based on the merged backup strategy simultaneously satisfies the requirements of both the first and second backup strategies.

[0038] Specifically, backup frequency rules are rules that define the time interval between two subsequent backups.

[0039] In another implementation of the first aspect, the first rule set includes a first backup activity rule, the second rule set includes a second backup activity rule, and the merge rule set includes the first backup activity rule and the second backup activity rule; and the merge backup strategy further defines creating the backup based on at least one backup activity rule in the merge rule set.

[0040] This ensures that backups will be created during at least one predefined backup activity (i.e., within at least one predefined time window).

[0041] Specifically, backup activity rules are rules that define the time windows in which backups can be created.

[0042] In another implementation of the first aspect, the first rule set includes a first retention period, the second rule set includes a second retention period, and the merge rule set includes the first retention period and the second retention period; and the merge backup strategy also defines that the backup retains the longer of the first retention period and the second retention period in predefined storage.

[0043] This ensures that the backup retention period is the longest possible.

[0044] Specifically, the predefined storage can be local storage or archive storage. Local storage is storage included in or directly attached to the device. Archive storage is separate storage located outside the device. In particular, archive storage is a cheaper storage tier, for example, used to retain copies for extended periods or to retain copies that are rarely accessed.

[0045] In another implementation of the first aspect, the first rule set includes a first backup replication rule, the second rule set includes a second backup replication rule, and the merge rule set includes the first backup replication rule and the second backup replication rule; and the merge backup strategy further defines replicating the backup according to each backup replication rule in the merge rule set.

[0046] This ensures that sufficient backup copies are maintained in predefined locations.

[0047] Specifically, backup replication rules define how long a copy is retained in predefined storage and / or which copy instance is retained in predefined storage.

[0048] In another implementation of the first aspect, the first rule set includes a first backup data format rule, the second rule set includes a second backup data format rule, and the merge backup strategy further defines the time period for which the backup is kept in a predefined data format based on the first backup data format rule, the second backup data format rule, the storage amount occupied by the backup created according to the first backup data format rule, and the storage amount occupied by the backup created according to the second backup data format rule.

[0049] This ensures that the backup format on which optimized storage backups are based is used.

[0050] Specifically, backup data format rules are rules that define how long backups are retained in a predefined data format (e.g., native format or deduplication format).

[0051] In another implementation of the first aspect, the device is further configured to: if the first backup policy and the second backup policy are assigned to the backup object, cancel the assignment of the first backup policy and the second backup policy from the backup object, and assign the merged backup policy to the backup object.

[0052] This ensures that the backup is created only according to the merged backup strategy, thereby saving resources by not creating additional backups based on the same first and second backup strategies.

[0053] In another implementation of the first aspect, the device is further configured to create a backup of the backup object based on the merged backup strategy.

[0054] This ensures that the device can also perform technical steps based on the merge backup strategy to actually create the backup.

[0055] A second aspect of the present invention provides a method for merging backup strategies, wherein the method includes the following steps: determining, by means of a device, whether a first backup strategy including a first set of rules and a second backup strategy including a second set of rules are assigned to a backup object; if the first backup strategy and the second backup strategy are assigned to the backup object, generating, by means of means of means a merged backup strategy including a merged set of rules based on the first backup strategy and the second backup strategy; wherein the resource consumption of the backup created according to the merged backup strategy is lower than a predefined threshold.

[0056] In one implementation of the second aspect, the resource consumption of the backup created according to the merged backup strategy is less than the sum of the resource consumption of the backup created according to the first backup strategy and the resource consumption of the backup created according to the second backup strategy.

[0057] In another implementation of the second aspect, the merge rule set is the union of the first rule set and the second rule set.

[0058] In another implementation of the second aspect, the merge backup strategy further defines the creation of the backup based on predefined rules in the merge rule set.

[0059] In another implementation of the second aspect, the merge backup strategy further defines creating the backup based on each rule in the merge rule set.

[0060] In another implementation of the second aspect, the merge backup strategy further defines creating the backup based on the maximum and / or minimum elements in the merge rule set.

[0061] In another implementation of the second aspect, the first rule set includes a first backup frequency rule, the second rule set includes a second backup frequency rule, and the merge rule set includes the first backup frequency rule and the second backup frequency rule; and the merge backup strategy further defines creating the backup according to each backup frequency rule in the merge rule set.

[0062] In another implementation of the second aspect, the first rule set includes a first backup activity rule, the second rule set includes a second backup activity rule, and the merge rule set includes the first backup activity rule and the second backup activity rule; and the merge backup strategy further defines creating the backup based on at least one backup activity rule in the merge rule set.

[0063] In another implementation of the second aspect, the first rule set includes a first retention period, the second rule set includes a second retention period, and the merge rule set includes the first retention period and the second retention period; and the merge backup strategy also defines that the backup retains the longer of the first retention period and the second retention period in predefined storage.

[0064] In another implementation of the second aspect, the first rule set includes a first backup replication rule, the second rule set includes a second backup replication rule, and the merge rule set includes the first backup replication rule and the second backup replication rule; and the merge backup strategy further defines replicating the backup according to each backup replication rule in the merge rule set.

[0065] In another implementation of the second aspect, the first rule set includes a first backup data format rule, the second rule set includes a second backup data format rule, and the merge backup strategy further defines the time period for which the backup is kept in a predefined data format based on the first backup data format rule, the second backup data format rule, the storage amount occupied by the backup created according to the first backup data format rule, and the storage amount occupied by the backup created according to the second backup data format rule.

[0066] In another implementation of the second aspect, the method further includes: if the first backup policy and the second backup policy are assigned to the backup object, then the assignment of the first backup policy and the second backup policy is canceled from the backup object by the device, and the merged backup policy is assigned to the backup object.

[0067] In another implementation of the second aspect, the method further includes creating a backup of the backup object by the device based on the merged backup strategy.

[0068] The second aspect and its implementation methods have the same advantages as the first aspect and its corresponding implementation methods.

[0069] A third aspect of the invention provides a computer program product including instructions that, when executed by a computer, cause the computer to perform the steps of the method of the second aspect or any implementation thereof.

[0070] The third aspect and its implementation methods include the same advantages as the second aspect and its corresponding implementation methods.

[0071] A fourth aspect of the invention provides a non-transitory computer-readable storage medium including instructions that, when executed by a computer, cause the computer to perform the steps of the method of the second aspect or any implementation thereof.

[0072] The fourth aspect and its implementation methods include the same advantages as the second aspect and its corresponding implementation methods.

[0073] In other words, this invention provides a scheme for merging multiple backup strategies into a new consistent strategy (i.e., the merged backup strategy). Therefore, when conflicts exist and multiple strategies are assigned to a single backup object, the scheme automatically creates a unified backup strategy that conforms to all strategy rules, generates the least amount of data, and does not require running multiple backup tasks or consuming more storage and CPU. When multiple backup strategies are assigned to a workload, the scheme automatically creates a new strategy (i.e., the merged backup strategy) and assigns it to the workload. The merged backup strategy merges all rules of available strategies by merging each rule, as will be explained below.

[0074] It should be noted that all devices, elements, units, and methods described in this application can be implemented in software or hardware elements or any combination thereof. All steps performed by the various entities described in this application and the functions to be performed by the various entities are intended to indicate that each entity is suitable for or used to perform its respective steps and functions. Although in the following description of specific embodiments, a particular function or step performed by an external entity is not reflected in the description of the specific element of the entity performing that particular step or function, it should be apparent to those skilled in the art that these methods and functions can be implemented in their respective hardware or software elements or any combination thereof. Attached Figure Description

[0075] The following description of specific embodiments, taken in conjunction with the accompanying drawings, will illustrate various aspects of the present invention and their implementations, wherein:

[0076] Figure 1 A schematic diagram of the device according to an embodiment of the present invention is shown;

[0077] Figure 2 A detailed schematic diagram of the device according to an embodiment of the present invention is shown;

[0078] Figure 3 A schematic diagram of a system according to an embodiment of the present invention is shown;

[0079] Figure 4 Another schematic diagram of the method according to an embodiment of the present invention is shown. Detailed Implementation

[0080] Figure 1 A schematic diagram of a device 100 according to an embodiment of the present invention is shown. The device 100 is used to merge backup policies 101 and 103. To this end, the device 100 is used to determine whether a first backup policy 101, which includes a first rule set 102, and a second backup policy 103, which includes a second rule set 104, are assigned to a backup object 105.

[0081] If the first backup policy 101 and the second backup policy 103 are assigned to the backup object 105, the device 100 is further configured to generate a merged backup policy 106 including a merged rule set 107 based on the first backup policy 101 and the second backup policy 103.

[0082] In other words, the merge backup strategy 106 is a merge backup strategy based on the contents of the first backup strategy 101 and the second backup strategy 103. Specifically, the merge rule set 107 is a merge rule set based on the first rule set 102 and the second rule set 104.

[0083] The resource consumption of backup 108 created according to the merged backup strategy 106 is lower than a predefined threshold. That is, creating backup 108 according to the merged backup strategy 106 helps save resources compared to creating backup 108 based on the first backup strategy 101 and the second backup strategy 103. Furthermore, the backup process involving only the merged backup strategy 106 can be automated more efficiently because no user interaction is required (e.g., to resolve conflicts in the backup strategy).

[0084] Specifically, backup 108 created according to the merge backup policy 106 (which involves processing rules in the merge rule set 107) conforms to the same service level agreement (SLA). If a backup is created according to the first backup policy 101 and also separately according to the second backup policy 103, the SLA will also be satisfied. In other words, backup 108 conforms to the SLA if it satisfies the SLA.

[0085] SLA refers to the agreed-upon specifications for service content, delivery metrics, and the acceptable range of these metrics (such as performance, capacity, availability, connectivity, redundancy, etc.). Within the scope of storage or backup systems, the term SLA is short for "Data Protection SLA" for backup objects.

[0086] Figure 2 A detailed schematic diagram of the device 100 according to an embodiment of the present invention is shown. Figure 2 The device 100 shown includes Figure 1 In addition to all the features and functions of the device 100 shown, the following optional features are also included:

[0087] like Figure 2 As shown, a first backup 201 can typically be created according to the first backup strategy 101, resulting in corresponding resource consumption. Similarly, a second backup 202 can typically be created according to the second backup strategy 103, also resulting in corresponding resource consumption. However, the resource consumption of the backup 108 created according to the merge backup strategy 106 is less than the sum of the resource consumption of the backup 201 created according to the first backup strategy 101 and the resource consumption of the backup 202 created according to the second backup strategy 103.

[0088] In a specific embodiment, this is because fewer steps are required when creating the backup 108 based on the merge rule set 107 compared to creating the first backup 201 based on the first rule set 102 and creating the second backup 202 based on the second rule set 104.

[0089] Optionally, the merge rule set 107 can be the union of the first rule set 102 and the second rule set 104. That is, when merging the first rule set 102 and the second rule set 104, the occurrence of identical dual elements in the merge rule set 107 is avoided. In other words, in this case, fewer rules need to be processed when creating backup 108 based on the merge rule set 107 compared to creating backups 201 and 202 based on the first rule set 102 and the second rule set 104 respectively.

[0090] Optionally, the merge backup strategy 106 can also define the creation of the backup 108 based on predefined rules 203 in the merge rule set 107. This avoids the need to create the backup 108 based on unnecessary rules, for example, when creating the backup 108 based on the predefined rules 203 can already meet the SLA.

[0091] Optionally, the merge backup strategy 106 may also define the creation of the backup 108 based on each rule in the merge rule set 107. This ensures that the backup 108 is created based on all necessary rules, for example, in cases where creating the backup 108 based on all rules in the merge rule set 107 would satisfy the SLA.

[0092] Optionally, the merge backup strategy 106 can also define the creation of the backup 108 based on the maximum element 204 and / or the minimum element 205 in the merge rule set 107. This ensures that the backup 108 is created based on the required maximum element 204 or minimum element 205, for example, when creating the backup 108 based solely on the maximum element 204 and / or minimum element 205 in the merge rule set 107 already satisfies the SLA. Therefore, creating the backup 108 based on other unnecessary elements can be avoided.

[0093] like Figure 2 As further shown, the first rule set 102 may include a first backup frequency rule 206, the second rule set 104 may include a second backup frequency rule 207, and the merge rule set 107 may include the first backup frequency rule 206 and the second backup frequency rule 207. The merge backup strategy 106 may also define the creation of the backup 108 based on each backup frequency rule 206, 207 in the merge rule set 107. Therefore, the backup 108 can be created at all time points defined in the first backup strategy 101 and the second backup strategy 103.

[0094] Specifically, backup frequency rules 206 and 207 define the frequency at which the backup 108 is created (e.g., hourly, daily, weekly, monthly). Specifically, frequency rules 206 and 207 define the backup frequency and / or backup retention.

[0095] More specifically, the backup frequency can be specified by the time interval 108 (every X time units) between backups. Backup frequency rules 206, 207 may include at least one of the following time intervals: hourly: every X hours; daily: every X days; weekly: every X weeks, on <working days (Sunday / Monday / ...)>; monthly: every X months, on <the 1st / 2nd / 3rd / 4th <working days> of each month>; quarterly: every X quarters; the first quarter of the year begins in <month>, on the <first / last><working day> of the quarter; annually: every X years; the first month of the year begins in <month>, on the <first / last><working day> of the year.

[0096] The specific implementation method for merging backup frequency rules 206 and 207 can be described as follows:

[0097] For example, if the first backup policy 101 is an hourly policy and (in the first rule set 102) defines a backup every two hours, while the second backup policy 103 is an hourly policy and (in the second rule set 104) defines a backup every four hours, then the merge rule set 107 in the merge backup policy 106 will define the backup 108 to be created every two hours. Generally, the number of hourly backups 108 (according to the merge rule set 107) will be the maximum value of all rules (i.e., the first rule set 102 and the second rule set 104). If a specific rule specifies that a backup 108 is created at a specific time, then all backups created according to those specific times will be included.

[0098] According to another example regarding daily backups, where the first rule set 102 defines creating a backup every two days, the second rule set 104 defines creating a backup every Sunday, and the merge backup policy 106 and the merge rule set 107 define creating the backup 108 every two days, but if backup 108 is created on Saturday, it will also be created on Sunday. The device 100 will create backups at the minimum frequency to ensure compliance with all backup frequency rules 206 and 207.

[0099] like Figure 2 As further shown, the first rule set 102 may include a first backup activity rule 208, and the second rule set 104 may include a second backup activity rule 209.

[0100] The merge rule set 107 may include the first backup activity rule 208 and the second backup activity rule 209, and the merge backup strategy 106 may also define the creation of the backup 108 based on at least one backup activity rule 208, 209 in the merge rule set 107.

[0101] Alternatively, backup activity rules 208 and 209 can restrict backup activity to a daily backup window, that is, a specific time range within a day. <hh:mm-hh:mm>Perform the copying activity. By default, no backup window is defined, meaning the backup 108 can be created at any time.

[0102] Optionally, backup activity rules 208 and 209 may begin creating backup 108 at a specific date and time. If another relevant backup window interval is exceeded, backup 108 will begin creation within the next backup window. By default, the first full backup will begin according to the frequency rules.

[0103] Backup activity rules 208 and 209 can be merged according to the following example: When merging backup activity rules 208 and 209, at least one of the backup activity rules 208 and 209 is defined to be followed in the merge backup policy 106. That is, it can be assumed that the backup activity rules 208 and 209 have an "OR" relationship because backup activity rules 208 and 209 define when backup activity is allowed. If multiple backup activity rules 208 and 209 are applied, the backup activity is allowed when one of the rules allows it.

[0104] For example, if one backup activity rule 208 defines that a backup should start between 8:00 AM and 10:00 AM, and another backup activity rule 209 defines that a backup should start between 9:00 AM and 12:00 PM, then backup 108 can be created between 8:00 AM and 12:00 PM.

[0105] like Figure 2 As further shown, the first rule set 102 may include a first retention period 210, and the second rule set 104 may include a second retention period 211. The merge rule set 107 may include the first retention period 210 and the second retention period 211, wherein the merge backup strategy 106 may also define that the backup 108 retains the longer of the first retention period 210 and the second retention period 211 in the predefined storage 212.

[0106] Retention periods 210 and 211 also define storage 212 for storing the backup 108, which can also be referred to as archiving rules. For example, the predefined storage 212 can be local storage or archive.

[0107] Archives can be used to offload backup 108 to a cheaper tier, where it is typically retained for a long time. As backup 108 becomes "colder" over time (i.e., less relevant and accessed less), it can be moved from local storage (more expensive, smaller) to archives (cheaper, larger) at some point. There are also more granular cases that can be managed using appropriate archive rules.

[0108] Retention periods 210 and 211 define the duration for which backup 108 is retained in local storage before being archived. For example, retention periods 210 and 211 can be specified in days, weeks, months, quarters, or years. For example, the maximum retention time for retention periods 210 and 211 can be defined in backup frequency rules 206 and 207. Backup 108 cannot be retained in local storage for longer than this maximum possible retention period.

[0109] However, the backup 108 can be archived while being retained locally. For example, the archive could be tape storage, a network file system (NFS), the cloud, etc. Specifically, local storage can be directly attached to the device 100. More specifically, the archive could be a separate and cheaper storage tier, for example, located outside the backup device, for long-term retention of the backup 108, or for retaining the backup 108 that is rarely accessed.

[0110] According to a specific example, a merge backup strategy 106 having a merge rule set 107 that includes a first retention period 210 and a second retention period 211 (also referred to as archiving rules) may include at least one of the following three specifications:

[0111] 1. How long the backup is retained in local storage (e.g., local secondary storage): This value will be the maximum of the first retention period 210 and the second retention period 211. Therefore, if the first retention period 210 defines retaining the backup 108 locally for 1 day, and the second retention period 211 defines retaining it for 3 days, then the merge backup policy 106 with the merge rule set 107 will be defined as retaining the backup 108 locally for 3 days.

[0112] 2. When will the backup 108 be moved to the archive: This value will be the minimum of the first retention period 210 and the second retention period 211. If the first retention period 210 defines that the backup 108 will be archived immediately, then the backup will be archived immediately, regardless of how the second retention period 211 is defined.

[0113] 3. How long will backup 108 be retained in the archive: This value will be the maximum of the first retention period 210 and the second retention period 211. For example, if the first retention period 210 defines retaining backup 108 in the archive for 1 month, and the second retention period 211 defines retaining the data for 3 months, then the merge backup strategy 106 with the merge rule set 107 will be defined as retaining the data for 3 months. If the first retention period 210 or the second retention period 211 includes a compliance rule that defines that the backup retention period does not need to exceed that period, then the merge backup strategy 106 will be defined as the retention period of backup 108 not exceeding the period specified by the compliance rule.

[0114] Specifically, retention refers to the act of retaining backup 108, and the retention period is usually a time period based on a policy. When backup 108 reaches its valid retention period, it can be removed. This is also known as expiration.

[0115] like Figure 2 As further shown, the first rule set 102 may include a first backup replication rule 213, and the second rule set 104 may include a second backup replication rule 214. The merge rule set 107 may include the first backup replication rule 213 and the second backup replication rule 214. The merge backup strategy 106 may also define how to replicate the backup 108 according to each backup replication rule in the merge rule set 107.

[0116] The replica is a copy of backup 108, copied from local storage to a (typically) remote system for disaster recovery purposes. Typically, the replica is a copy of backup 108 stored near a location where disaster recovery may be required.

[0117] For example, in order to recover quickly from a current disaster (typically at a disaster recovery site), replication is required. Therefore, when replication is used, a copy of backup 108 is copied once backup 108 is created.

[0118] Replication rules 213 and 214 can specify a copy retention period. This can include retaining only the most recent copy (for example, this is the default setting). Alternatively, this can include retaining a copy of backup 108 according to a specified copy retention period. For example, the retention period can be specified in units of days, weeks, months, quarters, or years.

[0119] To merge the first replication rule 213 and the second replication rule 214, the merge backup strategy 106 can define that both the first replication rule 213 and the second replication rule 214 are part of the merge rule set 107, and all replication rules 213 and 214 in the merge rule set will be applied to backup creation. That is, the backup replication rules will be merged in a manner similar to the backup frequency rules 206 and 207. For example, the replication will begin at the earliest time point defined in either the first replication rule 213 or the second replication rule 214.

[0120] like Figure 2 As further shown, the first rule set 102 may include a first backup data format rule 215, the second rule set 104 may include a second backup data format rule 216, and the merge backup strategy 106 may define a time period 217 for the backup 108 to be kept in a predefined data format based on the first backup data format rule 215, the second backup data format rule 216, the storage amount occupied by the backup 108 created according to the first backup data format rule 215, and the storage amount occupied by the backup 108 created according to the second backup data format rule 216.

[0121] In other words, when the merge backup strategy 106 is created, the space occupied by the backup 108 created according to the first backup data format rule 215 and the space occupied by the backup 108 created according to the second backup data format rule 216 are evaluated to define the data format required to retain the backup 108 for a predefined time period 217.

[0122] According to backup data format rules 215 and 216, backup 108 can be retained in multiple formats:

[0123] For example, this could include native formats that have lower space utilization but support rapid disaster recovery or rapid testing and development.

[0124] This can also include deduplication formats, which are efficient in using space but cannot be immediately used for disaster recovery or testing and development.

[0125] When backup 108 is archived, it is saved in a deduplicated format. When the data is copied, it is saved in the native format. However, locally stored backups can also be saved in either a deduplicated or native format.

[0126] There may also be data format rules that define the backup 108 to be retained in the native format for a period of time, and then converted to a deduplication format (either locally or sent to an external archive).

[0127] When the merge backup strategy 106 is created to define the time period 217 for saving the backup 108 in a predefined data format (based on the first backup data format rule 215 and the second backup data format rule 216), it is worth noting that the first backup data format rule 215 can specify saving the backup 108 in a deduplicated format and retaining it for a relatively long time (e.g., one month), while the second backup data format rule 216 can define saving the backup 108 in a native format but retaining it for only a short time (e.g., one week). However, saving the backup 108 in a native format is much more expensive.

[0128] According to one example, the merge backup strategy 106 can define saving the backup 108 in native format for a duration equal to the longest period of time defined in the first backup data format rule 215 or the second backup data format rule 216 for saving in native format. The backup 108 can then be saved in a deduplicated format.

[0129] Furthermore, since the deduplication format backup 108 may consume a large amount of space, there are several options available for saving the backup 108 in a hybrid format:

[0130] 1. The device 100 can assess the amount of space required to save the backup 108 in native format for the longest time period (e.g., for backup frequency intervals) defined in backup data format rules 215 and 216, and compare it with the amount of space required to save the backup 108 in native format for the desired predefined time period, and then convert it to a deduplication format. If the deduplication format does not save space, the device 100 will save the backup 108 in native format.

[0131] 2. The device 100 can also create a deduplication format. When the backup 108 becomes old, it saves the differences from the oldest native format image in a deduplication format. This deduplication format can significantly save space.

[0132] In a specific embodiment, the first option described above allows the use of other backup devices to manage the backup 108, while the second option described above requires a specific backup device, which is part of policy management.

[0133] In a specific embodiment, the example algorithm for merging backup strategies 101 and 103 can be implemented as follows:

[0134] The algorithm obtains Policy1 (i.e., the first backup policy 101) and Policy2 (i.e., the second backup policy 103). Policy1 and Policy2 will be merged into Policy3.

[0135] Policy1 includes backup-frequency-rule-1, backup-data-format-rule-1, backup-activity-rule-1, backup-retention-period-1, and backup-replication-rule-1.

[0136] Policy2 includes backup-frequency-rule-2, backup-data-format-rule-2, backup-activity-rule-2, backup-retention-period-2 and backup-replication-rule-2.

[0137] The merging algorithm will create a new policy, Policy3 (i.e., the merging backup policy 106).

[0138] Policy3 includes backup-frequency-rule-3, backup-data-format-rule-3, backup-activity-rule-3, backup-retention-period-3, and backup-replication-rule-3.

[0139] According to the processing of the device 100 that created the merge backup policy:

[0140] - The backup 108 created based on backup-frequency-rule-3 is a superset of the backup created based on backup-frequency-rule-1 and the backup created based on backup-frequency-rule-2;

[0141] - The backup 108 created based on backup-data-format-rule-3 is saved in native format for a longer or equal duration than those based on backup-data-format-rule-1 and backup-data-format-rule-2;

[0142] -According to backup-activity-rule-3, backup 108 can be created when backup-activity-rule-1 or backup-activity-rule-2 allows it;

[0143] -backup-retention-period-3 ensures that the backup 108 is archived when it needs to be archived based on backup-retention-period-1 or backup-retention-period-2;

[0144] -backup-replication-rule-3 will ensure that the replica is created when it should be created according to backup-replication-rule-1 or backup-replication-rule-2.

[0145] After all policy parameters are defined, a new policy (i.e., the merge backup policy 106) will be defined and assigned to the backup object 105.

[0146] If the first backup policy 101 and the second backup policy 103 are assigned to the backup object 105, the device 100 can remove the assignment of the first backup policy 101 and the second backup policy 103 from the backup object 105. The merge backup policy 106 will then be assigned to the backup object 105. Thus, the device 100 will no longer create the backup based on the first backup policy 101 and the second backup policy 103, but will create the backup only based on the merge backup policy 106.

[0147] The device 100 can also create the backup 108 of the backup object 105 based on the merge backup policy 106. That is, the device 100 not only creates the merge backup policy 106 including the merge rule set 107, but also performs the necessary technical steps to create the backup 108 based on the merge backup policy 106. Specifically, it copies data to storage based on the merge backup policy 106.

[0148] In a specific embodiment, the protected object may have unique metadata attributes (i.e., fingerprints), which can deterministically identify the protected object by changes that may occur in its native environment. The set of these attributes constitutes the protected object fingerprint.

[0149] Figure 3 A system 300 according to an embodiment of the present invention is shown. The system 300 is a backup system and includes the device 100. The system 300 also includes local storage 301. Although... Figure 3 The device 100 and the local storage 301 are shown as separate entities, but the device 100 may also include the local storage 301, or the device 100 and the local storage 301 may be configured as a single entity (e.g., Figure 3 (As shown in the dashed box).

[0150] The system 300 also includes several hosts 302, 303, and 304 (e.g., mainframe computers, i.e., physical computers). Thus, host 302 runs three virtual machines 302a, 302b, and 302c. However, the hosts and virtual machines can be arbitrarily distributed within the backup system 300. The system 300 also includes an archive 305 (i.e., storage for cold backups, which is less expensive). The system 300 also includes a replica site 306, i.e., storage associated with the host, or the virtual machines to which backups are restored. For example, all these entities are connected via a network connection.

[0151] The hosts 302, 303, 304 and the virtual machines 302a, 302b, 302c are backup objects 105. Figure 3 The device 100 is used to create a backup 108 of backup object 105 based on the merge backup strategy 106, as described in one of the above figures. For ease of explanation, Figure 3 The backup 108 and the merge backup strategy 106 are not shown in the diagram.

[0152] Typically, the backup 108 created by the backup device 100 is stored in the local storage 301. According to the merge backup strategy 106, the backup 108 can be defined to be stored in a predefined storage 212 (i.e., for example, in local storage 301 or archive 305). There, the retention period of the backup 108 can be the longer of a first retention period 210 and a second retention period 211, as illustrated in the example above.

[0153] The backup 108 created by the device 100 according to the merge backup policy 106 can also be stored in the replica site 306. The replica site 306 is associated with the backup object 105 to which the backup 108 may be restored. Figure 3 Alternatively, a backup 108 of the host 304, initially stored in the local storage 301, can be copied to the replica site 306. It can then be easily restored from the replica site 306 to the host 304. Therefore, backup 108 can be restored to the host 304 at the replica site, rather than to the production host. Restoration can be controlled by the merge backup policy 106, which defines how backup 108 should be copied according to backup replication rules 213 and 214 in the merge rule set 107.

[0154] The merge backup strategy 106 can also define a time period 217 in which the backup 108 is stored in a predefined data format in, for example, the local storage 301, the archive 305 and / or the replica site 306.

[0155] The backup 108 can be restored from the local storage 301, the archive 305, or the replica site 306 to a corresponding one of the backup objects 105 (controlled by the device 100). The device 100 may only control the restoration process, that is, restore the backup 108 directly to the backup object 105, rather than indirectly through the device 100. However, the device 100 may also receive and forward data to be restored.

[0156] Figure 4 A schematic diagram of a method 400 according to an embodiment of the present invention is shown. The method 400 is used to merge backup policies 101 and 103, and includes the following steps: determining, via device 100, whether a first backup policy 101 including a first rule set 102 and a second backup policy 103 including a second rule set 104 are assigned to a backup object 105. The method further includes the following steps: if the first backup policy 101 and the second backup policy 103 are assigned to the backup object 105, then via device 100 generating a merged backup policy 106 including a merged rule set 107 based on the first backup policy 101 and the second backup policy 103; wherein the resource consumption of the backup 108 created according to the merged backup policy 106 is lower than a predefined threshold.

[0157] This invention has been described in conjunction with various embodiments as examples and implementations. However, those skilled in the art, through practice of the claimed invention, study of the accompanying drawings, the invention itself, and the independent claims, will understand and derive other variations. In the claims and description, the word "comprising" does not exclude other elements or steps, and the word "an" does not exclude a plurality. A single element or other unit may fulfill the function of several entities or items recited in the claims. The enumeration of certain measures in dissimilar dependent claims does not imply that combinations of these measures cannot be used in advantageous implementations.

Claims

1. A device (100) for a merge backup policy (101, 103), characterized in that, The device (100) is configured to: determine whether a first backup policy (101) comprising a first rule set (102) and a second backup policy (103) comprising a second rule set (104) are assigned to a backup object (105); if the first backup policy (101) and the second backup policy (103) are assigned to the backup object (105), generate a merged backup policy (106) comprising a merged rule set (107) based on the first backup policy (101) and the second backup policy (103); wherein a resource consumption of a backup (108) created according to the merged backup policy (106) is below a predefined threshold, the resource consumption of the backup (108) created according to the merged backup policy (106) is less than a sum of a resource consumption of a backup (201) created according to the first backup policy (101) and a resource consumption of a backup (202) created according to the second backup policy (103); wherein the first rule set (102) comprises a first backup data format rule (215), the second rule set (104) comprises a second backup data format rule (216); and the merged backup policy (106) further defines a time period (217) in which the backup (108) remains in a predefined data format based on the first backup data format rule (215), the second backup data format rule (216), a storage amount occupied by the backup (108) created according to the first backup data format rule (215), and a storage amount occupied by the backup (108) created according to the second backup data format rule (216).

2. The device (100) according to claim 1, characterized in that The merged rule set (107) is a union of the first rule set (102) and the second rule set (104).

3. The device (100) according to claim 1 or 2, characterized in that The merged backup policy (106) further defines that the backup (108) is created based on a predefined rule (203) in the merged rule set (107).

4. The device (100) according to any one of claims 1 to 2, characterized in that, The merged backup policy (106) further defines that the backup (108) is created based on each rule in the merged rule set (107).

5. The device (100) according to any one of claims 1 to 2, characterized in that, The merged backup policy (106) further defines that the backup (108) is created based on a maximum element (204) and / or a minimum element (205) in the merged rule set (107).

6. The device (100) according to any one of claims 1 to 2, characterized in that The first rule set (102) comprises a first backup frequency rule (206), the second rule set (104) comprises a second backup frequency rule (207), and the merged rule set (107) comprises the first backup frequency rule (206) and the second backup frequency rule (207); and the merged backup policy (106) further defines that the backup (108) is created according to each backup frequency rule (206, 207) in the merged rule set (107).

7. The device (100) according to any one of claims 1 to 2, characterized in that the first rule set (102) comprises a first backup activity rule (208), the second rule set (104) comprises a second backup activity rule (209), and the merged rule set (107) comprises the first backup activity rule (208) and the second backup activity rule (209); and the merged backup policy (106) further defines to create the backup (108) according to at least one backup activity of the merged rule set (107).

8. The device (100) according to any one of claims 1 to 2, characterized in that the first rule set (102) comprises a first retention period (210), the second rule set (104) comprises a second retention period (211), and the merged rule set (107) comprises the first retention period (210) and the second retention period (211); and the merged backup policy (106) further defines that the backup (108) is retained in a predefined storage (212) for the longer one of the first retention period (210) and the second retention period (211).

9. The device (100) according to any one of claims 1 to 2, characterized in that, the first rule set (102) comprises a first backup copy rule (213), the second rule set (104) comprises a second backup copy rule (214), and the merged rule set (107) comprises the first backup copy rule (213) and the second backup copy rule (214); and the merged backup policy (106) further defines to copy the backup (108) according to each backup copy rule of the merged rule set (107).

10. The device (100) according to any one of claims 1 to 2, characterized in that, further configured to, if the first backup policy (101) and the second backup policy (103) are assigned to the backup object (105), cancel the assignment of the first backup policy (101) and the second backup policy (103) from the backup object (105) and assign the merged backup policy (106) to the backup object (105).

11. The device (100) according to any one of claims 1 to 2, characterized in that further configured to create the backup (108) of the backup object (105) based on the merged backup policy (106).

12. A method (400) for merging backup policies (101, 103), characterized by, the method (400) comprises the following steps: determining (401), by a device (100), whether a first backup policy (101) comprising a first rule set (102) and a second backup policy (103) comprising a second rule set (104) are assigned to a backup object (105); if the first backup policy (101) and the second backup policy (103) are assigned to the backup object (105), generating (402), by the device (100), a merged backup policy (106) comprising a merged rule set (107) based on the first backup policy (101) and the second backup policy (103); wherein a resource consumption of a backup (108) created according to the merged backup policy (106) is lower than a predefined threshold, the resource consumption of the backup (108) created according to the merged backup policy (106) being less than a sum of a resource consumption of a backup (201) created according to the first backup policy (101) and a resource consumption of a backup (202) created according to the second backup policy (103); wherein the first rule set (102) comprises a first backup data format rule (215) and the second rule set (104) comprises a second backup data format rule (216); and the merged backup policy (106) further defines a time period (217) for which the backup (108) is to remain in a predefined data format based on the first backup data format rule (215), the second backup data format rule (216), a storage amount occupied by the backup (108) created according to the first backup data format rule (215), and a storage amount occupied by the backup (108) created according to the second backup data format rule (216).

13. A computer program product comprising instructions, characterized in that, The instructions, when executed by a computer, cause the computer to perform the steps of the method (400) of claim 12.

Images