Data storage resource allocation by performing abbreviated resource checks based on relative chances of failure of the data storage resources to determine whether data storage requests would fail
US-9128883-B2 · Sep 8, 2015 · US
US11829331B2 · US · B2
| Field | Value |
|---|---|
| Publication number | US-11829331-B2 |
| Application number | US-202217695652-A |
| Country | US |
| Kind code | B2 |
| Filing date | Mar 15, 2022 |
| Priority date | Jun 27, 2019 |
| Publication date | Nov 28, 2023 |
| Grant date | Nov 28, 2023 |
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.
A system for performing continuous transaction log backups with minimal resource usage of the client computing devices that are processing the transactions is disclosed. The system detects at least one input/output (I/O) activity at a client computing device. The I/O activity can be associated with at least one database operation performed via the client computing device. The system then executes one or more native commands to backup transactions log data associated with the detected I/O activity to a virtualized location. Backing-up the transactions log data comprises dynamically identifying a mount path location corresponding to the virtualized location, and transferring the transactions log data to the dynamically identified mount path using the one or more native commands. The system can then perform data processing operations (for example, data chunking and deduplicating) on the transactions log data after it is received at the dynamically identified mount path location.
Opening claim text (preview).
What is claimed is: 1. A computer-implemented system comprising one or more processors configured to: determine that a transactions log backup trigger condition has been satisfied indicating that transactions log data is to be backed up; select a mount path from a plurality of available mount paths, the mount path corresponding to a virtualized location to which to back up the transactions log data; and transfer the transactions log data to the mount path using one or more native commands, wherein the mount path is associated with a computing device, wherein the computing device is configured to perform one or both of deduplication and formatting of the transactions log data prior to storage of a backup of the transactions log data. 2. The computer-implemented system of claim 1 , wherein the mount path is associated with a media agent installed on the computing device, and wherein the media agent performs the one or both of deduplication and formatting of the transactions log data. 3. The computer-implemented system of claim 1 , wherein the mount path is selected in a round-robin manner. 4. The computer-implemented system of claim 1 , wherein the transactions log backup trigger condition is detected based on a database command being invoked at the one or more processors. 5. The computer-implemented system of claim 1 , wherein the transactions log data is generated by a database application installed on the one or more processors. 6. The computer-implemented system of claim 1 , wherein the transactions log backup trigger condition is detected based on storage utilization. 7. The computer-implemented system of claim 1 , wherein the mount path is selected based on: availability of the mount path, network bandwidth availability, storage capacity, last mount path selected, or any combination thereof. 8. The computer-implemented system of claim 1 , wherein the computing device formats the transactions log data into a backup or archive format. 9. A method comprising: with one or more computing devices: determining that a transactions log backup trigger condition has been satisfied indicating that transactions log data is to be backed up; selecting a mount path from a plurality of available mount paths, the mount path corresponding to a virtualized location to which to back up the transactions log data; and transferring the transactions log data to the mount path using one or more native commands, wherein the mount path is associated with a computing device, wherein the computing device is configured to perform one or both of deduplication and formatting of the transactions log data prior to storage of a backup of the transactions log data. 10. The method of claim 9 , wherein the mount path is associated with a media agent installed on the computing device, and wherein the media agent performs the one or both of deduplication and formatting of the transactions log data. 11. The method of claim 9 , wherein the mount path is selected in a round-robin manner. 12. The method of claim 9 , wherein the transactions log backup trigger condition is detected based on a database command. 13. The method of claim 9 , wherein the transactions log data is generated by a database application. 14. The method of claim 9 , wherein the transactions log backup trigger condition is detected based on storage utilization. 15. The method of claim 9 , wherein the mount path is selected based on: availability of the mount path, network bandwidth availability, storage capacity, last mount path selected, or any combination thereof. 16. A computer program product embodied in a non-transitory computer readable medium and comprising computer instructions for: with a log backup agent installed on a first computing device: determining that a transactions log backup trigger condition has been satisfied indicating that transactions log data is to be backed up; identifying a mount path of a plurality of available mount paths, the mount path corresponding to a virtualized location to which to back up the transactions log data, wherein the virtualized location appears to the first computing device as a physical storage location; and transferring the transactions log data to the mount path using one or more native commands; wherein the mount path is associated with a second computing device, and wherein the second computing device is configured to perform one or both of deduplication and formatting of the transactions log data prior to storage of a backup of the transactions log data. 17. The computer program product of claim 16 , wherein the mount path is associated with a media agent installed on the second computing device, and wherein the media agent performs the one or both of deduplication and formatting of the transactions log data. 18. The computer program product of claim 16 , wherein the mount path is selected based on: availability of the mount path, network bandwidth availability, storage capacity associated with the mount path, last mount path selected, or any combination thereof. 19. The computer program product of claim 16 , wherein the transactions log data is generated by a database application installed on the first computing device. 20. The computer program product of claim 16 , wherein the transactions log backup trigger condition is detected based on storage utilization.
Details of monitoring file system events, e.g. by the use of hooks, filter drivers, logs · CPC title
Replication mechanisms · CPC title
by facilitating the process of upgrading existing storage systems, e.g. for improving compatibility between host and storage device · CPC title
Organizing or formatting or addressing of data · CPC title
Lifecycle management · CPC title
Related publications grouped by family.
Answers are generated from the same data shown on this page.