CN108279850B - Data resource storage method - Google Patents
Data resource storage method Download PDFInfo
- Publication number
- CN108279850B CN108279850B CN201710009416.3A CN201710009416A CN108279850B CN 108279850 B CN108279850 B CN 108279850B CN 201710009416 A CN201710009416 A CN 201710009416A CN 108279850 B CN108279850 B CN 108279850B
- Authority
- CN
- China
- Prior art keywords
- resource
- application
- data
- client
- server
- 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.)
- Expired - Fee Related
Links
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/0671—In-line storage system
-
- 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/0602—Interfaces specially adapted for storage systems specifically adapted to achieve a particular effect
- G06F3/0604—Improving or facilitating administration, e.g. storage management
-
- 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/0628—Interfaces specially adapted for storage systems making use of a particular technique
- G06F3/0629—Configuration or reconfiguration of storage systems
- G06F3/0631—Configuration or reconfiguration of storage systems by allocating resources to storage systems
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 application discloses a data resource storage method, which comprises the following steps: the resource providing devices are used for providing storage space, and when the application of the resource using device needs to store data, the application can apply for the storage space on the resource providing device for data storage from the server; after the server applies for resources from the resource providing equipment successfully, the application stores the data on certain resource providing equipment. Through the application, data storage can be conveniently realized.
Description
Technical Field
The present application relates to storage technologies, and in particular, to a method for storing data resources.
Background
Currently, in the field of computer and communication technology, the following situations occur in the implementation process of various items:
one situation is that the capacity of the server hard disk is configured according to the maximum requirement when a user configures the capacity of the server hard disk. However, such a peak usage scenario is often not achieved in reality. Under the condition, not only is the loss brought to the early investment of the user, but also the cost is increased in the subsequent operation and maintenance, such as the electric power cost of a machine room, the maintenance and depreciation cost of a large number of disks and the like;
the other situation is that the situation of future application growth is not fully considered in the early planning, so that the later storage resources are in short supply;
there is also a case where physical spaces such as machine room cabinets are already fully allocated, and there is no excess space to expand storage resources.
The above practical situations not only bring economic waste to users, but also greatly increase the operation and maintenance difficulty, and even may cause serious consequences such as system termination.
Disclosure of Invention
The application provides a data resource storage method which can conveniently realize data storage on the premise of not wasting physical storage resources.
In order to achieve the purpose, the following technical scheme is adopted in the application:
a storage method of data resources comprises the following steps:
a. the application on the resource using equipment requests a hardware resource sharing server for data storage through a client software client connected with the resource using equipment;
b. the server pre-allocates hardware resources of one resource providing device for the application according to the available resource conditions of all the current resource providing devices, and sends a pre-allocation result to an agent software agent connected with the corresponding resource providing device;
c. the agent judges whether to accept the corresponding pre-allocation result according to the received pre-allocation result and the current load condition of the resource providing equipment connected with the agent, and feeds the judgment result back to the server;
d. when the judgment result is acceptance, the server informs the application to store data on the appointed resource of the pre-distributed resource providing equipment through the client, and the application stores the data on the appointed resource of the pre-distributed resource providing equipment and informs the client and the server; after receiving the notification, the client and the server respectively establish a resource list corresponding to the application, and add the pre-allocated resource providing equipment and the specified resource information into the resource list corresponding to the application; when the judgment result is not accepted, re-executing the steps b, c and d;
wherein the specified resource is a hardware resource allocated to the application to store data.
Preferably, the method comprises: and when the judgment result is that the user name, the password and the access path of the specified resource are received, the agent allocates the user name, the password and the access path of the specified resource, sends the user name, the password and the access path to the server, and forwards the user name, the password and the access path to the application through the client.
Preferably, after the resource list corresponding to the application is established, the method further includes: the server selects N resource providing devices according to a backup strategy, is used for backing up the data of the application, and backs up the data of the application to the selected N resource providing devices; after the backup is completed, adding the information of the successfully backed-up resource providing device and the storage resource thereof into the resource list corresponding to the application, and informing the client to add the information of the successfully backed-up resource providing device and the storage resource thereof into the resource list corresponding to the application stored by the client;
and N is the redundancy number set by the user, and the storage resource is a hardware resource used for storing the data of the application.
Preferably, when the application needs to read the stored data, the method further comprises:
the application sends a data reading request to the client, the client selects a resource providing device for storing the application data according to a resource list corresponding to the application stored by the client, and feeds back information of the selected resource providing device and the storage resource thereof to the application, the application accesses the selected resource providing device for data reading according to the received information, and feeds back a reading result to the client.
Preferably, the selecting a resource providing device storing the application data includes: and selecting a resource providing device with the shortest access path from the resource list corresponding to the application stored by the client.
Preferably, when the read result fed back to the client by the application is a read failure, the method further includes:
the client reselects a resource providing device from the resource list corresponding to the application stored in the client, feeds back the information of the reselected resource providing device to the application, and deletes the resource providing device with read failure from the resource list corresponding to the application stored in the client; the application accesses the reselected resource providing equipment to read data according to the received information and feeds back a reading result to the client; and when the application successfully reads the data, the client sends the information of the resource providing equipment with the reading failure to the server, the server updates a resource list corresponding to the application stored by the server, selects new resource providing equipment to add into the resource list corresponding to the application, performs data backup, updates the resource list corresponding to the application stored by the server after the backup is completed, and notifies the client to update the resource list stored by the client.
Preferably, for any resource providing device in the system, the method further comprises: any resource providing device prestores self configuration information, monitors the access of resource using devices to self resources according to the configuration information, and informs the server when abnormity occurs; the resource providing equipment monitors the resource load condition of the resource providing equipment according to the configuration information, gradually releases the data resource of the backup attribute when the resource load is abnormal, releases all shared resources if the resource load is still abnormal after the data resource of the backup attribute is released, informs the server, and closes the resource sharing service; the any resource providing equipment monitors the connection service according to the configuration information, and if the connection service is abnormal, the connection is reestablished, and the resource information is updated;
wherein the configuration information comprises at least one of: the resource load calculation method comprises a maximum resource sharing threshold, a maximum connection number, a maximum resource load value, a maximum input/output (IO) load value, a resource load weight and an IO load weight.
Preferably, for any resource providing device in the system, the method further comprises: the agent connected with any resource providing device acquires the IO load and the disk space load of any resource providing device, calculates a load value and reports the load value to the server;
the selecting of the N resource providing devices according to the backup policy includes: the server selects N resource providing devices according to the load values reported by the agents;
for each resource providing device in the resource list corresponding to the application, the method further includes: the server detects the load of the resource providing equipment which has distributed the resource storage, and if the load is abnormal, the backup strategy under the abnormal condition comprises the following steps: the server reselects a resource providing device with normal load to replace the resource providing device with abnormal load, backups corresponding data to the reselected resource providing device from the resource providing device with normal load for storing the same data according to the data stored by the resource providing device with abnormal load, updates the self-stored resource list, and informs the client of the resource using device to which the corresponding data belongs to update the resource list.
Preferably, the backing up the data of the application to the selected N resource providing devices by the server includes:
and the server copies the data of the application to other resource providing equipment which does not finish backup from the pre-distributed resource providing equipment or the resource providing equipment which finishes backup.
Preferably, the agent calculating the load value comprises: the load value is disk IO weight IO load + disk space weight disk space load;
the selecting of the N resource providing devices includes: the N resource providing devices with the lowest load are selected.
According to the technical scheme, the resource providing devices are used for providing the storage space, and when the application of the resource using device needs to store data, the application can apply the storage space on the resource providing device for data storage to the server; after the server applies for resources from the resource providing equipment successfully, the application stores the data on certain resource providing equipment. By the above manner, the application on the resource using device may not store data locally on the resource using device, and may store data on other resource providing devices. Therefore, on one hand, the resource using equipment does not need to be configured with overlarge hard disk resources in early investment, and the data storage requirement of the application on the resource using equipment can still be ensured.
Drawings
FIG. 1 is a schematic diagram of a network architecture of a basic storage system according to the present application;
FIG. 2 is a schematic diagram of a basic flow of a data resource storage method according to the present application;
FIG. 3 is a diagram illustrating a resource application process according to an embodiment;
FIG. 4 is a diagram illustrating a resource backup process according to a second embodiment;
FIG. 5 is a diagram illustrating a data access flow according to a third embodiment;
FIG. 6 is a diagram illustrating a data access flow according to a fourth embodiment;
FIG. 7 is an exemplary diagram of a resource list in the present application;
fig. 8 is an exemplary diagram of a resource usage interface in the present application.
Detailed Description
For the purpose of making the objects, technical means and advantages of the present application more apparent, the present application will be described in further detail with reference to the accompanying drawings.
The basic idea of the application is as follows: a plurality of idle hard disk resources are integrated into a sharable resource pool, and the utilization rate of storage resources is improved.
On the basis of the basic idea, the following requirements can be preferably considered to be fulfilled for better data storage and management:
1) the self requirement of the resource providing equipment is not influenced, and when the self requirement is influenced, the shared resource can be automatically released;
2) data on the resource using equipment can be backed up to a plurality of resource providing equipment through a redundancy backup mechanism so as to ensure that the resource using of the resource using equipment is safe and reliable;
3) ensuring high efficiency of resource access of resource using equipment through a resource allocation strategy;
4) the shared resource access to the resource providing equipment is ensured to be safe and reliable through user authority management;
6) the system design is hardware independent.
The basic storage system network architecture of the present application includes: the system comprises an application program on the resource using device, Client software (Client), a hardware resource sharing Server (Server), Agent software (Agent) and a hard disk resource on the resource providing device. The whole resource platform adopts a Client/Server/Agent three-level mode, is flexible to use and low in coupling. A schematic diagram of a system network architecture is shown in fig. 1. The following describes each component of the system architecture.
Application on resource-using device: as a resource borrower, the application program calls an interface provided by the Client to establish connection with the resource sharing platform, so that the functions of application, release and the like of the storage resources are realized.
Client: the Client module is deployed at the same position as the resource using equipment, and is in butt joint with the resource using equipment on one hand and the resource platform Server module on the other hand, so that the transparent transmission function of instructions such as resource application, resource release and the like of a resource borrower is completed.
Server: the core control center serving as the resource sharing platform is responsible for integrating relevant resources such as resource using equipment and resource providing equipment. The reasonable, efficient, stable and reliable operation of the system is ensured by methods such as a resource load algorithm, a resource backup strategy and a resource allocation strategy.
Agent: the Agent module is deployed at the same location as the resource provider. And the system is responsible for the functions of resource calculation, resource protection, resource sharing, resource release and the like of the resource provider.
Hard disk resources on the resource providing device: the hard disk stores resources.
Fig. 2 is a schematic basic flow chart of a data resource storage method in the present application. As shown in fig. 1 and 2, the basic flow includes:
wherein the designated resource is a hardware resource allocated to the application to store data.
So far, the most basic data resource storage method flow in the application is finished. The above flow corresponds to the application process of the storage resource. Besides the application for the storage resources, the system structure can be used for accessing the storage data, backing up the storage data, monitoring the state of the resource providing equipment and the like. Next, the above-described flow is explained in detail by several specific examples.
The first embodiment is as follows:
fig. 3 is a schematic diagram of a resource application process according to a first embodiment. As shown in fig. 3, the process specifically includes:
step 301, establishing connection among the resource using device, the Client, the Server and the Agent.
Step 302, the resource using device sends a request for applying for resource to the Client, and the Client transparently transmits the request to the Server.
Step 303, the Server selects a resource providing device to pre-allocate resources, and sends a resource request message to the Agent connected to the selected resource providing device after pre-allocating resources.
Wherein pre-allocating resources comprises: the Server selects one resource providing device among the resource providing devices providing the hardware resource sharing. The selected resource providing device should be able to meet the data storage requirements of the application.
Step 304, the Agent receives the resource request message, calculates the sharable storage resource of the resource providing device connected with the Agent, if agreeing to pre-allocation, allocates the storage resource (hereinafter referred to as the designated resource), allocates the user name, the password and the access path of the designated resource, and returns the relevant information to the Server, and executes step 306; if the allocation is not approved, the Server is notified of the failure of the pre-allocation, step 305 is performed.
In step 305, the Server receives the resource information returned by the Agent, and re-executes step 303 and 304.
And step 306, the Server receives the resource information returned by the Agent, forwards the resource information to the Client, and forwards the resource information to the application on the resource using equipment.
Step 307, after receiving the resource information, the application on the resource using device uploads the data file to the specified resource of the resource providing device in an FTP manner.
And 308, after the resource using equipment uploads the file, sending a file transmission completion notification to the Client, and then transmitting the Client to the Server.
Step 309, after the Server and the Client receive the notification of the completion of the file transmission, establishing a resource list corresponding to the application, and adding the successfully stored resource using device and the specified resource information thereof into the resource list corresponding to the application.
And ending the specific process of the resource application.
Example two:
the embodiment is used for explaining a backup storage mode of application data on the resource utilization device, so as to ensure the storage security of the application data. Fig. 4 is a schematic diagram of a resource backup process in the second embodiment, and preferably, the process is started after the Server receives a file transfer complete message sent by the resource using device. As shown in fig. 4, the process specifically includes:
step 401, the Server selects N resource providing devices for backing up the data of the application according to the backup policy, and backs up the data of the application to the selected N resource providing devices.
Where N may be the number of redundancies set by the user. Preferably, each agent connected to the resource providing device collects IO loads and disk space loads of the corresponding resource providing device, calculates a load value, and reports the load value to the Server. The way to calculate the load may be: the load is disk IO weight IO load value + disk space weight disk space load value, and the disk IO weight and the disk space weight may be preset as needed. The Server can select N resource providing devices for backing up data according to the load values reported by the agents. Specifically, the N resource providing devices with the lowest load may be selected for data backup.
In addition, when backing up application data, data transmitted by the application on the resource using device can be copied from the storage resource of the resource providing device to other resource providing devices selected according to the backup policy. Alternatively, the data transmitted by the application on the resource using device may be copied from the resource providing device that has already completed backup to the resource providing device that has not completed backup, for example, from device a to backup device B, from backup device B to backup device C, from backup device C to backup device D, and so on.
Step 402, after the backup is completed, the Server adds the information of the successfully backed-up resource providing device and the storage resource thereof into the resource list corresponding to the application.
The storage resource is a hardware resource used for storing corresponding application data. And after the resource list corresponding to the application stored in the Server is updated, the resource list comprises all the information of the resource providing equipment and the storage resource for storing the application data.
Step 403, the Server notifies the client to add the information of the successfully backed up resource providing device and the storage resource thereof into the resource list corresponding to the application stored by the client.
The resource list saved by the client is updated as well as the resource list saved in the Server, so that the information of all the resource providing devices and the storage resources storing the corresponding application data can be included.
The backup processing process is a backup strategy flow under normal conditions. If the Server determines that a certain resource providing device is abnormal according to information such as load of the resource providing device reported by the agent or information of abnormal working of the resource providing device fed back by the application of the resource using device, a backup strategy flow under the abnormal condition needs to be executed, which specifically comprises the following steps:
and after judging that a certain resource providing device is abnormal according to the received information, the Server reselects the resource providing device for replacing the abnormal resource providing device. The Server executes a backup strategy, backups the application data stored on the normal resource providing equipment storing the same application data to the newly added resource providing equipment, updates the resource list corresponding to the application stored by the Server and informs the Client of synchronously updating the resource list corresponding to the application. The Client updates the resource list.
Example three:
this embodiment is used to explain the access of an application on a resource using device to stored data on a resource providing device. Fig. 5 is a schematic diagram of a data access process in the third embodiment, and preferably, the process is started after the Server completes storage and backup of application data on the resource providing device, and the Server and the client complete updating the resource list. As shown in fig. 5, the process specifically includes:
step 501, establishing connection among the application, the Client, the Server and the Agent on the resource using equipment.
Step 502, the application on the resource using device sends a read resource request to the Client.
Step 503, after receiving the resource reading request, the Client reads the resource list, and selects a suitable resource providing device from the resource list.
Preferably, a resource providing apparatus having the shortest access path may be selected.
In step 504, the Client returns the access information of the selected resource providing device to the application on the resource using device.
The information fed back is used to access the application data stored on the resource providing device, and may specifically include a user name, a password, an access path of the storage resource, and the like. Here, data of a plurality of different applications may be stored on one resource providing device, and these applications may belong to the same resource using device or may belong to different resource using devices, so that this step returns access information of the storage resource related to the request.
And 505, the application on the resource using device reads the data from the resource providing device and informs the Client of the reading result. If the resource access is successful, the process is ended. If the resource access fails, step 406 is performed.
Step 506, after receiving the access failure information, the Client reselects a resource providing device from the resource list, returns the information of the resource providing device to the application on the resource using device, and deletes the previous access failure resource providing device from the resource list.
In step 507, the application on the resource using device reads the file from the newly allocated resource providing device, and informs the Client of the result, if the access is successful, step 408 is executed, otherwise, step 406 is returned.
And step 508, after receiving the information of successful reading, the Client sends the information of the resource providing equipment with failed access to the Server.
In step 509, the Server deletes the failed resource providing device and the storage resource information thereof from the resource list corresponding to the application, selects a new resource providing device to add into the corresponding resource list, and executes the backup policy.
Here a backup strategy is performed, i.e. storing application data on the newly selected resource providing device.
And step 510, the Server executes a complete share strategy, updates a resource list corresponding to the application, and sends the resource list information to the Client.
Step 511, after receiving the information, the Client updates the resource list, and adds the newly added resource providing device and the storage resource information thereof into the resource list.
Example four:
this embodiment is used to explain the self-protection procedure of the resource providing device. Fig. 6 is a schematic diagram of a data access flow in the fourth embodiment. As shown in fig. 6, the process specifically includes:
step 601, the resource providing device starts and configures the relevant information.
Wherein the related information may include: a maximum resource sharing threshold, a maximum number of connections, a maximum resource load value, a maximum IO load value, a resource load weight, an IO load weight, and the like.
Step 602, a service for monitoring the status of application data is executed.
In particular, it may be determined whether the data is accessed by a third party and, if so, the monitoring service may continue to be performed. And if the data is abnormal, informing the Server of data abnormal information.
Step 603, executing a service for monitoring the condition of the resource providing device itself.
Wherein, the specific monitoring service specifically comprises: on one hand, the resource connection condition is judged, if the resource connection condition is normal, the monitoring is continued, and if the resource connection condition is abnormal, the resource use application is subsequently refused; on the other hand, the resource load condition is judged, if the resource load condition is normal, the monitoring is continued, if the resource load condition is abnormal, the data resource with the backup attribute is gradually released, and the resource load condition is judged again. If the load continues to exceed the standard, releasing all shared resources, informing the Server to update the resource list, and closing the resource sharing service.
Step 604, executing the status connection judgment service, judging the connection status, continuing to monitor if the connection status is normal, reestablishing the connection if the connection status is abnormal, and updating the resource information.
The foregoing is a specific implementation of the resource storage method in the present application. An example of a resource list is given next, which, as shown in fig. 7, comprises the following components:
1. index key: application name of resource using device as index, field length 30
2. Time stamping: time when the application of the resource using device has uploaded the file, field length 30
3. Resource-using device IP address: resource using device IP Address, field Length 20
4. Resource file name: resource File name, field Length 100
5. Resource file size: resource File Length, field Length 20
6. Resource providing device IP address: resource providing device IP Address, field Length 20
7. User name: user name of FTP access path with field length of 30
8. Password: cipher of FTP access path with field length of 100
FTP path: shared resource FTP access path with field length of 10
10. Priority: resource providing device priority, field length 10
11. And (3) fault marking: resource providing device failure pricing, field length 5
12. Load weight: resource providing device load weight, field length 10
The resource usage interface gives an example as shown in fig. 8. Which comprises the following steps:
connect (): the application on the resource using device is connected to the resource platform Client module.
Disconnect (): and the application on the resource using equipment disconnects the connection with the Client module of the resource platform.
BookResource (): the application on the resource using device applies for using the resource. And the resource platform returns resource information.
ReleaseResource (): the application on the resource-using device releases the resource.
SetFlag (): and the application on the resource using equipment informs the resource platform of the resource using condition.
Write (): an application on the resource-using device writes the data file.
Read (): an application on the resource-using device reads the data file.
Remove (): the application on the resource-using device deletes the data file.
Of course, the specific resource usage interface may not be limited to the interface manner provided above.
By the resource storage method provided by the application, the defect that the peak demand is met by high-allocation physical storage in the traditional project implementation is overcome. The existing idle storage resources are utilized to solve the problem that some storage requirements are insufficient. And a Client/Server/Agent three-level software architecture mode is adopted, so that the coupling is low. The priority of the idle resources is calculated by utilizing the load, the file backup is carried out by utilizing the load and the redundancy granularity, and meanwhile, the resource providing equipment can be automatically protected, so that the application program of the resource providing equipment is not influenced. The fixed investment and the operation and maintenance cost of the user are greatly reduced, and the aims of energy conservation and environmental protection are further fulfilled. The method is transparent to the resource providing equipment, cannot generate any influence and is convenient to apply. For the application on the resource utilization equipment, the coupling is low, and only a few simple interfaces need to be called. The safety and the reliability of the use of the user are ensured through various strategy designs. The writing of the data file is write-once, so that the use frequency of long connection is reduced, and the data access efficiency is improved. Independent of hardware equipment, no additional hardware cost is needed.
The above description is only for the purpose of illustrating the preferred embodiments of the present invention and is not to be construed as limiting the invention, and any modifications, equivalents, improvements and the like made within the spirit and principle of the present invention should be included in the scope of the present invention.
Claims (9)
1. A method for storing data resources is characterized by comprising the following steps:
a. the application on the resource using equipment requests a hardware resource sharing server for data storage through a client software client connected with the resource using equipment;
b. the server pre-allocates hardware resources of one resource providing device for the application according to the available resource conditions of all the current resource providing devices, and sends a pre-allocation result to an agent software agent connected with the corresponding resource providing device;
c. the agent judges whether to accept the corresponding pre-allocation result according to the received pre-allocation result and the current load condition of the resource providing equipment connected with the agent, and feeds the judgment result back to the server;
d. when the judgment result is acceptance, the server informs the application to store data on the appointed resource of the pre-distributed resource providing equipment through the client, and the application stores the data on the appointed resource of the pre-distributed resource providing equipment and informs the client and the server; after receiving the notification, the client and the server respectively establish a resource list corresponding to the application, and add the information of the pre-allocated resource providing equipment and the specified resource into the resource list corresponding to the application; when the judgment result is not accepted, re-executing the steps b, c and d;
wherein the designated resource is a hardware resource allocated to the application to store data;
for any resource providing device in the system, the method further comprises: any resource providing device prestores self configuration information, monitors the access of resource using devices to self resources according to the configuration information, and informs the server when abnormity occurs; any resource providing device monitors the self resource load condition according to the configuration information, gradually releases the data resource of the backup attribute when the resource providing device is abnormal, releases all shared resources if the resource load is still abnormal after the data resource of the backup attribute is released, notifies the server, and closes the resource sharing service; the any resource providing equipment monitors the connection service according to the configuration information, and if the connection service is abnormal, the connection is reestablished, and the resource information is updated; wherein the configuration information comprises at least one of: the resource load calculation method comprises a maximum resource sharing threshold, a maximum connection number, a maximum resource load value, a maximum input/output (IO) load value, a resource load weight and an IO load weight.
2. The method of claim 1, characterized in that the method comprises: and when the judgment result is that the user name, the password and the access path of the specified resource are received, the agent allocates the user name, the password and the access path of the specified resource, sends the user name, the password and the access path to the server, and forwards the user name, the password and the access path to the application through the client.
3. The method of claim 1, wherein after the establishing of the resource list corresponding to the application is completed, the method further comprises: the server selects N resource providing devices according to a backup strategy, is used for backing up the data of the application, and backs up the data of the application to the selected N resource providing devices; after the backup is completed, adding the information of the successfully backed-up resource providing device and the storage resource thereof into the resource list corresponding to the application, and informing the client to add the information of the successfully backed-up resource providing device and the storage resource thereof into the resource list corresponding to the application stored by the client;
and N is the redundancy number set by the user, and the storage resource is a hardware resource used for storing the data of the application.
4. A method according to claim 1 or 3, wherein when the application needs to read the stored data, the method further comprises:
the application sends a data reading request to the client, the client selects a resource providing device for storing the application data according to a resource list corresponding to the application stored by the client, and feeds back information of the selected resource providing device and the storage resource thereof to the application, the application accesses the selected resource providing device for data reading according to the received information, and feeds back a reading result to the client.
5. The method of claim 4, wherein selecting a resource providing device that stores the application data comprises: and selecting a resource providing device with the shortest access path from the resource list corresponding to the application stored by the client.
6. The method of claim 4, wherein when the read result fed back to the client by the application is a read failure, the method further comprises:
the client reselects a resource providing device from the resource list corresponding to the application stored in the client, feeds back the information of the reselected resource providing device to the application, and deletes the resource providing device with read failure from the resource list corresponding to the application stored in the client; the application accesses the reselected resource providing equipment to read data according to the received information and feeds back a reading result to the client; and when the application successfully reads the data, the client sends the information of the resource providing equipment with the reading failure to the server, the server updates a resource list corresponding to the application stored by the server, selects new resource providing equipment to add into the resource list corresponding to the application, performs data backup, updates the resource list corresponding to the application stored by the server after the backup is completed, and notifies the client to update the resource list stored by the client.
7. The method of claim 3, wherein for any resource providing device in the system, the method further comprises: the agent connected with any resource providing device acquires the IO load and the disk space load of any resource providing device, calculates a load value and reports the load value to the server;
the selecting of the N resource providing devices according to the backup policy includes: the server selects N resource providing devices according to the load values reported by the agents;
for each resource providing device in the resource list corresponding to the application, the method further includes: the server detects the load of the resource providing equipment which has distributed the resource storage, and if the load is abnormal, the backup strategy under the abnormal condition comprises the following steps: the server reselects a resource providing device with normal load to replace the resource providing device with abnormal load, backups corresponding data to the reselected resource providing device from the resource providing device with normal load for storing the same data according to the data stored by the resource providing device with abnormal load, updates the self-stored resource list, and informs the client of the resource using device to which the corresponding data belongs to update the resource list.
8. The method according to claim 3, wherein the server backing up the data of the application to the selected N resource providing devices comprises:
and the server copies the data of the application to other resource providing equipment which does not finish backup from the pre-distributed resource providing equipment or the resource providing equipment which finishes backup.
9. The method of claim 7, wherein the agent calculating a load value comprises: the load value is disk IO weight IO load + disk space weight disk space load;
the selecting of the N resource providing devices includes: the N resource providing devices with the lowest load are selected.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201710009416.3A CN108279850B (en) | 2017-01-06 | 2017-01-06 | Data resource storage method |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201710009416.3A CN108279850B (en) | 2017-01-06 | 2017-01-06 | Data resource storage method |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN108279850A CN108279850A (en) | 2018-07-13 |
| CN108279850B true CN108279850B (en) | 2021-05-14 |
Family
ID=62800765
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201710009416.3A Expired - Fee Related CN108279850B (en) | 2017-01-06 | 2017-01-06 | Data resource storage method |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN108279850B (en) |
Families Citing this family (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN111930566A (en) * | 2020-07-28 | 2020-11-13 | 友谊时光科技股份有限公司 | Data backup method and device, electronic equipment and storage medium |
Family Cites Families (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| JP4281658B2 (en) * | 2004-09-24 | 2009-06-17 | 日本電気株式会社 | File access service system, switching device, quota management method and program |
| US20070174429A1 (en) * | 2006-01-24 | 2007-07-26 | Citrix Systems, Inc. | Methods and servers for establishing a connection between a client system and a virtual machine hosting a requested computing environment |
| CN101674332A (en) * | 2009-10-23 | 2010-03-17 | 成都市华为赛门铁克科技有限公司 | Network-based storage space management method and server |
| CN103685055B (en) * | 2013-12-25 | 2017-06-16 | 深圳供电局有限公司 | The transregional isolated data balanced transmission method of power system and transregional isolator |
| CN104767822A (en) * | 2015-04-21 | 2015-07-08 | 成都影泰科技有限公司 | Data storage method based on version |
| CN105389210B (en) * | 2015-10-16 | 2019-07-30 | 浪潮(北京)电子信息产业有限公司 | A kind of memory space management and device |
-
2017
- 2017-01-06 CN CN201710009416.3A patent/CN108279850B/en not_active Expired - Fee Related
Non-Patent Citations (1)
| Title |
|---|
| Design and Implementation of a VBR Continuous Media File Server;Makaroff D 等;《IEEE Xplore》;20011231;全文 * |
Also Published As
| Publication number | Publication date |
|---|---|
| CN108279850A (en) | 2018-07-13 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US11360854B2 (en) | Storage cluster configuration change method, storage cluster, and computer system | |
| CN105025084A (en) | A cloud storage system based on synchronization agents and mixed storage | |
| CN111130835A (en) | Data center dual-active system, switching method, device, equipment and medium | |
| CN104468651B (en) | Distributed more copy data storage methods and device | |
| CN109151045A (en) | A kind of distribution cloud system and monitoring method | |
| WO2019128670A1 (en) | Method and apparatus for enabling self-recovery of management capability in distributed system | |
| CN105760519A (en) | Cluster file system and file lock allocation method thereof | |
| CN103780417A (en) | Database failure transfer method based on cloud hard disk and device thereof | |
| CN104572355A (en) | Asynchronous remote data copying method and device | |
| CN109254876A (en) | The management method and device of database in cloud computing system | |
| CN103428288B (en) | Based on the copies synchronized method of subregion state table and coordinator node | |
| CN104753987B (en) | A kind of distributed conversation management method and system | |
| CN111158949A (en) | Configuration method, switching method and device of disaster recovery architecture, equipment and storage medium | |
| CN113821168A (en) | Shared storage migration system and method, electronic equipment and storage medium | |
| CN105991752A (en) | Data block update method and apparatus | |
| CN113467873A (en) | Virtual machine scheduling method and device, electronic equipment and storage medium | |
| CN115658390A (en) | Container disaster tolerance method, system, device, equipment and computer readable storage medium | |
| CN108352995B (en) | SMB service fault processing method and storage device | |
| CN102541693A (en) | Multi-copy storage management method and system of data | |
| CN105760391A (en) | Data dynamic redistribution method and system, data node and name node | |
| CN108279850B (en) | Data resource storage method | |
| WO2021115043A1 (en) | Distributed database system and data disaster backup drilling method | |
| CN104052799B (en) | A kind of method that High Availabitity storage is realized using resource ring | |
| CN102982033A (en) | Small documents storage method and system thereof | |
| CN104504348B (en) | A kind of data guard method based on high availability storage system |
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 | ||
| CF01 | Termination of patent right due to non-payment of annual fee | ||
| CF01 | Termination of patent right due to non-payment of annual fee |
Granted publication date: 20210514 Termination date: 20220106 |