KR102362699B1 - Method for providing a file management service using a plurality of storage devices and Apparatus thereof - Google Patents

Abstract

A method of providing a file management service using a plurality of storage devices is provided. The method of providing a file management service according to an embodiment of the present invention, which is performed by a storage management device that provides read/write services for a plurality of storage devices, includes receiving a file write request for a first file, the storage management The method may include inquiring a storage profile corresponding to the attribute of the first file among a plurality of storage profiles managed by the device, and allowing the first file to be stored in a storage device pointed to by the inquired storage profile. .

Description

Method for providing a file management service using a plurality of storage devices and Apparatus thereof

The present invention relates to a method and apparatus for providing a file management service using a plurality of storage devices. More particularly, the present invention relates to a method for more effectively providing a file management service based on the purpose of each of a plurality of storage devices, and to an apparatus for performing the method.

As the amount of managed data increases exponentially, it is frequently necessary to add new storage to an existing storage system or to replace the storage system itself.

In most storage service systems, data migration of existing storage to new storage is performed when storage is added and/or storage is replaced. However, data migration takes a lot of time, and there is a risk of data loss during migration. In addition, since access to the data is not possible during data migration, the provision of the storage service is stopped. This causes a huge cost loss to the service provider and significant inconvenience to the user receiving the service.

In addition, most storage service systems do not provide a function of flexibly setting file management policies according to data characteristics and storage characteristics. For example, within a single system with multiple storages, important files are stored on primary storage with disaster recovery capabilities, and regular files are stored on secondary storage with no disaster recovery capabilities. It does not provide the ability to set the file management policy to be saved.

Therefore, there is a need for a method capable of expanding storage without data migration and setting a flexible file management policy according to data characteristics.

Korean Patent Publication No. 10-2013-0048594 (published on May 10, 2013)

An object of the present invention is to provide a method for providing a file management service using a plurality of storage devices and an apparatus for performing the method.

Another technical problem to be solved by the present invention is to provide a method of providing a file management service capable of expanding storage without data migration, and an apparatus for performing the method.

Another technical problem to be solved by the present invention is to provide a method of providing a file management service that provides a flexible file management policy setting function according to file characteristics and/or storage requirements, and an apparatus for performing the method will be.

The technical problems of the present invention are not limited to the technical problems mentioned above, and other technical problems not mentioned will be clearly understood by those skilled in the art from the following description.

In order to solve the above technical problem, a method of providing a file management service using a plurality of storage devices according to an embodiment of the present invention is performed by a storage management device that provides read/write services for the plurality of storage devices. The method comprising: receiving a file write request for a first file; inquiring a storage profile corresponding to an attribute of the first file from among a plurality of storage profiles managed by the storage management device; and allowing the first file to be stored in a storage device pointed to by the profile.

In an embodiment, the inquiring of the storage profile may include inquiring of a storage profile having a usage code corresponding to the attribute of the first file.

In an embodiment, the method may further include providing a storage identifier included in the inquired storage profile in response to the file write request.

In an embodiment, the method may further include storing the storage identifier included in the inquired storage profile together with the identifier of the first file in file meta information managed by the storage management device.

In an embodiment, a file read request including the identifier of the first file is provided from the storage management service using device, and in response i) the first file is stored in the file meta information using the identifier of the first file obtaining a storage identifier, ii) inquiring a storage profile having the obtained storage identifier among a plurality of storage profiles managed by the storage management device, iii) reading the first file from the storage device pointed to by the inquired storage profile The method may further include generating a command to come, and iv) providing the read first file to the storage management service using device.

In an embodiment, the receiving of the file write request for the first file includes receiving information indicating a storage requirement in which the first file is to be recorded, along with the file write request, Inquiring the storage profile may include determining a usage code corresponding to the attribute of the first file and a storage requirement in which the first file is to be recorded, and inquiring a storage profile having the determined usage code. may include

In an embodiment, the method may further include providing a user interface supporting an editing function for at least a portion of the plurality of storage profiles.

A storage management device according to an embodiment of the present invention for solving the above-described technical problem includes a processor, a network interface, a memory for loading a computer program executed by the processor, a plurality of storage profiles, and a computer program a storage for storing, wherein the computer program includes an operation for receiving a file write request for a first file, and a usage code corresponding to an attribute of the first file among the plurality of storage profiles managed by the storage management device It may include an operation of inquiring a storage profile having , and an operation of generating a command to store the first file in a storage device pointed to by the inquired storage profile.

A computer program according to an embodiment of the present invention for solving the above-described technical problem is coupled to a computing device, receiving a file write request for a first file, a plurality of storage managed by the storage management device In order to execute the steps of inquiring a storage profile having a usage code corresponding to the attribute of the first file in the profile and generating a command to store the first file in a storage device pointed to by the inquired storage profile may be stored in a readable recording medium.

According to the above-described embodiment of the present invention, a usage code indicating a usage of the corresponding storage is assigned to the storage profile, and a file write request may be forwarded to the target storage based on the usage code. Accordingly, the file management policy can be set in a simple way of assigning/changing the usage code of the storage profile, and thus the convenience of service management can be improved.

In addition, by assigning a usage code indicating write activation to the existing storage with a high usage rate and giving a usage code indicating write activation to the new storage, an extension function for the storage may be provided without migration. Accordingly, a non-disruptive file management service can be provided, time cost and human cost required for migration can be reduced, and loss caused by service interruption can be prevented.

In addition, since the use code is determined based on at least one of the file attribute and the storage requirement, a flexible file management policy may be set according to the file attribute and the storage requirement. For example, when a file management policy is set such that the target storage is determined based on the owner of the target file, a file management service differentiated for each user may be provided. As another example, when a file management policy is set such that the target storage is determined based on the management level of the target file, a file management service differentiated according to the importance of the file may be provided.

A user interface for editing the storage profile is also provided. Accordingly, the convenience of the administrator may be further improved.

Effects of the present invention are not limited to the above-mentioned effects, and other effects not mentioned will be clearly understood by those skilled in the art from the following description.

1 is a block diagram of a system for providing a file management service according to a first embodiment of the present invention.
2 is a block diagram of a system for providing a file management service according to a second embodiment of the present invention.
3 is a block diagram of a system for providing a file management service according to a third embodiment of the present invention.
4 is a block diagram illustrating a storage management apparatus according to an embodiment of the present invention.
5 is an exemplary diagram of a storage profile and file meta information that may be referenced in some embodiments of the present invention.
6 is a diagram for explaining a storage profile editing function according to an embodiment of the present invention.
7 and 8 are diagrams for explaining a method of providing a file management service according to an embodiment of the present invention.
9 is a hardware configuration diagram of an exemplary computing device capable of implementing a storage management device according to an embodiment of the present invention.

Hereinafter, preferred embodiments of the present invention will be described in detail with reference to the accompanying drawings. Advantages and features of the present invention and methods of achieving them will become apparent with reference to the embodiments described below in detail in conjunction with the accompanying drawings. However, the present invention is not limited to the embodiments disclosed below, but may be implemented in various different forms, and only these embodiments allow the disclosure of the present invention to be complete, and common knowledge in the art to which the present invention pertains It is provided to fully inform those who have the scope of the invention, and the present invention is only defined by the scope of the claims. Like reference numerals refer to like elements throughout.

Unless otherwise defined, all terms (including technical and scientific terms) used herein may be used with the meaning commonly understood by those of ordinary skill in the art to which the present invention belongs. In addition, terms defined in a commonly used dictionary are not to be interpreted ideally or excessively unless clearly defined in particular. The terminology used herein is for the purpose of describing the embodiments and is not intended to limit the present invention. In this specification, the singular also includes the plural unless specifically stated otherwise in the phrase.

As used herein, "comprises" and/or "comprising" refers to the presence of one or more other components, steps, operations and/or elements mentioned. or addition is not excluded.

Hereinafter, some embodiments of the present invention will be described in detail with reference to the accompanying drawings.

1 is a block diagram of a file management service providing system according to a first embodiment of the present invention.

Referring to FIG. 1 , the file management service providing system according to the first embodiment includes a storage management device 100 , a plurality of storage devices 10a , 10b , 10c , 10n , and at least one user terminal 30 . can be configured to However, this is only a preferred embodiment for achieving the object of the present invention, and it goes without saying that some components may be added or deleted as needed. In addition, it should be noted that each of the components of the file management service providing system shown in FIG. 1 represents functionally separated functional elements, and at least one component may be implemented in a form that is integrated with each other in an actual physical environment. do.

In the file management service providing system according to the first embodiment, the storage management device 100 is a computing device that provides a file management service and manages a plurality of storages 10a, 10b, 10c, and 10n. The computing device may be a notebook computer, a desktop computer, a laptop computer, etc., but is not limited thereto, and may include any type of device equipped with a computing function and a communication function. However, when providing a file management service for a plurality of users, the storage management device 100 may be preferably implemented as a high-performance server computing device.

According to an embodiment of the present invention, in response to an upload request for a target file received from the user terminal 30 , the storage management apparatus 100 may determine a target storage in which the target file is to be stored. Specifically, the storage management apparatus 100 may determine a storage having a purpose that meets the attribute of the target file and/or a storage requirement as the target storage. A detailed description of the present embodiment will be described later in detail with reference to FIGS. 4 to 7 .

According to an embodiment of the present invention, the storage management apparatus 100 provides an extension function for storage without data migration. For example, it is assumed that a new storage device is added due to a capacity problem of the n-th storage device 10n. At this time, the storage management device 100 forwards the file read request of the user terminal 300 to the n-th storage device 10n, but the file write request of the user terminal 300 is forwarded to the n-th storage device 10n. Instead, it is possible to control forwarding to the new storage device. Accordingly, a storage expansion function may be provided without a separate data migration. The above control may be performed through the use code of the storage profile for the new storage device and the n-th storage device 10n. A detailed description thereof will be described later with reference to FIGS. 4 and 5 . According to the present embodiment, the time cost for data migration can be reduced, loss caused by service interruption during data migration can be prevented, and a safe file management service can be provided without the risk of data migration.

A detailed description of the configuration and operation of the storage management device 100 will be described later in detail with reference to FIGS. 4 to 6 .

In the file management service providing system according to the first embodiment, the plurality of storages 10a, 10b, 10c, and 10n respond to a file write request and/or a file read request forwarded by the storage management device 100, A device that writes or reads files. Each storage 10a, 10b, 10c, 10n may be configured to include any storage medium (e.g. HDD, SDD) for recording files.

In the file management service providing system according to the first embodiment, the user terminal 30 is a terminal receiving the file management service provided by the storage management apparatus 100 and the plurality of storages 10a, 10b, 10c, 10n. to be. The user may download or upload the target file through the user terminal 30 . In this specification, the user terminal 30 may be used interchangeably with the term file management service using device.

The storage management device 100 and the user terminal 30 may communicate through the network 20 . The network 20 includes all types of wired/wireless networks such as a local area network (LAN), a wide area network (WAN), a mobile radio communication network, and a Wibro (Wireless Broadband Internet). can be implemented.

So far, a system for providing a file management service according to a first embodiment of the present invention has been described with reference to FIG. 1 . Next, a system for providing a file management service according to a second embodiment of the present invention will be described with reference to FIG. 2 . In particular, FIG. 2 further illustrates a detailed configuration of the storage management apparatus 100 .

Referring to FIG. 2 , in the file management service providing system according to the second embodiment, the storage management device 100 may provide an integrated file management service based on a plurality of storage service systems 40a and 40b. have.

In the file management service providing system according to the second embodiment, the storage management device 100 may be configured to include the storage adapter 102 , the storage management module 104 , and the service module 106 .

The storage adapter 102 provides an interface function to a storage device (e.g. storage 10a shown in FIG. 1 ) or storage service systems 40a and 40b. The storage adapter 102 receives a file read command and/or a file write command and a storage identifier from the storage management module 104 , and transmits the received command/information to a target storage indicated by the storage identifier to read and/or read a file Or, allow file writes to be performed.

The storage adapter 102 may be configured to include various interworking modules to interwork with different storage devices and/or storage service systems provided by different vendors.

The storage management module 104 is a module that provides a profile management function for a plurality of storages and a file read/write request processing function. In this case, the storage is a generic term referring to the storage service systems 40a and 40b as shown in FIG. 2 or a storage device as shown in FIG. 1 .

The storage management module 104 sends an identifier of the target storage for the target file and a file read/write command to the storage adapter 102 in response to a file read/write request for the target file received from the service module 106 . transmit A more detailed description of the storage management module 104 will be described later with reference to FIG. 4 .

The service module 106 is a module that provides an interface function with the user terminal 30 . Specifically, the service module 106 provides a file write request for the upload file 60a received from the user terminal 30 to the storage management module 104 . In addition, the service module 106 provides a file read request to the storage management module 104 in response to the file download request received from the user terminal 300 , and the download file 60b provided by the storage management module 104 ) is provided to the user terminal 30 .

According to an embodiment of the present invention, the service module 106 manages file meta information for a target file. The file meta information is information including attribute information of the file and the identifier of the storage in which the target file is stored, and is used for determining the identifier of the target storage when processing a file write request or for identifying the target storage when processing a file read request do. However, according to an embodiment, the file meta information may be managed by the storage management module 104 . A specific example and method of using the file meta information will be described later with reference to FIGS. 4 to 5 .

Meanwhile, according to an embodiment of the present invention, the service module 106 may be implemented as an independent device 200 as shown in FIG. 3 . In this case, the storage management device 100 may be configured to include only the storage adapter 102 and the storage management module 104 .

In the file management service providing system according to the second embodiment, the storage service systems 40a and 40b are systems that provide cloud storage services such as Amazon's simple storage service (S3) and Google's storage service.

As shown in FIG. 2 , the first storage service system 40a may be configured to include a plurality of storages 10d and 10e and a service management device 50a for managing the plurality of storages. In this embodiment, if the storage adapter 102 and the storage management module 104 serve to forward the file write/read request to the target storage service system, the service management device 50a receives the file write/read request It may be understood that a role of forwarding to the target storage devices 10d and 10e is performed.

Some embodiments of the present invention described with reference to FIG. 1 may be equally applied to the environment shown in FIG. 2 . For example, the storage management apparatus 100 may determine the target storage of the storage service systems 40a and 40b having a purpose that meets the attribute of the target file and/or a storage requirement. As another example, the storage management device 100 changes the purpose of the first storage service system 40a and 40b to read-only, and adds a new storage service system (not shown) having read and write-only purposes. It can provide non-disruptive storage expansion function.

So far, a system for providing a file management service according to some embodiments of the present invention has been described with reference to FIGS. 2 and 3 . Next, with reference to FIG. 4 , the configuration and operation of the storage management apparatus 100 will be described in detail.

4 is a block diagram illustrating a storage management apparatus 100 according to an embodiment of the present invention. In particular, FIG. 4 further shows a detailed configuration of the storage management module 104 . Since the description of the storage adapter 102 is the same as described above, the configuration and operation of the storage management module 104 will be described in detail.

Referring to FIG. 4 , the storage management module 104 may be configured to include a storage unit 140 , a file read/write request processing unit 142 , and a storage profile management unit 144 . However, only the components related to the embodiment of the present invention are illustrated in FIG. 4 . Accordingly, those skilled in the art to which the present invention pertains can see that other general-purpose components other than the components shown in FIG. 4 may be further included. In addition, it should be noted that each of the components shown in FIG. 4 represents functional elements that are functionally separated, and at least one component may be implemented in a form that is integrated with each other in an actual physical environment.

Looking at each component, the storage unit 140 stores and manages the storage profile 140a and the file meta information 140b. However, according to an embodiment, the file meta information 140b may be managed by a separate device (eg, the service providing device 200 ). The storage unit 140 may be configured to include any storage medium to provide the above functions.

The storage profile 140a is profile information about each storage device, and one storage device may correspond to at least one storage profile. An example of a storage profile 140a is shown in FIG. 5 . Referring to FIG. 5 , the storage profile 140a includes, for example, a storage identifier 1400 , a storage name 1401 , a storage URL 1402 , storage connection IDs and passwords 1403 , 1404 , and a storage usage code 1405 . ) and a description 1406 of the usage code.

Among the information included in the storage profile 140a, the storage identifier 1400 is information that uniquely identifies each storage. The storage identifier 1400 is also included in the file meta information 140b to identify the target storage in which the target file is recorded. In the process of processing a file write request, when a target storage is determined, an identifier of the target storage may be inserted into the file meta information 140b. In addition, in the process of processing the file read request, the storage identifier 1400 included in the file meta information 140b is used to identify the target storage. In the process of processing a file read/write request, a more detailed description of a method in which the storage identifier 1400 is used will refer to FIGS. 7 and 8 .

Among the information included in the storage profile 140a, the usage code 1405 is a code indicating the usage of each storage. When a plurality of storages having the same purpose exist, the plurality of storages may have the same usage code.

According to an embodiment of the present invention, the usage code of each storage may be assigned according to an attribute of a file and/or a storage requirement. In this case, the properties of the file may include, for example, the extension of the file, the owner of the file, the size of the file, and the management level of the file. In addition, the requirements for the storage may include, for example, an I/O request rate, disaster recovery support, a geographic location of the storage, a storage service vendor, and the like. According to the present embodiment, a flexible file management policy may be set based on a file attribute and/or a storage requirement. For example, the administrator may allow the file having the first attribute to be managed in the first storage by assigning the first usage code corresponding to the first attribute of the file to the first storage. As another example, the administrator may assign a second usage code corresponding to the first requirement for storage to the second storage, so that the file having the first requirement is managed in the second storage. In order to provide more convenience of understanding, some examples of setting the usage code will be described.

In one example, a usage code for each storage may be assigned based on a file owner among attributes of a file. In this example, the file of the first user may be managed in the first storage, and the file of the second user may be managed in the second storage. Accordingly, a file management service differentiated for each user may be provided. For example, files of users who subscribe to paid services are managed in the primary storage that provides disaster recovery function or fast I/O speed, and files of users who use free services are managed by users who do not provide the above functions. 2 It is possible to provide differentiated services by allowing them to be managed in storage.

In another example, a usage code for each storage may be assigned based on the management level of the file among the attributes of the file. In this example, a first file having a high management level may be managed in a first storage having a high security level, and a second file having a low management level may be managed in a second storage having a low security level. Accordingly, a file management service differentiated for each file level can be provided.

In another example, a usage code for each storage may be assigned according to a file attribute such as a file extension or a storage requirement such as an I/O request rate and disaster recovery support. Through this, it is possible to set flexible file management policies, such as allowing files with the same extension to be managed in the same storage or files requiring disaster recovery support to be managed in a storage with disaster recovery function.

So far, some examples of assigning a usage code for each storage have been described. However, the above examples are for explaining some embodiments of the present invention, and the scope of the present invention is not limited to the above examples.

Meanwhile, according to an embodiment of the present invention, the usage code may include a code for activating/deactivating a read/write function. Through this, the file management policy may be set such that the first storage is read-only and the second storage is read/write-only. In the present embodiment, a storage expansion function without data migration may be provided by assigning a usage code indicating write activation to the new storage and giving a usage code indicating write inactivity to the existing storage whose usage ratio exceeds a specific value. That is, by using the existing storage as read-only and allowing new files to be stored in the new storage, a non-disruptive file management service can be provided without separate data migration. Accordingly, time and human costs associated with data migration can be reduced, and losses caused by service interruption can be prevented.

The file meta-information 140b refers to general information about attributes of a file. An example of the file meta information 140b is illustrated in FIG. 5 . Referring to FIG. 5 , the file meta information 140b includes attribute information such as an identifier of a file, a size of a file, and an owner of the file. In addition, the file meta information 140b may further include attribute information on the management level of the file. In addition, the file meta information 140b includes a storage identifier 1400 indicating the target storage of the target file identified by the file identifier. The storage identifier 1400 is inserted into the file meta information 140b through the process of processing the write request of the target file, and is then used to process the file read request of the target file. This will be described in more detail with reference to FIGS. 7 and 8 .

Referring back to FIG. 4 , the file read/write request processing unit 142 processes a file read and/or file write request received from the service providing apparatus 200 and/or the user terminal 30 .

Specifically, in response to the file read request of the target file, the file read/write request processing unit 142 transmits the storage identifier included in the file meta information 140b of the target file to the storage adapter 102 together with the file read command. to provide. Through this, file reading may be performed from the target storage indicated by the storage identifier.

In addition, in response to the file write request of the target file, the file read/write request processing unit 142 generates a usage code corresponding to the file attribute and/or storage requirement included in the file meta information 140b of the target file. and obtains an identifier of the target storage having the usage code by using the storage profile 140a. Next, the file read/write request processing unit 142 provides an identifier of the target storage and a file write command to the storage adapter 102 . Through this, file writing may be performed in the target storage indicated by the storage identifier.

According to an embodiment of the present invention, automatic migration of a target file may be performed by the file read/write request processing unit 142 . For example, it is assumed that the target storage in which the target file is stored is changed to write inactive, and the user downloads the target file, then modifies some contents and uploads it again. In the above case, as the use of the target storage is changed to read-only, the file read/write request processing unit 142 may cause the modified target file to be stored in the new target storage having a use code indicating write activation. Through this, whenever the target file is re-uploaded, the storage location of the target file is automatically changed, so that automatic migration can be performed without service interruption.

Next, the storage profile manager 144 manages storage profiles for a plurality of storages. The storage profile manager 144 may provide a user interface (hereinafter, referred to as a “storage profile editing interface”) that provides an editing function for the storage profile. The storage profile editing interface may be provided in the form of a predetermined graphic user interface (GUI) for convenience of management, but may be provided in any form.

A manager having the manager terminal 70 may manage the storage profile using the storage editing interface. An example of the storage editing interface is shown in FIG. 6 . Referring to FIG. 6 , the storage editing interface 80 may include a first area 81 providing a storage profile search/inquiry function and a second area 82 providing a storage profile editing function.

For example, the administrator may inquire a storage profile for a storage having a storage usage rate equal to or greater than a specific value among a plurality of storage profiles by using the interface of the first area 81 . The inquired storage profile may be provided in the second area 88 , and information 81a on the number of the inquired storage profile may also be provided.

Also, the administrator may edit the value 82b of the storage profile having the storage identifier 82a using the interface of the second area 88 . For example, an administrator can change the purpose of that storage to read-only by changing the usage code in the storage profile for storage with utilization above a certain number to a value that points to write-disabled. Accordingly, an uninterrupted file management service without data migration can be provided.

According to an embodiment of the present invention, the storage profile management unit 144 determines whether the storage usage rate is equal to or greater than a first specific value, and in response to the determination that the usage rate is equal to or greater than the first specific value, returns to the manager terminal 70 . An alarm message can be provided. Accordingly, the administrator can perform storage management based on the received alarm message without continuously monitoring the storage usage rate, and thus the convenience of management can be greatly improved.

In addition, the storage profile management unit 144 determines whether the storage usage rate is equal to or greater than a second specific value, and in response to determining that the usage rate is equal to or greater than the second specific value, automatically writes the storage usage code indicating inactivation value can be changed. In this case, the storage profile manager 144 may provide an alarm message indicating addition of new storage to the manager terminal 70 .

Each component of the storage management device 100 shown in FIGS. 2 and 4 may mean software or hardware such as a field programmable gate array (FPGA) or an application-specific integrated circuit (ASIC). can However, the above components are not meant to be limited to software or hardware, and may be configured to be in an addressable storage medium or configured to execute one or more processors. A function provided in the above components may be implemented by a more subdivided component, or may be implemented as a single component that performs a specific function by combining a plurality of components.

So far, the configuration and operation of the storage management apparatus 100 according to the embodiment of the present invention has been described with reference to FIGS. 4 to 6 . Next, a process of processing a file write request and a file read request in the method of providing a file management service according to an embodiment of the present invention will be described with reference to FIGS. 7 and 8 .

Hereinafter, each step of the method of providing a file management service according to an embodiment of the present invention may be performed by a computing device. For example, the computing device may be the storage management device 100 or the service providing device 200 . However, for convenience of description, the description of the operating subject of each step included in the method of providing the file management service may be omitted. In addition, each step of the method for providing the file management service may be implemented as each operation of a computer program loaded into a memory and executed by a processor. have.

7 is a flowchart illustrating a file write request processing method according to an embodiment of the present invention. However, this is only a preferred embodiment for achieving the object of the present invention, and it goes without saying that some steps may be added or deleted as needed. In particular, FIG. 7 illustrates a process in which a file write request is processed by the storage management apparatus 100 .

Referring to FIG. 7 , in step S100 , the storage management device 100 receives a file write request for a target file. For example, the storage management apparatus 100 may receive a file write request for the target file from the user terminal 30 . Alternatively, the storage management device 100 may receive the file write request from the service providing device 200 .

In step S102, the storage management device 100 determines the attribute of the target file. As described above, the properties of the target file may include, for example, the extension of the file, the owner of the file, the size of the file, and the management level of the file.

In step S104, the storage management device 100 determines a requirement for the target storage in which the target file is to be recorded. In this case, the requirements for the target storage may include, for example, information such as an I/O request rate, disaster recovery support, a geographic location of storage, and a storage service vendor.

In an embodiment, the storage requirement may be provided together with a file write request of the target file. For example, suppose that a user of a file management service is provided with the ability to select requirements for storage. Then, when the user uploads an important file with a high management level, a storage that supports the disaster recovery function may be selected, and accordingly, a storage requirement indicating disaster recovery support may be provided from the user terminal 30 . However, the above example is only for explaining some embodiments of the present invention, and the manner in which the storage requirements are provided may vary according to the embodiments.

In an embodiment, the storage requirement may be determined based on attribute information of the target file. For example, when a storage requirement according to attribute information of a file is set as a file management policy, a storage requirement corresponding to attribute information of the target file may be determined according to the file management policy. As a more specific example, according to the file management policy, when the size of the target file is equal to or greater than a threshold value, the storage requirement may be determined as a “fast I/O request rate”. In this example, the user's perceived response speed can be improved by allowing a large file to be stored in a storage having a high I/O speed. For another example, if the management level of the target file is high, the storage requirement may be determined as "disaster recovery support". As another example, according to the above file management policy, if the owner of the target file is a user using a paid or expensive file management service, the storage requirement is "fast I/O request rate" and/or "disaster recovery" support" can be determined. However, the above examples are for explaining some embodiments of the present invention, and it goes without saying that various file management policies may be set.

In step S106, the storage management device 100 determines the usage code. In more detail, the storage management device 100 determines a corresponding usage code based on at least one element among the properties of the target file and the requirements for storage. For example, the storage management apparatus 100 may determine the usage code by using predetermined mapping information. As another example, when the file attribute and storage requirements correspond to the first code and the second code, respectively, and the usage code is given as a combination of the first code and the second code, the storage management device ( 100) converts the property and storage requirements of the target file into a corresponding code, and may determine the usage code by inquiring the usage code including the converted code. However, the above examples are for explaining some embodiments of the present invention, and the method of determining the usage code may be changed.

In step S108 , the storage management device 100 inquires for a storage profile having a determined usage code from among a plurality of storage profiles.

Meanwhile, when a plurality of storage devices used for the same purpose exist, a plurality of storage profiles may be inquired as a result of the inquiry. Whether a plurality of storage devices exist may be determined by whether different storage identifiers appear in the queried storage profile. In this case, the storage management device 100 may select any one storage profile based on the priority given to the storage profile. In this case, the priority may be a fixed priority given by an administrator or a priority that is automatically changed based on factors such as a storage device usage rate and I/O performance.

In step S110 , the storage management device 100 provides the storage identifier of the inquired storage profile as a response to the file write request. The storage identifier provided in response to the file write request may be recorded in meta information of the target file.

In step S112 , the storage management device 100 generates a command to store the target file in the storage of the inquired storage profile. According to the command, the target file may be stored in the storage indicated by the inquired storage profile.

So far, a file write request processing method according to an embodiment of the present invention has been described with reference to FIG. 7 . Next, a process of processing a file read request according to an embodiment of the present invention will be described with reference to FIG. 8 .

8 is a flowchart illustrating a method of processing a file read request according to an embodiment of the present invention. However, this is only a preferred embodiment for achieving the object of the present invention, and it goes without saying that some steps may be added or deleted as needed. In particular, FIG. 8 illustrates a process in which a file read request is processed after a file write request is processed between the service providing device 200 and the storage management device 100 .

Referring to FIG. 8 , in step S200 , the service providing device 200 provides a file write request of an upload file to the storage management device 100 . According to an embodiment, the service providing device 200 may be implemented as a module inside the storage management device 100 as the service module 106 , but for convenience of understanding, a separate device (eg, see FIG. 3 ) It is assumed that it is explained.

In step S202 , the service providing device 200 receives a storage identifier from the storage management device 100 . As described with reference to FIG. 7 , a usage code may be determined based on an attribute of an upload file and/or a storage requirement, and a storage identifier of the target storage having the usage code may be provided through a profile inquiry.

In step S204, the service providing apparatus 200 inserts a storage identifier into the file meta information of the upload file.

In step S206, the service providing device 200 receives a download request of the uploaded file. For example, the service providing apparatus 200 may receive a download request of an uploaded file from the user terminal 30 .

In step S208, the service providing apparatus 200 obtains the storage identifier by using the file identifier (FILE_ID) of the uploaded file in the file meta information.

In step S210 , the service providing device 200 provides a file read request including the storage identifier to the storage management device 100 . Then, the storage management apparatus 100 generates a command to read a file from the target storage having the storage identifier. In addition, the storage management apparatus 100 provides the read file according to the generated command to the service providing apparatus 200 .

Up to now, a process in which a file read request is processed after a file write request is processed according to an embodiment of the present invention has been described with reference to FIG. 8 . Next, an exemplary computing device that can be used to implement the storage management device 100 will be described with reference to FIG. 9 .

9 is a hardware configuration diagram of an exemplary computing device 300 capable of implementing the storage management device 100 according to an embodiment of the present invention.

Referring to FIG. 9 , the computing device 300 includes one or more processors 301 , a bus 305 , a network interface 307 , and a memory 303 for loading a computer program executed by the processor 301 . and a storage 309 for storing software 309a for providing a file management service using a plurality of storage devices. However, only the components related to the embodiment of the present invention are illustrated in FIG. 9 . Accordingly, a person skilled in the art to which the present invention pertains can know that other general-purpose components other than the components shown in FIG. 9 may be further included.

The processor 301 controls the overall operation of each component of the storage management apparatus 100 . The processor 301 includes a central processing unit (CPU), a micro processor unit (MPU), a micro controller unit (MCU), a graphic processing unit (GPU), or any type of processor well known in the art. can be In addition, the processor 301 may perform an operation on at least one application or program for executing the method according to the embodiments of the present invention. The storage management apparatus 100 may include one or more processors.

The memory 303 stores various data, commands and/or information. The memory 303 may load one or more programs 309a from the storage 309 to execute the method of providing a file management service using a plurality of storage devices according to embodiments of the present invention. A RAM is shown as an example of a memory 303 in FIG. 9 .

The bus 305 provides a communication function between components of the storage management device 100 . The bus 305 may be implemented as various types of buses, such as an address bus, a data bus, and a control bus.

The network interface 307 supports wired/wireless Internet communication of the storage management device 100 . Also, the network interface 307 may support various communication methods other than Internet communication. To this end, the network interface 307 may be configured to include a communication module well-known in the art.

The storage 309 may non-temporarily store the one or more programs 309a. In FIG. 9 , a file management service providing software 309a using a plurality of storage devices is illustrated as an example of the one or more programs 309a.

The storage 309 is a non-volatile memory such as a read only memory (ROM), an erasable programmable ROM (EPROM), an electrically erasable programmable ROM (EEPROM), a flash memory, a hard disk, a removable disk, or well in the art to which the present invention pertains. It may be configured to include any known computer-readable recording medium.

The file management service providing software 309a may be loaded into the memory 303 and include an operation for causing the processor 301 to execute the file management service providing method according to an embodiment of the present invention.

For example, the file management service providing software 309a provides an operation for receiving a file write request for the first file, and a usage code corresponding to an attribute of the first file among a plurality of storage profiles managed by the storage management device. It may include an operation of inquiring a storage profile having , and an operation of generating a command to store the first file in a storage device indicated by the inquired storage profile.

So far, an exemplary computing device 300 capable of implementing the storage management device 100 according to an embodiment of the present invention has been described with reference to FIG. 9 .

The concepts of the present invention described with reference to FIGS. 1 to 9 may be implemented as computer-readable codes on a computer-readable medium. The computer-readable recording medium may be, for example, a removable recording medium (CD, DVD, Blu-ray disk, USB storage device, removable hard disk) or a fixed recording medium (ROM, RAM, computer-equipped hard disk). can The computer program recorded on the computer-readable recording medium may be transmitted to another computing device through a network such as the Internet and installed in the other computing device, thereby being used in the other computing device.

Although acts are shown in a particular order in the drawings, it should not be understood that the acts must be performed in the specific order or sequential order shown, or that all illustrated acts must be performed to obtain a desired result. In certain circumstances, multitasking and parallel processing may be advantageous. Moreover, the separation of the various components in the embodiments described above should not be construed as necessarily requiring such separation, and the described program components and systems may generally be integrated together into a single software product or packaged into multiple software products. It should be understood that there is

Although embodiments of the present invention have been described above with reference to the accompanying drawings, those of ordinary skill in the art to which the present invention pertains can realize that the present invention can be embodied in other specific forms without changing its technical spirit or essential features. can understand Therefore, it should be understood that the embodiments described above are illustrative in all respects and not restrictive.

Claims (10)

A method performed by a storage management device that provides read/write services for a plurality of storage devices, the method comprising:
receiving a file write request for the first file;
inquiring a storage profile corresponding to the attribute of the first file among a plurality of storage profiles managed by the storage management device; and
and allowing the first file to be stored in a storage device pointed to by the inquired storage profile,
Inquiring the storage profile comprises:
obtaining a requirement for storage to which the first file is to be written;
determining an attribute of the first file and a usage code corresponding to a storage requirement in which the first file is to be recorded; and
Including the step of inquiring the storage profile having the determined usage code,
A method of providing a file management service using a plurality of storage devices. According to claim 1,
Further comprising the step of providing a storage identifier included in the inquired storage profile in response to the file write request,
A method of providing a file management service using a plurality of storage devices. According to claim 1,
The method further comprising: storing the storage identifier included in the inquired storage profile together with the identifier of the first file in file meta information managed by the storage management device;
A method of providing a file management service using a plurality of storage devices. A method performed by a storage management device that provides read/write services for a plurality of storage devices, the method comprising:
receiving a file write request for the first file;
inquiring a storage profile corresponding to the attribute of the first file among a plurality of storage profiles managed by the storage management device;
storing the first file in a storage device indicated by the inquired storage profile; and
receiving a file read request including the identifier of the first file from the storage management service using device, and in response i) obtaining a storage identifier in which the first file is stored from the file meta information using the identifier of the first file; ii) retrieving a storage profile having the obtained storage identifier among a plurality of storage profiles managed by the storage management device, and iii) generating a command to read the first file from the storage device pointed to by the inquired storage profile and iv) performing an operation of providing the read first file to the storage management service using device,
A method of providing a file management service using a plurality of storage devices. According to claim 1,
The step of obtaining a requirement for storage in which the first file is to be recorded includes:
Comprising the step of receiving information indicating a storage requirement in which the first file is to be recorded, along with the file write request,
A method of providing a file management service using a plurality of storage devices. According to claim 1,
The properties of the first file are,
Information indicating at least a part of the extension of the first file, the owner of the first file, the size of the first file, and the management level of the first file,
A method of providing a file management service using a plurality of storage devices. According to claim 1,
The requirements for the storage in which the first file is to be recorded are,
information that points to at least some of the I/O demand rates, disaster recovery support, the geographic location of the storage, and storage service vendors;
A method of providing a file management service using a plurality of storage devices. According to claim 1,
The step of obtaining a requirement for storage in which the first file is to be recorded includes:
Determining a requirement for storage in which the first file is to be recorded based on an attribute of the first file,
A method of providing a file management service using a plurality of storage devices. According to claim 1,
The steps to inquire the storage profile are:
In the case where there are a plurality of inquired storage profiles and at least some of them have different storage identifiers, inquiring one storage profile based on the priority given to the storage profile;
A method of providing a file management service using a plurality of storage devices. A method performed by a storage management device that provides read/write services for a plurality of storage devices, the method comprising:
receiving a file write request for the first file;
inquiring a storage profile corresponding to the attribute of the first file among a plurality of storage profiles managed by the storage management device;
storing the first file in a storage device indicated by the inquired storage profile; and
Comprising the step of providing a user interface supporting an editing function for at least a part of the plurality of storage profiles,
A method of providing a file management service using a plurality of storage devices.

Images