CN102024044A - Distributed file system - Google Patents
Distributed file system Download PDFInfo
- Publication number
- CN102024044A CN102024044A CN2010105872357A CN201010587235A CN102024044A CN 102024044 A CN102024044 A CN 102024044A CN 2010105872357 A CN2010105872357 A CN 2010105872357A CN 201010587235 A CN201010587235 A CN 201010587235A CN 102024044 A CN102024044 A CN 102024044A
- Authority
- CN
- China
- Prior art keywords
- data
- metadata
- storage system
- module
- backup
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Granted
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/10—File systems; File servers
- G06F16/18—File system types
- G06F16/182—Distributed file systems
Abstract
The embodiment of the invention provides a distributed file system comprising an access module, a metadata management unit, a main storage system, a backup storage system and an external storage system, wherein the access module, the metadata management unit, the main storage system and the backup storage system are connected through system buses; and the external storage system is connected with the main storage system and the backup storage system through networks. In the distributed file system, the data are written into the main storage system and backed up into the backup storage system through an asynchronous backup machine without influencing the read and write performance of the high-speed equipment; and on-line data recovery can be realized, data recovery is automatically realized in the process of external service, and the recovery process is quickened.
Description
Technical field
The embodiment of the invention relates to the data backup technology, relates in particular to a kind of distributed file system.
Background technology
Along with the internet develops to wider direction, all trades and professions are used more and more, and particularly Streaming Media is used, content delivery network (Content Delivery Network; Hereinafter to be referred as: Content supply server performance and reliability CDN) are more and more important, and the core document system of carrying these application datas requires also more and more higher to Performance And Reliability.
For reliability, prior art mainly adopts raid-array (Redundant Arrayof Independent Disk; Hereinafter to be referred as: RAID) technology uses the redundancy backup characteristic to guarantee.Briefly, RAID be a kind of polylith independently hard disk (physical hard disk) combine by different modes and form a hard disk groups (logic hard disk), thereby provide than the higher memory property of single hard disk and the data backup technology be provided.And for performance, prior art adopts the storage striping of distributed file system to manage the polymerization hard disk bandwidth that superposes usually.Described band turns to a kind of management function, and its effect is that data are dispersed on a plurality of memory devices by a fixed step size, and making walks abreast when reading obtains from a plurality of physical storage devices, realizes the stack of many physical storage devices performance.The data redundancy of RAID technology and data striping characteristic have guaranteed the high reliability and the high-performance of distributed file system.
In general, distributed file system is appreciated that and becomes to be based upon on the network store system.Under constantly increase form of high performance demands, the trend development that hard disk is replaced by solid state hard disc gradually because solid-state disk is very expensive, adopts the RAID technology of solid state hard disc backup solid state hard disc to cause server cost expense to increase severely this moment.The RAID technology often adopts RAID1 and RAID5 to realize.Wherein, RAID1 is the 1st a grade of RAID technology, adopts a kind of complete mirror back-up, needs the storage system of two homogeneities to carry out read-write operation synchronously, mirror image each other, even a disk failures is arranged, system still can operate as normal.RAID5 is the storage solution that a kind of memory property, data security and carrying cost are taken into account, the data to storage do not back up, but data and corresponding parity information are stored on each disk of forming RAID5, and parity information is stored in respectively on the different disks with corresponding data.After the data in magnetic disk of RAID5 is damaged, utilize remaining data and corresponding parity information to go to recover impaired data.
In realizing process of the present invention, the inventor finds that there are the following problems at least in the prior art: in the CDN network, use the RAID technology to have following shortcoming: equal capacity, form RAID and need more disk, particularly RAID1 needs double disk, and solid-state disk is very expensive, thereby carrying cost causes system cost too high; The modification of any data of RAID5 need rewrite verification, and it is slow slightly to cause writing data, and data are of a specified duration release time, may influence business; And, the be damaged restriction of quantity of disk of the recovery of data backup.
Summary of the invention
The embodiment of the invention provides a kind of distributed file system, comprise: access module, the metadata management unit that is connected with described access module, and main storage system and the accumulator backup system used that is connected with described metadata management unit respectively, described access module also is connected with described accumulator backup system with storage system with described master respectively; Described access module, described metadata management unit, described main with connecting by system bus between storage system and the described accumulator backup system; Also comprise external storage system, described external storage system is connected with described accumulator backup system with storage system with described master by network; Wherein:
Described access module, be used to receive the read/write data request, send the data metadata corresponding that metadata request is asked to obtain to described metadata management unit, and use described metadata and read and write data with storage system or described accumulator backup system to described master;
Described metadata management unit is used for when the described metadata of described access module request, search the data of being asked described master with the position on storage system or the described accumulator backup system, and construct described metadata, return to described access module; Described master uses storage system, is used for providing the data of being asked for described access module when described distributed file system is in normal condition; Described accumulator backup system is used for when described distributed file system is in abnormality or returns to form, for described master provides data backup with storage system; Described external storage system is used to described master to provide data backup with storage system.
In the distributed file system that the embodiment of the invention provides, main by writing data into in the storage system, adopt async backup mechanism to backup to accumulator backup system, do not influence the readwrite performance of high-speed equipment; And can be implemented in the line restore data, and realize the data recovery in the external service process of data automatically, accelerate rejuvenation.
Description of drawings
In order to be illustrated more clearly in the embodiment of the invention or technical scheme of the prior art, to do one to the accompanying drawing of required use in embodiment or the description of the Prior Art below introduces simply, apparently, accompanying drawing in describing below is some embodiments of the present invention, for those of ordinary skills, under the prerequisite of not paying creative work, can also obtain other accompanying drawing according to these accompanying drawings.
Fig. 1 forms synoptic diagram for one embodiment of the invention distributed file system;
Fig. 2 forms synoptic diagram for another embodiment of the present invention distributed file system;
Fig. 3 is embodiment of the invention distributed file system treatment scheme synoptic diagram under normal condition;
Fig. 4 is that embodiment of the invention distributed file system is under abnormality and be the treatment scheme synoptic diagram under the read data request situation;
Fig. 5 is that embodiment of the invention distributed file system is under abnormality and be the treatment scheme synoptic diagram under the write data requests situation;
Fig. 6 is returning to form response readings according to the processing of request schematic flow sheet for embodiment of the invention distributed file system;
Fig. 7 embodiment of the invention distributed file system is at the treatment scheme synoptic diagram of response write data requests down that returns to form;
Fig. 8 is the treatment scheme synoptic diagram of embodiment of the invention distributed file system data recovery procedure under the system recovery state.
Embodiment
For the purpose, technical scheme and the advantage that make the embodiment of the invention clearer, below in conjunction with the accompanying drawing in the embodiment of the invention, technical scheme in the embodiment of the invention is clearly and completely described, obviously, described embodiment is the present invention's part embodiment, rather than whole embodiment.Based on the embodiment among the present invention, those of ordinary skills belong to the scope of protection of the invention not making the every other embodiment that is obtained under the creative work prerequisite.
Fig. 1 forms synoptic diagram for one embodiment of the invention distributed file system, as shown in Figure 1, this distributed file system 1 comprises access module 11, the metadata management unit 12 that is connected with access module 11, and main storage system 13 and the accumulator backup system 14 used that is connected with metadata management unit 12 respectively, access module 11 also is connected with accumulator backup system 14 with storage system 13 with main respectively; Wherein, access module 11, metadata management unit 12, master all are arranged in internal network with storage system 13 and accumulator backup system 14, connect by system bus between each functional module; This distributed file system 1 also comprises the external storage system 15 that is arranged in external network, external storage system 15 by main with storage system 13 and accumulator backup system 14 networks be connected.
Normal condition refers to that the memory device of leading with storage system 13 does not break down, and data storage can backup on the accumulator backup system 14 on leading with storage system whenever necessary.
Abnormality refers to that the master has memory device to break down with storage system 13, needs main storage system 13, accumulator backup system 14 co-operation used this moment, and data storage is finished in coordination, and preserves and coordinate the result, coordinates the result and is used for data recovery procedure.
Return to form, refer to main recovered failed storage equipment with storage system 13 after, triggering system is carried out the system data recovery, mainly uses the Backup Data on the accumulator backup system 14 to return to the data that are stored in originally on the failed storage equipment.
Further, metadata management unit 12 is responsible for when access module 11 request metadata, search data on storage system the position and construct metadata, return to access module 11.Metadata management unit 12 also is in charge of system state, and it receives main with storage system 13 equipment state incidents, according to event information, and converting system state, selection storage system, determination data memory device (position); Also be responsible for the reliability of system, it is according to data access information, automatically backup data.When equipment failure, according to main DATA DISTRIBUTION situation, form available metadata automatically with, standby, external storage system, guarantee the availability of system; And responsible system data automatic on-line recovers, and guarantees the availability and the data consistency of data.Data Management Unit 12 can be deployed in separately on the server.
Main with storage system 13, be used under described normal condition, providing the data of being asked for access module 11.Particularly, main is main storages of distributed file system 1 with storage system 13, be used for all data of saved system, with high readwrite performance is purpose, use under system's normal condition mainly to read and write data and total data all is kept at and mainly is made up of high speed storing equipment with on the storage system 13, use and store striping technical support memory bandwidth polymerization raising readwrite performance with storage system 13, the block access mode is provided, and access module 11 can be with the data of block mode direct read storage on it.
Above-mentioned internal network is to connect access module 11, metadata management unit 12, main with the direct-connected network of storage system 13 and accumulator backup system 14, can be that Ethernet also can be internal bus (as the PCIe bus).Metadata mainly is the information of data of description attribute, being used for supporting as indication memory location, historical information, resource information and file logging etc., for example can be the memory address (can be to comprise memory device number, storage block number, data-bias) of the data (length of request and skew) of the request of preserving.Metadata also can be the inode number of data.The index node of data is kept in the memory device, and the memory address of identification data.According to the inode number of data, can calculate the memory address of index node.
Fig. 2 forms synoptic diagram for another embodiment of the present invention distributed file system, based on the foregoing description, as shown in Figure 2, this distributed file system 1 comprises access module 11, metadata management unit 12, main with storage system 13 and accumulator backup system 14 and external storage system 15.Further, metadata management unit 12 comprises metadata operation module, backup module and abnormal restoring module; Wherein:
Described metadata operation module, respectively with access module 11, main be connected with storage system 13, be used to receive described metadata request, return described metadata to leading with storage system 13 or abnormal restoring module request metadata and to access module 11; Also be used for upgrading described system state according to the main equipment state incident that reports with storage system 13 that receives; Also be responsible for the condition managing of system, write down the data control information in the described read/write data request.Particularly, described metadata operation module receives all metadata request of access module 11, at first retrieve its metadata cache, if do not find metadata, then need to main with storage system 13 or accumulator backup system 14 request metadata, buffer memory obtains metadata, returns metadata at last and gives access module 11.
Under normal condition, the retrieval metadata cache if do not have, is then noted the data control information in the metadata request that receives to main with storage system 13 request metadata simultaneously, returns metadata then and gives access module 11.Data control information can record internal memory, also can be persisted to database.In the present embodiment, metadata management unit 12 can comprise a data control information logging modle, is connected between metadata operation module and the backup module, is used for the described data control information of permanent storage.
Under abnormality, the metadata request that the metadata operation module is sent receiver module 11 is transmitted to the abnormal restoring module, is responsible for obtaining metadata information to main with storage system 13, accumulator backup system 14 by the abnormal restoring module.
Returning to form down, the write data process is with the same under the normal condition, and the metadata operation module is to main storage system 13 request metadata of using; Reading data course, request abnormal restoring module is responsible for processing.
The metadata operation module is responsible for condition managing, main is responsible for the reporting equipment state events with storage system 13, when receiving the equipment failure incident, and the record trouble device id, system state is unusual by normally transferring to; When the equipment that receives recovered incident, system state was by transferring recovery unusually to; When recovery operation was finished, after abnormal restoring module circular metadata operation module, system state was transferred to normal by recovery.
Described backup module, be connected with accumulator backup system 13 with described metadata operation module, be used to read the described data control information that described metadata operation module records is got off, generate the data backup control information operation and send to accumulator backup system 14, backup in the accumulator backup system 14 will lead with the data on the storage system 13.Particularly, described backup module is under normal condition, move with background thread, read the data control information that metadata operation module records is for the previous period got off, analyze the data behaviour in service and generate data backup requests according to backup policy, on accumulator backup system 14, send backup operation control information (action type, file destination path then, the source file path), requirement will be led with the assigned address to the slack storage server of the file backup on the storage system.Described backup module can be realized various data backup scenario flexibly in conjunction with backup policy, comprises the full backup scheme, only analyzes data writing operation when analyzing data, in case be to have write data just to need to generate backup request; Comprise the focus backup scenario, an assay readings is according to operating position (read data request number of times, read data frequency), according to the data focus condition in the strategy (can access times, read data frequency) when analyzing data; Comprise backup specific data scheme, can analyze the specific data condition code and generate backup request when analyzing data by tactful specific data condition code; Comprise the backup request information in the data that analyzes, generate backup request according to backup request information.
Described abnormal restoring module; be connected with accumulator backup system 14 with storage system 13 with described metadata operation module, described backup module, master respectively, be used under described abnormality and described returning to form, obtaining described metadata and return to described metadata operation module.Validity unusual, that return to form down and obtain metadata information and safeguard metadata cache that described abnormal restoring module is responsible for, and control is main with storage system 13 data restore operation is to support the master with storage system 13 system availability that breaks down down.
Described abnormal restoring module can comprise following submodule:
First processing sub, be used under described abnormality, for read data request, to lacking the piece detection from buffer memory or from the main metadata that obtains with storage system 13, if detecting described metadata has the disappearance piece, then send the address that solicited message comprises disappearance block message and external storage system 14 to accumulator backup system 14; After accumulator backup system 14 returns described metadata, carry out the heavy bindings of block address, the available metadata of recombinating also sends.Particularly; under abnormality; for read data request; described abnormal restoring module is at first retrieved its metadata cache by first processing sub; if do not find metadata; to main storage system 13 request metadata of using; then metadata is lacked piece (data storage detects its memory device ID on failed storage equipment) and detect, if find to have the disappearance piece; again to accumulator backup system 14 request metadata; solicited message comprises disappearance block message (piece number, data ID, skew) and external storage system 15 addresses; after accumulator backup system 14 returns metadata, carry out the heavy bindings of block address.The heavy bindings of block address refers to the disappearance piece metadata corresponding information on the accumulator backup system 14 is replaced main with the disappearance piece metadata corresponding information on the storage system 13, reassembles into this metadata of available metadata and buffer memory and obtains to accelerate metadata.
Second processing sub is used under described abnormality, for write data requests, only to accumulator backup system 14 request metadata and return to described metadata operation module; Also be used to write down data writing operation, data sync used in the storage system 13 to main with write data operation in data recovery procedure according to record.Particularly; under abnormality; for write data requests; described abnormal restoring module selects accumulator backup system 14 to be the storage target by second processing sub automatically; only to accumulator backup system 14 request metadata and return request results to the metadata operation module; like this; access module 11 can all be write data on the accumulator backup system 14 according to metadata information; the abnormal restoring module also can be noted data writing operation; in the data recovery procedure, can use storage system 13 to data sync to the master according to these records.
Return to form down, the abnormal restoring module is responsible for online data and is recovered, and can carry out data, services and data simultaneously and recover.The abnormal restoring module represents to lack the piece recovery situation by failed storage equipment bitmap bitmap, and in the rejuvenation, the abnormal restoring module is responsible for safeguarding the renewal of bitmap.When detecting the disappearance piece, earlier according to memory device ID, whether the pairing bitmap of correlation data piece recovers again.
The abnormal restoring module can also comprise the 3rd processing sub, be used for returning to form down described, for read data request, to lacking the piece detection from buffer memory or from the main metadata that obtains with storage system 13, if detecting described metadata has the disappearance piece, then send solicited message and comprise the disappearance block message, after accumulator backup system 14 returns metadata to accumulator backup system 14, structural deficiency piece recovery operation information is carried out data for main storage system 13 and is recovered; And the failed storage equipment bitmap of renewal main storage system 13, return described metadata.
Particularly; returning to form down; for read data request; the abnormal restoring module is at first retrieved its metadata cache by the 3rd processing sub; if do not find metadata; then to main storage system 13 request metadata of using; then to lacking the piece detection from buffer memory or the main metadata that obtains with storage system 13; if find to have the disappearance piece; again to accumulator backup system 14 request metadata; transmit disappearance block message (piece number; data ID, skew), after accumulator backup system 14 returns metadata; construct the main storage system 13 disappearance piece recovery operation information of using, the main storage system 13 of using is according to this information or to accumulator backup system 14 or to external storage system 15 restore data.After the recovery, upgrade failed storage equipment bitmap bitmap, return metadata.
The abnormal restoring module can also comprise that manages submodule everywhere; be used for returning to form down described; for write data requests; to main storage system 13 request metadata of using; after obtaining described metadata; if detecting described metadata has the disappearance piece, then upgrade the failed storage equipment bitmap of main storage system 13, return described metadata.Particularly; returning to form down; for write data requests; the abnormal restoring module by the manage everywhere submodule to main with storage system 13 request metadata; after obtaining metadata; detect the disappearance piece with the failed storage device id,, return request results then to the metadata operation module if the disappearance piece is arranged then directly upgrade failed storage equipment bitmap bitmap.
Returning to form down, the abnormal restoring module starts a backstage and recovers thread.Recover the type of thread, select rejuvenation according to restorer.If memory device is not is not read and write fault (may be to turn back to again after the memory device hot plug), only need be saved in the master to the data of between anomalistic period, writing accumulator backup system and use storage system, and delete the heavily metadata cache of binding.
If memory device read-write fault; the main data of traversal with storage system; its rejuvenation is as follows: the abnormal restoring module is at first retrieved its metadata cache; if find metadata cache; whether will check has data at accumulator backup system; if data are arranged accumulator backup system (metadata cache of heavily binding is just arranged), then structure is main with storage disappearance piece recovery operation information, main storage system according to this information to the backup storage system restore data.After the recovery, delete the metadata cache of heavily binding and upgrade failed storage equipment bitmap bitmap.
If do not find metadata at metadata cache, then to the main storage system request metadata of using, then detect lacking piece from the main metadata that obtains with storage system, if find to have the disappearance piece, again to the accumulator backup system request metadata, solicited message comprises disappearance block message (piece number, data ID, skew), but do not comprise the exterior storage address, after accumulator backup system returned metadata, structure was main with storage system disappearance piece recovery operation information, and main storage system is according to this information or to backup storage system or to the external storage system restore data.After the recovery, upgrade failed storage equipment bitmap bitmap.
It is main with after the data of storage system in traversal that thread is recovered on the backstage; also travel through data writing operation under abnormal restoring module records between anomalistic period; the data that responsible handle writes on accumulator backup system are saved in mainly uses storage system, upgrades failed storage equipment bitmap bitmap then and deletes metadata cache.
As shown in Figure 2, can also comprise the main data management module of using in this distributed file system, be connected main using between storage system 13 and the metadata management unit 12, be used to manage main data of being stored, response element request of data and data operation request with storage system 13.Particularly, main be responsible for the response element request of data with data management module, also be responsible for receiving recovery operation information and realize that also data recover, recovery operation information has two classes, a kind of have an accumulator backup system address information, and a kind of have an external storage system address information.The main data management module of using is according to recovery operation information, perhaps to accumulator backup system or external storage system recover data blocks.
Can also comprise the preliminary data administration module in this distributed file system, be connected between 12 yuan of accumulator backup system 14 and the metadata management lists, be used to manage the data that accumulator backup system 14 is stored, response element request of data and data operation request.Particularly, the preliminary data administration module is responsible for the response element request of data, also is responsible for receiving backup request and realizing data backup.Metadata request has two classes, the first kind has the exterior storage address information, second class does not have the external storage system address, the preliminary data administration module to the difference of this two classes metadata request is: if retrieve less than metadata at accumulator backup system 14, can and store to external storage system 15 all data of request when then handling the first kind, return the metadata after the storage.When accumulator backup system 14 is handled backup request,, directly also preserve with storage system 13 request msgs to main according to backup request.
In the above-mentioned distributed file system, the master comprises several high speed storing equipment with storage system, and described high speed storing equipment includes but not limited to SCSI hard disk, SATA hard disk, the SSD of high data transmission rate.Main with the also responsible monitoring self of storage system storage device status, and reporting equipment incident (as equipment failure, equipment recovers).The said equipment fault comprises memory device read-write fault, hot plug storage equipment.Accumulator backup system comprises several high speed storing equipment and/or low speed storage device, and wherein, high speed storing equipment includes but not limited to SCSI hard disk, SATA hard disk, the SSD of high data transmission rate; Low speed storage device includes but not limited to the memory device of low data transmission rate.
Recovery operation information described in the foregoing description has two classes, a kind of have an accumulator backup system address information, and a kind of have an external storage system address information.The main data management module of using is according to recovery operation information, perhaps to accumulator backup system or external storage system recover data blocks.That is to say, the recovery operation information that the accumulator backup system address information is arranged, the main recovery operation information that the external storage system address information is arranged from the accumulator backup system recover data blocks with data management module, the master is returning to form down from the external storage system recover data blocks with data management module, during read data, will construct top recovery operation information, like this, the data that the read data service not only were provided but also recovered to be visited at once, principle of locality according to data, the data of the just most of users' concerns of the data of visit recently, these data of priority restores help improving performance.
About the exterior storage address: under abnormality, during read data, need be to the accumulator backup system request metadata, this comprises the exterior storage address, when this wishes metadata that accumulator backup system itself do not have to be asked, accumulator backup system returns metadata more earlier from external storage system request msg (being equivalent to all data are backuped to accumulator backup system from external storage system).Like this, not only guarantee the read data service but also data are backuped to the accumulator backup system from external storage system, and can be from accumulator backup system when recovering restore data, thereby expedited data recovers.Returning to form down, during read data or back-end data when recovering thread, may be to the accumulator backup system request metadata, this is not comprise the exterior storage address, like this, if accumulator backup system itself does not have the metadata of being asked, accumulator backup system can be to outside storage memory system request msg, and accumulator backup system returns sky.Then main with storage system use exterior storage address, to external storage system request msg (the only request disappearance data that piece comprised only need be recovered to lack the data that piece comprises when data are recovered).
The distributed file system that the embodiment of the invention provides writes data into main using in the storage system, adopts async backup mechanism to backup to accumulator backup system, does not influence the readwrite performance of high-speed equipment; Can online restore data, realize automatically in the external service process of data that data recover, accelerate rejuvenation; And do not need during restore data to calculate, even not backup of data still can recover by exterior storage; Under the CDN environment, usage policy Backup Data mechanism is obtained with available exterior storage does not have backed up data, can realize the partial data backup and does not influence availability; In addition, can form accumulator backup system, reduce cost of products with cheap memory device.
Fig. 3 is embodiment of the invention distributed file system treatment scheme synoptic diagram under normal condition, and as shown in Figure 3, this flow process comprises:
Step 3, preliminary data administration module receive the backup control request (action type, file destination path, source file path) that backup management module sends, and according to backup control request information, send backup request to main with data management module;
Step 4, master receive backup request with data management module, to the main memory device reading of data of using in the storage system;
Step 6, preliminary data administration module are write data on the memory device in the accumulator backup system;
Fig. 4 be embodiment of the invention distributed file system under abnormality and be the treatment scheme synoptic diagram under the read data request situation, as shown in Figure 4, this flow process comprises:
Step 3, metadata operation module are transmitted to the abnormal restoring module reading metadata request;
Step 4, abnormal restoring module turned to for the 6th step earlier in metadata information cache lookup metadata if find;
Whether step 6, abnormal restoring module check have the disappearance piece to exist from metadata cache or the main metadata information that returns with storage system, have then and initiate metadata request and be with a last external backup control information (to comprise the external storage system position to accumulator backup system, Data Position information), then do not return metadata information to the metadata operation module, and turned to for the 9th step;
If these data of step 7 have backed up at accumulator backup system, then the preliminary data administration module returns metadata, otherwise the preliminary data administration module to the external storage system request msg, at accumulator backup system, and returns metadata information to the gained data storage according to the external backup control information;
Fig. 5 be embodiment of the invention distributed file system under abnormality and be the treatment scheme synoptic diagram under the write data requests situation, as shown in Figure 5, this flow process comprises:
Step 3, metadata operation module are transmitted to the abnormal restoring module reading metadata request;
Step 4, abnormal restoring module are directly initiated metadata request to accumulator backup system;
Step 6, abnormal restoring module are returned metadata information and are given the metadata operation module;
Response readings is according to the processing of request schematic flow sheet under returning to form for embodiment of the invention distributed file system for Fig. 6, and as shown in Figure 6, this flow process comprises:
Step 3, metadata operation module are transmitted to the abnormal restoring module reading metadata request;
Step 4, abnormal restoring module retrieval metadata cache if do not find, are then used the storage system request metadata to main, jump to for the 6th step if find;
Whether step 6, abnormal restoring module check lack piece, if having then to the accumulator backup system request metadata, if do not have, then jump to for the 11st step;
The metadata that step 7, abnormal restoring module are returned according to accumulator backup system, structure are recovered control information and are issued the main storage system of using;
Fig. 7 embodiment of the invention distributed file system is at the treatment scheme synoptic diagram of response write data requests down that returns to form, and as shown in Figure 7, this flow process comprises:
Step 3, metadata operation module are transmitted to the abnormal restoring module reading metadata request;
Step 4, abnormal restoring module are to the main storage system request metadata of using;
Whether step 6, abnormal restoring module check lack piece, if having, then upgrade the disappearance piece bitmap bitmap that has recovered, and the pairing bitmap of disappearance piece is set to 1;
Fig. 8 is the treatment scheme synoptic diagram of embodiment of the invention distributed file system data recovery procedure under the system recovery state, and as shown in Figure 8, this flow process comprises:
If step 2 finds metadata cache, whether back-end data is recovered the thread inspection has data on accumulator backup system, if do not have data on accumulator backup system, jumps to for the 11st step;
If step 3 has data on accumulator backup system, back-end data is recovered the thread constructing master and is lacked piece recovery operation information and issue the main storage system of using with storage;
Step 4, main receiving with storage system lack piece recovery operation information and execution, with the accumulator backup system data
To the disappearance piece, return disappearance piece recovery operation result;
If step 6 does not find metadata at metadata cache, then back-end data is recovered thread to the main storage system request metadata of using;
If step 8 has the disappearance piece, back-end data is recovered thread request to the accumulator backup system restore data;
If the 8th step of step 9 backs up successfully, then jumped to for the 11st step;
If the 8th step of step 10 backup failure, then back-end data is recovered thread request to the external storage system restore data;
One of ordinary skill in the art will appreciate that: all or part of step that realizes said method embodiment can be finished by the relevant hardware of programmed instruction, aforesaid program can be stored in the computer read/write memory medium, this program is carried out the step that comprises said method embodiment when carrying out; And aforesaid storage medium comprises: various media that can be program code stored such as ROM, RAM, magnetic disc or CD.
It should be noted that at last: above embodiment only in order to technical scheme of the present invention to be described, is not intended to limit; Although with reference to previous embodiment the present invention is had been described in detail, those of ordinary skill in the art is to be understood that: it still can be made amendment to the technical scheme that aforementioned each embodiment put down in writing, and perhaps part technical characterictic wherein is equal to replacement; And these modifications or replacement do not make the essence of appropriate technical solution break away from the spirit and scope of various embodiments of the present invention technical scheme.
Claims (7)
1. distributed file system, it is characterized in that, comprise: access module, the metadata management unit that is connected with described access module, and main storage system and the accumulator backup system used that is connected with described metadata management unit respectively, described access module also is connected with described accumulator backup system with storage system with described master respectively; Described access module, described metadata management unit, described main with connecting by system bus between storage system and the described accumulator backup system; Also comprise external storage system, described external storage system is connected with described accumulator backup system with storage system with described master by network; Wherein:
Described access module, be used to receive the read/write data request, send the data metadata corresponding that metadata request is asked to obtain to described metadata management unit, and use described metadata and read and write data with storage system or described accumulator backup system to described master;
Described metadata management unit is used for when the described metadata of described access module request, search the data of being asked described master with the position on storage system or the described accumulator backup system, and construct described metadata, return to described access module; Described master uses storage system, is used for providing the data of being asked for described access module when described distributed file system is in normal condition; Described accumulator backup system is used for when described distributed file system is in abnormality or returns to form, for described master provides data backup with storage system; Described external storage system is used to described master to provide data backup with storage system.
2. distributed file system according to claim 1 is characterized in that, described metadata management unit comprises: metadata operation module, backup module and abnormal restoring module; Wherein:
Described metadata operation module, be connected with storage system with described access module, described master respectively, be used to receive described metadata request, return described metadata with storage system or described abnormal restoring module request metadata and to described access module to described master; Also be used for according to the described master who receives upgrading described system state with the equipment state incident that storage system reports; Also be used for writing down the data control information of described read/write data request;
Described backup module, be connected with described accumulator backup system with described metadata operation module, be used to read the described data control information that described metadata operation module records is got off, generate the data backup control information operation and send to described accumulator backup system, so that described master is backuped in the described accumulator backup system with the data on the storage system;
Described abnormal restoring module; be connected with described accumulator backup system with storage system with described metadata operation module, described backup module, described master respectively, be used under described abnormality and described returning to form, obtaining described metadata and return to described metadata operation module.
3. distributed file system according to claim 2 is characterized in that, described metadata management unit also comprises:
The data control information logging modle is connected between described metadata operation module and the described backup module, is used to store described data control information.
4. distributed file system according to claim 2 is characterized in that, described abnormal restoring module comprises:
First processing sub, be used under described abnormality, for read data request, to lacking the piece detection from buffer memory or from the metadata that described master obtains with storage system, if detecting described metadata has the disappearance piece, then send the address that solicited message comprises disappearance block message and described external storage system to described accumulator backup system; After described accumulator backup system returns described metadata, carry out the heavy bindings of block address, the available metadata of recombinating also sends;
Second processing sub is used under described abnormality, for write data requests, only to described accumulator backup system request metadata and return to described metadata operation module; Also be used to write down data writing operation, data sync used in the storage system to described master with write data operation in data recovery procedure according to record;
The 3rd processing sub, be used for returning to form down described, for read data request, to lacking the piece detection from buffer memory or from the metadata that described master obtains with storage system, if detecting described metadata has the disappearance piece, then send solicited message and comprise the disappearance block message, after described accumulator backup system returns metadata to described accumulator backup system, structural deficiency piece recovery operation information is carried out data for described main storage system and is recovered; And upgrade the failed storage equipment bitmap of described main storage system, return described metadata;
The manages submodule everywhere, is used for returning to form down described, for write data requests, after described master uses the storage system request metadata, obtains described metadata, the disappearance piece is arranged if detect described metadata, then upgrade the failed storage equipment bitmap of described main storage system, return described metadata.
5. according to claim 1 or 2 or 3 or 4 described distributed file systems, it is characterized in that, also comprise:
The master uses data management module, is connected described main using between storage system and the described metadata management unit, is used to manage described main data of storing with storage system, response element request of data and data operation request; And
The preliminary data administration module is connected between described accumulator backup system and the described metadata management unit, is used to manage the data that described accumulator backup system is stored, response element request of data and data operation request.
6. distributed file system according to claim 5 is characterized in that, described master comprises several high speed storing equipment with storage system, and described high speed storing equipment includes but not limited to SCSI hard disk, SATA hard disk, the SSD of high data transmission rate;
Described accumulator backup system comprises several high speed storing equipment and/or low speed storage device, and wherein, described high speed storing equipment comprises SCSI hard disk, SATA hard disk, SSD.
7. distributed file system according to claim 1 is characterized in that,
Described normal condition refers to main not break down with storage system;
Described abnormality refers to main break down with storage system, mainly coordinates to finish data storage with storage system and accumulator backup system co-operation, preserves and coordinates the result, and wherein, described coordination result is used for data recovery procedure;
Described returning to form is meant through after the abnormality, uses the data on the accumulator backup system to recover main with the data in the storage system.
Priority Applications (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CN2010105872357A CN102024044B (en) | 2010-12-08 | 2010-12-08 | Distributed file system |
PCT/CN2011/079685 WO2012075845A1 (en) | 2010-12-08 | 2011-09-15 | Distributed file system |
Applications Claiming Priority (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CN2010105872357A CN102024044B (en) | 2010-12-08 | 2010-12-08 | Distributed file system |
Publications (2)
Publication Number | Publication Date |
---|---|
CN102024044A true CN102024044A (en) | 2011-04-20 |
CN102024044B CN102024044B (en) | 2012-11-21 |
Family
ID=43865341
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
CN2010105872357A Active CN102024044B (en) | 2010-12-08 | 2010-12-08 | Distributed file system |
Country Status (2)
Country | Link |
---|---|
CN (1) | CN102024044B (en) |
WO (1) | WO2012075845A1 (en) |
Cited By (25)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
WO2012075845A1 (en) * | 2010-12-08 | 2012-06-14 | 华为技术有限公司 | Distributed file system |
CN102867035A (en) * | 2012-08-28 | 2013-01-09 | 浪潮(北京)电子信息产业有限公司 | High-availability method and device of distributed document system cluster |
CN102890716A (en) * | 2012-09-29 | 2013-01-23 | 南京中兴新软件有限责任公司 | Distributed file system and data backup method thereof |
CN103095767A (en) * | 2011-11-03 | 2013-05-08 | 中兴通讯股份有限公司 | Distributed cache system and data reconfiguration method based on distributed cache system |
CN103167026A (en) * | 2013-02-06 | 2013-06-19 | 数码辰星科技发展(北京)有限公司 | Processing method, system and device for cloud storage environmental data |
CN103207894A (en) * | 2013-03-14 | 2013-07-17 | 深圳市知正科技有限公司 | Multipath real-time video data storage system and cache control method thereof |
CN103220162A (en) * | 2012-01-19 | 2013-07-24 | 百度在线网络技术(北京)有限公司 | Small computer system interface (SCSI) fault-tolerant optimization method and device based on hadoop distributed file system (HDFS) |
CN103347086A (en) * | 2013-07-11 | 2013-10-09 | 南京大学 | Synergy kernel construction method based on distributed type negotiation algorithm |
CN103473184A (en) * | 2013-08-01 | 2013-12-25 | 记忆科技(深圳)有限公司 | Caching method and system for file system |
CN103513629A (en) * | 2012-06-14 | 2014-01-15 | 英国德尔格安全有限公司 | A telemetry monitoring system and a data recovery method for a telemetry monitoring system |
CN103516736A (en) * | 2012-06-20 | 2014-01-15 | 中兴通讯股份有限公司 | Data recovery method of distributed cache system and a data recovery device of distributed cache system |
WO2014089981A1 (en) * | 2012-12-14 | 2014-06-19 | 华为技术有限公司 | Data processing method and storing system for applied metadata |
CN104135539A (en) * | 2014-08-15 | 2014-11-05 | 华为技术有限公司 | Data storage method, SDN controller and distributed network storage system |
WO2015015502A1 (en) * | 2013-07-29 | 2015-02-05 | Hewlett-Packard Development Company, L.P. | Writing to files and file meta-data |
CN104657392A (en) * | 2013-11-25 | 2015-05-27 | 腾讯科技(深圳)有限公司 | Method and device for realizing retrieve abnormity reducing |
WO2016029744A1 (en) * | 2014-08-27 | 2016-03-03 | 华为技术有限公司 | Metadata recovery method and relevant device |
CN105915600A (en) * | 2016-04-13 | 2016-08-31 | 乐视控股(北京)有限公司 | Data writing-in method based CDN network system and CDN network system thereof |
CN103902349B (en) * | 2012-12-27 | 2017-05-31 | 中国移动通信集团江西有限公司 | A kind of virtual platform storage managing server and its management method |
CN108108422A (en) * | 2017-12-15 | 2018-06-01 | 郑州云海信息技术有限公司 | A kind of metadata acquisition methods, device and the medium of Ceph file system |
CN108388604A (en) * | 2018-02-06 | 2018-08-10 | 平安科技(深圳)有限公司 | User right data administrator, method and computer readable storage medium |
CN109327539A (en) * | 2018-11-15 | 2019-02-12 | 上海天玑数据技术有限公司 | A kind of distributed block storage system and its data routing method |
WO2019148841A1 (en) * | 2018-01-31 | 2019-08-08 | 华为技术有限公司 | Distributed storage system, data processing method and storage node |
CN110659157A (en) * | 2019-08-30 | 2020-01-07 | 安徽芃睿科技有限公司 | Distributed multi-language retrieval platform and method for lossless recovery |
CN111026432A (en) * | 2019-12-06 | 2020-04-17 | 中国建设银行股份有限公司 | Big data processing platform, platform construction method and storage medium |
CN112532525A (en) * | 2020-11-25 | 2021-03-19 | 北京金山云网络技术有限公司 | Processing method, device and system for equipment recovery service |
Citations (7)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20030115433A1 (en) * | 2001-12-14 | 2003-06-19 | Hitachi Ltd. | Remote storage system and method |
US20050216788A1 (en) * | 2002-11-20 | 2005-09-29 | Filesx Ltd. | Fast backup storage and fast recovery of data (FBSRD) |
CN1955939A (en) * | 2006-10-13 | 2007-05-02 | 清华大学 | Backup and recovery method based on virtual flash disk |
CN101394424A (en) * | 2008-10-27 | 2009-03-25 | 中国科学院计算技术研究所 | Hard disc stage network data backup system and method |
CN101408855A (en) * | 2008-11-07 | 2009-04-15 | 北京威视数据系统有限公司 | Method for protecting remote backup equipment of temporary abnormal by continuous data protective system |
CN101436149A (en) * | 2008-12-19 | 2009-05-20 | 华中科技大学 | Method for rebuilding data of magnetic disk array |
CN101436151A (en) * | 2008-12-01 | 2009-05-20 | 成都索贝数码科技股份有限公司 | Data real time backup method and system based on file system |
Family Cites Families (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
EP1256225B1 (en) * | 2000-02-04 | 2010-08-18 | Listen.Com, Inc. | System for distributed media network and meta data server |
CN101539873B (en) * | 2009-04-15 | 2011-02-09 | 成都市华为赛门铁克科技有限公司 | Data recovery method, data node and distributed file system |
CN102024044B (en) * | 2010-12-08 | 2012-11-21 | 华为技术有限公司 | Distributed file system |
-
2010
- 2010-12-08 CN CN2010105872357A patent/CN102024044B/en active Active
-
2011
- 2011-09-15 WO PCT/CN2011/079685 patent/WO2012075845A1/en active Application Filing
Patent Citations (7)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20030115433A1 (en) * | 2001-12-14 | 2003-06-19 | Hitachi Ltd. | Remote storage system and method |
US20050216788A1 (en) * | 2002-11-20 | 2005-09-29 | Filesx Ltd. | Fast backup storage and fast recovery of data (FBSRD) |
CN1955939A (en) * | 2006-10-13 | 2007-05-02 | 清华大学 | Backup and recovery method based on virtual flash disk |
CN101394424A (en) * | 2008-10-27 | 2009-03-25 | 中国科学院计算技术研究所 | Hard disc stage network data backup system and method |
CN101408855A (en) * | 2008-11-07 | 2009-04-15 | 北京威视数据系统有限公司 | Method for protecting remote backup equipment of temporary abnormal by continuous data protective system |
CN101436151A (en) * | 2008-12-01 | 2009-05-20 | 成都索贝数码科技股份有限公司 | Data real time backup method and system based on file system |
CN101436149A (en) * | 2008-12-19 | 2009-05-20 | 华中科技大学 | Method for rebuilding data of magnetic disk array |
Cited By (39)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
WO2012075845A1 (en) * | 2010-12-08 | 2012-06-14 | 华为技术有限公司 | Distributed file system |
CN103095767A (en) * | 2011-11-03 | 2013-05-08 | 中兴通讯股份有限公司 | Distributed cache system and data reconfiguration method based on distributed cache system |
CN103095767B (en) * | 2011-11-03 | 2019-04-23 | 中兴通讯股份有限公司 | Distributed cache system and data reconstruction method based on distributed cache system |
CN103220162A (en) * | 2012-01-19 | 2013-07-24 | 百度在线网络技术(北京)有限公司 | Small computer system interface (SCSI) fault-tolerant optimization method and device based on hadoop distributed file system (HDFS) |
CN103513629A (en) * | 2012-06-14 | 2014-01-15 | 英国德尔格安全有限公司 | A telemetry monitoring system and a data recovery method for a telemetry monitoring system |
CN103513629B (en) * | 2012-06-14 | 2017-07-14 | 英国德尔格安全有限公司 | Telemonitoring system and the data reconstruction method for telemonitoring system |
CN103516736A (en) * | 2012-06-20 | 2014-01-15 | 中兴通讯股份有限公司 | Data recovery method of distributed cache system and a data recovery device of distributed cache system |
CN102867035A (en) * | 2012-08-28 | 2013-01-09 | 浪潮(北京)电子信息产业有限公司 | High-availability method and device of distributed document system cluster |
CN102890716A (en) * | 2012-09-29 | 2013-01-23 | 南京中兴新软件有限责任公司 | Distributed file system and data backup method thereof |
CN102890716B (en) * | 2012-09-29 | 2017-08-08 | 南京中兴新软件有限责任公司 | The data back up method of distributed file system and distributed file system |
WO2014089981A1 (en) * | 2012-12-14 | 2014-06-19 | 华为技术有限公司 | Data processing method and storing system for applied metadata |
CN103902349B (en) * | 2012-12-27 | 2017-05-31 | 中国移动通信集团江西有限公司 | A kind of virtual platform storage managing server and its management method |
CN103167026A (en) * | 2013-02-06 | 2013-06-19 | 数码辰星科技发展(北京)有限公司 | Processing method, system and device for cloud storage environmental data |
CN103167026B (en) * | 2013-02-06 | 2016-05-18 | 数码辰星科技发展(北京)有限公司 | A kind of cloud store environmental data processing method, system and equipment |
CN103207894A (en) * | 2013-03-14 | 2013-07-17 | 深圳市知正科技有限公司 | Multipath real-time video data storage system and cache control method thereof |
CN103347086B (en) * | 2013-07-11 | 2016-06-29 | 南京大学 | Collaborative kernel construction method based on Distributed Coordination algorithm |
CN103347086A (en) * | 2013-07-11 | 2013-10-09 | 南京大学 | Synergy kernel construction method based on distributed type negotiation algorithm |
WO2015015502A1 (en) * | 2013-07-29 | 2015-02-05 | Hewlett-Packard Development Company, L.P. | Writing to files and file meta-data |
CN103473184B (en) * | 2013-08-01 | 2016-08-10 | 记忆科技(深圳)有限公司 | The caching method of file system and system |
CN103473184A (en) * | 2013-08-01 | 2013-12-25 | 记忆科技(深圳)有限公司 | Caching method and system for file system |
CN104657392B (en) * | 2013-11-25 | 2020-02-11 | 腾讯科技(深圳)有限公司 | Method and device for realizing retrieval abnormity restoration |
CN104657392A (en) * | 2013-11-25 | 2015-05-27 | 腾讯科技(深圳)有限公司 | Method and device for realizing retrieve abnormity reducing |
CN104135539A (en) * | 2014-08-15 | 2014-11-05 | 华为技术有限公司 | Data storage method, SDN controller and distributed network storage system |
CN104135539B (en) * | 2014-08-15 | 2018-03-16 | 华为技术有限公司 | Date storage method, SDN controllers and distributed network storage system |
WO2016023370A1 (en) * | 2014-08-15 | 2016-02-18 | 华为技术有限公司 | Data storage method, sdn controller and distributed network storage system |
US10567506B2 (en) | 2014-08-15 | 2020-02-18 | Huawei Technologies Co., Ltd. | Data storage method, SDN controller, and distributed network storage system |
WO2016029744A1 (en) * | 2014-08-27 | 2016-03-03 | 华为技术有限公司 | Metadata recovery method and relevant device |
CN105915600A (en) * | 2016-04-13 | 2016-08-31 | 乐视控股(北京)有限公司 | Data writing-in method based CDN network system and CDN network system thereof |
CN108108422A (en) * | 2017-12-15 | 2018-06-01 | 郑州云海信息技术有限公司 | A kind of metadata acquisition methods, device and the medium of Ceph file system |
US11262916B2 (en) | 2018-01-31 | 2022-03-01 | Huawei Technologies Co., Ltd. | Distributed storage system, data processing method, and storage node |
WO2019148841A1 (en) * | 2018-01-31 | 2019-08-08 | 华为技术有限公司 | Distributed storage system, data processing method and storage node |
CN108388604A (en) * | 2018-02-06 | 2018-08-10 | 平安科技(深圳)有限公司 | User right data administrator, method and computer readable storage medium |
WO2019153592A1 (en) * | 2018-02-06 | 2019-08-15 | 平安科技(深圳)有限公司 | User authority data management device and method, and computer readable storage medium |
CN108388604B (en) * | 2018-02-06 | 2022-06-10 | 平安科技(深圳)有限公司 | User authority data management apparatus, method and computer readable storage medium |
CN109327539A (en) * | 2018-11-15 | 2019-02-12 | 上海天玑数据技术有限公司 | A kind of distributed block storage system and its data routing method |
CN110659157A (en) * | 2019-08-30 | 2020-01-07 | 安徽芃睿科技有限公司 | Distributed multi-language retrieval platform and method for lossless recovery |
CN111026432A (en) * | 2019-12-06 | 2020-04-17 | 中国建设银行股份有限公司 | Big data processing platform, platform construction method and storage medium |
CN112532525A (en) * | 2020-11-25 | 2021-03-19 | 北京金山云网络技术有限公司 | Processing method, device and system for equipment recovery service |
CN112532525B (en) * | 2020-11-25 | 2022-11-25 | 北京金山云网络技术有限公司 | Processing method, device and system for equipment recovery service |
Also Published As
Publication number | Publication date |
---|---|
WO2012075845A1 (en) | 2012-06-14 |
CN102024044B (en) | 2012-11-21 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
CN102024044B (en) | Distributed file system | |
CN103136074B (en) | Data storage method and data storage system of multiple disk array systems | |
CN101571815B (en) | Information system and i/o processing method | |
CN100407121C (en) | Information processing system, primary storage device, and computer readable recording medium recorded thereon logical volume restoring program | |
US7904647B2 (en) | System for optimizing the performance and reliability of a storage controller cache offload circuit | |
US8438332B2 (en) | Apparatus and method to maintain write operation atomicity where a data transfer operation crosses a data storage medium track boundary | |
US9946655B2 (en) | Storage system and storage control method | |
CN101755257B (en) | Managing the copying of writes from primary storages to secondary storages across different networks | |
CN100524235C (en) | Recovery operations in storage networks | |
EP2879040B1 (en) | Data storage method, data storage apparatus, and storage device | |
US20090150629A1 (en) | Storage management device, storage system control device, storage medium storing storage management program, and storage system | |
US9823955B2 (en) | Storage system which is capable of processing file access requests and block access requests, and which can manage failures in A and storage system failure management method having a cluster configuration | |
CN103763383A (en) | Integrated cloud storage system and storage method thereof | |
CN105183581A (en) | Database disaster tolerance system | |
US7984260B2 (en) | Storage system provided with a plurality of controller modules | |
US20060190682A1 (en) | Storage system, method for processing, and program | |
CN103942112A (en) | Magnetic disk fault-tolerance method, device and system | |
CN103037004A (en) | Implement method and device of cloud storage system operation | |
CN103534688A (en) | Data recovery method, storage equipment and storage system | |
KR20200113047A (en) | Operation method of open-channel storage device | |
CN102177496A (en) | System and method for transferring data between different RAID data storage types for current data and replay data | |
CN104424052A (en) | Automatic redundant distributed storage system and method | |
US10642508B2 (en) | Method to limit impact of partial media failure of disk drive and detect/report the loss of data for objects due to partial failure of media | |
CN101390059A (en) | Apparatus for concurrent raid array relocation | |
US20030188102A1 (en) | Disk subsystem |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
C06 | Publication | ||
PB01 | Publication | ||
C10 | Entry into substantive examination | ||
SE01 | Entry into force of request for substantive examination | ||
C14 | Grant of patent or utility model | ||
GR01 | Patent grant | ||
TR01 | Transfer of patent right |
Effective date of registration: 20210423 Address after: Unit 3401, unit a, building 6, Shenye Zhongcheng, No. 8089, Hongli West Road, Donghai community, Xiangmihu street, Futian District, Shenzhen, Guangdong 518040 Patentee after: Honor Device Co.,Ltd. Address before: 518129 Bantian HUAWEI headquarters office building, Longgang District, Guangdong, Shenzhen Patentee before: HUAWEI TECHNOLOGIES Co.,Ltd. |
|
TR01 | Transfer of patent right |