CN112241243A - Method for realizing active object storage system - Google Patents
Method for realizing active object storage system Download PDFInfo
- Publication number
- CN112241243A CN112241243A CN202011115392.8A CN202011115392A CN112241243A CN 112241243 A CN112241243 A CN 112241243A CN 202011115392 A CN202011115392 A CN 202011115392A CN 112241243 A CN112241243 A CN 112241243A
- Authority
- CN
- China
- Prior art keywords
- user
- osd
- method object
- policy
- strategy
- 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.)
- Granted
Links
- 238000000034 method Methods 0.000 title claims abstract description 213
- 238000012545 processing Methods 0.000 claims description 46
- 238000004891 communication Methods 0.000 claims description 12
- 238000012217 deletion Methods 0.000 claims description 6
- 230000037430 deletion Effects 0.000 claims description 6
- 230000008569 process Effects 0.000 claims description 6
- 230000001960 triggered effect Effects 0.000 claims description 3
- 238000005516 engineering process Methods 0.000 claims 1
- 230000006870 function Effects 0.000 abstract description 4
- 238000007781 pre-processing Methods 0.000 abstract description 3
- 238000003745 diagnosis Methods 0.000 abstract description 2
- 238000001914 filtration Methods 0.000 abstract description 2
- 238000011084 recovery Methods 0.000 abstract description 2
- 238000012216 screening Methods 0.000 abstract description 2
- 230000003993 interaction Effects 0.000 description 4
- 230000009286 beneficial effect Effects 0.000 description 2
- 230000004048 modification Effects 0.000 description 2
- 238000012986 modification Methods 0.000 description 2
- 230000005540 biological transmission Effects 0.000 description 1
- 238000010586 diagram Methods 0.000 description 1
- 230000002708 enhancing effect Effects 0.000 description 1
- 230000006872 improvement Effects 0.000 description 1
- 230000004044 response Effects 0.000 description 1
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F3/00—Input arrangements for transferring data to be processed into a form capable of being handled by the computer; Output arrangements for transferring data from processing unit to output unit, e.g. interface arrangements
- G06F3/06—Digital input from, or digital output to, record carriers, e.g. RAID, emulated record carriers or networked record carriers
- G06F3/0601—Interfaces specially adapted for storage systems
- G06F3/0668—Interfaces specially adapted for storage systems adopting a particular infrastructure
- G06F3/067—Distributed or networked storage systems, e.g. storage area networks [SAN], network attached storage [NAS]
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Human Computer Interaction (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
Abstract
The invention provides an implementation method of an active object storage system, and relates to the technical field of cloud computing. The invention provides an intelligent active object storage system, which can flexibly realize data preprocessing such as filtering, screening, data checking and various self-defining functions in the node of the object storage system by adding an interface supporting active storage, modifying each layer of modules of the traditional object storage system and adding an active storage module, and endowing the node with certain autonomy such as active fault diagnosis and data recovery, thereby improving the performance of the storage system.
Description
Technical Field
The invention relates to the technical field of network storage, in particular to a method for realizing an active object storage system.
Background
Conventional object storage systems do not support active storage functionality.
Disclosure of Invention
The invention aims to provide a method for realizing an active object storage system.
The invention adopts the following technical scheme that the invention provides a method for realizing an active object storage system, which is designed to comprise a client and an active storage node OSD, wherein the client is used for providing files, blocks and object interfaces for a user, and also comprises an active object service module and a communication service module; the OSD is positioned on a file interface, a block interface and an object interface, the OSD comprises an active storage module, an active object management module, a file interface VFS and a communication service module, the object is stored in a local file system of the OSD through the file interface VFS at the bottom layer of the OSD, and each object in the active object storage system is mapped into a file of the local file system according to the ID of the object;
the active storage module is positioned between an active object management module of the OSD and a file interface VFS at the bottom layer and comprises a method object processing module and a strategy object processing module; the active object service and communication service module of the client contains a package for actively storing related commands; the communication service module of the OSD is used for analyzing the command transmitted by the client, and if the command is irrelevant to the active storage, the command is processed according to the processing mode of the traditional object storage system; if the active storage is related, the method object processing module and the strategy object processing module are handed over to carry out active storage processing;
the method object processing module adopts a method object to realize active storage processing, the method object is a main implementation means of active storage, after the method object is introduced, a user can download required operation into OSD (on screen display), and the operation is used as the method object to be stored and managed by the OSD; the method object is divided into a user method object and a system method object, the user method object is a method object for operating the user object, the system method object is a method object for realizing a certain OSD autonomous management function according to a strategy object, and the triggering execution methods of the user method object and the system method object are different; when the method object is triggered to be executed, the OSD reads the content of the method object through the file interface VFS autonomously to operate.
Preferably, the method object processing module completes registration and deletion of the method object according to the user method object related request, and associates and disassociates the corresponding user object; when a user sends a read command with an active storage mark to a system, the method object processing module can automatically read the content of the method object associated with the given user object according to the given user object, schedule and execute the user object as the input of the method object, and return the executed result to the user; when a user sends a write command with an active storage tag to the system, the method object processing module can automatically read the content of the method object associated with the given user object according to the given user object, the input stream is used as the input of the method object to be scheduled and executed, and the executed result is stored in the corresponding user object.
Preferably, when data is divided into a plurality of user objects and stored on different OSDs, the synchronization of the storage position and the operation result is considered when implementing the method object;
for the user method object, uploading it to the OSD where each user object associated with it is located, for the system method object, uploading it to the OSD where each strategy object associated with it is located, and all the method objects and strategy objects are not divided;
the process of uploading is as follows: if the user method object is required to be uploaded, the user method object is randomly uploaded to an OSD, the information is stored in an external metadata server, when a client sends out a related associated command, the metadata server is searched, the user method object and the OSD where the corresponding user object is located are found, the method object is transferred and copied to the OSD where all the user objects related to the method object are located, and the related information is written into the information attribute pages of the method object and the user object. It should be noted that if a user object is deleted or migrated, the user method object associated with it also needs to do the same work;
if the object needs to be uploaded is a system method object, the object is randomly uploaded to an OSD, the information is stored in a metadata server, when a client sends out an associated command related to the object, the metadata server is searched, the OSD where the system method object and a corresponding strategy object are located is found, the system method object is transferred and copied to the OSD where the strategy object related to the system method object is located, the associated information is written into information attribute pages of the system method object and the strategy object, and if the strategy object is deleted and migrated, the system method object related to the strategy object also needs to do the same work.
Preferably, the method objects are stored as multiple copies on different devices, when data is distributed on multiple OSDs, and users request data, they send read-write requests for using the method objects to different OSDs in turn according to their (offsets, len), and on each OSD, read the corresponding user object according to their own (offsets, len) relative to the object, and return the final result, so that the data are integrated in turn at the client in the order of reading.
Preferably, the OSD monitors the system condition according to the condition of the policy object, the policy object is also associated with a system method object, when each condition of the policy object returns a true value, the policy object triggers the corresponding system method object to automatically execute, and the policy object is a precondition for the automatic execution of the system method object.
Preferably, when the policy object processing module interacts with the file interface VFS, the policy object processing module completes registration and deletion of the policy object according to the policy request, and associates and disassociates the corresponding method object; when the strategy object is associated with the method object, a kernel thread is operated to read the system information in the root information attribute page and compare with the conditions, once the conditions are met, the method object associated with the strategy object is called to execute, and the realization of the strategy object is the basis of the automatic execution of the system method object.
Preferably, when the user needs to use the policy object to implement the automatic execution of the system method object, the following procedures are executed:
(1) submitting system method objects to be executed to a system;
(2) registering AND writing a POLICY object to the system by using an OSD _ CREATE _ AND _ WRITE _ POLICY command;
(3) using an OSD _ ASSOCIATE _ POLICY command to ASSOCIATE the strategy object with the system method object required to be executed;
(4) after the user finishes the steps, the strategy object processing module automatically reads the information in the root object attribute page, monitors the system operation condition, reads the strategy object attribute page attribute to obtain the system method object ID associated with the strategy object attribute page, and calls the system method object to execute when the system operation condition enables the conditions in the strategy object to return true;
(5) when the user no longer needs to use the POLICY object, the OSD _ UNASSOCIATE _ POLICY command is used to disassociate the POLICY object from the system METHOD object, and the OSD _ REMOVE _ METHOD command is used to delete the POLICY object.
The invention also provides an active object storage system designed by the method.
The invention also provides an application of the active object storage system in the technical field of network storage.
The beneficial effects of the invention include: the invention provides an intelligent active object storage system, which can flexibly realize data preprocessing such as filtering, screening, data checking and various self-defining functions in the node of the object storage system by adding an interface supporting active storage, modifying each layer of modules of the traditional object storage system and adding an active storage module, and endowing the node with certain autonomy such as active fault diagnosis and data recovery, thereby improving the performance of the storage system.
Drawings
FIG. 1 is a block diagram of an active object storage system in accordance with the present invention;
FIG. 2 is a flow chart of the interaction between the method object processing module and the system of the present invention;
FIG. 3 is a flow chart of a storage process of a method object in the present invention;
fig. 4 is an interaction flowchart of the policy object processing module and the file interface VFS according to the present invention.
Detailed Description
The technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the drawings in the embodiments of the present application.
The framework of the active object storage system with the active storage module is shown in fig. 1, and comprises a Client (Client) and an active storage node (OSD), wherein the Client is used for providing files, blocks and object interfaces for a user, and also comprises an active object service module and a communication service module; the OSD is positioned on a file interface, a block interface and an object interface, the OSD comprises an active storage module, an active object management module, a file interface VFS and a communication service module, the object is stored in a local file system of the OSD through the file interface VFS at the bottom layer of the OSD, and each object in the active object storage system is mapped into a file of the local file system according to the ID of the object;
the active storage module is positioned between an active object management module of the OSD and a file interface VFS at the bottom layer and comprises a method object processing module and a strategy object processing module; the active object service and communication service module of the client contains a package for actively storing related commands; the communication service module of the OSD is used for analyzing the command transmitted by the client, and if the command is irrelevant to the active storage, the command is processed according to the processing mode of the traditional object storage system; if the active storage is related, the method object processing module and the strategy object processing module are handed over to carry out active storage processing.
The method object processing module adopts the method object to realize the active storage processing, the method object is the main implementation means of the active storage, after the method object is introduced, a user can conveniently download the required operation to the OSD, and the OSD is used as the method object to carry out the storage and the management. The method object is divided into a user method object and a system method object, the user method object is a method object for operating the user object, the system method object is a method object for realizing a certain OSD autonomous management function according to a strategy object, and the main difference between the method object and the system method object is that the triggering execution methods are different; when the method object is triggered to be executed, the OSD reads the content of the method object through the file interface VFS autonomously to run; the method object is put forward, so that the operation which can be downloaded to the storage device can be a calculation task or a management task, the calculation task and the management task can be unified, and meanwhile, the method object is flexible to write and convenient to download, so that the expandability of the active storage of the system is greatly expanded.
The interaction flow of the method object processing module and other modules of the whole system is shown in fig. 1. The method object processing module completes the registration and deletion of the method object according to the related request of the user method object, and associates and disassociates the corresponding user object; when a user sends a read command with an active storage mark to a system, the method object processing module can automatically read the content of the method object associated with the given user object according to the given user object, schedule and execute the user object as the input of the method object, and return the executed result to the user; when a user sends a write command with an active storage tag to the system, the method object processing module can automatically read the content of the method object associated with the given user object according to the given user object, the input stream is used as the input of the method object to be scheduled and executed, and the executed result is stored in the corresponding user object.
When data is divided into a plurality of user objects and stored on different OSDs, more factors, such as storage location, synchronization of operation results, etc., need to be considered when implementing method objects.
For a user method object, it needs to be uploaded to the OSD where each associated user object is located, for a system method object, it needs to be uploaded to the OSD where each associated policy object is located, and all method objects and policy objects are not split to maintain their integrity. The storage process of the method object and the policy object is shown in fig. 3.
The process of uploading is as follows: if the user method object is required to be uploaded, the user method object is randomly uploaded to a certain OSD, the information is stored in an external metadata server, when a client sends out a related associated command, the metadata server is searched, the user method object and the OSD where the corresponding user object is located are found, the method object is transferred and copied to the OSD where all the user objects related to the method object are located, and the associated information is written into the method object and the information attribute page of the user object. It should be noted that if a user object is deleted or migrated, the user method object associated with it will do the same.
If the object needs to be uploaded is the system method object, the object is randomly uploaded to a certain OSD, the information is stored in a metadata server, when a client sends out an associated command related to the object, the metadata server is searched, the OSD where the system method object and the corresponding strategy object are located is found, the system method object is transferred and copied to the OSD where the strategy object related to the system method object is located, and the associated information is written into the information attribute pages of the system method object and the OSD. If a policy object is deleted and migrated, the system method object associated with it will do the same.
The method objects are stored on different devices as a plurality of copies, which is beneficial to improving the parallelism of the devices and reducing the response time of users, and although a certain storage space is occupied, the performance of the storage device is greatly improved. When data is distributed over a plurality of OSDs and a user requests the data, a read/write request for a method object is sequentially issued to different OSDs according to the offset (len). On each OSD, the corresponding user object is read according to its own relative object (offset, len), and the final result is returned. Therefore, the data can be sequentially integrated at the client according to the reading sequence, and the system does not need to perform additional processing.
A policy object is a collection of conditions. It is similar to the conditional judgment statement in C language, and can judge each condition of the policy object and return a boolean value. The OSD monitors the system conditions according to the conditions of the policy objects. The policy object also needs to be associated with a system method object, and when each condition of the policy object returns a true value, the policy object triggers the corresponding system method object to automatically execute. A policy object is a prerequisite for the automatic execution of a system method object.
The interaction flow between the policy object processing module and the file interface VFS is shown in fig. 4. The strategy object processing module completes the registration and deletion of the strategy object according to the strategy request, and associates and disassociates the corresponding method object; when the policy object is associated with the method object, a kernel thread is run to read the system information in the root information tab and compare it with its condition. Once the conditions are satisfied, the method object associated therewith is invoked for execution. The implementation of the policy object is the basis for the automatic execution of the system method object. When a user needs to use a policy object to implement automatic execution of a system method object, the following processes need to be executed:
(1) submitting system method objects to be executed to a system;
(2) registering AND writing a POLICY object to the system by using an OSD _ CREATE _ AND _ WRITE _ POLICY command;
(3) using an OSD _ ASSOCIATE _ POLICY command to ASSOCIATE the strategy object with the system method object required to be executed;
(4) after the user finishes the steps, the strategy object processing module automatically reads the information in the root object attribute page, monitors the system operation condition, reads the strategy object attribute page attribute to obtain the system method object ID associated with the strategy object attribute page, and calls the system method object to execute when the system operation condition enables the conditions in the strategy object to return true;
(5) when the user no longer needs to use the POLICY object, the OSD _ UNASSOCIATE _ POLICY command is used to disassociate the POLICY object from the system METHOD object, and the OSD _ REMOVE _ METHOD command is used to delete the POLICY object.
It can be seen that the system of the present invention utilizes the redundant parallel computing power in the storage system by placing part of the operation modules of the application program in the Object Storage Device (OSD), reducing the data transmission amount on the network, reducing the requirement of the application program on the network bandwidth, and enhancing the intelligence of the OSD. The object storage and the active storage are combined to form an active object storage system, so that the advantages of the object storage and the active storage are absorbed, and the performance of the storage system is improved. The intelligent active object storage system provided by the invention can flexibly realize data preprocessing in the object storage system node, endow the node with certain autonomy and improve the performance of the storage system.
The above description is only an example of the present application and is not intended to limit the scope of the present application, and various modifications and changes may be made by those skilled in the art. Any modification, equivalent replacement, improvement and the like made within the spirit and principle of the present application shall be included in the protection scope of the present application.
Claims (9)
1. The method for realizing the active object storage system is characterized in that in the method, the system is designed to comprise a client and an active storage node OSD, wherein the client is used for providing files, blocks and object interfaces for a user, and also comprises an active object service module and a communication service module; the OSD is positioned on a file interface, a block interface and an object interface, the OSD comprises an active storage module, an active object management module, a file interface VFS and a communication service module, the object is stored in a local file system of the OSD through the file interface VFS at the bottom layer of the OSD, and each object in the active object storage system is mapped into a file of the local file system according to the ID of the object;
the active storage module is positioned between an active object management module of the OSD and a file interface VFS at the bottom layer and comprises a method object processing module and a strategy object processing module; the active object service and communication service module of the client contains a package for actively storing related commands; the communication service module of the OSD is used for analyzing the command transmitted by the client, and if the command is irrelevant to the active storage, the command is processed according to the processing mode of the traditional object storage system; if the active storage is related, the method object processing module and the strategy object processing module are handed over to carry out active storage processing;
the method object processing module adopts a method object to realize active storage processing, the method object is a main implementation means of active storage, after the method object is introduced, a user can download required operation into OSD (on screen display), and the operation is used as the method object to be stored and managed by the OSD; the method object is divided into a user method object and a system method object, the user method object is a method object for operating the user object, the system method object is a method object for realizing a certain OSD autonomous management function according to a strategy object, and the triggering execution methods of the user method object and the system method object are different; when the method object is triggered to be executed, the OSD reads the content of the method object through the file interface VFS autonomously to operate.
2. The method of claim 1, wherein the method object processing module completes the registration and deletion of the method object according to the user method object related request, and associates and disassociates the corresponding user object; when a user sends a read command with an active storage mark to a system, the method object processing module can automatically read the content of the method object associated with the given user object according to the given user object, schedule and execute the user object as the input of the method object, and return the executed result to the user; when a user sends a write command with an active storage tag to the system, the method object processing module can automatically read the content of the method object associated with the given user object according to the given user object, the input stream is used as the input of the method object to be scheduled and executed, and the executed result is stored in the corresponding user object.
3. The implementation method of claim 2, wherein when the data is divided into a plurality of user objects and stored on different OSDs, the synchronization of the operation results is performed in consideration of the storage location when implementing the method object;
for the user method object, uploading it to the OSD where each user object associated with it is located, for the system method object, uploading it to the OSD where each strategy object associated with it is located, and all the method objects and strategy objects are not divided;
the process of uploading is as follows: if the user method object is required to be uploaded, the user method object is randomly uploaded to an OSD, the information is stored in an external metadata server, when a client sends out a related associated command, the metadata server is searched, the user method object and the OSD where the corresponding user object is located are found, the method object is transferred and copied to the OSD where all the user objects related to the method object are located, and the related information is written into the information attribute pages of the method object and the user object. It should be noted that if a user object is deleted or migrated, the user method object associated with it also needs to do the same work;
if the object needs to be uploaded is a system method object, the object is randomly uploaded to an OSD, the information is stored in a metadata server, when a client sends out an associated command related to the object, the metadata server is searched, the OSD where the system method object and a corresponding strategy object are located is found, the system method object is transferred and copied to the OSD where the strategy object related to the system method object is located, the associated information is written into information attribute pages of the system method object and the strategy object, and if the strategy object is deleted and migrated, the system method object related to the strategy object also needs to do the same work.
4. The method of claim 3, wherein the method objects are stored as multiple copies on different devices, when the data is distributed on multiple OSDs, the user requests the data according to its (offset, len) to send the read/write request of the method object to different OSDs in turn, on each OSD, the corresponding user object is read according to its own (offset, len) relative object, and the final result is returned, so that the data are integrated in turn in the reading order at the client.
5. The method of claim 4, wherein the OSD monitors the system condition according to the condition of the policy object, the policy object is also associated with a system method object, and when each condition of the policy object returns a true value, the policy object triggers the corresponding system method object to automatically execute, the policy object being a precondition for the automatic execution of the system method object.
6. The implementation method of claim 5, wherein when the policy object processing module interacts with the file interface VFS, the policy object processing module completes registration and deletion of the policy object according to the policy request, and associates and disassociates the corresponding method object; when the strategy object is associated with the method object, a kernel thread is operated to read the system information in the root information attribute page and compare with the conditions, once the conditions are met, the method object associated with the strategy object is called to execute, and the realization of the strategy object is the basis of the automatic execution of the system method object.
7. The implementation method of claim 6, wherein when the user needs to use the policy object to implement the automatic execution of the system method object, the following procedure is executed:
(1) submitting system method objects to be executed to a system;
(2) registering AND writing a POLICY object to the system by using an OSD _ CREATE _ AND _ WRITE _ POLICY command;
(3) using an OSD _ ASSOCIATE _ POLICY command to ASSOCIATE the strategy object with the system method object required to be executed;
(4) after the user finishes the steps, the strategy object processing module automatically reads the information in the root object attribute page, monitors the system operation condition, reads the strategy object attribute page attribute to obtain the system method object ID associated with the strategy object attribute page, and calls the system method object to execute when the system operation condition enables the conditions in the strategy object to return true;
(5) when the user no longer needs to use the POLICY object, the OSD _ UNASSOCIATE _ POLICY command is used to disassociate the POLICY object from the system METHOD object, and the OSD _ REMOVE _ METHOD command is used to delete the POLICY object.
8. An active object storage system designed using the method of any one of claims 1 to 7.
9. Use of the active object storage system of claim 8 in the field of network storage technology.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202011115392.8A CN112241243B (en) | 2020-10-19 | 2020-10-19 | Method for realizing active object storage system |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202011115392.8A CN112241243B (en) | 2020-10-19 | 2020-10-19 | Method for realizing active object storage system |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN112241243A true CN112241243A (en) | 2021-01-19 |
| CN112241243B CN112241243B (en) | 2024-01-26 |
Family
ID=74169156
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202011115392.8A Active CN112241243B (en) | 2020-10-19 | 2020-10-19 | Method for realizing active object storage system |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN112241243B (en) |
Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| JP2006178926A (en) * | 2004-10-18 | 2006-07-06 | Hitachi Ltd | Storage apparatus, system and method using a plurality of object-based storage devices |
| WO2010040255A1 (en) * | 2008-10-07 | 2010-04-15 | 华中科技大学 | Method for managing object-based storage system |
| US9002805B1 (en) * | 2012-12-14 | 2015-04-07 | Amazon Technologies, Inc. | Conditional storage object deletion |
| CN105656952A (en) * | 2014-11-11 | 2016-06-08 | 田鹏 | Data exchange platform with reliable application level |
| CN107920067A (en) * | 2017-11-10 | 2018-04-17 | 华中科技大学 | A kind of intrusion detection method in active objects storage system |
| KR20190055009A (en) * | 2017-11-14 | 2019-05-22 | 성균관대학교산학협력단 | Method and apparatus for providing security service |
-
2020
- 2020-10-19 CN CN202011115392.8A patent/CN112241243B/en active Active
Patent Citations (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| JP2006178926A (en) * | 2004-10-18 | 2006-07-06 | Hitachi Ltd | Storage apparatus, system and method using a plurality of object-based storage devices |
| WO2010040255A1 (en) * | 2008-10-07 | 2010-04-15 | 华中科技大学 | Method for managing object-based storage system |
| CN101796514A (en) * | 2008-10-07 | 2010-08-04 | 华中科技大学 | The management method of object storage system |
| US9002805B1 (en) * | 2012-12-14 | 2015-04-07 | Amazon Technologies, Inc. | Conditional storage object deletion |
| CN105656952A (en) * | 2014-11-11 | 2016-06-08 | 田鹏 | Data exchange platform with reliable application level |
| CN107920067A (en) * | 2017-11-10 | 2018-04-17 | 华中科技大学 | A kind of intrusion detection method in active objects storage system |
| KR20190055009A (en) * | 2017-11-14 | 2019-05-22 | 성균관대학교산학협력단 | Method and apparatus for providing security service |
Also Published As
| Publication number | Publication date |
|---|---|
| CN112241243B (en) | 2024-01-26 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US20230244404A1 (en) | Managing digital assets stored as components and packaged files | |
| US10657008B2 (en) | Managing a redundant computerized database using a replicated database cache | |
| US20220229736A1 (en) | Synthesizing a restore image from one or more secondary copies to facilitate data restore operations to a file server | |
| US9785523B2 (en) | Managing replicated virtual storage at recovery sites | |
| US8738883B2 (en) | Snapshot creation from block lists | |
| KR20030086311A (en) | Collecting and restoring user environment data using removable storage | |
| US9183130B2 (en) | Data control system for virtual environment | |
| US9223797B2 (en) | Reparse point replication | |
| CN107809467B (en) | Method for deleting container mirror image data in cloud environment | |
| CN104881466A (en) | Method and device for processing data fragments and deleting garbage files | |
| Sim et al. | Analyzethis: an analysis workflow-aware storage system | |
| US9471366B2 (en) | Virtual machine disk image backup using block allocation area | |
| Ganelin et al. | Spark: Big data cluster computing in production | |
| US11675674B2 (en) | Instant recovery of databases | |
| CN105469001A (en) | Disk data protection method and device | |
| US11010408B2 (en) | Hydration of a hierarchy of dehydrated files | |
| CN112241243A (en) | Method for realizing active object storage system | |
| US20140040191A1 (en) | Inventorying and copying file system folders and files | |
| US11269739B2 (en) | Method and system for managing backup data | |
| CN105426489A (en) | Memory calculation based distributed expandable data search system | |
| US7890963B2 (en) | Vector replacement method | |
| CN114880103B (en) | System and method for flight task adaptation hadoop ecology | |
| US12007856B2 (en) | Dynamic resizing and re-distribution of destination data storage resources for bare metal restore operations in a data storage management system | |
| US20240095225A1 (en) | Intelligently storing data in a fault tolerant system using robotic process automation and blockchain | |
| CN112596955A (en) | Emergency processing system and method for processing large-scale system emergency in cloud computing |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |