CN1862502A - Method and system for implementing data back-up between main-standby nodes - Google Patents
Method and system for implementing data back-up between main-standby nodes Download PDFInfo
- Publication number
- CN1862502A CN1862502A CN 200610003111 CN200610003111A CN1862502A CN 1862502 A CN1862502 A CN 1862502A CN 200610003111 CN200610003111 CN 200610003111 CN 200610003111 A CN200610003111 A CN 200610003111A CN 1862502 A CN1862502 A CN 1862502A
- Authority
- CN
- China
- Prior art keywords
- data
- backup
- data object
- node
- module
- 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
Landscapes
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
Abstract
The present invention relates to a method for implementing data backup between major and standby nodes and its system. It is mainly characterized by that firstly, the major node can transfer the data object having need of backup and processing mode correspondent to the described data object to stand-by node; then according to the received processing mode the stand-by node can be used for processing the described backup data object so as to obtain correspondent backup information.
Description
Technical field
The present invention relates to the communications field, relate in particular to the backup of data.
Background technology
Based on the purpose that improves the device systems operational reliability, often adopt active and standby two Analysis of Nested Design for some important module, with box lunch wherein during a set of modules device fails, another set of module device can be directly switch in the current system and uses, this two set of modules equipment relation of active and standby usefulness each other in system is called main with module device (being also referred to as host node) and spare module equipment (being also referred to as slave node).The master makes consistent with module device on hardware with spare module equipment, have only a module to be in the master during actual motion and externally provide function and interface with state, another module is in stand-by state does not externally provide function and interface, has only the activestandby state generation transition of two module devices when needed, master originally reduces to spare module equipment with module device, and spare module equipment originally is upgraded to lead with module device and replace original master outwards provides function and interface with module device.Main in order to guarantee with after module device and the switching in real time of spare module equipment, the software of spare module equipment can directly substitute main software with module device and continue operation, and to almost not influence of original system, some internal storage datas that rely in the time of the software of these two module devices normally need being moved carry out complete backup in real time between two module devices.
Prior art related to the present invention is when between active and standby node during the archive memory data, specifies the data volume of size according to data designated start address and data volume size are disposable from reference position identical reference position backup to slave node of host node appointment.
By the technical scheme of prior art as can be seen, there is following defective in it:
During 1, by the active and standby internodal data backup of existing techniques in realizing, it should be identical specifying the start address of internal storage data in active and standby node of backup, and its data volume size also is consistent when using these specified memory data.And in actual the realization, tend to exist the situation of dynamic discrete storage allocation, that is to say, there is the inconsistent situation of the start address of same internal storage data on active and standby node, if still back up by start address this moment, obviously on active and standby node, write down the start address of each data, realize wanting complicated a lot of in the operation.
If the data volume of 2 specified memory data is bigger, when data change on the host node, then need to back up a complete data volume, obviously backup data quantity can be very big.
Summary of the invention
The purpose of this invention is to provide a kind of method that realizes data back-up between main-standby nodes, by the present invention, when the start address of same internal storage data on active and standby node is inconsistent, or when data volume is not of uniform size when causing, all can realize the backup of data smoothly, so the present invention specifies the internal storage data organizational form of backup can be more scattered, the mode of data backup also relatively flexibly, active and standby node backed up data amount is relatively also less, and the efficient of backup is also corresponding to higher.
The objective of the invention is to be achieved through the following technical solutions:
The invention provides a kind of method that realizes data back-up between main-standby nodes, it comprises:
A, master will need the processing mode of backed up data object and described data object correspondence to send to secondary node with node;
B, secondary node are handled described Backup Data object according to the processing mode that receives, and obtain corresponding backup information.
Wherein, described steps A specifically comprises:
A1, main with the processing mode structure Backup Data entity of node according to need backed up data object and described data object correspondence;
A2, send the Backup Data entity behind the described structure to described secondary node.
Wherein, when need backed up data object was discrete data, described steps A 1 specifically comprised:
A11, main with node structure Backup Data district; And
Main use separately in the system applies layer unified module to number with node and secondary node, need in module, need divide by the backed up data object by the backed up data object according to object type and object number, and according to the position location information of the information specified data object after dividing;
The data object after A12, master will divide according to described position location information with node and the processing mode of described Backup Data object correspondence are stored in the Backup Data district of described structure, are built into the Backup Data entity.
Wherein, when need backed up data object is discrete data, and described data object is when comprising subobject, and described steps A 1 specifically comprises:
A13, main with node structure Backup Data district; And
Main use separately in the system applies layer unified module to number with node and secondary node, need backed up data object object number according to the subobject of object type, object number and described data object in module need be divided by the backed up data object, and according to the position location information of the information specified data object after dividing;
The data object after A14, master will divide according to described position location information with node and the processing mode of described Backup Data object correspondence are stored in the Backup Data district of described structure, are built into the Backup Data entity.
Wherein, described steps A 1 specifically comprises:
A15, main use separately in the system applies layer unified module to number with node and secondary node, in module, need divide by the backed up data object according to object type and object number, and according to the position location information of the information specified data object after dividing;
Data object after A16, master will divide according to described position location information with node adopts corresponding processing mode to encapsulate, and is built into the Backup Data entity.
Wherein, when need backed up data object comprised subobject, described steps A 1 specifically comprised:
A17, main use separately in the system applies layer unified module to number with node and secondary node, need backed up data object numbering according to the subobject of object type, object number and described data object in module need be divided by the backed up data object, and according to the position location information of the information specified data object after dividing;
Data object after A18, master will divide according to described position location information with node adopts corresponding processing mode to encapsulate, and is built into the Backup Data entity.
Wherein, described processing mode comprises: the backup operation mode.
Wherein, described backup operation mode comprises: function mode of operation or message mode of operation.
Wherein, described processing mode also comprises: backup numerical result, backup messages or backup file stream.
The invention provides a kind of system that realizes data back-up between main-standby nodes, it comprises:
Main with node and secondary node;
Described master will need the processing mode of backed up data object and described Backup Data object to send to secondary node with node; Secondary node is handled described Backup Data object according to the processing mode that receives, and obtains corresponding backup information.
Wherein, described master comprises with node:
Backup Data makes up the module and the first data backup module;
Described Backup Data makes up module and makes up the Backup Data entity based on the processing mode of need backed up data object and described data object correspondence, and the buffer queue etc. of then described Backup Data entity being put into the first data backup module is to be sent.
Wherein, described secondary node comprises:
Backup Data recovers the module and the second data backup module;
The described second data backup module receives described Backup Data entity, and it is left in the corresponding buffer queue; Described Backup Data recovers module to be handled corresponding data object according to the processing mode of the data object in the Backup Data entity in the buffer queue in the described second data backup module, obtains corresponding backup information.
As seen from the above technical solution provided by the invention, the master will need the processing mode of backed up data object and described data object correspondence to send to secondary node with node among the present invention; Secondary node is handled described Backup Data object according to the processing mode that receives, and obtains corresponding backup information.By the present invention's method of the processing mode of Backup Data object simultaneously, when the start address of same internal storage data on active and standby node is inconsistent, or when data volume is not of uniform size when causing, all can realize the backup of data smoothly, therefore the present invention specifies the internal storage data organizational form of backup can be more scattered, also relatively flexibly, active and standby node backed up data amount is relatively also less for the mode of data backup, and the efficient of backup is also corresponding to higher.
Description of drawings
Fig. 1 is the system architecture synoptic diagram of first embodiment provided by the invention;
Fig. 2 is the process flow diagram of second embodiment provided by the invention;
Fig. 3 is the process flow diagram of the 4th embodiment provided by the invention.
Embodiment
The invention provides a kind of method and system of realizing data back-up between main-standby nodes, by the present invention, the content that backs up between main-standby nodes not only comprises the end value of Backup Data object, but also has increased the source input of concrete data object between main-standby nodes and the backup of source method of operating.Its core is: the master will need the processing mode of backed up data object and described data object correspondence to send to secondary node with node; Secondary node is handled described Backup Data object according to the processing mode that receives, and obtains corresponding backup information.
Provide first embodiment at system of the present invention, its system architecture synoptic diagram as shown in Figure 1, it comprises main with node and secondary node.Described master comprises again that with node Backup Data makes up the module and the first data backup module, and described Backup Data makes up module and is positioned at the main node application layer of using; Described spare module comprises that again Backup Data recovers the module and the second data backup module, and described Backup Data recovers the application layer that module is positioned at secondary node.
The Backup Data that main each Backup Data with node makes up module and secondary node recovers module and uses separately in the system applies layer unified module to number, need backed up data object object number according to the subobject of object type, object number and this data object in module need be divided by the backed up data object position location information of specified data object.
Main with the position location information of the structure of the Backup Data in node module based on need backed up data object, the processing mode of need backed up data object and described data object correspondence is built into the Backup Data entity, and buffer queue of then described Backup Data entity being put into the first data backup module etc. is to be sent.
After the Backup Data entity arrived secondary node, the second data backup module received described Backup Data, and it is left in the corresponding buffer queue; The Backup Data that is arranged in the secondary node application layer recovers module and extracts the data object of Backup Data according to the position location information of its data object from the buffer queue of the described second data backup module, and according to the type and the numbering of described data object, adopt corresponding processing mode that described data object is handled, obtain corresponding backup information.
At method of the present invention, the invention provides second embodiment, realized the centralized backup of discrete data by this embodiment, specific implementation process comprises as shown in Figure 2:
At first, main with the processing mode structure Backup Data of node based on need backed up data object and described data object correspondence.Specific implementation process is as follows:
The Backup Data that main each Backup Data with node makes up module and secondary node recovers module and uses separately in the system unified module to number, need backed up data object object number according to the subobject of object type, object number and this data object in module need be divided by the backed up data object position location information of specified data object.
typedef?struct
{
Unsigned long dwModuleld; / * application layer module numbering, User Defined */
Unsigned long dwObjectType; / * needs the Backup Data object type, User Defined */
Unsigned long dwObjectld; / * needs the Backup Data object number, User Defined */
Unsigned long dwSubObjectld; / * needs Backup Data object subobject numbering, User Defined */
Unsigned long dwBackupMod; / * backup method comprises backup operation mode, backup numerical result, backup messages, backup file stream etc., can expand */
Unsigned long dwDataLen; The concrete Backup Data section length of/* */
Unsigned char abData[1024]; The concrete Backup Data of/* district content, concrete length according to actual conditions by dwDataLen determine */
}STR_DATA_BACKUP；
By above-mentioned data structure, be positioned at main data backup structure module and at first make up the Backup Data district with the node application layer, the main then dwModuleId that uses system's unification separately to number with the module that is positioned at application layer in node and the secondary node unifies to divide in module by the type dwObjectType of this data object and the numbering dwObjectId of this data object to need backed up data object.Data after the division constitute the position location information that needs the Backup Data object.
Backup method dwBackupMod is in order to specify backup object thereafter to belong to which kind of type of backup.For example, when backup object is the backup operation mode, when then expression makes up Backup Data, should comprise the mode of operation that needs Backup Data; When backup object is the backup numerical result, when then expression makes up Backup Data, should comprise the numerical result that needs Backup Data; When backup object is backup messages, when then expression makes up Backup Data, should comprises the software module inlet that needs Backup Data and drive message; When backup object is backup file stream, when then expression makes up Backup Data, should comprise the backup file data stream that needs Backup Data.
DwDataLen represents the length in follow-up formal Backup Data district, and abData then is the content in concrete Backup Data district, and the length of this section Backup Data can be applied for the content space of corresponding size according to actual dwDataLen.
Through above-mentioned analysis as can be seen, utilize above-mentioned data structure can determine concrete Backup Data object, backup method and concrete Backup Data content.
For example, suppose that the master is the memory block that is scattered in 10 different start addresses with the concrete data member of certain data object of the preliminary data module that is arranged in application layer in the node, then according to the method described above, at first by the position location information of specified data objects such as module No., data object type and data object numbering, and in backup method dwBackupMod field the follow-up Backup Data of definition district.Then according to main backup mode a with node and the predefined discrete internal memory of secondary node, 10 discrete memory blocks are put into the Backup Data district according to the position location information of described established data object, be combined as a complete data information entities, promptly constitute the Backup Data entity.
Step 103 sends the Backup Data behind the described structure to described secondary node.
After Backup Data sends described secondary node from the master with node by main data backup module with node, be arranged in the secondary node application layer and have the data recovery module of the corresponding dwModuleId of backup complete data information entities, be that Backup Data resolves to 10 discrete memory blocks according to backup mode a, and assignment is to the above data object of secondary node, and in each concrete data member of the subobject of described data object.So far realized the backup of discrete internal storage data through said process.
The invention provides the 3rd embodiment, be to be discrete data at need backed up data object, and the concrete backup procedure when described data object does not comprise subobject, the difference part of itself and second embodiment is: when the position location information of specified data object, do not need the numbering according to the subobject of data object.Specific implementation is embodied in the step 101, that is:
Main with node structure Backup Data district; And,
The Backup Data that main each Backup Data with node makes up module and secondary node recovers module and uses unified numbering the in the system separately, need in module, need divide by the backed up data object position location information of specified data object by the backed up data object according to object type and object number.
The data structure of implementation procedure foundation does not comprise following subitem:
Unsigned long dwSubObjectld; / * needs Backup Data object subobject numbering, User Defined */
This is because when there is not the subobject numbering in data object, does not need to use the position that described dwSubObjectId distinguishes needs the Backup Data object.
Second embodiment provided by the invention and the 3rd embodiment provide the specific embodiments that realizes discrete internal storage data centralized backup.And the invention provides the specific embodiments that the 4th embodiment provides source input data by the Backup Data object and source mode of operation to realize the backup of data object net result.Specific implementation process comprises as shown in Figure 3:
Step 302 will determine that the data object after the good position locating information adopts corresponding processing mode to encapsulate, and is built into the Backup Data entity.
In main application layer, when the crucial internal storage data Object Operations that needs are carried out active/standby backup carries out the interface encapsulation, can use the mode of function mode or message with node and secondary node.For example, the Backup Data of specified memory data object in application layer made up in the module, according to dwModuleId, data object type and data object numbering the data object is unified to divide, use the mode of function to encapsulate according to data object number, data subobject being numbered data manipulations such as corresponding data value conducts interviews, modification then, concrete interface function structure is as follows:
void?FunGetParaValur(unsigned?long?dwObjectType，unsigned?long?dwObjectId，unsigned?long?dwSubObjectld，unsigned?long?
*pdwParaVlaue)；
void?FunSetParaValue(unsigned?long?dwObjectType，unsigned?long?dwObjectId，unsigned?long?dwSubObjectId，unsigned?long?dwParaVlaue)。
Wherein dwParaVlaue is meant the data value of the subdata object dwSubObjectId among the data object dwObjectId.
Subject to the foregoing, main carry out uniform operation when the initialization with need backed up data object in node and the secondary node, guaranteeing the initialization back (all finish be initialized as this judgement time point with active and standby two nodes) that finishes, main initial value with this data object in node and the secondary node is consistent.
When the data value of the subobject dwSubObjectId of specified data object dwObjectId need be revised as input parameter dwParaVlaue in leading with the application layer of node, the Backup Data that has dwModuleId in the application layer of master with node makes up in the module, need backed up data according to the main Backup Data interface structure with node and secondary node of above-mentioned definition.When making up Backup Data, the corresponding direct typing of data object locating information is main with the corresponding field in the data backup interface of node and secondary node.The backup method Field Definition is the data value setting operation of certain subobject of Backup Data object dwObjectId, and concrete argument section abData is typing dwObjectType, dwObjectId, dwSubObjectId and dwParaVlaue then.
Step 303 sends the Backup Data entity behind the described structure to described secondary node.
After structure Backup Data entity finishes, the master makes up module notification data backup module with the Backup Data in the node application layer Backup Data entity that builds is backuped on the secondary node with node from main, the Backup Data that has same numbering (dwModuleId) on the secondary node in the application corresponding layer recovers module again according to the data value setting operation (being the FunSetParaValue operation herein) of the dwObjectId that defines in the backup method field in the Backup Data entity that receives, and the Backup Data that need are backed up (is dwObjectType herein, dwObjectId, dwSubObjectId and dwParaVlaue) be revised as the operation of the concrete data value of certain subobject of data object dwObjectId on the secondary node, thus realize the backup of the specified memory data volume between main-standby nodes.
The 5th embodiment provided by the invention, the difference part of itself and the 4th embodiment is, data object does not comprise subobject, at this moment in the step 301, each Backup Data makes up module when the position location information of specified data object in the application layer, the number information of the subobject of data object no longer still, and only use unified application layer module numbering in the system separately, need the object type and the object number of backed up data object need to divide by the backed up data object position location information of specified data object.
In the step 302, will determine that the data object after the good position locating information adopts corresponding processing mode to encapsulate, when making up the Backup Data entity, utilize the interface function of following structure:
Void FunGetParaValur (unsigned long dwObjectType, unsigned long dwObjectId, unsigned long
*PdwParaVlaue)/* Chinese */.
After structure Backup Data entity finished, the master made up module notification data backup module with the Backup Data in the node application layer Backup Data entity that builds is backuped on the secondary node with node from main.
Afterwards, described secondary node is handled corresponding data object according to the processing mode in the described Backup Data entity, and some difference among the process of acquisition need backed up data and the 4th embodiment is specific as follows:
The Backup Data that has same numbering (dwModuleld) on the secondary node in the application corresponding layer recovers the data value setting operation (herein be FunSetParaValue operation) of module according to the dwObjectId that defines in the backup method field in the Backup Data entity that receives, and the Backup Data (being dwObjectType, dwObjectId and pdwParaVlaue herein) of need backups is revised as the operation of the concrete data value of data object dwObjectId on the secondary node, thereby realize the backup of the specified memory data volume between main-standby nodes.
Among the 4th embodiment provided by the invention and the 5th embodiment, the embodiment that realizes data backup by function interface has been described, in the time of on expanding to the message interface aspect, that is to say, when being input to main message when directly backuping on the secondary node with node, directly corresponding data object is done respective handling by secondary node according to the processing mode in the backup messages that receives, with the Backup Data that need to obtain.
As can be seen from the above-described embodiment, the present invention has only changed in the prior art mode that the concrete numerical value to the archive memory data object backs up, but prior art is expanded at the processing mode that internal storage data itself backs up, increased the mode of operation of data object and operating parameter have been backed up or the like backup mode, and described backup mode and Backup Data object be integrated into a Backup Data entity, under this Backup Data entity, can realize main flexibly with the data backup between node and secondary node, for example, the backup of discrete data piece, the backup of the file data that part is revised, the operation backup of data object and module inlet processing messages or the like.Therefore, can be more scattered by the present invention in the main organizational form of the internal storage data that need back up between node and secondary node of using, can be that start address is different, the size of data volume also can be different.The mode of data backup is more flexible, and main-standby nodes backed up data amount is relatively also less, and therefore the efficient of backup is corresponding to higher.
The above; only for the preferable embodiment of the present invention, but protection scope of the present invention is not limited thereto, and anyly is familiar with those skilled in the art in the technical scope that the present invention discloses; the variation that can expect easily or replacement all should be encompassed within protection scope of the present invention.Therefore, protection scope of the present invention should be as the criterion with the protection domain of claim.
Claims (12)
1, a kind of method that realizes data back-up between main-standby nodes is characterized in that, comprising:
A, master will need the processing mode of backed up data object and described data object correspondence to send to secondary node with node;
B, secondary node are handled described Backup Data object according to the processing mode that receives, and obtain corresponding backup information.
2, method according to claim 1 is characterized in that, described steps A specifically comprises:
A1, main with the processing mode structure Backup Data entity of node according to need backed up data object and described data object correspondence;
A2, send the Backup Data entity behind the described structure to described secondary node.
3, method according to claim 2 is characterized in that, when need backed up data object was discrete data, described steps A 1 specifically comprised:
A11, main with node structure Backup Data district; And
Main use separately in the system applies layer unified module to number with node and secondary node, need in module, need divide by the backed up data object by the backed up data object according to object type and object number, and according to the position location information of the information specified data object after dividing;
The data object after A12, master will divide according to described position location information with node and the processing mode of described Backup Data object correspondence are stored in the Backup Data district of described structure, are built into the Backup Data entity.
4, method according to claim 2 is characterized in that, when need backed up data object is discrete data, and described data object is when comprising subobject, and described steps A 1 specifically comprises:
A13, main with node structure Backup Data district; And
Main use separately in the system applies layer unified module to number with node and secondary node, need backed up data object object number according to the subobject of object type, object number and described data object in module need be divided by the backed up data object, and according to the position location information of the information specified data object after dividing;
The data object after A14, master will divide according to described position location information with node and the processing mode of described Backup Data object correspondence are stored in the Backup Data district of described structure, are built into the Backup Data entity.
5, method according to claim 2 is characterized in that, described steps A 1 specifically comprises:
A15, main use separately in the system applies layer unified module to number with node and secondary node, in module, need divide by the backed up data object according to object type and object number, and according to the position location information of the information specified data object after dividing;
Data object after A16, master will divide according to described position location information with node adopts corresponding processing mode to encapsulate, and is built into the Backup Data entity.
6, method according to claim 2 is characterized in that, when need backed up data object comprised subobject, described steps A 1 specifically comprised:
A17, main use separately in the system applies layer unified module to number with node and secondary node, need backed up data object numbering according to the subobject of object type, object number and described data object in module need be divided by the backed up data object, and according to the position location information of the information specified data object after dividing;
Data object after A18, master will divide according to described position location information with node adopts corresponding processing mode to encapsulate, and is built into the Backup Data entity.
7, according to the described any described method of claim 1 to 6, it is characterized in that described processing mode comprises:
The backup operation mode.
8, method according to claim 7 is characterized in that, described backup operation mode comprises:
Function mode of operation or message mode of operation.
9, method according to claim 7 is characterized in that, described processing mode also comprises:
Backup numerical result, backup messages or backup file stream.
10, a kind of system that realizes data back-up between main-standby nodes is characterized in that, comprising:
Main with node and secondary node;
Described master will need the processing mode of backed up data object and described Backup Data object to send to secondary node with node; Secondary node is handled described Backup Data object according to the processing mode that receives, and obtains corresponding backup information.
11, system according to claim 10 is characterized in that, described master comprises with node:
Backup Data makes up the module and the first data backup module;
Described Backup Data makes up module and makes up the Backup Data entity based on the processing mode of need backed up data object and described data object correspondence, and the buffer queue etc. of then described Backup Data entity being put into the first data backup module is to be sent.
12, system according to claim 11 is characterized in that, described secondary node comprises:
Backup Data recovers the module and the second data backup module;
The described second data backup module receives described Backup Data entity, and it is left in the corresponding buffer queue; Described Backup Data recovers module to be handled corresponding data object according to the processing mode of the data object in the Backup Data entity in the buffer queue in the described second data backup module, obtains corresponding backup information.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CNB2006100031113A CN100498729C (en) | 2006-02-14 | 2006-02-14 | Method and system for implementing data back-up between main-standby nodes |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CNB2006100031113A CN100498729C (en) | 2006-02-14 | 2006-02-14 | Method and system for implementing data back-up between main-standby nodes |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN1862502A true CN1862502A (en) | 2006-11-15 |
| CN100498729C CN100498729C (en) | 2009-06-10 |
Family
ID=37389936
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CNB2006100031113A Expired - Fee Related CN100498729C (en) | 2006-02-14 | 2006-02-14 | Method and system for implementing data back-up between main-standby nodes |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN100498729C (en) |
Cited By (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2010145542A1 (en) * | 2009-06-18 | 2010-12-23 | 成都市华为赛门铁克科技有限公司 | Data backup process method, data stroage node device and data storage apparatus |
| CN101944119A (en) * | 2010-09-21 | 2011-01-12 | 国网电力科学研究院 | Real-time event management method for intelligent electronic equipment |
| CN102255741A (en) * | 2010-05-21 | 2011-11-23 | 中兴通讯股份有限公司 | Subscriber service information backup method and device |
| CN105049258A (en) * | 2015-08-14 | 2015-11-11 | 深圳市傲冠软件股份有限公司 | Data transmission method of network disaster-tolerant system |
| CN108572890A (en) * | 2018-04-26 | 2018-09-25 | 赵程章 | Transaction Information synchronous method and device |
-
2006
- 2006-02-14 CN CNB2006100031113A patent/CN100498729C/en not_active Expired - Fee Related
Cited By (9)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2010145542A1 (en) * | 2009-06-18 | 2010-12-23 | 成都市华为赛门铁克科技有限公司 | Data backup process method, data stroage node device and data storage apparatus |
| CN102255741A (en) * | 2010-05-21 | 2011-11-23 | 中兴通讯股份有限公司 | Subscriber service information backup method and device |
| WO2011143891A1 (en) * | 2010-05-21 | 2011-11-24 | 中兴通讯股份有限公司 | Method and apparatus for backup of subscriber service information |
| CN102255741B (en) * | 2010-05-21 | 2015-09-16 | 中兴通讯股份有限公司 | User service information backup method and device |
| CN101944119A (en) * | 2010-09-21 | 2011-01-12 | 国网电力科学研究院 | Real-time event management method for intelligent electronic equipment |
| CN101944119B (en) * | 2010-09-21 | 2013-04-10 | 国网电力科学研究院 | Real-time event management method for intelligent electronic equipment |
| CN105049258A (en) * | 2015-08-14 | 2015-11-11 | 深圳市傲冠软件股份有限公司 | Data transmission method of network disaster-tolerant system |
| CN105049258B (en) * | 2015-08-14 | 2019-02-26 | 深圳市傲冠软件股份有限公司 | The data transmission method of network disaster tolerance system |
| CN108572890A (en) * | 2018-04-26 | 2018-09-25 | 赵程章 | Transaction Information synchronous method and device |
Also Published As
| Publication number | Publication date |
|---|---|
| CN100498729C (en) | 2009-06-10 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN1129831C (en) | Method for setting computer having power saving function into power saving mode when using network | |
| CN1862502A (en) | Method and system for implementing data back-up between main-standby nodes | |
| CN101034364A (en) | Method, device and system for implementing RAM date backup | |
| CN101079902A (en) | A great magnitude of data hierarchical storage method | |
| CN1852101A (en) | Parallel downloading method and terminal | |
| JP2005216298A (en) | Adaptive garbage collection method and device for implementing this method | |
| CN1445787A (en) | Data processing method in large capacity quick electric erasing and writing programmable read-only memory system | |
| CN1763729A (en) | The data processing equipment and the method that are used for flash memory | |
| CN1831781A (en) | Computer system and data backup method in computer system | |
| CN1908907A (en) | A method for improving writing data efficiency and subsystem and system implementing the same | |
| CN1801096A (en) | Method and system for implementing thread sleep in computer system | |
| CN101038562A (en) | Memory device key data backup and recovering system and method thereof | |
| CN1829220A (en) | Mapping method for USB apparatus with storage function on network computer | |
| JP2007226800A (en) | System and method for managing resources by using virtual ids in multiple java application environment | |
| CN1737764A (en) | Task scheduling method for embedded real-time operation system supporting OSEK standard | |
| CN101035010A (en) | Network element device configuration method in the passive optical network | |
| CN100339848C (en) | Method for automatic configuration or restoring of computer system network configuration | |
| CN101030148A (en) | Method and device for realizing double mapping | |
| CN1882152A (en) | Data configuration method for access network device | |
| CN1366636A (en) | Computer system and computer-readable record medium | |
| CN1215422C (en) | Network | |
| CN1447561A (en) | Network management systm, appts. need to be managed, managing device and program thereof | |
| CN1949175A (en) | Method of displacing data in software | |
| CN1863085A (en) | Method and system for ensuring network managment and element configuration data consistency | |
| CN101051267A (en) | Extendable file model and method for managing file model |
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 |
Granted publication date: 20090610 Termination date: 20220214 |
|
| CF01 | Termination of patent right due to non-payment of annual fee |