Tenant-level database recovery
US-2024281344-A1 · Aug 22, 2024 · US
Protection method and device for metadata of file
US2017193005A1 · US · A1
| Field | Value |
|---|---|
| Publication number | US-2017193005-A1 |
| Application number | US-201615376553-A |
| Country | US |
| Kind code | A1 |
| Filing date | Dec 12, 2016 |
| Priority date | Dec 31, 2015 |
| Publication date | Jul 6, 2017 |
| Grant date | — |
How to read this patent
A practical reading order for non-experts. Skip the full description unless you need deep technical detail.
- Title
What the patent document calls the invention.
- Abstract
A short plain-language summary of the technical disclosure.
- Assignees and inventors
Who owns or filed the patent and who is credited as inventor.
- Key dates
Filing, priority, publication, and grant dates set the timeline.
- First independent claim
The legal scope of protection — read this for what is actually claimed.
- CPC / IPC classifications
Technology tags used to group this patent with similar filings.
- Citations and related patents
Prior art links and similar publications in this corpus.
Abstract
Official abstract text for this publication.
Disclosed is a protection method and device for metadata of a file. The protection method may include pre-allocating, to a storage device, a preset quantity of initialized blocks for a journal file and journaling, in the storage device, updated metadata of the journal file by calling a data synchronization function.
First claim
Opening claim text (preview).
What is claimed is: 1 . A protection method comprising: pre-allocating, to a storage device, a preset quantity of initialized blocks for a journal file; and journaling, in the storage device, updated metadata of the journal file by calling a data synchronization function. 2 . The protection method of claim 1 , further comprising: committing a log, which is database restoration information, to the blocks. 3 . The protection method of claim 2 , wherein the committing comprises: writing the log in the blocks pre-allocated to the storage device from a database, through a direct input and output (DIO) method or a buffered input and output (IO) method. 4 . The protection method of claim 1 , wherein the journaling comprises: storing, in the storage device, the metadata of the journal file by synchronizing the metadata through the data synchronization function. 5 . The protection method of claim 1 , wherein the blocks allocated to the storage device are initialized by filling the blocks with zero, or applying a discard command to the storage device. 6 . The protection method of claim 1 , further comprising: re-allocating a preset quantity of blocks when all the allocated blocks are full by committing a log. 7 . The protection method of claim 6 , further comprising: journaling the metadata of the journal file by synchronizing the metadata when a size of the journal file changes in response to the re-allocation of the blocks. 8 . A protection device performing a protection method for metadata of a file, the protection device comprising: a processor, wherein the processor is configured to: pre-allocate, to a storage device, a preset quantity of initialized blocks for a journal file; and journal, in the storage device, updated metadata of the journal file by calling a data synchronization function. 9 . The protection device of claim 8 , wherein the processor is further configured to commit a log, which is database restoration information, to the blocks after journaling the metadata. 10 . The protection device of claim 9 , wherein the processor is configured to write the log in the blocks pre-allocated to the storage device from a database through a direct input and output (DIO) method or a buffered input and output (IO) method. 11 . The protection device of claim 8 , wherein the processor is configured to perform the journaling by storing, in the storage device, the metadata of the journal file by synchronizing the metadata through the data synchronization function. 12 . The protection device of claim 8 , wherein the blocks allocated to the storage device are initialized by filling the blocks with zero, or applying a discard command to the storage device. 13 . The protection device of claim 8 , wherein the processor is further configured to re-allocate a preset quantity of blocks when all the allocated blocks are full by committing a log. 14 . The protection device of claim 13 , wherein the processor is further configured to journal the metadata of the journal file by synchronizing the metadata when a size of the journal file changes in response to the re-allocation of the blocks.
Assignees
Inventors
Classifications
- G06F16/1815Primary
Journaling file systems · CPC title
Details of non-transparently synchronising file systems · CPC title
Replication, distribution or synchronisation of data between databases or within a distributed database system; Distributed database system architectures therefor · CPC title
- G06F17/30191Primary
Physics · mapped topic
Physics · mapped topic
Patent family
Related publications grouped by family.
External sources
Frequently asked questions
Answers are generated from the same data shown on this page.
- What does patent US2017193005A1 cover?
- Disclosed is a protection method and device for metadata of a file. The protection method may include pre-allocating, to a storage device, a preset quantity of initialized blocks for a journal file and journaling, in the storage device, updated metadata of the journal file by calling a data synchronization function.
- Who is the assignee on this patent?
- Industry-Univ Coop Found Hanyang Univ, Unist (Ulsan Nat Inst Of Science And Technology)
- What technology area does this patent fall under?
- Primary CPC classification G06F16/1815. Mapped technology areas include Physics.
- When was this patent published?
- Publication date Thu Jul 06 2017 00:00:00 GMT+0000 (Coordinated Universal Time) (A1). Legal status and post-grant events are not shown on this page.
- What related patents are in patentsdb?
- We list 8 related publications on this page (citations in our corpus or others sharing the same primary CPC).