Nothing Special   »   [go: up one dir, main page]

CN101470645A - High-speed cache data recovery method and apparatus - Google Patents

High-speed cache data recovery method and apparatus Download PDF

Info

Publication number
CN101470645A
CN101470645A CNA2007103083010A CN200710308301A CN101470645A CN 101470645 A CN101470645 A CN 101470645A CN A2007103083010 A CNA2007103083010 A CN A2007103083010A CN 200710308301 A CN200710308301 A CN 200710308301A CN 101470645 A CN101470645 A CN 101470645A
Authority
CN
China
Prior art keywords
file
cache
backup data
files
information
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
Application number
CNA2007103083010A
Other languages
Chinese (zh)
Other versions
CN101470645B (en
Inventor
林霖
李静
姚杰
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Huawei Technologies Co Ltd
Original Assignee
Huawei Technologies Co Ltd
Priority date (The priority date 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 date listed.)
Filing date
Publication date
Application filed by Huawei Technologies Co Ltd filed Critical Huawei Technologies Co Ltd
Priority to CN2007103083010A priority Critical patent/CN101470645B/en
Priority to PCT/CN2008/073656 priority patent/WO2009092254A1/en
Publication of CN101470645A publication Critical patent/CN101470645A/en
Application granted granted Critical
Publication of CN101470645B publication Critical patent/CN101470645B/en
Expired - Fee Related legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Images

Classifications

    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F12/00Accessing, addressing or allocating within memory systems or architectures
    • G06F12/02Addressing or allocation; Relocation
    • G06F12/08Addressing or allocation; Relocation in hierarchically structured memory systems, e.g. virtual memory systems
    • G06F12/0802Addressing of a memory level in which the access to the desired data or data block requires associative addressing means, e.g. caches
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F11/00Error detection; Error correction; Monitoring
    • G06F11/07Responding to the occurrence of a fault, e.g. fault tolerance
    • G06F11/14Error detection or correction of the data by redundancy in operation
    • G06F11/1402Saving, restoring, recovering or retrying
    • G06F11/1415Saving, restoring, recovering or retrying at system level
    • G06F11/1435Saving, restoring, recovering or retrying at system level using file system or storage system metadata

Landscapes

  • Engineering & Computer Science (AREA)
  • Theoretical Computer Science (AREA)
  • Physics & Mathematics (AREA)
  • General Engineering & Computer Science (AREA)
  • General Physics & Mathematics (AREA)
  • Library & Information Science (AREA)
  • Quality & Reliability (AREA)
  • Information Retrieval, Db Structures And Fs Structures Therefor (AREA)

Abstract

The embodiment of the invention discloses a method for recovering high speed cache data, which comprises: reading backup data, wherein the backup data is used to record file information of files, the files in the backup data ,which correspond to the file information are written in high speed cache. The embodiment of the invention further discloses a device for recovering the high speed cache data. The embodiment of the invention recovers the files in the high speed cache through using the backup data which is stored a memory, can recover the files in the high speed cache in a short time, and the hit rate of the high speed cache is rapidly increased.

Description

Method and device for recovering cache data
Technical Field
The present invention relates to the field of computer storage technologies, and in particular, to a method and an apparatus for recovering cache data.
Background
A cache is a block of memory space between a processor and memory that is smaller than the memory, and the processor accesses the cache much faster than the processor accesses the memory.
When the processor receives an access request of a file, the processor firstly accesses the memory and opens and reads the file. Due to the slow access speed of the memory, if the files are stored in the cache, the processing efficiency is greatly improved, and the access time of the files is shortened. The cache capacity of the system is limited and it is not possible to store all files in the cache.
At present, the access frequency of files on a record memory is adopted, and files with frequent partial access are loaded into a cache periodically or aperiodically, and files stored in the cache are updated at the same time, so that the defect of limited cache capacity is solved.
For example, the color ring back tone of the operator or the server device of the customer service bureau point is shown in fig. 1.
Fig. 1 is a block diagram of a color ring back tone or customer service bureau server device of an operator, which includes a manager 101, a file server 102, a plurality of signaling processors 104, a plurality of service processors 106, and a plurality of resource processors 108. Wherein,
the manager 101 is used for maintaining and monitoring files, interacting with a user interface and the like;
the file server 102 is used for storing all files for the resource processor 108 to access and read;
the signaling processor 104 is used for exchanging and processing signaling with other devices;
the service processor 106 is used for providing services;
the resource handler 108 is used for reading and calling files.
Each signaling processor 104, service processor 106 and resource processor 108 in the server device are identified by a number that is independent and unique within the device, and each processor has an internal communication mechanism for information interaction.
FIG. 2 is a block diagram of the resource processor 108. As shown in FIG. 2, the resource handler includes a control module 201, a file call module 202, an IO module 203, and a cache 204.
The control module 201 is configured to receive and process an operation request sent by the manager 101 or other processors, control the relevant modules to complete corresponding operations, and return a response and a result of execution of the operation request to the manager 101 or other processors.
The file calling module 202 is configured to process the file read by the IO module 203 according to the control of the control module 201.
The IO module 203 is configured to complete interaction between the control module 201 and the cache 204 and between the control module 201 and the file server 205, including operations of constructing the cache 204, reading a data file from the cache 204 and the file server 205, and the like.
The cache 204 is used for storing frequently accessed files on the file server, and is used for the IO module 203 to perform fast reading or calling.
For example, in a ring back tone or a customer service bureau of an operator, the ring tone file is typically stored on the file server 205. When the resource processor needs to perform voice playback operation, the control module 201 controls the IO module 203 to access the file server 205, open and read the ring tone file, and then the file calling module 202 performs playback. In order to increase the speed of file access and reading, the resource processor may create a cache 204 in memory, and the resource processor loads frequently used ring tone files into the cache 204 periodically or aperiodically according to the file access frequency, and updates the ring tone files stored in the cache 204. When the file calling module 202 accesses these files loaded in the cache 204, it does not need to access the file server 205, but directly plays the ring tone file in the cache 204. Since the access frequency of the file is variable, the control module 201 needs to eliminate and update the file in the cache 204 according to a certain mechanism, delete the file with the lower access frequency from the cache 204, and store the new file with the higher access frequency in the cache 204.
Since the cache 204 is actually part of the memory, and the access frequency information of the file is also stored in the memory, the cache 204 will lose all the stored data whenever the resource processor is restarted, and the data can only be rebuilt.
There are two ways to establish the data in the cache 204:
first, the resource handler is restarted, and after a period of time, the control module 201 instructs the IO module 203 to select the file accessed on the file server 205 to be loaded into the cache 204 during the period of time. Thereafter, the control module 201 instructs the IO module 203 to evict and update the data in the cache 204 according to a certain mechanism.
Second, the resource handler is restarted, and each time a file on the file server 205 is accessed, the control module 201 instructs the IO module 203 to load the accessed file into the cache 204. After the cache 204 is full, the control module 201 instructs the IO module 203 to evict and update the data in the cache 204 according to a certain mechanism.
In implementing the present invention, the inventors have discovered that the selection of files stored on a cache is important because the space of the cache is much less than the storage space on the file server. Each resource handler in the server device is relatively independent, and for each resource handler, after each reboot, a relatively long and relatively large number of file accesses are required before the files stored in the cache are relatively stable, and the cache hit rate (the number of times a file is read from the cache as a proportion of the total number of times the resource handler accesses files from the file server and the cache) is relatively high.
Taking a color ring office as an example, in a first mode, under the condition that the proportion of the storage space of a cache and a file server is 1:10000, after an exchanger environment is initially constructed, the hit rate of the cache is increased from initial 0% to about 95%, and about 30 days are needed; and by adopting the second mode, the cache hit rate is increased to about 95% in the same condition, which requires about 45 days.
That is, in both the first and second modes, the data in the cache is rebuilt after a long period of time and multiple file accesses, and a longer period of time is needed to keep the cache data relatively stable.
Disclosure of Invention
Embodiments of the present invention provide a method for recovering cached data, which can recover data in a cache when needed.
The embodiment of the invention also provides a device for recovering the cache data, which can quickly recover the data in the cache when needed.
In one aspect, an embodiment of the present invention provides a method for recovering cache data, including,
reading backup data, wherein the backup data is used for recording file information of a file;
and writing the file corresponding to the file information in the backup data into a cache.
In another aspect, an embodiment of the present invention provides an apparatus for recovering cached data, including,
a backup data reading unit for reading backup data for recording file information of a file;
and the file recovery unit is used for writing the files corresponding to the file information in the backup data into a cache.
According to the technical scheme, the method for recovering the cache data can recover the files in the cache in a short time by recovering the files in the cache by using the backup data.
On the other hand, the apparatus for cache data recovery of the present invention can recover the files in the cache in a shorter time by recovering the files in the cache using the backup data.
Drawings
Fig. 1 is a block diagram of an operator's office point server apparatus.
Fig. 2 is a block diagram of a resource handler in a carrier's office point server equipment.
FIG. 3 is a block diagram of a resource processor according to an embodiment of the invention.
Fig. 4 is a flowchart of cache backup according to an embodiment of the present invention.
Fig. 5 is a flowchart of cache reconstruction according to an embodiment of the present invention.
Detailed Description
In order to make the objects, technical solutions and advantages of the present invention more apparent, the present invention is further described in detail below with reference to the accompanying drawings and examples.
The embodiment of the invention can recover the files in the cache in a short time by recovering the files in the cache by using the backup data, so that the data of the cache does not need to be re-created, and the hit rate of the cache is favorably improved in a short time.
Example one
The technical scheme of the embodiment comprises two parts of cache backup and reconstruction.
The backup of the cache refers to exporting and saving the file information of the files in the cache in the backup data.
And the reconstruction of the cache refers to that the resource processor reads the backup data and reconstructs the cache according to the file information in the backup data.
The file information saved in the backup data may be an attribute of the file or a complete file, where the file attribute is a file name of the file and/or a file path that characterizes a storage location of the file on the file server.
The cache backup can be implemented in four ways:
the first way is to store the contents of the cache as a separate file, and only the file attributes of each file stored in the cache, such as the file path and/or file name at the file server, are listed in the file. This approach is suitable for situations where the file path in the file server is not constantly changing.
The second way is to store the cached content as a separate file, where all the files in the cache and their organization structure, i.e. the complete content of the cache, are stored. This approach is applicable to situations where the file path in the file server is not fixed.
A third way is to store the contents of the cache in a directory, where each individual file in the directory or a sub-directory thereof is a complete file stored in the cache.
A fourth way is to store the content in the cache in a directory, where the files in this directory or a sub-directory thereof list the file attributes of each file stored in the cache, such as the file path and/or the file name in the file server, etc.
The embodiment still uses the customer service bureau point device of the operator as an example to describe the implementation manner of the present invention.
FIG. 3 is a diagram illustrating the structure of a resource processor according to the present embodiment.
The resource handler of the present embodiment includes: a control module 301, a file call module 302, an IO module 303, and a cache 304.
The IO module 303 in this embodiment may perform information interaction with not only the file server 305 but also the storage 306.
The memory 306 is used to store files in the cache. The memory 306 may be a storage device separate from the file server, a storage device of the file server, or a storage device inside the resource processor, such as FLASH or RAM.
The cache data recovery apparatus of this embodiment can recover a file in a cache, and mainly includes the following functional units:
a backup data generation unit configured to generate backup data for recording information of the files stored in the cache;
a backup data writing unit for writing the backup data into a memory;
a backup data reading unit for reading backup data for recording file information of the files stored in the cache from the memory;
and the file recovery unit is used for writing the files corresponding to the file information in the backup data into a cache.
The function of the cache data recovery apparatus is performed by the IO module 303 as a preferred embodiment of the present invention, but it should be understood by those skilled in the art that the cache data recovery apparatus may be a separate apparatus or exist in other devices or modules or perform its function by other devices or components.
Fig. 4 is a flowchart of cache backup in this embodiment. As shown in fig. 4, the backup process of the cache includes the following steps.
Step 401: the backup of the cache is started, i.e. a backup request for backing up the cache data is sent to the control module. The backup request can be sent to the control module by the manager through manual starting of a user, or can be sent to the control module by the manager through timing starting.
Step 402: after receiving the backup request, the control module sets the state of the cache as unavailable, so as to avoid the influence of the operation of reading and updating the cache on the backup process.
Step 403: the control module instructs the IO module to initiate a backup of the cache.
Step 404: and after receiving a backup instruction for starting the cache, the IO module creates backup data on the memory, wherein the backup data is used for recording file information of files stored in the cache. The backup data may have different forms, such as files or directories, according to the selected backup mode.
For example, when the IO module uses a method of backing up a complete file, each file in the cache is read in sequence, and each read file is written into the backup data in sequence;
when the IO module adopts a mode of backing up file attributes, reading each file in the cache in sequence to obtain the attributes of each file, and writing the attributes of each file, such as the file name and/or the file path representing the storage position of the file on the file server, into the backup data in sequence.
In order to prevent backup data of multiple similar devices at different times from interfering with each other, the backup data needs to be identified by the unique device identifier of the device performing backup at the customer service bureau point and the current time of writing the backup data.
Step 406: and the IO module determines a backup mode according to the configuration, reads the first file in the cache, and extracts the file information of the file for backup.
Depending on the backup method, the backed-up file information may be a list of file attributes in the cache, such as a list of file paths and file names, or all files in the cache and their organization structure. The backup data may be an independent file of a file attribute list in the cache, an independent file of a complete file and structure in the cache, a directory of a complete file and structure in the cache, or a directory of file attributes of each file in the cache.
For an independent file only storing a file attribute list in a cache, the IO module only needs to sequentially write file attributes of each file, such as a file path and/or a file name of each file, into backup data;
for storing the complete files and the independent files with the structures in the cache, the IO module needs to read each file in the cache in sequence and write the files into the backup data in sequence;
for the forms of storing complete files and structural directories in the cache respectively, the IO module is to store the files in the cache into the directories of the backup data respectively;
for the directory format that respectively stores the file attributes of the files in the cache, the IO module is to respectively store the file attributes of each file in the cache, such as the file path and/or the file name in the file server, into the directory of the backup data.
To distinguish backup data for different resource processors at different times, the naming of the backup data may be in the form: "resource handler number + backup time", for example, backup data generated by the resource manager number 252 at point 11 on 14 th 02/07/2007, which may be named "252 _ 200707140211". If only the file name and path of each file on the file server are saved in the backup data, the content in the backup data may be in the form of:
“y:\playfile\yesterdayoncemore.wav;
y:\playfile\whenyoubelieve.wav;
y:\playfile\prodeoffly.wav;”
since the cache is set as unavailable during the backup process, it may be selected to initiate the backup of the cache at a time of least traffic, e.g., early in the morning, in order to minimize the impact of the backup on the development of normal traffic.
Step 408: and the IO module writes the file information of the first file into the backup data created on the memory.
Step 410: the IO module reads the second file in the cache and extracts the information of the file to be backed up.
Step 412: and the IO module writes the file information of the second file into the backup data created on the memory.
Step 414: and the IO module sequentially reads the files in the cache until the last file in the cache and extracts the information of the files needing to be backed up.
Step 416: and the IO module writes the file information of the last file into the backup data created on the memory.
Step 418: and the IO module writes the current backup time information into the backup data.
Step 419: the IO module returns the cache backup result to the control module, namely whether the backup is successful or not.
Step 420: and the control module receives the cache backup result of the IO module and sets the cache function to be available.
Step 422: the control module returns the cache backup result to the manager, namely whether the backup is successful or not.
When the resource processor is restarted, the reconfiguration process of the cache can be started manually or automatically.
Fig. 5 is a flowchart of cache reconstruction in the present embodiment, which includes the following steps.
Step 501: and starting the reconstruction of the cache, namely sending a reconstruction request for reconstructing cache data to the control module. The reconfiguration request may trigger the control module by the resource manager to perform reconfiguration of the cache when the resource processor is restarted.
Step 502: the control module sets the state of the cache as unavailable after receiving the cache reconfiguration request.
Step 504: the control module instructs the IO module to initiate reconfiguration of the cache.
Step 505: and the IO module reads the backup data information in the memory.
Step 506: the IO module selects backup data for cache reconstruction from the backup data. Preferably, the IO module selects a backup data of the resource handler that is the latest, for example, a backup data of which creation time is the latest may be selected from the selectable backup data.
Step 508: and the IO module reads the first file information in the selected backup data.
The file information may be the attribute of the file or the complete file, and the backup data may be in the form of an independent file or a directory, depending on the backup method.
When the IO module judges that the backup data is an independent file or a directory containing complete files, sequentially reading each file corresponding to each file information in the backup data, and sequentially writing each read file into the cache;
when the IO module judges that the backup data is an independent file or a directory containing file attributes of the file, sequentially reading the file attributes in the backup data, such as the recorded file name and the recorded file path, accessing a file server for storing the file according to the file name and/or the file path, sequentially reading the file corresponding to the file attributes from the file server, and writing the file into the cache.
For individual files or directories that only hold a list of file attributes in the cache, step 509 is performed;
step 510 is performed for individual files that hold all files and structures in the cache, or each file in the cache is held in the form of a directory.
Step 509: and the IO module accesses the file server and reads the corresponding file according to the file information. If no corresponding file is found, go to step 512; otherwise, execution continues at step 510.
Step 510: the IO module writes the first file into the cache.
Step 512: and the IO module reads the second file information. If only the file path and/or file name is saved, step 513 is performed, otherwise step 514 is performed.
Step 513: and the IO module accesses the file server and reads the corresponding file according to the file path and/or the file name. If no corresponding file is found, go to step 516; otherwise, execution continues with step 514.
Step 514: the IO module writes the second file to the cache.
Step 516: and the IO module sequentially reads the file information in the cache until the last file information in the cache.
517: the backup data only stores the path and the file name of the file, the IO module accesses the file server, and reads the corresponding file according to the file path and/or the file name. If no corresponding file is found, go to step 519; otherwise, execution continues with step 518.
Step 518: the IO module writes the last file into the cache.
Step 519: and the IO module returns the result of cache reconstruction to the control module.
Step 520: and the control module receives a cache reconstruction result returned by the IO module and sets the state of the cache to be available.
Step 522: the control module returns the results of the cache reconstruction.
Through the above steps, the cache is restored to the state of the last backup, where the files were the most frequently accessed files from the last backup.
In addition, after a certain resource handler is restarted, if the file backed up by the resource handler is not found, the backup files of other resource handlers can be selected to be loaded.
When the technical scheme of the embodiment is applied to the color ring office of the operator, the color ring file with the most times of access to the office can be backed up, and when the resource processor is restarted, the data in the cache can be quickly recovered by using the backup file; when the technical scheme of the embodiment is applied, the server providing the video service can back up the video files which are watched or downloaded most, and the like.
For local sites that are already functioning properly, each resource processor may periodically or manually build its cached backup data. When a resource handler is restarted, backup data created by the resource handler or created by other resource handlers in the local site can be loaded immediately.
For the newly established local point, because the hit rate of the cache in the resource processor needs a long time to be stabilized at a higher level just after the local point starts to operate, and the practicability of the backup data of the cache is not high, the cache backup data of other local points can be directly used, or the backup data of popular files can be manually created according to the current popular information to construct the cache of the new local point, so that the hit rate of the cache of the new local point is improved.
For some similar local points in application, such as intelligent peripheral local points of an intelligent network, because the resources are relatively fixed, cache backup data can be manually generated in advance for the local points to be directly loaded into the cache, so that the hit rate of the cache of the local points can be greatly increased, and the construction time of the cache can be obviously reduced.
It can be seen from the above embodiments that the method for recovering cache data of the present invention can recover data in a cache when needed, and can rapidly improve the hit rate of the cache.
The device for recovering the cache data can recover the data in the cache of the device when needed and can quickly improve the hit rate of the cache.
In summary, the above are only some examples of the present invention, and are not intended to limit the scope of the present invention. Any modification, equivalent replacement, or improvement made within the spirit and principle of the present invention should be included in the protection scope of the present invention.

Claims (13)

1. A method of cache data recovery, comprising,
reading backup data, wherein the backup data is used for recording file information of a file;
and writing the file corresponding to the file information in the backup data into a cache.
2. The method of claim 1, further comprising,
and generating the backup data.
3. The method of claim 2, wherein the generating the backup data comprises,
and generating backup data for recording the file information of the file according to the file stored in the cache.
4. The method of claim 2, wherein the generating the backup data comprises,
and generating the backup data for recording the file information of the files according to the files needing to be saved in the cache.
5. The method according to any one of claims 1 to 4, wherein the file information is a complete file;
the writing the file corresponding to the file information in the backup data into the cache comprises:
reading a complete file recorded in the backup data;
writing the file read to the cache.
6. The method according to any one of claims 1 to 4, wherein the file information is an attribute of a file;
the writing the file corresponding to the backup data file information into the cache comprises:
reading file attributes recorded by file information in the backup data;
and accessing a file server for storing files according to the file attributes, reading the files corresponding to the file attributes from the file server, and writing the files into the cache.
7. The method of claim 6, wherein the attribute of the file is a file name of the file and/or a file path that characterizes a storage location of the file on a file server.
8. The method according to claim 2 or 3, wherein the file information is a complete file;
said generating said backup data comprises generating said backup data by,
sequentially reading each file in the cache;
and sequentially writing the read files into the backup data as file information.
9. The method according to claim 2 or 3, wherein the file information is an attribute of a file;
said generating said backup data comprises generating said backup data by,
sequentially reading each file in the cache to obtain the file attribute of the file;
and sequentially writing the file attribute of each file as file information into the backup data.
10. The method of claim 1, wherein the backup data further comprises time information for writing the file information into the backup data.
11. The method of claim 1, wherein the backup data further comprises device identification information.
12. An apparatus for cache data recovery, comprising,
a backup data reading unit for reading backup data for recording file information of a file;
and the file recovery unit is used for writing the files corresponding to the file information in the backup data into a cache.
13. The apparatus of claim 12, further comprising,
and the backup data generating unit is used for generating the backup data.
CN2007103083010A 2007-12-29 2007-12-29 Method and device for recovering cache data Expired - Fee Related CN101470645B (en)

Priority Applications (2)

Application Number Priority Date Filing Date Title
CN2007103083010A CN101470645B (en) 2007-12-29 2007-12-29 Method and device for recovering cache data
PCT/CN2008/073656 WO2009092254A1 (en) 2007-12-29 2008-12-22 Method, device and system for recovering data of cache

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN2007103083010A CN101470645B (en) 2007-12-29 2007-12-29 Method and device for recovering cache data

Publications (2)

Publication Number Publication Date
CN101470645A true CN101470645A (en) 2009-07-01
CN101470645B CN101470645B (en) 2012-04-25

Family

ID=40828131

Family Applications (1)

Application Number Title Priority Date Filing Date
CN2007103083010A Expired - Fee Related CN101470645B (en) 2007-12-29 2007-12-29 Method and device for recovering cache data

Country Status (2)

Country Link
CN (1) CN101470645B (en)
WO (1) WO2009092254A1 (en)

Cited By (10)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102262657A (en) * 2011-06-29 2011-11-30 成都市华为赛门铁克科技有限公司 Method and system for storing multimedia data
US8521959B2 (en) 2011-12-21 2013-08-27 Huawei Technologies Co., Ltd. Method and device for recovering description information, and method and device for caching data in database
CN103885901A (en) * 2012-12-21 2014-06-25 联想(北京)有限公司 File reading method, memory device and electronic device
CN104331343A (en) * 2014-11-06 2015-02-04 深圳市中兴移动通信有限公司 File backup method and system
CN104881334A (en) * 2015-02-06 2015-09-02 北京飞杰信息技术有限公司 Crash-proof cache data protection method and system
CN105302671A (en) * 2015-11-11 2016-02-03 中国建设银行股份有限公司 Automatic backup and rollback method and device
CN105718330A (en) * 2016-01-15 2016-06-29 浪潮(北京)电子信息产业有限公司 Linux system backup data recovery method and device
US9684596B2 (en) 2015-02-25 2017-06-20 Microsoft Technology Licensing, Llc Application cache replication to secondary application(s)
US9684607B2 (en) 2015-02-25 2017-06-20 Microsoft Technology Licensing, Llc Automatic recovery of application cache warmth
CN112925759A (en) * 2021-03-31 2021-06-08 北京金山云网络技术有限公司 Data file processing method and device, storage medium and electronic device

Families Citing this family (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2016069030A1 (en) * 2014-10-29 2016-05-06 Hewlett Packard Enterprise Development Lp Data restoration using allocation maps
CN108173665B (en) * 2016-12-07 2021-02-23 北京云中融信网络科技有限公司 Data backup method and device

Family Cites Families (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20030005219A1 (en) * 2001-06-29 2003-01-02 Royer Robert J. Partitioning cache metadata state
CN1754155A (en) * 2003-01-17 2006-03-29 泰斯特网络公司 Method and system for use of storage caching with a distributed file system
CN100461806C (en) * 2005-04-07 2009-02-11 华为技术有限公司 Voice value-added service data information processing method
CN1318974C (en) * 2005-08-05 2007-05-30 北京九州汇宝软件有限公司 Method for compression and search of database backup data
KR100781520B1 (en) * 2006-02-24 2007-12-03 삼성전자주식회사 Storage apparatus using non volatile memory as cache and mapping information recovering method for the same

Cited By (15)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102262657A (en) * 2011-06-29 2011-11-30 成都市华为赛门铁克科技有限公司 Method and system for storing multimedia data
US8521959B2 (en) 2011-12-21 2013-08-27 Huawei Technologies Co., Ltd. Method and device for recovering description information, and method and device for caching data in database
CN103885901A (en) * 2012-12-21 2014-06-25 联想(北京)有限公司 File reading method, memory device and electronic device
CN104331343B (en) * 2014-11-06 2017-09-19 努比亚技术有限公司 File backup method and system
CN104331343A (en) * 2014-11-06 2015-02-04 深圳市中兴移动通信有限公司 File backup method and system
CN104881334A (en) * 2015-02-06 2015-09-02 北京飞杰信息技术有限公司 Crash-proof cache data protection method and system
CN104881334B (en) * 2015-02-06 2018-04-10 北京华胜天成软件技术有限公司 Data cached anti-lost electric protection method and system
US9684596B2 (en) 2015-02-25 2017-06-20 Microsoft Technology Licensing, Llc Application cache replication to secondary application(s)
US9684607B2 (en) 2015-02-25 2017-06-20 Microsoft Technology Licensing, Llc Automatic recovery of application cache warmth
US10114765B2 (en) 2015-02-25 2018-10-30 Microsoft Technology Licensing, Llc Automatic recovery of application cache warmth
US10204048B2 (en) 2015-02-25 2019-02-12 Microsoft Technology Licensing, Llc Replicating a primary application cache within a secondary application cache
CN105302671A (en) * 2015-11-11 2016-02-03 中国建设银行股份有限公司 Automatic backup and rollback method and device
CN105718330A (en) * 2016-01-15 2016-06-29 浪潮(北京)电子信息产业有限公司 Linux system backup data recovery method and device
CN112925759A (en) * 2021-03-31 2021-06-08 北京金山云网络技术有限公司 Data file processing method and device, storage medium and electronic device
CN112925759B (en) * 2021-03-31 2024-05-31 北京金山云网络技术有限公司 Data file processing method and device, storage medium and electronic device

Also Published As

Publication number Publication date
WO2009092254A1 (en) 2009-07-30
CN101470645B (en) 2012-04-25

Similar Documents

Publication Publication Date Title
CN101470645B (en) Method and device for recovering cache data
CN106407040B (en) A kind of duplicating remote data method and system
CN102667772B (en) File level hierarchical storage management system, method, and apparatus
US8589353B2 (en) Method for backing up terminal data and system thereof
KR101137299B1 (en) Hierarchical storage management for a file system providing snapshots
CN111176549B (en) Data storage method and device based on cloud storage and storage medium
JPS61502846A (en) How to back up your database
CN111506253B (en) Distributed storage system and storage method thereof
CN109582686B (en) Method, device, system and application for ensuring consistency of distributed metadata management
JP7215971B2 (en) METHOD AND APPARATUS FOR PROCESSING DATA LOCATION IN STORAGE DEVICE, COMPUTER DEVICE AND COMPUTER-READABLE STORAGE MEDIUM
CN115061630A (en) Data migration method, device, equipment and medium
CN114168380A (en) Database configuration method, device, system and storage medium
JP4755244B2 (en) Information generation method, information generation program, and information generation apparatus
CN114528255A (en) Metadata management method, electronic device and computer program product
CN101937378B (en) Method for carrying out back-up protection on data of storage equipment and computer system
CN115617264A (en) Distributed storage method and device
CN111399753B (en) Method and device for writing pictures
CN104424115B (en) Recover method, storage device and the electronic equipment of the preset state of electronic equipment
CN108271420B (en) Method for managing files, file system and server system
CN113190241B (en) Method and device for expanding capacity of data partition, electronic equipment and storage medium
CN118120212A (en) File deduplication method, device and equipment
CN116760913B (en) Method and system for issuing k8s cluster protocol conversion platform configuration
CN113419897A (en) File processing method and device, electronic equipment and storage medium thereof
CN109558082B (en) Distributed file system
CN115421856A (en) Data recovery method and device

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
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: 20120425

Termination date: 20161229