Point-in-time recovery on deduplicated storage
US-10255137-B1 · Apr 9, 2019 · US
US2020019471A1 · US · A1
| Field | Value |
|---|---|
| Publication number | US-2020019471-A1 |
| Application number | US-201816035246-A |
| Country | US |
| Kind code | A1 |
| Filing date | Jul 13, 2018 |
| Priority date | Jul 13, 2018 |
| Publication date | Jan 16, 2020 |
| Grant date | — |
A practical reading order for non-experts. Skip the full description unless you need deep technical detail.
What the patent document calls the invention.
A short plain-language summary of the technical disclosure.
Who owns or filed the patent and who is credited as inventor.
Filing, priority, publication, and grant dates set the timeline.
The legal scope of protection — read this for what is actually claimed.
Technology tags used to group this patent with similar filings.
Prior art links and similar publications in this corpus.
Official abstract text for this publication.
Systems and methods for performing data protection operation on an application in a manner that is integrated with the environment of the application being protected. A dynamic policy is associated with the data protection application so that a data protection operation can be performed whenever the policy is triggered.
Opening claim text (preview).
What is claimed is: 1 . A method for performing a data protection operation in a cloud based application, the method comprising: determining that an action is to be performed on an application or on a portion of the application; evaluating the action, based on a policy to determine whether to perform the data protection operation; and performing the data protection operation when the action satisfies the policy. 2 . The method of claim 1 , further comprising receiving a notification that the action is to be performed. 3 . The method of claim 1 , wherein the action includes one of an upgrade to a component of the application, a scaling of the application, or an addition to the application. 4 . The method of claim 1 , wherein the action include a push to production. 5 . The method of claim 1 , wherein determining that an action is to be performed on an application includes monitoring the application and determining that a monitoring event has occurred. 6 . The method of claim 5 , wherein the monitoring event includes at least one of crossing a threshold related to traffic, detecting a hardware outage, or detecting a hardware change. 7 . The method of claim 1 , wherein the data protection application includes a backup operation. 8 . The method of claim 1 , further comprising updating the policy dynamically based on the action or other actions related to the application. 9 . The method of claim 1 , further comprising integrating the application with a data protection application. 10 . The method of claim 1 , wherein evaluating the action, based on a policy to determine whether to perform the data protection operation, includes automatically creating a backup whenever there is a deployment or whenever the application is upgraded or whenever a function is added or modified. 11 . The method of claim 1 , wherein evaluating the action, based on a policy to determine whether to perform the data protection operation includes automatically creating a backup whenever the application is scaled. 12 . The method of claim 1 , wherein evaluating the action, based on a policy to determine whether to perform the data protection operation includes creating a backup whenever there is a change in traffic or a service failure of a failed health check on the application. 13 . The method of claim 1 , wherein the backup application is integrated with monitoring tools wherein evaluating the action, based on a policy to determine whether to perform the data protection operation includes creating a backup on prior to each push to production. 14 . The method of claim 1 , further comprising performing a backup to run in an integration or staging environment. 15 . The method of claim 1 , further comprising creating a backup on degradation of a cluster or based on an infrastructure outage. 16 . The method of claim 1 , wherein performing the backup is initiated by a microservice. 17 . The method of claim 16 , wherein code of the application is annotated with a backup indicator, further comprising performing the data protection application when the backup indicator is reached during execution of the code. 18 . The method of claim 1 , further comprising monitoring services included in the application and performing the data protection application without disturbing underlying code of the monitored services.
Updates (security arrangements therefor G06F21/57) · CPC title
for networked environments · CPC title
Backup scheduling policy · CPC title
Protecting data · CPC title
where the computing system component is a software system · CPC title
Related publications grouped by family.
Answers are generated from the same data shown on this page.