CN101354713A - Method and system for storing data - Google Patents
Method and system for storing data Download PDFInfo
- Publication number
- CN101354713A CN101354713A CNA2008101197346A CN200810119734A CN101354713A CN 101354713 A CN101354713 A CN 101354713A CN A2008101197346 A CNA2008101197346 A CN A2008101197346A CN 200810119734 A CN200810119734 A CN 200810119734A CN 101354713 A CN101354713 A CN 101354713A
- Authority
- CN
- China
- Prior art keywords
- data
- completed
- filing
- current
- history lists
- 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.)
- Pending
Links
Images
Landscapes
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
Abstract
The invention discloses a method and a system for storing data. An embodiment of the data storing method comprises the following steps: the uncompleted data is stored in a current list; the data which is converted into the complete data in the current list is transferred to an archiving list; and the data which is completed to achieve or exceed the preset time in the archiving list is transferred to a historical list. The method and the system improve the operation efficiency of the core application and the hotspot function aiming at the current list.
Description
Technical field
The present invention relates to the telecommunication technology field, particularly a kind of date storage method and system.
Background technology
At present field of telecommunications business support system (BSS)/operation support system (OSS) is towards the development of function specialized direction, and the flow process integrated functionality by the service release system is connected each professional system and realizes end-to-end service fulfillment.
In the service release system, process data amount in the core information entities such as similar service order, construction worker list, flow instance can be more and more huger along with the prolongation of system service time, causes the core application such as construction processing and the focus function treatment performance of procedure-oriented data in the application system to descend day by day easily.So-called focus function refers to that system or personnel use the most frequent software module, for example order scheduling, worker singly generate, the worker singly distributes, the worker singly inquires about, worker Dan Lingdan, the singly withdrawal of currency from circulation of worker, process pilot, professional supervision etc., be the core ingredient of system, its performance performance is a key index of weighing the total system performance.These focus functions are mainly reflected in the relation of core information entity: owing to the data volume of the corresponding core data table of Core Feature is generally all bigger, so along with online implementing is long more working time, the data volume of core data table can be more and more huger, the data of Core Feature correspondence are when the focus function treatment, when for example carrying out operation such as concrete inquiry, renewal, insertion, performance can descend.Therefore, need provide a kind of method of can be at any time data in time being handled, with the efficient of operations such as the inquiry that improves core application and focus function, renewal, insertion.
Just how to improve the database access performance, improve the DB Backup aspect from the application system design angle in the prior art at present, common design proposal is as follows:
1: his-and-hers watches use partitioning technique;
2: use the secondary storage pattern of current table and history lists combination, regularly the data that met or exceeded for first schedule time of being completed in the current table are transferred in the history lists.
Here the data of being completed are relative with the data of not being completed.In general, business is not also finished data in the construction of opening,, can not in time file promptly to the data of not being completed.
Concerning the data of being completed, the aforementioned focus function of mentioning does not often operate on it, and need relate to when just sometimes inquiring about.
In research and practice process to prior art, the inventor finds to exist in the prior art following problem:
Because in the prior art, what adopt is the secondary storage pattern, be regularly to transfer to first predetermined time data that meets or exceeds that has been completed in the current table in the history lists by the gross, like this, before these data of being completed in shifting current table, still be stored in the current table in time of a suitable segment length that the data of being completed may be after completion, thereby filed timely.For example first schedule time of prior art is set to half a year, be once the data of being completed in the current table to be transferred in the history lists in every month, as carrying out respectively once the beginning of each month, then if the data of being completed at the beginning of 2 months, then will exist up to meeting or exceeding for first schedule time at current table always, at the beginning of just 7 months, and can not filed timely.Like this, will cause having the data of being completed in a large number in the current table, and add the data of not being completed, total data volume record number can be very big, and the data magnitude of current table is 120～180 times of example of the present invention.Like this,,, will in comprising the mass data current table of (comprising be completed the data and the data of not being completed), carry out, cause performance not high as operations such as concrete inquiry, renewal, insertions for the aforementioned focus function treatment of mentioning.
Summary of the invention
The purpose of the embodiment of the invention provides a kind of date storage method and system, to realize the efficient to the timely filing and the feature operation of lifting focus of data.
For solving the problems of the technologies described above, the embodiment of the invention provides a kind of date storage method and system to be achieved in that
A kind of date storage method comprises:
The data storage of will not being completed is in current table;
The data that being converted in the current table has been completed are transferred in the filing table in real time;
Meeting or exceeding the data of the schedule time with being completed in the filing table transfers in the history lists.
Preferably, in the described method, describedly meet or exceed the data of the schedule time with being completed in the filing table and transfer in the history lists, to comprise:
Met or exceeded for first schedule time with being completed in the filing table and the data within second schedule time are transferred in the history lists.
Preferably, in the described method, described current table, filing table are deployed in the Current Library, and history lists is deployed in the history library.
Preferably, in the described method, described current table is deployed in the Current Library, and the filing table is deployed in the filing storehouse.
Preferably, in the described method, described history lists is deployed in the history library.
Preferably, in the described method, described current table, filing table and history lists are planned respectively in different table spaces.
Preferably, in the described method, described current table is carried out full backup every day, carried out incremental backup in per 2 hours; The filing table is carried out full backup weekly, carry out incremental backup every day; History lists carried out full backup in every month, carried out incremental backup weekly.
Preferably, in the described method, when disaster happens suddenly, recover current table earlier, recover the filing table again, recover history lists at last.
A kind of data-storage system comprises:
Current table is used for storing the data of not being completed;
The filing table is used for storing the data of being completed; The data of being completed of storing in the described filing table are by the not completion data conversion in the current table, and do not meet or exceed the data of the schedule time for being completed;
History lists is used to store the completion data that completion meets or exceeds the schedule time; The data of being completed of storing in the described history lists are transformed by the filing data in the filing table, and meet or exceed the data of the schedule time for being completed.
Preferably, in the described system, the data of being completed of storing in the described history lists meet or exceed first schedule time and the data within second schedule time for being completed.
Preferably, in the described system, described current table, filing table are deployed in the Current Library, and history lists is deployed in the history library.
Preferably, in the described system, described current table is deployed in the Current Library, and the filing table is deployed in the filing storehouse.
Preferably, in the described system, described history lists is deployed in the history library.
Preferably, in the described system, described current table, filing table and history lists are planned respectively in different table spaces.
The technical scheme that is provided by the above embodiment of the invention as seen, by real-time automatically every professional corresponding data of having opened in time being filed, therefore the data volume of core data table maintains on the stable order of magnitude always like this, can avoid core data table in the current table to increase with time of online implementing and cause data volume more and more huger.Like this, can lift pins to the core application and the focus function operations efficient of current table.
Description of drawings
Fig. 1 is the process flow diagram of the inventive method embodiment;
Fig. 2 is the schematic diagram of the present invention one method embodiment;
Fig. 3 is the block diagram of system embodiment of the present invention.
Embodiment
The embodiment of the invention provides a kind of date storage method and system.
In order to make those skilled in the art person understand the present invention program better, the embodiment of the invention is described in further detail below in conjunction with drawings and embodiments.
Fig. 1 shows the process flow diagram of date storage method one embodiment of the present invention, and as shown in Figure 1, this embodiment comprises:
S101: the data storage of will not being completed is in current table.
Data in the service fulfillment process are divided into several stages.Receiving the service order, it is single to generate the construction worker, is in the data that data in the flow instance process etc. are not finished service fulfillment, all belongs to the data of not being completed.Along with the progress of construction and the passing of time, after finishing service fulfillment, the described data of not being completed will be converted into the data of being completed.
Here, current table is the general designation of storing all tables of the data of not being completed.Like this, current table can be towards the focus function in the construction processing (neck list, receipt, monitoring), only storage activities object.Moving object comprises the object that does not also become history in the life cycle state or also do not have to cancel, system or personnel also can operate on it, and cause the migration of its life cycle state, and its state is also in the earthquake track, and unlike historical data, it has been that static state no longer changes.Moving object generically can be regarded as a series of of user's correspondence that do not activate the service and opens relevant data with construction, such as order information, the single information of worker, flow instance information etc.Saying that object is more popular here is meant data, also is the saying abstract to data, can become object as order, worker are single etc., during instantiation with regard to existence activity order, active trouble ticket.Therefore, in the service release system, moving object can unify to be interpreted as " the still unfinished data that are associated with the service order ".For example, active trouble ticket can refer to worker's list that the associated link of current active node of the flow process of still unfinished service order correspondence is sent.
In a word, in only comprising the current table of the data of not being completed, carry out the processing of focus function, because the data volume in the current table is not too big, especially with respect to prior art, the data of much being completed can't be comprised, therefore, the handling property of focus function can be improved.
S102: in real time the data of being completed in the current table are transferred in the filing table.
For the data of being completed, the focus function does not generally often operate on it, and just may relate to when inquiry sometimes.
Therefore, here, in real time the data of being completed in the current table are transferred to the filing table, promptly the data in real time of being completed in the current table is moved away, guarantee that the data volume of core data table in the current table maintains on the stable order of magnitude by the mode that the data in real time of being completed is filed.The data volume that can not occur core data table in the current table like this can be more and more huger with the increase of online implementing time.Like this, can lift pins to the core application and the focus function operations efficient of current table (particularly wherein core data table).
With respect to can not timely the data of being completed in time being filed in the prior art, but regularly a collection of data migtation that met or exceeded for first schedule time of being completed is walked, such as the data before 3 months or half a year, thisly belong to non-timely non real-time operation.And the embodiment of the invention is proposed here, and be real-time automatically every professional corresponding data of having opened in time being filed, the data volume of core data table maintains on the stable order of magnitude always like this.
S103: meet or exceed the data of the schedule time with being completed in the filing table and transfer in the history lists.
Completion data in the filing table, may still can be inquired about (or other operation) within a certain period of time, and as time passes, after certain hour, will seldom might be operated again, therefore, the completion data that are divided into filing table and history lists storage different time sections, utilize history lists to deposit exactly and have been brought to completion, and the filing table is deposited newer completion data, so that follow-up operation is only carried out in the filing table than long data.
The described schedule time can preestablish, and for example can be redefined for 3 months, then files in the storehouse be completed data in three months of storage.When the data of being completed met or exceeded 3 months in the storehouse in filing, this part data will be stored in the history library.
Especially, establishing the above-mentioned schedule time is M month, then the data that storage has been completed and has been met or exceeded M month in the history lists.Can also set another schedule time N on this basis, N for example can also meet or exceed M month with being completed, and in data storage within the N in history lists.N can for example can be 3 according to the actual conditions adjustment.If be called for first schedule time with M month, N was called for second schedule time, was above then: met or exceeded for first schedule time with being completed in the filing table and the data within second schedule time are transferred in the history lists.
Above-mentioned current table, filing table and the deployment of history lists in database can be in such a way:
Mode one: adopt two storehouses, one is Current Library, and another is a history library.Current table, filing table are deployed in the Current Library, and history lists is deployed in the history library.
Mode two: adopt three storehouses, one is that Current Library, one are the filing storehouses, and one is history library.Current table is deployed in the Current Library, and the filing table is deployed in the filing storehouse, and history lists is deployed in the history library.
Adopt different storehouses to store different tables respectively respectively, different data qualification isolated storage can be convenient to management like this, also be beneficial to the safety of data.
Fig. 2 shows the schematic diagram that the present invention stores data method one embodiment, can embody foregoing.Need to prove, can store 100,000,1,000,000 grades data in the current table, can be in the face of the operation at moving object such as the list of the group in the telecommunication system, neck list, receipt, monitoring; Can store ten million in the file table, hundred million grades data, and adopt the table partitioning technique; Can store hundred million, 1,000,000,000 grades data in the history lists, and adopt the table partitioning technique.Filing table and history lists can be towards operations such as inquiry, statistics, trackings.
Current table, filing table and history lists can be planned respectively in different table spaces.Table space is the notion of a logic, and it is made up of one or several in esse file in disk, is used for the various objects in store data storehouse, is exactly to finish tissue to data by table space as Oracle.The explanation of giving an example, in Oracle, an example (database) has a plurality of table spaces (SYSTEM, SYSAUX, TEMP etc. and user oneself create), and an oracle database is made up of one or more logic storage units that are called table space.
Current table, filing table and history lists planning can be convenient to backup, be convenient to recover, be convenient to management in different table spaces, as RMAN (Recovery Manager, a kind of backup reset mode, can be used for backing up and restore data library file, archive log and control documents) can realize that the backup of single table space recovers, recover software as backups such as common IBM TSM, Legato, Veritas, all provide backup to recover based on table space.
Consider security, stability and the economy of data storage, below provide a kind of more excellent data storage method: adopt the three-level schema storage scheme, current table and filing table place table space leave on the fiber reel, (RAID is the abbreviation of " Redundant Array of Independent Disk " to adopt RAID10, Chinese is raid-array) mode stores, not only guaranteed the safety of data but also be convenient to fast access; History lists place table space leaves on SATA (Serial Advanced Technology Attachment, the Serial Advanced Technology Attachment) dish, adopts the RAID5 mode to store, and can satisfy the online query needs, has relative high cost performance simultaneously.
About backup Restoration Mechanism aspect, below provide a kind of more excellent backup method and restoration methods respectively.
Backup method: owing to current table, filing table, history lists lay respectively on different table space or the disparate databases, therefore, can show formulation backup policy separately flexibly to three covers according to data volume and Data Update frequency surface, suggestion is carried out full backup every day to current table (or also comprising basic data), carries out incremental backup in per 2 hours; The filing table is carried out full backup weekly, carry out incremental backup every day; History lists carried out full backup in every month, carried out incremental backup weekly.
Restoration methods: when disaster happens suddenly, recover step by step according to backup policy, recover current table (or also comprising basic data) earlier, the assurance system normally moves to satisfy the production and operation needs; Recover the filing table again, recover history lists at last.Because in general current table storage activities object only, for the telecommunication system of ten million rank customer volume, can recover to finish in ten minutes, and stored the two-stage pattern storage scheme of the data of being completed, then often needed several hours release time for current table.
Above-mentioned back-up restoring method is convenient to DB Backup and recovery carrying out and fast quick-recovery stage by stage.
By above embodiment as seen, by real-time automatically every professional corresponding data of having opened in time being filed, the data volume of core data table maintains on the stable order of magnitude always like this, therefore can avoid the data volume of core data table in the current table more and more huger with the increase of online implementing time.Otherwise, like this can lift pins to the core application and the focus function operations efficient of current table.
In addition, by above-mentioned back-up restoring method, can be beneficial to DB Backup and recovery carrying out and fast quick-recovery stage by stage.
Below introduce data-storage system embodiment of the present invention, Fig. 3 shows the block diagram of this embodiment, as figure, comprising:
Current table 301 is used for storing the data of not being completed;
Filing table 302 is used for storing the data of being completed; The data of being completed of storage are by the not completion data conversion in the current table 301 in the described filing table 302, and do not meet or exceed the data of the schedule time for completion;
History lists 303 is used to store the completion data that completion meets or exceeds the schedule time; The data of being completed of storage are transformed by the filing data in the filing table 302 in the described history lists 303, and meet or exceed the data of the schedule time for being completed.
The data of being completed of storage meet or exceed first schedule time and the data within second schedule time for being completed in the described history lists 302.
Described current table 301, filing table 302 are deployed in the Current Library, and history lists is deployed in the history library.
Described current table is deployed in the Current Library, and the filing table is deployed in the filing storehouse.
Described history lists is deployed in the history library.
Described current table, filing table and history lists are planned respectively in different table spaces.
Though above described the present invention by embodiment, those of ordinary skills know, the present invention has many distortion and variation and does not break away from spirit of the present invention, wishes that appended claim comprises these distortion and variation and do not break away from spirit of the present invention.
Claims (14)
1, a kind of date storage method is characterized in that, comprising:
The data storage of will not being completed is in current table;
The data that being converted in the current table has been completed are transferred in the filing table in real time;
Meeting or exceeding the data of the schedule time with being completed in the filing table transfers in the history lists.
2, the method for claim 1 is characterized in that, describedly meets or exceeds the data of the schedule time with being completed in the filing table and transfers in the history lists, comprising:
Met or exceeded for first schedule time with being completed in the filing table and the data within second schedule time are transferred in the history lists.
3, the method for claim 1 is characterized in that, described current table, filing table are deployed in the Current Library, and history lists is deployed in the history library.
4, the method for claim 1 is characterized in that, described current table is deployed in the Current Library, and the filing table is deployed in the filing storehouse.
5, the method for claim 1 is characterized in that, described history lists is deployed in the history library.
6, the method for claim 1 is characterized in that, described current table, filing table and history lists are planned respectively in different table spaces.
7, the method for claim 1 is characterized in that, described current table is carried out full backup every day, carries out incremental backup in per 2 hours; The filing table is carried out full backup weekly, carry out incremental backup every day; History lists carried out full backup in every month, carried out incremental backup weekly.
8, the method for claim 1 is characterized in that, when disaster happens suddenly, recovers current table earlier, recovers the filing table again, recovers history lists at last.
9, a kind of data-storage system is characterized in that, comprising:
Current table is used for storing the data of not being completed;
The filing table is used for storing the data of being completed; The data of being completed of storing in the described filing table are by the not completion data conversion in the current table, and do not meet or exceed the data of the schedule time for being completed;
History lists is used to store the completion data that completion meets or exceeds the schedule time; The data of being completed of storing in the described history lists are transformed by the filing data in the filing table, and meet or exceed the data of the schedule time for being completed.
10, system as claimed in claim 9 is characterized in that, the data of being completed of storing in the described history lists meet or exceed first schedule time and the data within second schedule time for being completed.
11, system as claimed in claim 9 is characterized in that, described current table, filing table are deployed in the Current Library, and history lists is deployed in the history library.
12, system as claimed in claim 9 is characterized in that, described current table is deployed in the Current Library, and the filing table is deployed in the filing storehouse.
13, system as claimed in claim 9 is characterized in that, described history lists is deployed in the history library.
14, system as claimed in claim 9 is characterized in that, described current table, filing table and history lists are planned respectively in different table spaces.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CNA2008101197346A CN101354713A (en) | 2008-09-08 | 2008-09-08 | Method and system for storing data |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CNA2008101197346A CN101354713A (en) | 2008-09-08 | 2008-09-08 | Method and system for storing data |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN101354713A true CN101354713A (en) | 2009-01-28 |
Family
ID=40307523
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CNA2008101197346A Pending CN101354713A (en) | 2008-09-08 | 2008-09-08 | Method and system for storing data |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN101354713A (en) |
Cited By (15)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101788938A (en) * | 2010-03-26 | 2010-07-28 | 北京邮电大学 | Data backup method based on user storing actions |
| CN102541694A (en) * | 2012-01-18 | 2012-07-04 | 浪潮(北京)电子信息产业有限公司 | Method and device for database backup |
| CN103020169A (en) * | 2012-11-27 | 2013-04-03 | 山东黄金矿业（莱州）有限公司 | Effectiveness and uniqueness processing method for electric data |
| CN103684837A (en) * | 2012-09-25 | 2014-03-26 | 中国电信股份有限公司 | Back-up processing method, system and back-up processing server for communication information |
| CN103853713A (en) * | 2012-11-28 | 2014-06-11 | 成都勤智数码科技股份有限公司 | Efficient storage method of mass data |
| CN103853719A (en) * | 2012-11-28 | 2014-06-11 | 成都勤智数码科技股份有限公司 | Extensible mass data collection system |
| CN104572867A (en) * | 2014-12-18 | 2015-04-29 | 上海新炬网络信息技术有限公司 | Data processing method based on Oracle |
| CN105786975A (en) * | 2016-02-04 | 2016-07-20 | 北京中盛益华科技有限公司 | Massive video storage method used for quick search |
| CN106201780A (en) * | 2016-07-08 | 2016-12-07 | 浪潮通用软件有限公司 | A kind of historical data method of reducing |
| CN106202374A (en) * | 2016-07-07 | 2016-12-07 | 无锡天脉聚源传媒科技有限公司 | A kind of data processing method and device |
| CN106445738A (en) * | 2016-09-13 | 2017-02-22 | 郑州云海信息技术有限公司 | Database backup method and device |
| CN107870981A (en) * | 2017-09-30 | 2018-04-03 | 平安科技（深圳）有限公司 | Electronic installation, the method and storage medium of tables of data filing processing |
| CN108664525A (en) * | 2017-04-01 | 2018-10-16 | 北京京东尚科信息技术有限公司 | Data processing method and device for data processing server |
| CN110704465A (en) * | 2019-09-26 | 2020-01-17 | 中电万维信息技术有限责任公司 | Method, device and storage medium for processing service work order table |
| CN113138877A (en) * | 2020-01-17 | 2021-07-20 | 伊姆西Ip控股有限责任公司 | Method, apparatus and computer program product for managing backup systems |
-
2008
- 2008-09-08 CN CNA2008101197346A patent/CN101354713A/en active Pending
Cited By (23)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101788938B (en) * | 2010-03-26 | 2011-12-14 | 北京邮电大学 | Data backup method based on user storing actions |
| CN101788938A (en) * | 2010-03-26 | 2010-07-28 | 北京邮电大学 | Data backup method based on user storing actions |
| CN102541694A (en) * | 2012-01-18 | 2012-07-04 | 浪潮(北京)电子信息产业有限公司 | Method and device for database backup |
| CN103684837B (en) * | 2012-09-25 | 2018-01-09 | 中国电信股份有限公司 | Backup processing method, system and the back-up processing server of communication information |
| CN103684837A (en) * | 2012-09-25 | 2014-03-26 | 中国电信股份有限公司 | Back-up processing method, system and back-up processing server for communication information |
| CN103020169A (en) * | 2012-11-27 | 2013-04-03 | 山东黄金矿业（莱州）有限公司 | Effectiveness and uniqueness processing method for electric data |
| CN103853719B (en) * | 2012-11-28 | 2018-05-22 | 勤智数码科技股份有限公司 | Easily extension mass data collection system |
| CN103853713A (en) * | 2012-11-28 | 2014-06-11 | 成都勤智数码科技股份有限公司 | Efficient storage method of mass data |
| CN103853719A (en) * | 2012-11-28 | 2014-06-11 | 成都勤智数码科技股份有限公司 | Extensible mass data collection system |
| CN103853713B (en) * | 2012-11-28 | 2018-04-24 | 勤智数码科技股份有限公司 | The efficient storage method of mass data |
| CN104572867A (en) * | 2014-12-18 | 2015-04-29 | 上海新炬网络信息技术有限公司 | Data processing method based on Oracle |
| CN105786975A (en) * | 2016-02-04 | 2016-07-20 | 北京中盛益华科技有限公司 | Massive video storage method used for quick search |
| CN105786975B (en) * | 2016-02-04 | 2018-12-28 | 北京中盛益华科技有限公司 | Massive video storage method for quick-searching |
| CN106202374A (en) * | 2016-07-07 | 2016-12-07 | 无锡天脉聚源传媒科技有限公司 | A kind of data processing method and device |
| CN106201780A (en) * | 2016-07-08 | 2016-12-07 | 浪潮通用软件有限公司 | A kind of historical data method of reducing |
| CN106445738A (en) * | 2016-09-13 | 2017-02-22 | 郑州云海信息技术有限公司 | Database backup method and device |
| CN108664525A (en) * | 2017-04-01 | 2018-10-16 | 北京京东尚科信息技术有限公司 | Data processing method and device for data processing server |
| CN107870981A (en) * | 2017-09-30 | 2018-04-03 | 平安科技（深圳）有限公司 | Electronic installation, the method and storage medium of tables of data filing processing |
| WO2019062189A1 (en) * | 2017-09-30 | 2019-04-04 | 平安科技（深圳）有限公司 | Electronic device, method and system for conducting data table filing processing, and storage medium |
| CN107870981B (en) * | 2017-09-30 | 2021-10-22 | 平安科技（深圳）有限公司 | Electronic device, data sheet filing method and storage medium |
| CN110704465A (en) * | 2019-09-26 | 2020-01-17 | 中电万维信息技术有限责任公司 | Method, device and storage medium for processing service work order table |
| CN113138877A (en) * | 2020-01-17 | 2021-07-20 | 伊姆西Ip控股有限责任公司 | Method, apparatus and computer program product for managing backup systems |
| CN113138877B (en) * | 2020-01-17 | 2024-04-19 | 伊姆西Ip控股有限责任公司 | Method, apparatus and computer program product for managing backup systems |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN101354713A (en) | Method and system for storing data | |
| CN101477486B (en) | File backup recovery method based on sector recombination | |
| US7222133B1 (en) | Method for reducing database recovery time | |
| US6745304B2 (en) | Method and device for storing computer data with back-up operations | |
| KR101150025B1 (en) | Method, system, and apparatus for creating an architectural model for generating robust and easy to manage data protection applications in a data protection system | |
| CN101460934B (en) | Creating frequent application-consistent backups efficiently | |
| EP1637997B1 (en) | Method for reporting an alert in a data protection computer system | |
| US6411969B1 (en) | Enhanced system and method for management of system database utilities | |
| CN103927238B (en) | Technique For Timeline Compression In Data Store | |
| CN104102737B (en) | A kind of historical data storage method and system | |
| US8060493B2 (en) | Developing enterprise information life cycle management policies and solutions | |
| US20060235905A1 (en) | Method and system for preserving real-time access to a system in case of a disaster | |
| US20060053305A1 (en) | Method, system, and apparatus for creating saved searches and auto discovery groups for a data protection system | |
| US7774315B1 (en) | Backup system | |
| CN101739313B (en) | Method for protecting and restoring continuous data | |
| CN103455557B (en) | A kind of structural data synchronous method based on daily record | |
| CN105069134A (en) | Method for automatically collecting Oracle statistical information | |
| CN107391306A (en) | A kind of isomeric data library backup file access pattern method | |
| CN104541252A (en) | Server-based hierarchical mass storage system | |
| CN101017453A (en) | Method and system for managing deletions in backup sets | |
| CN102541694A (en) | Method and device for database backup | |
| CN102033889A (en) | Distributed database parallel processing system | |
| CN102360357A (en) | Data synchronization component of network relation database nodes of SCADA (Supervisory Control and Data Acquisition) system | |
| CN101976243A (en) | System for processing satellite data | |
| CN106569751A (en) | Multi-controller cache mirroring method and system |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| C06 | Publication | ||
| PB01 | Publication | ||
| C10 | Entry into substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| C12 | Rejection of a patent application after its publication | ||
| RJ01 | Rejection of invention patent application after publication |
Open date: 20090128 |