WO2025087516A1 - Method for generation of backup service level agreement based on deep content analysis - Google Patents
Method for generation of backup service level agreement based on deep content analysis Download PDFInfo
- Publication number
- WO2025087516A1 WO2025087516A1 PCT/EP2023/079718 EP2023079718W WO2025087516A1 WO 2025087516 A1 WO2025087516 A1 WO 2025087516A1 EP 2023079718 W EP2023079718 W EP 2023079718W WO 2025087516 A1 WO2025087516 A1 WO 2025087516A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- memory controller
- application
- content
- backup
- further configured
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
Classifications
-
- G—PHYSICS
- G06—COMPUTING OR CALCULATING; COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/07—Responding to the occurrence of a fault, e.g. fault tolerance
- G06F11/14—Error detection or correction of the data by redundancy in operation
- G06F11/1402—Saving, restoring, recovering or retrying
- G06F11/1446—Point-in-time backing up or restoration of persistent data
- G06F11/1448—Management of the data involved in backup or backup restore
- G06F11/1451—Management of the data involved in backup or backup restore by selection of backup contents
-
- G—PHYSICS
- G06—COMPUTING OR CALCULATING; COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/07—Responding to the occurrence of a fault, e.g. fault tolerance
- G06F11/14—Error detection or correction of the data by redundancy in operation
- G06F11/1402—Saving, restoring, recovering or retrying
- G06F11/1446—Point-in-time backing up or restoration of persistent data
- G06F11/1458—Management of the backup or restore process
-
- G—PHYSICS
- G06—COMPUTING OR CALCULATING; COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/07—Responding to the occurrence of a fault, e.g. fault tolerance
- G06F11/14—Error detection or correction of the data by redundancy in operation
- G06F11/1402—Saving, restoring, recovering or retrying
- G06F11/1446—Point-in-time backing up or restoration of persistent data
- G06F11/1458—Management of the backup or restore process
- G06F11/1461—Backup scheduling policy
-
- G—PHYSICS
- G06—COMPUTING OR CALCULATING; COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F2201/00—Indexing scheme relating to error detection, to error correction, and to monitoring
- G06F2201/84—Using snapshots, i.e. a logical point-in-time copy of the data
Definitions
- the disclosure generally relates to backup policy selection, and more particularly, the disclosure relates to a memory controller configured to provide a backup for an application.
- the disclosure also relates to a method for a memory controller configured to backup for an application.
- Today's data center applications include a wide range of workloads.
- the wide range of workloads includes modern components and traditional components.
- the modern components may include containers, virtual machines, VMs, and cloud-based entities like functions. Each function has unique interaction strategies and mechanisms.
- the VMs are virtualization or emulation of a computer system.
- the VMs are based on computer architectures and provide the functionality of a physical computer. Their implementations may involve specialized hardware, software, or a combination of the two.
- the containers may be microservices and Kubernetes, K8S.
- the K8S is an open-source container orchestration system for automating software deployment, scaling, and management. Originally designed by Google, the project is now maintained by a cloud-native computing foundation.
- the modern elements and the traditional elements rely on a variety of storage systems.
- the variety of storage systems may be a combination of block, file, or object storage.
- the variety of storage systems may be shared storage systems or dedicated storage systems. Additionally, the data center applications may be incorporated with specialized hardware or other equipment.
- Modern applications may be any application that is developed and launched using the latest technologies, and cutting-edge development approaches, for delivering an optimal user experience.
- the modern applications are designed to be cloud-native and structured as a network of microservices that communicate through Application Programming Interfaces, APIs to a user, rather than traditional tightly integrated monolithic applications.
- the Microservices- based applications are commonly associated with cloud-native technologies like containers and Kubernetes, K8S.
- the modern applications are designed based on agility, scalability, portability, and reliability.
- the modern applications are designed as the microservices, rather than monolithic structures.
- the modern applications are developed using agile development methodologies and follow Development Operations, DevOps, with a heavy emphasis on automation throughout a continuous integration and delivery, CI/CD pipeline.
- An application discovery is a process of identifying and compiling all applications deployed and utilized within an enterprise.
- the application discovery enables gathering, monitoring, and managing of portfolios of all applications of the enterprise within an Information Technology, IT environment, or on individual computers and networks, such as business and/or productivity applications, database applications, and client and/or server applications.
- Computers are utilized in content analysis by automating a process of labeling or coding documents.
- Basic computational techniques may provide descriptive data such as word frequencies and document lengths.
- Machine learning classifiers label a wide range of texts.
- CATA program analyzes the texts based on predefined linguistic, semantic, and psychological attributes.
- a memory controller configured to provide backup for an application.
- the memory controller is further configured to detect one or more than one data storage asset utilized by the application.
- the memory controller is further configured to determine a type of content stored by the application in the data storage asset, determine a priority level for the data storage asset based on the type of content, and select a backup policy for the data storage asset based on the type of content, for each of the one or more than one data storage asset.
- the backup policy is selected to be one of a continuous data protection, CDP, technology, or a snapshot backup technology.
- the memory controller automatically generates backup Service Level Agreements, SLAs for the application using content-based backup policies.
- the memory controller protects the application by ensuring that all required assets and/or data are appropriately backed up with a proper backup policy.
- the memory controller adjusts the backup policy for the application in real time if the content in the data storage asset associated with the application is changed.
- the memory controller is further configured to determine the type of content based on meta-data for the data storage asset.
- the metadata relates to file attributes.
- the metadata relates to a file permission.
- the memory controller is further configured to select the backup policy to be continuous data protection, CDP, technology for type of content being indicated to be of high importance, and snapshot backup technology for other type(s) of content.
- the memory controller is further configured to indicate the type of content to be of high importance if the content relates to sensitive data, financial data, and/or encrypted data.
- the memory controller is further configured to indicate the type of content to be of high importance if the content relates to data having an update rate exceeding a threshold level.
- the memory controller is further configured to determine a snapshot frequency for the snapshot backup technology based on the type of content.
- a type of content having a first priority level is given a higher snapshot frequency than a type of content having a second.
- the first priority level is higher than the second priority level.
- the memory controller is further configured to indicate a low priority level to data content being source code file(s).
- the memory controller is further configured to indicate a low priority level to data content being at least one of configuration file(s) and static file(s).
- the static file is an image file (s).
- the memory controller is further configured to determine the type of content based on deep data inspection.
- the memory controller is further configured to determine the type of content based on resource consumption.
- the memory controller is further configured to detect one or more than one data storage asset utilized by the application by determining one or more than one services utilized by the application and determining one or more than one data storage asset utilized by the application to be one or more than one data storage asset utilized by the one or more than one services.
- the memory controller is further configured to determine the one or more than one services utilized by the application to include target services of the one or more than one services.
- the memory controller is further configured to determine a starting point for the application and detect one or more than one data storage asset utilized by the application based on a scan starting for the starting point.
- the memory controller is further configured to determine the starting point for the application to be one, some, or all of an application configuration file, application source code, an application deployment recipe, and/or an application access point.
- the memory controller is further configured to determine the starting point when at least one of an asset and a service instance is added to the application.
- the memory controller is further configured to provide the backup of a memory to a persistent storage.
- the memory controller is further configured to, before selecting a backup policy, determine if there is a service level agreement in place for an application, and if not generate a service level agreement for the application.
- the memory controller is further configured to determine if the service level agreement in place for the application is to be modified and if so, modifying the service level agreement for the application.
- the memory controller is further configured to provide the backup at intervals.
- the memory controller is further configured to receive a backup trigger and in response thereto provide the backup.
- a method for a memory controller configured to provide backup for an application.
- the method includes detecting one or more than one data storage asset utilized by the application.
- the method includes determining a type of content stored by the application in the data storage asset, determining a priority level for the data storage asset based on the type of content, and selecting a backup policy for the data storage asset based on the type of content, for each of the one or more than one data storage asset.
- the backup policy is selected to be one of a continuous data protection, CDP, technology, or a snapshot backup technology.
- This method automatically generates backup Service Level Agreements, SLAs for the application using content-based backup policies. This method protects the application by ensuring that all required assets and/or data are appropriately backed up with a proper backup policy. This method adjusts the backup policy for the application in real time if content in the data storage asset associated with the application is changed.
- a computer program product includes program instructions for performing the method when executed by one or more processors in a memory controller system.
- a memory controller is configured to provide backup for an application.
- the memory controller selects a backup policy efficiently for the application based on a type of content in the data storage asset of the application in real time.
- FIG. 1 is a block diagram that illustrates a memory controller configured to provide a backup for an application in accordance with an implementation of the disclosure
- FIG. 2 illustrates a block diagram of a service level agreement, SLA, generator to generate a backup service level agreement, SLA based on a deep content analysis for an application in accordance with an implementation of the disclosure
- FIG. 3 is a flow diagram that illustrates a method for method for a memory controller configured to provide a backup for an application in accordance with an implementation of the disclosure
- FIG. 4 is an illustration of a computer system (e.g., a memory controller) in which the various architectures and functionalities of the various previous implementations may be implemented.
- Implementations of the disclosure provide a memory controller and a method for the memory controller configured to provide a backup for an application.
- a process, a method, a system, a product, or a device that includes a series of steps or units is not necessarily limited to expressly listed steps or units but may include other steps or units that are not expressly listed or that are inherent to such process, method, product, or device.
- Service Level Agreement is a commitment between a service provider and a customer. Particular aspects of a service quality, availability, and responsibilities are agreed between the service provider and the service user.
- FIG. 1 is a block diagram that illustrates a memory controller 102 configured to provide a backup for an application 106 in accordance with an implementation of the disclosure.
- the application 106 includes a data storage asset 104.
- the memory controller 102 is associated with the application 106.
- the memory controller 102 is further configured to detect one or more than one data storage asset 104 utilized by the application 106.
- the memory controller 102 is further configured to determine a type of content stored by the application 106 in the data storage asset 104, determine a priority level for the data storage asset 104 based on the type of content, and select a backup policy for the data storage asset 104 based on the type of content, for each of the one or more than one data storage asset.
- the backup policy is selected to be one of a continuous data protection, CDP, technology, or a snapshot backup technology.
- the memory controller 102 automatically generates backup Service Level Agreements, SLAs for the application 106 using content-based backup policies.
- the memory controller 102 protects the application 106 by ensuring that all required assets and/or data are appropriately backed up with a proper backup policy.
- the memory controller 102 adjusts the backup policy for the application 106 in real-time if the content in the data storage asset 104 associated with the application 106 is changed.
- the memory controller 102 is further configured to determine the type of content based on meta-data for the data storage asset 104.
- the metadata relates to file attributes.
- the metadata relates to a file permission.
- the memory controller 102 is further configured to select the backup policy to be continuous data protection, CDP, technology for type of content being indicated to be of high importance, and snapshot backup technology for other type(s) of content.
- the memory controller 102 is further configured to indicate the type of content to be of high importance if the content relates to sensitive data, financial data, and/or encrypted data.
- the sensitive data may include information about a particular group of personal data on an individual such as religion, political opinions, sexual orientation, and biometric and genetic data.
- the financial data may include account numbers, company results, and bank transfer details.
- the memory controller 102 is further configured to indicate the type of content to be of high importance if the content relates to data having an update rate exceeding a threshold level.
- the memory controller 102 is further configured to determine a snapshot frequency for the snapshot backup technology based on the type of content. A type of content having a first priority level is given a higher snapshot frequency than a type of content having a second, wherein the first priority level is higher than the second priority level.
- the memory controller 102 is further configured to indicate a low priority level to data content being source code file(s).
- the memory controller 102 is further configured to indicate a low priority level to data content being at least one of configuration file(s) and static file(s).
- the static file is an image file (s).
- the memory controller 102 is further configured to determine the type of content based on deep data inspection.
- the memory controller 102 is further configured to determine the type of content based on resource consumption.
- the memory controller 102 is further configured to detect one or more than one data storage asset 104 utilized by the application 106 by determining one or more than one services utilized by the application 106 and determining one or more than one data storage asset 104 utilized by the application 106 to be one or more than one data storage asset 104 utilized by the one or more than one services.
- the memory controller 102 is further configured to determine the one or more than one services utilized by the application 106 to include target services of the one or more than one services.
- the memory controller 102 is further configured to determine a starting point for the application 106 and detect one or more than one data storage asset 104 utilized by the application 106 based on a scan starting for the starting point.
- the memory controller 102 is further configured to determine the starting point for the application 106 to be one, some, or all of an application configuration file, application source code, an application deployment recipe, and/or an application access point.
- the memory controller 102 is further configured to determine the starting point when at least one of an asset and a service instance is added to the application.
- the memory controller 102 determines the starting point or the starting point provided by a user of the application 106.
- the application 106 access the starting point with the application access point.
- the application access point may be a Uniform Resource Locator, URL, Internet Protocol, IP and port, process identification, ID, and the like.
- the memory controller 102 sets an empty list to represent protected assets associated with the starting point.
- the memory controller 102 retrieves metadata information relevant to the new data storage asset and detects the content in the new data storage asset based on the metadata information.
- the memory controller 102 retrieves the metadata information by (i) scanning a size of the block-level assets, (ii) scanning at least one type, size, tree structure, file attributes, or permissions of the file system assets, and (iii) scanning at least one type, table, schema, size, and indices of the database assets, while executing the deep content inspection algorithm on the data storage asset 104.
- the memory controller 102 may read data from the data storage asset 104 until the content is detected or a predefined threshold is exceeded.
- the predefined threshold includes an interval timeout or resource consumption limits.
- the memory controller 102 may read data from the new data storage asset by searching at least one (i) sensitive data, (ii) encrypted data, (iii) source codes and/or other static data, i.e. configuration files, and (iv) data that is changed frequently in the new data storage asset.
- the memory controller 102 is further configured to provide the backup of a memory to a persistent storage.
- the memory controller 102 is further configured to, before selecting a backup policy, determine if there is a service level agreement in place for an application 106, and if not generate a service level agreement for the application 106.
- the memory controller 102 is further configured to determine if the service level agreement in place for the application 106 is to be modified and if so, modifying the service level agreement for the application 106.
- the memory controller 102 is further configured to provide the backup at intervals.
- the memory controller 102 is further configured to receive a backup trigger and in response thereto provide the backup.
- FIG. 2 illustrates a block diagram of a service level agreement, SLA, generator 202 to generate a backup service level agreement, SLA 230 based on a deep content analysis for an application 204 in accordance with an implementation of the disclosure.
- the SLA generator 202 is associated with the application 204.
- the application 204 includes a first service 208, a second service 212, and a third service 216 that are deployed on a first host machine 206, a second host machine 210, and a third host machine 214.
- the first host machine 206 includes a block volume 218 and a Structured Query Language, SQL database, DB 220 that are utilized by the first service 208.
- the second host machine 210 includes a file system with sensitive data 222 that is utilized by the second service 212.
- the third host machine 214 includes a file system with static data 224 that is utilized by the third service 216.
- a cloud 228 that includes no SQL DB 226 that is utilized by the third service 216.
- the SLA generator 202 is configured to scan and analyze content in the application 204.
- the block volume 218 on the first host machine 206 may contain plain data that undergoes frequent modification due to operation of the first service 208 in real-time.
- the operations may be user data updates or transaction records, which enables the SLA generator 202 to generate a snapshot-based backup policy with a high interval for the block volume 218.
- the SQL database 220 on the first host machine 206 contains encrypted data i.e. important data which enables the SLA generator 202 to generate a Continuous Data Protection, CDP -based backup policy for the SQL database 220.
- the file system on the second host machine 210 contains sensitive data i.e. important data, which enables the SLA generator 202 to generate the CDP -based backup policy for the file system with sensitive data 222.
- the file system on the third host machine 214 contains the static data, which enables the SLA generator 202 to generate the snapshot-based backup policy with a low interval for the file system with static data 224.
- the No SQL database 226 on the third host machine 214 contains indexed data i.e. important data, which enables the SLA generator 202 to generate the CDP -based backup policy for the No SQL database 226.
- the SLA generator 202 generates the backup SLA 230 for a volume based on a priority level of a content stored inside the volume.
- the volume may be the block volume 218, the SQL DB 220, the file system with sensitive data 222, and the file system with static data 224.
- the SLA generator 202 generates the backup SLA 230 based on the volume.
- the volume with a high level priority may be set as the Continues data protection, CDP backup policy
- the volume with a low level priority may be set as the snapshot backup policy at low frequency
- the volume with a medium level may be set as the snapshot backup policy at high frequency.
- the high level priority of volume may be encrypted data, data related to the application 204 with login details, or a database with high traffic.
- the low level priority of the volume may be browser element data, configuration file, or source code.
- the backup SLA 230 is stored in a backup storage 232 for the application 204 once the backup SLA 230 is generated by the SLA generator 202.
- a memory controller of the application 204 creates the backup SLA 230 for the application 204 or updates the backup SLA 230 if the backup SLA 230 already exists for the application 204, ensuring the backup policy for the application 204 is appropriately provided for each volume.
- the memory controller enables the SLA generator 202 again to generate the backup SLA 230 for the application 204 to detect changes in the application 204 and/or if any content exists in the volume.
- FIG. 3 is a flow diagram that illustrates a method for a memory controller configured to provide a backup for an application in accordance with an implementation of the disclosure.
- the method includes detecting one or more than one data storage asset utilized by an application.
- the method includes determining a type of content stored by the application in the data storage asset, determining a priority level for the data storage asset based on the type of content, and selecting a backup policy for the data storage asset based on the type of content, for each of the one or more than one data storage asset.
- the backup policy is selected to be one of a continuous data protection, CDP, technology, or a snapshot backup technology.
- This method automatically generates a backup Service Level Agreements, SLAs for the application using content-based backup policies.
- This method protects the application by ensuring that all required assets and/or data are appropriately backed up with a proper backup policy.
- This method adjusts the backup policy for the application in real-time if the content in the data storage asset associated with the application is changed.
- a computer program product comprising program instructions for performing the method, when executed by one or more processors in a memory system.
- FIG. 4 is an illustration of a computer system (e.g., a memory controller) in which the various architectures and functionalities of the various previous implementations may be implemented.
- the computer system 400 includes at least one processor 404 that is connected to a bus 402, wherein the computer system 400 may be implemented using any suitable protocol, such as Peripheral Component Interconnect, PCI-Express, Accelerated Graphics Port, AGP, Hyper Transport, or any other bus or point-to-point communication protocol.
- the computer system 400 also includes a memory 406.
- Control logic (software) and data are stored in the memory 406 which may take a form of random-access memory, RAM.
- a single semiconductor platform may refer to a sole unitary semiconductor-based integrated circuit or chip. It should be noted that the term single semiconductor platform may also refer to multi-chip modules with increased connectivity which simulate on-chip modules with increased connectivity which simulate on- chip operation, and make substantial improvements over utilizing a conventional central processing unit, CPU and bus implementation. Of course, the various modules may also be situated separately or in various combinations of semiconductor platforms per the desires of the user.
- the computer system 400 may also include a secondary storage 410.
- the secondary storage 410 includes, for example, a hard disk drive and a removable storage drive, representing a floppy disk drive, a magnetic tape drive, a compact disk drive, digital versatile disk, DVD drive, recording device, universal serial bus, USB flash memory.
- the removable storage drive at least one of reads from and writes to a removable storage unit in a well-known manner.
- Computer programs, or computer control logic algorithms may be stored in at least one of the memory 406 and the secondary storage 410. Such computer programs, when executed, enable the computer system 400 to perform various functions as described in the foregoing.
- the memory 406, the secondary storage 410, and any other storage are possible examples of computer-readable media.
- the architectures and functionalities depicted in the various previous figures may be implemented in the context of the processor 404, a graphics processor coupled to a communication interface 412, an integrated circuit (not shown) that is capable of at least a portion of the capabilities of both the processor 404 and a graphics processor, a chipset (namely, a group of integrated circuits designed to work and sold as a unit for performing related functions, and so forth).
- the architectures and functionalities depicted in the various previous-described figures may be implemented in a context of a general computer system, a circuit board system, a game console system dedicated for entertainment purposes, an application-specific system.
- the computer system 400 may take the form of a desktop computer, a laptop computer, a server, a workstation, a game console, an embedded system.
- the computer system 400 may take the form of various other devices including, but not limited to a personal digital assistant, PDA device, a mobile phone device, a smart phone, a television, and so forth. Additionally, although not shown, the computer system 400 may be coupled to a network (for example, a telecommunications network, a local area network, LAN, a wireless network, a wide area network, WAN such as the Internet, a peer-to-peer network, a cable network, or the like) for communication purposes through an I/O interface 408.
- a network for example, a telecommunications network, a local area network, LAN, a wireless network, a wide area network, WAN such as the Internet, a peer-to-peer network, a cable network, or the like
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Quality & Reliability (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
Abstract
A memory controller 102 is configured to provide a backup for an application 106, 204. The memory controller 102 is further configured to provide the backup to detect one or more than one data storage asset 104 utilized by the application 106, 204, The memory controller 102 is further configured to determine a type of content stored by the application 106, 204 in the data storage asset 104, determine a priority level for the data storage asset 104 based on the type of content, and select a backup policy for the data storage asset 104 based on the type of content, for each of the one or more than one data storage asset 104. The backup policy is selected to be one of a continuous data protection, CDP, technology, or a snapshot backup technology.
Description
METHOD FOR GENERATION OF BACKUP SERVICE LEVEL AGREEMENT
BASED ON DEEP CONTENT ANALYSIS
TECHNICAL FIELD
The disclosure generally relates to backup policy selection, and more particularly, the disclosure relates to a memory controller configured to provide a backup for an application. The disclosure also relates to a method for a memory controller configured to backup for an application.
BACKGROUND
Today's data center applications include a wide range of workloads. The wide range of workloads includes modern components and traditional components. The modern components may include containers, virtual machines, VMs, and cloud-based entities like functions. Each function has unique interaction strategies and mechanisms. The VMs are virtualization or emulation of a computer system. The VMs are based on computer architectures and provide the functionality of a physical computer. Their implementations may involve specialized hardware, software, or a combination of the two. The containers may be microservices and Kubernetes, K8S. The K8S is an open-source container orchestration system for automating software deployment, scaling, and management. Originally designed by Google, the project is now maintained by a cloud-native computing foundation. The modern elements and the traditional elements rely on a variety of storage systems. The variety of storage systems may be a combination of block, file, or object storage. The variety of storage systems may be shared storage systems or dedicated storage systems. Additionally, the data center applications may be incorporated with specialized hardware or other equipment.
Modern applications may be any application that is developed and launched using the latest technologies, and cutting-edge development approaches, for delivering an optimal user experience. The modern applications are designed to be cloud-native and structured as a network of microservices that communicate through Application Programming Interfaces, APIs to a user, rather than traditional tightly integrated monolithic applications. The Microservices- based applications are commonly associated with cloud-native technologies like containers and Kubernetes, K8S. The modern applications are designed based on agility, scalability, portability, and reliability. The modern applications are designed as the microservices, rather
than monolithic structures. The modern applications are developed using agile development methodologies and follow Development Operations, DevOps, with a heavy emphasis on automation throughout a continuous integration and delivery, CI/CD pipeline.
An application discovery is a process of identifying and compiling all applications deployed and utilized within an enterprise. The application discovery enables gathering, monitoring, and managing of portfolios of all applications of the enterprise within an Information Technology, IT environment, or on individual computers and networks, such as business and/or productivity applications, database applications, and client and/or server applications.
Computers are utilized in content analysis by automating a process of labeling or coding documents. Basic computational techniques may provide descriptive data such as word frequencies and document lengths. Machine learning classifiers label a wide range of texts. Further, a Computer-Aided Text Analysis, CATA program analyzes the texts based on predefined linguistic, semantic, and psychological attributes.
Most of the existing backup systems rely on pre-defined instructions such as fixed backup policies for well-known applications, which include a pre-defined backup policy for each volume used by the application. However, these existing backup systems lack efficiency in automation for modern applications and/or for cases where the modern applications evolve dynamically, including contents stored on each volume during runtime. The existing backup system is not compatible with the modern applications as the existing backup system involves a mix of workloads and dynamic changes. Consequently, users often need to perform a lot of manual tasks to ensure that all the data assets and/or volumes utilized by the modern application are sufficiently backed up with appropriate backup policies. However, managing the fixed backup policies manually for the modern applications with multiple services is difficult. Moreover, the existing backup system fails to select the appropriate backup policies might lead to data loss.
Therefore, there arises a need to address the aforementioned technical problem/drawbacks of selecting an appropriate backup policy for an application.
SUMMARY
It is an object of the disclosure to provide a memory controller configured to provide backup for an application and a method for a memory controller configured to backup for an application while avoiding one or more disadvantages of prior art approaches.
This object is achieved by the features of the independent claims. Further, implementation forms are apparent from the dependent claims, the description, and the figures.
According to a first aspect, there is a memory controller configured to provide backup for an application. The memory controller is further configured to detect one or more than one data storage asset utilized by the application. The memory controller is further configured to determine a type of content stored by the application in the data storage asset, determine a priority level for the data storage asset based on the type of content, and select a backup policy for the data storage asset based on the type of content, for each of the one or more than one data storage asset. The backup policy is selected to be one of a continuous data protection, CDP, technology, or a snapshot backup technology.
The memory controller automatically generates backup Service Level Agreements, SLAs for the application using content-based backup policies. The memory controller protects the application by ensuring that all required assets and/or data are appropriately backed up with a proper backup policy. The memory controller adjusts the backup policy for the application in real time if the content in the data storage asset associated with the application is changed.
Optionally, the memory controller is further configured to determine the type of content based on meta-data for the data storage asset.
Optionally, the metadata relates to file attributes.
Optionally, the metadata relates to a file permission.
Optionally, the memory controller is further configured to select the backup policy to be continuous data protection, CDP, technology for type of content being indicated to be of high importance, and snapshot backup technology for other type(s) of content.
Optionally, the memory controller is further configured to indicate the type of content to be of high importance if the content relates to sensitive data, financial data, and/or encrypted data.
Optionally, the memory controller is further configured to indicate the type of content to be of high importance if the content relates to data having an update rate exceeding a threshold level.
Optionally, the memory controller is further configured to determine a snapshot frequency for the snapshot backup technology based on the type of content. A type of content having a first priority level is given a higher snapshot frequency than a type of content having a second. The first priority level is higher than the second priority level.
Optionally, the memory controller is further configured to indicate a low priority level to data content being source code file(s).
Optionally, the memory controller is further configured to indicate a low priority level to data content being at least one of configuration file(s) and static file(s).
Optionally, the static file is an image file (s).
Optionally, the memory controller is further configured to determine the type of content based on deep data inspection.
Optionally, the memory controller is further configured to determine the type of content based on resource consumption.
Optionally, the memory controller is further configured to detect one or more than one data storage asset utilized by the application by determining one or more than one services utilized by the application and determining one or more than one data storage asset utilized by the application to be one or more than one data storage asset utilized by the one or more than one services.
Optionally, the memory controller is further configured to determine the one or more than one services utilized by the application to include target services of the one or more than one services.
Optionally, the memory controller is further configured to determine a starting point for the application and detect one or more than one data storage asset utilized by the application based on a scan starting for the starting point.
Optionally, the memory controller is further configured to determine the starting point for the application to be one, some, or all of an application configuration file, application source code, an application deployment recipe, and/or an application access point.
Optionally, the memory controller is further configured to determine the starting point when at least one of an asset and a service instance is added to the application.
Optionally, the memory controller is further configured to provide the backup of a memory to a persistent storage.
Optionally, the memory controller is further configured to, before selecting a backup policy, determine if there is a service level agreement in place for an application, and if not generate a service level agreement for the application.
Optionally, the memory controller is further configured to determine if the service level agreement in place for the application is to be modified and if so, modifying the service level agreement for the application.
Optionally, the memory controller is further configured to provide the backup at intervals.
Optionally, the memory controller is further configured to receive a backup trigger and in response thereto provide the backup.
According to a second aspect, there is provided a method for a memory controller configured to provide backup for an application. The method includes detecting one or more than one data storage asset utilized by the application. The method includes determining a type of content stored by the application in the data storage asset, determining a priority level for the data storage asset based on the type of content, and selecting a backup policy for the data storage asset based on the type of content, for each of the one or more than one data storage asset. The
backup policy is selected to be one of a continuous data protection, CDP, technology, or a snapshot backup technology.
This method automatically generates backup Service Level Agreements, SLAs for the application using content-based backup policies. This method protects the application by ensuring that all required assets and/or data are appropriately backed up with a proper backup policy. This method adjusts the backup policy for the application in real time if content in the data storage asset associated with the application is changed.
According to a third aspect, a computer program product includes program instructions for performing the method when executed by one or more processors in a memory controller system.
Therefore, in contradistinction to the existing solutions, a memory controller is configured to provide backup for an application. The memory controller selects a backup policy efficiently for the application based on a type of content in the data storage asset of the application in real time.
These and other aspects of the disclosure will be apparent from the implementation(s) described below.
BRIEF DESCRIPTION OF DRAWINGS
Implementations of the disclosure will now be described, by way of example only, with reference to the accompanying drawings, in which:
FIG. 1 is a block diagram that illustrates a memory controller configured to provide a backup for an application in accordance with an implementation of the disclosure;
FIG. 2 illustrates a block diagram of a service level agreement, SLA, generator to generate a backup service level agreement, SLA based on a deep content analysis for an application in accordance with an implementation of the disclosure;
FIG. 3 is a flow diagram that illustrates a method for method for a memory controller configured to provide a backup for an application in accordance with an implementation of the disclosure; and
FIG. 4 is an illustration of a computer system (e.g., a memory controller) in which the various architectures and functionalities of the various previous implementations may be implemented.
DETAILED DESCRIPTION OF THE DRAWINGS
Implementations of the disclosure provide a memory controller and a method for the memory controller configured to provide a backup for an application.
To make solutions of the disclosure more comprehensible for a person skilled in the art, the following implementations of the disclosure are described with reference to the accompanying drawings.
Terms such as "a first", "a second", "a third", and "a fourth" (if any) in the summary, claims, and foregoing accompanying drawings of the disclosure are used to distinguish between similar objects and are not necessarily used to describe a specific sequence or order. It should be understood that the terms so used are interchangeable under appropriate circumstances, so that the implementations of the disclosure described herein are, for example, capable of being implemented in sequences other than the sequences illustrated or described herein. Furthermore, the terms "include" and "have" and any variations thereof, are intended to cover a non-exclusive inclusion. For example, a process, a method, a system, a product, or a device that includes a series of steps or units, is not necessarily limited to expressly listed steps or units but may include other steps or units that are not expressly listed or that are inherent to such process, method, product, or device.
Definitions:
Service Level Agreement, SLA is a commitment between a service provider and a customer. Particular aspects of a service quality, availability, and responsibilities are agreed between the service provider and the service user.
FIG. 1 is a block diagram that illustrates a memory controller 102 configured to provide a backup for an application 106 in accordance with an implementation of the disclosure. The application 106 includes a data storage asset 104. The memory controller 102 is associated with the application 106. The memory controller 102 is further configured to detect one or more than one data storage asset 104 utilized by the application 106. The memory controller 102 is further
configured to determine a type of content stored by the application 106 in the data storage asset 104, determine a priority level for the data storage asset 104 based on the type of content, and select a backup policy for the data storage asset 104 based on the type of content, for each of the one or more than one data storage asset. The backup policy is selected to be one of a continuous data protection, CDP, technology, or a snapshot backup technology.
The memory controller 102 automatically generates backup Service Level Agreements, SLAs for the application 106 using content-based backup policies. The memory controller 102 protects the application 106 by ensuring that all required assets and/or data are appropriately backed up with a proper backup policy. The memory controller 102 adjusts the backup policy for the application 106 in real-time if the content in the data storage asset 104 associated with the application 106 is changed.
Optionally, the memory controller 102 is further configured to determine the type of content based on meta-data for the data storage asset 104.
Optionally, the metadata relates to file attributes.
Optionally, the metadata relates to a file permission.
Optionally, the memory controller 102 is further configured to select the backup policy to be continuous data protection, CDP, technology for type of content being indicated to be of high importance, and snapshot backup technology for other type(s) of content.
Optionally, the memory controller 102 is further configured to indicate the type of content to be of high importance if the content relates to sensitive data, financial data, and/or encrypted data. The sensitive data may include information about a particular group of personal data on an individual such as religion, political opinions, sexual orientation, and biometric and genetic data. The financial data may include account numbers, company results, and bank transfer details.
Optionally, the memory controller 102 is further configured to indicate the type of content to be of high importance if the content relates to data having an update rate exceeding a threshold level.
Optionally, the memory controller 102 is further configured to determine a snapshot frequency for the snapshot backup technology based on the type of content. A type of content having a first priority level is given a higher snapshot frequency than a type of content having a second, wherein the first priority level is higher than the second priority level.
Optionally, the memory controller 102 is further configured to indicate a low priority level to data content being source code file(s).
Optionally, the memory controller 102 is further configured to indicate a low priority level to data content being at least one of configuration file(s) and static file(s).
Optionally, the static file is an image file (s).
Optionally, the memory controller 102 is further configured to determine the type of content based on deep data inspection.
Optionally, the memory controller 102 is further configured to determine the type of content based on resource consumption.
Optionally, the memory controller 102 is further configured to detect one or more than one data storage asset 104 utilized by the application 106 by determining one or more than one services utilized by the application 106 and determining one or more than one data storage asset 104 utilized by the application 106 to be one or more than one data storage asset 104 utilized by the one or more than one services.
Optionally, the memory controller 102 is further configured to determine the one or more than one services utilized by the application 106 to include target services of the one or more than one services.
Optionally, the memory controller 102 is further configured to determine a starting point for the application 106 and detect one or more than one data storage asset 104 utilized by the application 106 based on a scan starting for the starting point.
Optionally, the memory controller 102 is further configured to determine the starting point for the application 106 to be one, some, or all of an application configuration file, application source code, an application deployment recipe, and/or an application access point.
Optionally, the memory controller 102 is further configured to determine the starting point when at least one of an asset and a service instance is added to the application.
Optionally, the memory controller 102 determines the starting point or the starting point provided by a user of the application 106. For example, the application 106 access the starting point with the application access point. The application access point may be a Uniform Resource Locator, URL, Internet Protocol, IP and port, process identification, ID, and the like. The memory controller 102 sets an empty list to represent protected assets associated with the starting point.
Optionally, the memory controller 102 is configured to scan the application 106 and identify the one or more services utilized by the application 106 when the empty list has been set. Optionally, the memory controller 102 is configured to scan the data storage asset 104 for each service for detecting new data storage assets utilized by the application 106. The data storage assets 104 may include block volumes, file systems, databases, and the like. Optionally, the memory controller 102 is configured to add the new data storage assets, to the list of protected assets. Optionally, the memory controller 102 is configured to identify characteristics of the new data storage assets by executing a deep content inspection algorithm or a deep data inspection algorithm on the data storage asset 104. For example, the characteristics of the new data storage assets may be block-level assets, file system assets, and database assets.
Optionally, the memory controller 102 retrieves metadata information relevant to the new data storage asset and detects the content in the new data storage asset based on the metadata information. Optionally, the memory controller 102 retrieves the metadata information by (i) scanning a size of the block-level assets, (ii) scanning at least one type, size, tree structure, file attributes, or permissions of the file system assets, and (iii) scanning at least one type, table, schema, size, and indices of the database assets, while executing the deep content inspection algorithm on the data storage asset 104. The memory controller 102 may read data from the data storage asset 104 until the content is detected or a predefined threshold is exceeded. Optionally, the predefined threshold includes an interval timeout or resource consumption
limits. The memory controller 102 may read data from the new data storage asset by searching at least one (i) sensitive data, (ii) encrypted data, (iii) source codes and/or other static data, i.e. configuration files, and (iv) data that is changed frequently in the new data storage asset.
Optionally, the memory controller 102 is further configured to provide the backup of a memory to a persistent storage.
Optionally, the memory controller 102 is further configured to, before selecting a backup policy, determine if there is a service level agreement in place for an application 106, and if not generate a service level agreement for the application 106.
Optionally, the memory controller 102 is further configured to determine if the service level agreement in place for the application 106 is to be modified and if so, modifying the service level agreement for the application 106.
Optionally, the memory controller 102 is further configured to provide the backup at intervals.
Optionally, the memory controller 102 is further configured to receive a backup trigger and in response thereto provide the backup.
FIG. 2 illustrates a block diagram of a service level agreement, SLA, generator 202 to generate a backup service level agreement, SLA 230 based on a deep content analysis for an application 204 in accordance with an implementation of the disclosure. The SLA generator 202 is associated with the application 204. The application 204 includes a first service 208, a second service 212, and a third service 216 that are deployed on a first host machine 206, a second host machine 210, and a third host machine 214. The first host machine 206 includes a block volume 218 and a Structured Query Language, SQL database, DB 220 that are utilized by the first service 208. The second host machine 210 includes a file system with sensitive data 222 that is utilized by the second service 212. The third host machine 214 includes a file system with static data 224 that is utilized by the third service 216. Optionally, a cloud 228 that includes no SQL DB 226 that is utilized by the third service 216.
Optionally, the SLA generator 202 is configured to scan and analyze content in the application 204. The block volume 218 on the first host machine 206 may contain plain data that undergoes
frequent modification due to operation of the first service 208 in real-time. For example, the operations may be user data updates or transaction records, which enables the SLA generator 202 to generate a snapshot-based backup policy with a high interval for the block volume 218.
The SQL database 220 on the first host machine 206 contains encrypted data i.e. important data which enables the SLA generator 202 to generate a Continuous Data Protection, CDP -based backup policy for the SQL database 220. The file system on the second host machine 210 contains sensitive data i.e. important data, which enables the SLA generator 202 to generate the CDP -based backup policy for the file system with sensitive data 222. The file system on the third host machine 214 contains the static data, which enables the SLA generator 202 to generate the snapshot-based backup policy with a low interval for the file system with static data 224. The No SQL database 226 on the third host machine 214 contains indexed data i.e. important data, which enables the SLA generator 202 to generate the CDP -based backup policy for the No SQL database 226.
The SLA generator 202 generates the backup SLA 230 for a volume based on a priority level of a content stored inside the volume. The volume may be the block volume 218, the SQL DB 220, the file system with sensitive data 222, and the file system with static data 224. Optionally, the SLA generator 202 generates the backup SLA 230 based on the volume. The volume with a high level priority may be set as the Continues data protection, CDP backup policy, the volume with a low level priority may be set as the snapshot backup policy at low frequency, and the volume with a medium level may be set as the snapshot backup policy at high frequency. The high level priority of volume may be encrypted data, data related to the application 204 with login details, or a database with high traffic. The low level priority of the volume may be browser element data, configuration file, or source code. The backup SLA 230 is stored in a backup storage 232 for the application 204 once the backup SLA 230 is generated by the SLA generator 202.
Once the backup SLA 230 is generated for the application 204 by the SLA generator 202, a memory controller of the application 204 creates the backup SLA 230 for the application 204 or updates the backup SLA 230 if the backup SLA 230 already exists for the application 204, ensuring the backup policy for the application 204 is appropriately provided for each volume. The memory controller enables the SLA generator 202 again to generate the backup SLA 230
for the application 204 to detect changes in the application 204 and/or if any content exists in the volume.
FIG. 3 is a flow diagram that illustrates a method for a memory controller configured to provide a backup for an application in accordance with an implementation of the disclosure. At a step 302, the method includes detecting one or more than one data storage asset utilized by an application. At a step 304, the method includes determining a type of content stored by the application in the data storage asset, determining a priority level for the data storage asset based on the type of content, and selecting a backup policy for the data storage asset based on the type of content, for each of the one or more than one data storage asset. The backup policy is selected to be one of a continuous data protection, CDP, technology, or a snapshot backup technology.
This method automatically generates a backup Service Level Agreements, SLAs for the application using content-based backup policies. This method protects the application by ensuring that all required assets and/or data are appropriately backed up with a proper backup policy. This method adjusts the backup policy for the application in real-time if the content in the data storage asset associated with the application is changed.
In an implementation, a computer program product comprising program instructions for performing the method, when executed by one or more processors in a memory system.
FIG. 4 is an illustration of a computer system (e.g., a memory controller) in which the various architectures and functionalities of the various previous implementations may be implemented. As shown, the computer system 400 includes at least one processor 404 that is connected to a bus 402, wherein the computer system 400 may be implemented using any suitable protocol, such as Peripheral Component Interconnect, PCI-Express, Accelerated Graphics Port, AGP, Hyper Transport, or any other bus or point-to-point communication protocol. The computer system 400 also includes a memory 406.
Control logic (software) and data are stored in the memory 406 which may take a form of random-access memory, RAM. In the disclosure, a single semiconductor platform may refer to a sole unitary semiconductor-based integrated circuit or chip. It should be noted that the term single semiconductor platform may also refer to multi-chip modules with increased connectivity which simulate on-chip modules with increased connectivity which simulate on-
chip operation, and make substantial improvements over utilizing a conventional central processing unit, CPU and bus implementation. Of course, the various modules may also be situated separately or in various combinations of semiconductor platforms per the desires of the user.
The computer system 400 may also include a secondary storage 410. The secondary storage 410 includes, for example, a hard disk drive and a removable storage drive, representing a floppy disk drive, a magnetic tape drive, a compact disk drive, digital versatile disk, DVD drive, recording device, universal serial bus, USB flash memory. The removable storage drive at least one of reads from and writes to a removable storage unit in a well-known manner.
Computer programs, or computer control logic algorithms, may be stored in at least one of the memory 406 and the secondary storage 410. Such computer programs, when executed, enable the computer system 400 to perform various functions as described in the foregoing. The memory 406, the secondary storage 410, and any other storage are possible examples of computer-readable media.
In an implementation, the architectures and functionalities depicted in the various previous figures may be implemented in the context of the processor 404, a graphics processor coupled to a communication interface 412, an integrated circuit (not shown) that is capable of at least a portion of the capabilities of both the processor 404 and a graphics processor, a chipset (namely, a group of integrated circuits designed to work and sold as a unit for performing related functions, and so forth).
Furthermore, the architectures and functionalities depicted in the various previous-described figures may be implemented in a context of a general computer system, a circuit board system, a game console system dedicated for entertainment purposes, an application-specific system. For example, the computer system 400 may take the form of a desktop computer, a laptop computer, a server, a workstation, a game console, an embedded system.
Furthermore, the computer system 400 may take the form of various other devices including, but not limited to a personal digital assistant, PDA device, a mobile phone device, a smart phone, a television, and so forth. Additionally, although not shown, the computer system 400 may be coupled to a network (for example, a telecommunications network, a local area network,
LAN, a wireless network, a wide area network, WAN such as the Internet, a peer-to-peer network, a cable network, or the like) for communication purposes through an I/O interface 408.
It should be understood that the arrangement of components illustrated in the figures described are exemplary and that other arrangement may be possible. It should also be understood that the various system components (and means) defined by the claims, described below, and illustrated in the various block diagrams represent components in some systems configured according to the subject matter disclosed herein. For example, one or more of these system components (and means) may be realized, in whole or in part, by at least some of the components illustrated in the arrangements illustrated in the described figures.
In addition, while at least one of these components are implemented at least partially as an electronic hardware component, and therefore constitutes a machine, the other components may be implemented in software that when included in an execution environment constitutes a machine, hardware, or a combination of software and hardware.
Although the disclosure and its advantages have been described in detail, it should be understood that various changes, substitutions, and alterations can be made herein without departing from the spirit and scope of the disclosure as defined by the appended claims.
Claims
1. A memory controller (102) configured to provide a backup for an application (106, 204), wherein the memory controller (102) is further configured to provide the backup by detecting one or more than one data storage asset (104) utilized by the application (106, 204) and for each of the one or more than one data storage asset (104) determining a type of content stored by the application (106, 204) in the data storage asset (104) determining a priority level for the data storage asset (104) based on the type of content, and selecting a backup policy for the data storage asset (104) based on the type of content, wherein the backup policy is selected to be one of a continuous data protection, CDP, technology, or a snapshot backup technology.
2. The memory controller (102) according to claim 1, wherein the memory controller (102) is further configured to determine the type of content based on meta-data for the data storage asset (104).
3. The memory controller (102) according to any preceding claim 2, wherein the meta data relates to file attributes.
4. The memory controller (102) according to any preceding claim 2 or 3, wherein the meta data relates to a file permission.
5. The memory controller (102) according to any preceding claim, wherein the memory controller (102) is further configured to select the backup policy to be continuous data protection, CDP, technology for type of content being indicated to be of high importance, and snapshot backup technology for other type(s) of content.
6. The memory controller (102) according to claim 5, wherein the memory controller (102) is further configured to indicate the type of content to be of high importance if content relates to sensitive data, financial data, and/or encrypted data.
7. The memory controller (102) according to any of claims 5 or 6, wherein the memory controller (102) is further configured to indicate the type of content to be of high importance if content relates to data having an update rate exceeding a threshold level.
8. The memory controller (102) according to any preceding claim, wherein the memory controller (102) is further configured to determine a snapshot frequency for the snapshot backup technology based on the type of content, wherein a type of content having a first priority level is given a higher snapshot frequency than a type of content having a second, wherein the first priority level is higher than the second priority level.
9. The memory controller (102) according to claim 8, wherein the memory controller (102) is further configured to indicate a low priority level to data content being source code file(s).
10. The memory controller (102) according to claim 8 or 9, wherein the memory controller (102) is further configured to indicate a low priority level to data content being at least one of configuration file(s) and static file(s).
11. The memory controller (102) according to claim 10, wherein the static file (s) is an image file.
12. The memory controller (102) according to any preceding claim, wherein the memory controller (102) is further configured to determine the type of content based on deep data inspection.
13. The memory controller (102) according to claim 12, wherein the memory controller (102) is further configured to determine the type of content based on resource consumption.
14. The memory controller (102) according to any preceding claim, wherein the memory controller (102) is further configured to detect one or more than one data storage asset (104) utilized by the application (106, 204) by determining one or more than one services (208, 212, 216) utilized by the application (106, 204) and determining one or more than one data storage asset utilized by the application (106, 204) to be one or more than one data storage asset (104) utilized by the one or more than one services (208, 212, 216).
15. The memory controller (102) according to claim 14, wherein the memory controller (102) is further configured to determine the one or more than one services (208, 212, 216) utilized by the application (106, 204) to include target services of the one or more than one services (208, 212, 216).
16. The memory controller (102) according to any preceding claim, wherein the memory controller (102) is further configured to determine a starting point for the application (106, 204); and detect one or more than one data storage asset (104) utilized by the application (106, 204) based on a scan starting for the starting point.
17. The memory controller (104) according to claim 16, wherein the memory controller (104) is further configured to determine the starting point for the application (106, 204) to be one, some or all of an application configuration file, application source code, an application deployment recipe, and/or an application access point.
18. The memory controller (102) according to claims 16 or 17, wherein the memory controller (102) is further configured to determine the starting point when at least one of an asset and a service instance is added to the application (106,204).
19. The memory controller (102) according to any preceding claim, wherein the memory controller (102) is further configured to provide the backup of a memory (406) to a persistent storage.
20. The memory controller (102) according to any preceding claim, wherein the memory controller (102) is further configured to, before selecting a backup policy, determine if there is a service level agreement (230) in place for an application (106, 204), and if not generate the service level agreement (230) for the application (106, 204).
21. The memory controller according to claim 20, wherein the memory controller (102) is further configured to determine if a service level agreement (230) in place for the application (106, 204) is to be modified and if so, modifying the service level agreement (230) for the application (106, 204).
22. The memory controller (102) according to any preceding claim, wherein the memory controller (102) is further configured to provide the backup at intervals.
23. The memory controller (102) according to any preceding claim, wherein the memory controller (102) is further configured to receive a backup trigger and in response thereto provide the backup.
24. A method for a memory controller (102) configured to provide backup for an application (106, 204), wherein the method comprises detecting one or more than one data storage asset (104) utilized by the application (106, 204) and for each of the one or more than one data storage asset (104) determining a type of content stored by the application (106, 204) in the data storage asset (104), determining a priority level for the data storage asset (104) based on the type of content, and selecting a backup policy for the data storage asset (104) based on the type of content, wherein the backup policy is selected to be one of a continuous data protection, CDP, technology, or a snapshot backup technology.
25. A computer program product comprising program instructions for performing the method according to claim 24, when executed by one or more processors in a memory system.
Priority Applications (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
PCT/EP2023/079718 WO2025087516A1 (en) | 2023-10-25 | 2023-10-25 | Method for generation of backup service level agreement based on deep content analysis |
Applications Claiming Priority (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
PCT/EP2023/079718 WO2025087516A1 (en) | 2023-10-25 | 2023-10-25 | Method for generation of backup service level agreement based on deep content analysis |
Publications (1)
Publication Number | Publication Date |
---|---|
WO2025087516A1 true WO2025087516A1 (en) | 2025-05-01 |
Family
ID=88585232
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/EP2023/079718 Pending WO2025087516A1 (en) | 2023-10-25 | 2023-10-25 | Method for generation of backup service level agreement based on deep content analysis |
Country Status (1)
Country | Link |
---|---|
WO (1) | WO2025087516A1 (en) |
Citations (14)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
WO2007067699A2 (en) * | 2005-12-08 | 2007-06-14 | Nvidia Corporation | Emergency data preservation services |
US20120123999A1 (en) * | 2010-11-16 | 2012-05-17 | Actifio, Inc. | System and method for managing data with service level agreements that may specify non-uniform copying of data |
US9355104B1 (en) * | 2013-03-15 | 2016-05-31 | Emc Corporation | Intelligent pairing using a lookup database for snapshot based backups |
US20160232061A1 (en) * | 2015-02-11 | 2016-08-11 | International Business Machines Corporation | Method for automatically configuring backup client systems and backup server systems in a backup environment |
EP3185125A1 (en) * | 2014-08-22 | 2017-06-28 | ZTE Corporation | Data backup method, system, node and computer storage media |
US20200133795A1 (en) * | 2018-10-26 | 2020-04-30 | EMC IP Holding Company LLC | Smart dynamic restore for kubernetes based applications |
US20200320215A1 (en) * | 2019-04-05 | 2020-10-08 | International Business Machines Corporation | Protecting data based on a sensitivity level for the data |
US20200348846A1 (en) * | 2019-05-02 | 2020-11-05 | EMC IP Holding Company LLC | Method and system for intelligent environment aware software defined enterprise multi-application protection |
US20210011811A1 (en) * | 2019-07-12 | 2021-01-14 | Trilio Data, Inc. | Scalable Cloud-Based Backup Method |
US20210120039A1 (en) * | 2019-10-18 | 2021-04-22 | EMC IP Holding Company LLC | Storage and data protection as a service in a cloud native environment |
US20220035713A1 (en) * | 2017-11-22 | 2022-02-03 | Acronis International Gmbh | System and method for automating formation and execution of a backup strategy |
US20220107869A1 (en) * | 2017-03-15 | 2022-04-07 | Acronis International Gmbh | System and method for selecting a backup plan for newly stored files |
US20220317881A1 (en) * | 2021-03-30 | 2022-10-06 | EMC IP Holding Company LLC | Method and apparatus for affinity based smart data protection policy for pooled protection targets |
US20230052851A1 (en) * | 2021-08-12 | 2023-02-16 | EMC IP Holding Company LLC | Automatically assigning data protection policies using anonymized analytics |
-
2023
- 2023-10-25 WO PCT/EP2023/079718 patent/WO2025087516A1/en active Pending
Patent Citations (14)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
WO2007067699A2 (en) * | 2005-12-08 | 2007-06-14 | Nvidia Corporation | Emergency data preservation services |
US20120123999A1 (en) * | 2010-11-16 | 2012-05-17 | Actifio, Inc. | System and method for managing data with service level agreements that may specify non-uniform copying of data |
US9355104B1 (en) * | 2013-03-15 | 2016-05-31 | Emc Corporation | Intelligent pairing using a lookup database for snapshot based backups |
EP3185125A1 (en) * | 2014-08-22 | 2017-06-28 | ZTE Corporation | Data backup method, system, node and computer storage media |
US20160232061A1 (en) * | 2015-02-11 | 2016-08-11 | International Business Machines Corporation | Method for automatically configuring backup client systems and backup server systems in a backup environment |
US20220107869A1 (en) * | 2017-03-15 | 2022-04-07 | Acronis International Gmbh | System and method for selecting a backup plan for newly stored files |
US20220035713A1 (en) * | 2017-11-22 | 2022-02-03 | Acronis International Gmbh | System and method for automating formation and execution of a backup strategy |
US20200133795A1 (en) * | 2018-10-26 | 2020-04-30 | EMC IP Holding Company LLC | Smart dynamic restore for kubernetes based applications |
US20200320215A1 (en) * | 2019-04-05 | 2020-10-08 | International Business Machines Corporation | Protecting data based on a sensitivity level for the data |
US20200348846A1 (en) * | 2019-05-02 | 2020-11-05 | EMC IP Holding Company LLC | Method and system for intelligent environment aware software defined enterprise multi-application protection |
US20210011811A1 (en) * | 2019-07-12 | 2021-01-14 | Trilio Data, Inc. | Scalable Cloud-Based Backup Method |
US20210120039A1 (en) * | 2019-10-18 | 2021-04-22 | EMC IP Holding Company LLC | Storage and data protection as a service in a cloud native environment |
US20220317881A1 (en) * | 2021-03-30 | 2022-10-06 | EMC IP Holding Company LLC | Method and apparatus for affinity based smart data protection policy for pooled protection targets |
US20230052851A1 (en) * | 2021-08-12 | 2023-02-16 | EMC IP Holding Company LLC | Automatically assigning data protection policies using anonymized analytics |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US11048490B2 (en) | Service placement techniques for a cloud datacenter | |
JP6258494B2 (en) | Move instance of virtual computer processing | |
US9460117B2 (en) | Image searching | |
US11403356B2 (en) | Personalizing a search of a search service | |
CN102938039B (en) | For the selectivity file access of application | |
US11042646B2 (en) | Selecting data storage based on data and storage classifications | |
US9400700B2 (en) | Optimized system for analytics (graphs and sparse matrices) operations | |
US11237749B2 (en) | System and method for backup data discrimination | |
US11048738B2 (en) | Records search and management in compliance platforms | |
US20240004993A1 (en) | Malware detection in containerized environments | |
US20230112332A1 (en) | Multiple data labels within a backup system | |
US11983184B2 (en) | Multi-tenant, metadata-driven recommendation system | |
EP3497586A1 (en) | Discovery of calling application for control of file hydration behavior | |
US11841965B2 (en) | Automatically assigning data protection policies using anonymized analytics | |
CN112115105A (en) | Service processing method, device and equipment | |
US9734229B1 (en) | Systems and methods for mining data in a data warehouse | |
CN112182562A (en) | Data auditing method and system in sandbox environment, electronic equipment and medium | |
US20230385889A1 (en) | Predictive service orchestration using threat modeling analytics | |
US9785724B2 (en) | Secondary queue for index process | |
US20190340542A1 (en) | Computational Efficiency in Symbolic Sequence Analytics Using Random Sequence Embeddings | |
US9842297B1 (en) | Establishing industry ground truth | |
US20220058195A1 (en) | Index selection for database query | |
US11210352B2 (en) | Automatic check of search configuration changes | |
US12380074B2 (en) | Optimizing metadata enrichment of data assets | |
US10922366B2 (en) | Self-adaptive web crawling and text extraction |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
121 | Ep: the epo has been informed by wipo that ep was designated in this application |
Ref document number: 23797772 Country of ref document: EP Kind code of ref document: A1 |