CN201532631U - Database remote backup system - Google Patents

Database remote backup system Download PDF

Info

Publication number
CN201532631U
CN201532631U CN2009200781496U CN200920078149U CN201532631U CN 201532631 U CN201532631 U CN 201532631U CN 2009200781496 U CN2009200781496 U CN 2009200781496U CN 200920078149 U CN200920078149 U CN 200920078149U CN 201532631 U CN201532631 U CN 201532631U
Authority
CN
China
Prior art keywords
backup
database
data
local
machine room
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Expired - Lifetime
Application number
CN2009200781496U
Other languages
Chinese (zh)
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.)
Shanghai spades Interactive Network Technology Co., Ltd.
Original Assignee
Shengdong Network Technology Development (Shanghai) 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 Shengdong Network Technology Development (Shanghai) Co Ltd filed Critical Shengdong Network Technology Development (Shanghai) Co Ltd
Priority to CN2009200781496U priority Critical patent/CN201532631U/en
Application granted granted Critical
Publication of CN201532631U publication Critical patent/CN201532631U/en
Anticipated expiration legal-status Critical
Expired - Lifetime legal-status Critical Current

Links

Images

Landscapes

  • Information Retrieval, Db Structures And Fs Structures Therefor (AREA)

Abstract

The utility model provides a database remote backup system, which includes a local database, a first remote database, a second remote database, an off-line magnetic tape unit, a finance/bank safeguard system, a local telecom machine room, and a local netcom machine room, and can realize local backup, remote backup and off-line backup respectively. Besides, each remote database (12) and the second remote database include respective script modules which are connected with each other to transfer parameters and variables required during the backup process. The database remote backup system and the method of the utility model can provide a method for building a macroscopical data disaster preparation system which has stronger conformability and can be widely applied to various database backup systems; and through building local and remote multilayer grading backup systems, the utility model can efficiently improve the disaster tolerant strength of the whole database system and ensure the safety and stability of data.

Description

Database remote backup system
Technical field
The utility model relates to a kind of database full-volume standby system, relates in particular to a kind of database remote backup system.
Background technology
Loss of data all is a nightmare concerning big small enterprise, business datum and enterprise's day to day operation running are as close as lips and teeth, lose these data, even it is temporary, also can threaten the competitive edge that enterprise works hard and earns, more may destroy the reputation of your company, maybe may cause expensive lawsuit and claim expense.
After the world-shaking U.S. " 911 " terrorist incident took place, many people turned one's attention to mammon Stanley Morgan.This financial institution of family rents at World Trade Organization's mansion 25 floor, and tragedy has more than 2000 employee just to handle official business in the building when taking place, and company is inflicted heavy losses on.Hold one's own wrist when deeply regretting just when everybody, the said firm announces that global sales department can work in second day as usual.Its main cause is that it has set up Disaster Preparation Center in the New Jersey, and is keeping data backup, thereby ensures running without interruption of company's world business.Importance and immense value that calamity is equipped with are seen some from this.
So-called data calamity is equipped with, and just is meant the data system of setting up a strange land, and this system is available duplicating of local crucial application data.When disaster appears in local data and whole application system, system at least in this locality or the strange land preserve the data of a available key business.These data can be and the duplicating fully in real time of local production data, also can be more backward slightly than local data, but must be available.The major technique that adopts is that data are duplicated, technology such as data transmission and data storage.
Traditional calamity is equipped with system (data backup system), and its system is huge, complex structure, and comparatively harsh to the requirement of equipment, thereby the expense costliness.Simultaneously, these traditional calamities are equipped with system and all are provided with special control system according to separately database set-up mode, and are difficult to and other existing system compatibilities.
Reduce cost along with the increasing traditional forms of enterprises begins consider to use the product of increasing income, the database aspect is especially outstanding with MySQL, and utilizes MySQL also to fail fully to be developed in the application that the database calamity of enterprise-level is equipped with in the system.
Mention backup, some instruments that the well-known MySQL of utilization provided can be finished simple backup, but are equipped with the problem of the construction of system in the calamity of the database that relates to enterprise-level, but without any the existing comparatively successful precedent of putting into practice.Therefore, for the basis that utilizes MySQL, there has been following demand in undertaking of construction level data library backup system:
You only needed a backup command or a backup tool just can finish when ■ had only several databases when you,
■ is when you have database about hundred, and you can have to write script and help you to finish automatically,
■ works as you more multiple database, and you can find to safeguard every day this backup list, opening and closing, and adjusting some backup will become a bottleneck, and this moment, you needed a web system more easy system to finish these line services,
When ■ becomes increasingly complex when business system, different storage engines, different logics, different backup keeps demand miscellaneous such as interval all can make our constantly extended function on standby system
■ is when safeguarding the back-up job of MySQL and Oracle simultaneously, and this moment, you needed a platform can hold different DB Backup demands,
How ■ ensures this locality after the backup details of these bottoms all realizes, the disaster of this city still has backed up data to recover after taking place, and this just relates to how the data of local backup are kept with the strange land, city different city, or even bank's preservation, a whole set of strategy
The final foundation that ■ solves disaster at last is that the data after the disaster are recovered, so how to formulate data recovers, and the strategy of disaster manoeuvre, and record experience,
Above-mentioned these all be general data storehouse operation and maintainer in practice process the problem that can generally run into, and the demand that these are general is integrated, and solve targetedly, step by step the distillation, like this from simple order line backup to finally obtain one the cover complete calamity be equipped with system.More than these realize details from backups of the bottom, to the function that satisfies various backup requirements, arrive the disaster-tolerant recovery strategy, just constituted calamity together and be equipped with system.
The utility model content
The purpose of this utility model is to provide a kind of stable, reliable and high database remote backup system and method for compatibility, it mainly utilizes existing MySQL data base management system (DBMS), and be compatible with the oracle database management system, by setting up the network platform, employing is with strange land, city, the multiple remote backup modes coexist in strange land, different city, and the utilization of uniting by online, offline storage equipment, and the reasonable disposition and the integrated management of data transmission between the various data platforms realized.
The technical scheme that database remote backup provided by the utility model system is taked is as follows:
The utility model provides a kind of database remote backup system, comprising: with city data 11, the first different city databases 12, the second different city databases 13, off-line magnetic tape station 20, finance/bank's safeguard system 30, local telecommunication machine room 41, local network machine room 42;
Described local telecommunication machine room 41 and local network machine room 42 be connected the backup local data with city database 11;
Describedly connect successively, back up the strange land data mutually with city database 11, the first different city databases 12, the second different city databases 13;
Describedly all be connected the schedule backup off-line data with off-line magnetic tape station 20 with city database 11, the first different city databases 12, the second different city databases 13;
Describedly include separately script module 10 with city database 11, the first different city databases 12, the second different city databases 13, be connected to each other between each script module 10, transmission backup is carried out the required parameter of process, variable.
Above-mentioned database remote backup system, wherein, each script module 10 is connected with a management end, by the input media of management end, manually sets the instruction of standby system.
Above-mentioned database remote backup system wherein, describedly transfers to first different city database 12 by network with Backup Data with city database 11; The first different city database 12 transfers to the first different city database 13 by network with Backup Data; The second different city database 13 transfers to Backup Data with city database 11 by network, forms circulation long-distance data backup system.
Above-mentioned database remote backup system, wherein, described off-line data is stored in the off-line tape of off-line magnetic tape station 20, and described off-line tape is deposited in described finance/bank's safeguard system.
Above-mentioned database remote backup system, wherein, described local telecommunication machine room 41 all with city database 11 is built up in the different location respectively with local network machine room 42.
In the backup method of database remote backup of the present utility model system, between the database machine room in strange land, described different city, the data of transmission primaries the previous day are to another strange land, different city database machine room weekly;
Strange land, different city database machine room is also realized local backup, the local backup machine room in city, machine room place, backup data transmitting Value Data storehouse in the city at its place.
The utility model also provides the backup method of a kind of database remote backup system, wherein, described local telecommunication machine room 41 and local network machine room 42, carry out local backup with described with city database 11, and the intersection backup policy is adopted in backup, controls twice continuous backup and backs up respectively on different local machine rooms.
The utility model also provides the backup method of a kind of database remote backup system, and wherein, the cycle of local backup is every other day carried out full backup one time for per hour carrying out incremental backup one time.
The utility model also provides the backup method of a kind of database remote backup system, wherein, comprises the steps:
Step 500, the beginning step;
Step 501 is set public variable, comprising: Host List, know the date, backup date;
Step 502, operation backup address script;
Step 503 is set backup address;
Step 507 begins to remove expired backup process.
The utility model also provides the backup method of a kind of database remote backup system, and wherein, when judging that backup address 2 does not exist in the backup address script in the step 502, setting backup address 2 be the target backup address, and the file of removing backup address 1; When backup address 2 existed, selecting backup address 1 was target backup address and the file of removing backup address 2.
The erection method that database remote backup system and method for the present utility model can provide a kind of data calamity of macroscopic view to be equipped with system, and it has stronger conformability, can be widely used in the various database backup systems.Especially pass through with multiple remote backup means such as strange land, city, strange land, different city, off-line tapes, set up the standby system of multi-layer classification, can effectively improve the disaster tolerance intensity of entire database system, even under the situation that various disaster incidents take place, can ensure that also database can return to certain hour state before, has ensured safety of data and stability.
Description of drawings
Fig. 1 is the construction module figure of database remote backup of the present utility model system;
Fig. 2 is the main process flow diagram of database remote backup of the present utility model system;
Fig. 3 is the MySQL backup process flow diagram of database backup system of the present utility model;
Fig. 4 is the Oracle backup process flow diagram of database backup system of the present utility model;
Fig. 5 is the detail flowchart of database remote backup of the present utility model system;
Fig. 6 is the link block figure of database remote backup of the present utility model system.
Embodiment
As shown in Figure 1, be a kind of preferred network architecture module map of database backup system of the present utility model.Database backup system of the present utility model comprises with city database 11, different city database 12, different city database 13, off-line magnetic tape station 20, finance/bank's safeguard system 30, local machine room 41 (local telecommunication machine room), local machine room 42 (local network machine room).Wherein, be connected with local backup machine room 42 mutual networks with local backup machine room 41, the Backup Data on the database is transferred to the local backup machine room, promptly finish the local backup flow process with city database 11.Local backup can customization backup week period interval, for example set and carry out incremental backup every half an hour, 1 hour or 2 hours etc., every day or every other day carry out full backup, Backup Data is stored on the local machine room.The intersection backup policy is adopted in described backup, promptly for example, data backup for the first time is on local backup machine room 41, then data backup for the second time is on another local backup machine room 42, back up on the local backup machine room 41 for the third time again, so circulation intersects, to maximally utilise the storage capacity of backup machine room.
Because the frequent data exchange of home server, it needs data quantity stored can constantly increase as time passes, therefore need take above-mentioned local backup flow process, to transfer to a local backup machine room 41 or 42 with the Backup Data on the city local data base machine room 11 with the city, preferred this database machine room 11 and local backup machine room 41,42 are erected at different places, promptly so-called " with the strange land, city ", mainly be not influenced by same external condition for the ease of placing database machine room and local backup machine room, as: network failure, power supply trouble, various natural and man-made calamities such as communication cable damage, thereby improved the disaster tolerance intensity of backup machine room, the data that can not cause all to back up machine rooms because of the fault of local data base machine room suffer damage and have lost the value that backs up.
In addition, between the database machine room in strange land, different city, also need to carry out remote backup, for example: will set some cycles with the Backup Data of city database machine room 11, and transfer to strange land, different city database machine room 12.Equally, strange land, different city database machine room 12 also can be realized local backup in the city at its place, the local backup machine room (not shown) in city, machine room 12 place, backup data transmitting Value Data storehouse, its structure operational mode with similar between city database machine room 11 and the home server 41,42.Described backup cycle should be greater than the cycle of local full backup, as implementing remote backup 1 time or 2 times weekly.Simultaneously, strange land, different city database machine room 12 also can be provided with according to some cycles and carry out the Backup Data transmission to another strange land, different city database machine room 13, thereby has dynamically formed the data remote backup.In like manner, become strange land database machine room 13 also its Backup Data can be resent to, constituted a circulation with strange land, city database machine room 11.
Simultaneously, each database machine room 11,12,13 according to certain cycle, is concentrated its Backup Data to be transferred to off-line magnetic tape station 20 and to carry out offline backup.This needed greater than the remote backup cycle in cycle, can be set at per 2 weeks or carry out one time offline backup every 1 month.Data storage after the offline backup is on the off-line tape, and described off-line tape can entrust finance/bank's safeguard system to deposit.
In above-mentioned framework, the quantity of each database machine room is not limited to three, can be erected between the database machine room in a plurality of cities, as five or more according to actual conditions.And home server only is divided into local telecommunication machine room 41 and local network machine room 42 according to existing two kinds of main Network Provider in Fig. 1, but can also provide more local machine room at each supplier in actual applications, and in the database of the enterprise-level that provides Internet resources to share, the quantity of the main frame that each machine room provided is more, usually reach tens even up to a hundred, and be provided with specific server according to actual conditions and diverse network supplier and use for it.
As shown in Figure 2, be the detail flowchart of the backup-step that database backup system of the present utility model adopted, comprise following each step:
Step 100, the backup flow process begins.
Step 101, initial parameter is set, and comprises MySQL backup parameter and Oracle backup parameter.
Step 102, the backup control documents generates backup process.
Step 103 generates the total parameter of backup control documents.
Step 104, whether the total parameter of inquiry backup control documents exists.As not existing, promptly total parameter generates failure, then enters step 160, and the backup flow process finishes; As existing, then enter next step 105.
Step 105, whether inquiry MySQL and Oracle backup command exist.If do not exist, promptly described parameter initialization is failed or other faults is arranged, and then enters step 160; If exist, then carry out backup command, and enter next step 106.
Step 106 is removed the space in the backup file.
Step 107 reads delegation's control documents record.
Step 108 generates the backup parameter.
Step 109 is obtained name of remote host.As fail and obtain, then enter step 160; Enter step 110 after obtaining successfully.
Step 110 is obtained the current ROLE (task) of this distance host machine.
Step 120 is carried out ROLE (task).Enter MySQL process and Oracle process subsequently respectively.
Step 121, the MySQL process first step is obtained MySQL backup parameter.
Step 122 imports the MySQL backup script.
Step 123 is carried out the MySQL backup script.
Step 131, the Oracle process first step is obtained Oracle backup parameter.
Step 132 imports the Oracle backup script.
Step 133 is carried out the Oracle backup script.
Step 140 after MySQL and Oracle process are all finished, reads the next line configuration information.
Step 150 judges whether to be last column.As be last column, then enter step 160; As not being last column, then getting back to step 107 and continue to carry out subsequent operation.
Step 160, the backup flow process finishes.
As shown in Figure 3, be the MySQL backup process flow diagram of database backup system of the present utility model, it specifically comprises the steps:
Step 200, MySQL backup flow process begins.
Step 201, initial parameter is set.
Step 202, the example on the traversal server.
Step 203 obtains backup information according to SOCK (port) to monitoring equipment, can comprise corresponding first backup address and second backup address.
Step 204 judges whether second backup address is set.If set, then enter step 205; Otherwise, enter step 208.
Step 205, because second backup address is set, whether contrast Last Backup address is consistent with first backup address.As inconsistent, then enter step 206; As unanimity, then enter step 207.
Step 206, inconsistent through judging the Last Backup address and first backup address, then this backup address still is made as first backup address, enter step 209 then.
Step 207, consistent through judging the Last Backup address with first backup address, then this backup address is made as second backup address, enter step 209 then.
Step 208 is not set through judging second backup address, then backup address is made as first backup address.
Step 209 generates this backup information.
Step 210, whether backup directory exists.If backup directory does not exist, then enter step 211; If backup directory exists, then enter step 213.
Step 211 is created backup directory.If backup directory is created failure, enter step 212; Otherwise, enter step 213.
Step 212, backup directory is created failure, and output error message stops backup this time, enters step 240.
Step 213 is judged and is carried out MySQL backup management order, as: MySQL, instruments such as MySQLadmin and MySQLdump.Then enter step 214 as carrying out; Otherwise, enter step 215.
Step 214 can't be carried out owing to judge MySQL backup management order, and output error message stops backup this time, and enters step 240.
Step 215 after the MySQL administration order is carried out, is selected information such as backup mode, backup database, destination address, placement catalogue, can determine by the direct specify default information of backup management system or by outside input information.
Step 216 judges whether to back up all databases.According to actual input condition, judge to enter which kind of backup mode, when input--during the databases order, enter step 217; When input-A orders, enter step 218.
Step 217 according to selected database, is carried out each data of database backup.Enter step 220 subsequently.
Step 218 backs up all databases, enters step 220 afterwards.
Step 220 is selected concrete backup mode.It is selective to list file names with each branch, but comprises that step 221-226 supplies concrete backup mode equality selection in 6.
Step 221, the S_INNODB_DUMP pattern is for adopting the backup flow process of INNODB instrument and MySQL SlaveInnoDB DUMP strategy.Enter step 230 after finishing backup.
Step 222, the M_INNODB_DUMP pattern be to adopt INNODB instrument and MySQL MasterInnoDB DUMP strategy, enters step 230 after finishing backup.
Step 223, the T_STRUCTURE_DUMP pattern is for adopting the backup flow process of MySQL STRUCTUREDUMP strategy.Enter step 230 after finishing backup.
Step 224, the S_MYISAM_TAR pattern is for adopting the backup flow process of MYISAM instrument and MySQL SlaveMyISAM TAR strategy.Enter step 230 after finishing backup.
Step 225, the S_MYISAM_DUMP pattern is for adopting the backup flow process of MYISAM instrument and MySQL SlaveMyISAM DUMP strategy.Enter step 230 after finishing backup.
Step 226, the M_ARCHIVE_TAR pattern is for adopting the backup flow process of MySQL Master ARCHIVE TAR strategy.Enter step 230 after finishing backup.
Step 230 judges whether to exist the not SOCK of traversal, if exist, then returns step 203 and continues operation; If do not exist, then enter step 240.
Step 240, flow process finishes.
As shown in Figure 4, the Oracle backup process flow diagram for database backup system of the present utility model specifically comprises the steps.
Step 300, Oracle backup flow process begins.Corresponding to the Oracle backup command.
Step 301 is obtained environmental variance.
Step 302 judges whether second backup address exists.If exist, then enter step 303; If do not exist, enter step 307.
Step 303 is when judging that second backup address exists, and then compares the Last Backup address and first backup address.When the Last Backup address equals first backup address, enter step 304; When the Last Backup address is not equal to first backup address, enter step 305.
Step 304 because the Last Backup address equates with first backup address and second backup address exists, according to intersecting the principle that backs up, is deposited backup to second backup address.Enter step 306 subsequently.
Step 305 is because the Last Backup address then deposits backup in first backup address with backup address is different for the first time.Enter step 306 subsequently.
Step 306 saves as this backup address " Last Backup address ", supplies follow-up recycle ratio than usefulness.Enter step 307.
Step 307 after second backup address does not exist or finished backup according to second backup address, is promptly carried out and is obtained the variable step.
Step 308 judges whether the remote backup catalogue exists.If do not exist, then enter step 309; If exist, then enter step 312.
Step 309 because the remote backup catalogue does not exist, is then created described remote backup catalogue.Enter step 310.
Step 310 judges whether directory creating is normal.If unusual, then enter step 311; If normal, then enter step 312.
Step 311, when judging that directory creating is unusual, output error message then, and enter step 330.
Step 312, input parameter comprises backup mode, backup database, destination address, places catalogue etc., and checks parameter validity.If input parameter is invalid, then enter step 313.If input parameter is effective, then enter step 314.
Step 313 is because the input parameter inspection is invalid, so behind the output error message, enter step 330.
Step 314, input parameter is effective, then begins to back up according to input parameter, generates backup file.
Step 315 is transmitted described backup file.
Step 316, the transmission situation is judged.If the transmission situation takes place unusual, then enter step 317; If the transmission situation is normal, then continue to enter step 318.
Step 317 when judging that the transmission situation is unusual, produces error reporting information, and exports this error message.Enter step 330 subsequently.
Step 318 checks whether backup file exists.If backup file does not exist, then enter step 319; If backup file exists, continue to enter step 320.
Step 319, backup file does not exist, and then generates corresponding error reporting information, and transmits this error message.Enter step 330 subsequently.
Step 320 is calculated backup size.
Step 321 shows the backup size that calculates, and selects to adopt which kind of mode to back up.If select " automatically " backup, then enter step 322; If select " manually " backup, then enter step 323.
Step 322 is carried out the automated back-up operation, upgrades automated back-up information.Enter step 324.
Step 323 enters manual backup operation and waits for process, according to the corresponding subsequent command-execution operation.Upgrade automated back-up information.Enter step 324.
Step 324 is finished backup, knows backup file.
Step 325, backup procedure finishes.
As shown in Figure 5, be the detail flowchart of database remote backup of the present utility model system, it specifically comprises the steps:
Step 500, the beginning step is carried out the remote backup instruction of different city.
Step 501 is set public variable, comprising: Host List, know the date, backup date.
Step 502, operation backup address script.Judge whether backup address 2 files exist, and do not exist as backup address 2 files, then enter step 503; Exist as backup address 2 files, then enter step 505.
Step 503, setting backup address 2 is the target backup address.
Step 504 is removed backup address 1 file.
Step 505 is removed backup address 2 files.
Step 506, setting backup address 1 is the target backup address.
Step 507 begins to remove expired backup process.
As described in Figure 6, be the link block key diagram of database remote backup of the present utility model system, comprising with city database 11, different city database 12, different city database 13 wherein also includes strange land, different city DB Backup script module 10.This script module is set in the database of corresponding strange land, and by carrying out the detailed step of remote backup system, comes the strange land automated back-up of fulfillment database system.Each strange land database 12,13 and with connecting by communication network between the city database 11, with backup data transmitting.And interconnect between each script module 10 and information such as transmission backup address or concrete backup script order, before the backup real process begins, carry out earlier connecting early stage, to confirm concrete backup process.
Script module also is connected (not shown) with a management end, can realize manual backup by the instruction of management end input.When needs impose a condition when backing up, backup mode, select target address, backup file size, date and the BACKUP TIME that can control and regulate whole backup process by default parameter of management end and variable then, and automated back-up and backup with good conditionsi.
Above-mentioned; only be preferred embodiment of the present utility model; and be not used in and limit protection domain of the present utility model; technology general knowledge according to this area; in conjunction with the existing technology in this area; to the conspicuous modifications and variations that foregoing is done, it also should fall into protection domain of the present utility model.

Claims (5)

1. a database remote backup system is characterized in that, comprising: with city database (11), the first different city database (12), the second different city database (13), off-line magnetic tape station (20), finance/bank's safeguard system (30), local telecommunication machine room (41), local network machine room (42);
Described local telecommunication machine room (41) and local network machine room (42) be connected the backup local data with city database (11);
Described with city database (11), the first different city database (12), the second different city database (13) connects successively, backs up the strange land data mutually;
Described with city database (11), the first different city database (12), the second different city database (13) all is connected the schedule backup off-line data with off-line magnetic tape station (20);
Described with city database (11), the first different city database (12), the second different city database (13) includes script module (10) separately, and each script module is connected to each other between (10), and transmission backup is carried out the required parameter of process, variable.
2. database remote backup as claimed in claim 1 system is characterized in that each script module (10) is connected with a management end, by the input media of management end, manually sets the instruction of standby system.
3. database remote backup as claimed in claim 1 system is characterized in that, describedly by network Backup Data is transferred to the first different city database (12) with city database (11); The first different city database (12) transfers to the first different city database (13) by network with Backup Data; The second different city database (13) transfers to Backup Data with city database (11) by network, forms circulation long-distance data backup system.
4. database remote backup as claimed in claim 1 system is characterized in that described off-line data is stored in the off-line tape of off-line magnetic tape station (20), and described off-line tape is deposited in described finance/bank's safeguard system.
5. database remote backup as claimed in claim 1 system is characterized in that, described local telecommunication machine room (41) all with city database (11) is built up in the different location respectively with local network machine room (42).
CN2009200781496U 2009-07-13 2009-07-13 Database remote backup system Expired - Lifetime CN201532631U (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN2009200781496U CN201532631U (en) 2009-07-13 2009-07-13 Database remote backup system

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN2009200781496U CN201532631U (en) 2009-07-13 2009-07-13 Database remote backup system

Publications (1)

Publication Number Publication Date
CN201532631U true CN201532631U (en) 2010-07-21

Family

ID=42528032

Family Applications (1)

Application Number Title Priority Date Filing Date
CN2009200781496U Expired - Lifetime CN201532631U (en) 2009-07-13 2009-07-13 Database remote backup system

Country Status (1)

Country Link
CN (1) CN201532631U (en)

Cited By (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN103959710A (en) * 2012-11-22 2014-07-30 华为技术有限公司 Method, device and system for backing up device information
CN104850471A (en) * 2015-05-12 2015-08-19 浪潮电子信息产业股份有限公司 Itanium platform-based method for realizing two places and three centers of DB2 database
CN106452911A (en) * 2016-11-10 2017-02-22 郑州云海信息技术有限公司 City-wide disaster backup system
CN108009046A (en) * 2017-11-21 2018-05-08 广州慧睿思通信息科技有限公司 A kind of method of ORACLE data remote backup

Cited By (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN103959710A (en) * 2012-11-22 2014-07-30 华为技术有限公司 Method, device and system for backing up device information
CN103959710B (en) * 2012-11-22 2018-01-23 华为技术有限公司 A kind of method of facility information backup, equipment and system
CN104850471A (en) * 2015-05-12 2015-08-19 浪潮电子信息产业股份有限公司 Itanium platform-based method for realizing two places and three centers of DB2 database
CN106452911A (en) * 2016-11-10 2017-02-22 郑州云海信息技术有限公司 City-wide disaster backup system
CN108009046A (en) * 2017-11-21 2018-05-08 广州慧睿思通信息科技有限公司 A kind of method of ORACLE data remote backup

Similar Documents

Publication Publication Date Title
CN101923498A (en) Database full-volume automatic backup system and method
CN101957783A (en) Database offsite backup system and method
CN101963928A (en) System and method of database full backup
CN101923497A (en) Enterprise-level database backup system and method
CN103853837B (en) Oracle does not stop the table level back-up restoring method of Production database automatically
CN104809510A (en) Building method of ticket pool middleware for providing ticket support, ticket purchasing and ticket locking methods
CN201532631U (en) Database remote backup system
US20060149991A1 (en) Concept of zero-dense wave division multiplex disaster recovery process
CN101930431A (en) Database backup information clearing system and method
CN109101364A (en) Double center dual-active data processing systems and method
CN108874590A (en) A kind of system of cloud host automated back-up and recovery
CN101996094A (en) Method and system for managing distributed resources
CN114780301B (en) Disaster recovery method and system supporting multi-cloud production environment
CN201508546U (en) Enterprise-level database backup system
CN201503584U (en) Database total automatic backup system
CN101996282B (en) Multi-mode data transformation service (DTS) interconnection method based on power flow matching and computation model splicing
CN102289506A (en) Mail system backup method
CN201532630U (en) Database full backup system
Gray et al. Distributed computer systems: Four case studies
CN106878063A (en) A kind of method for recovering network topological sum business configuration data from network element
CN108153621B (en) Cloud disaster backup emergency switching management system
JP2000259505A (en) Inter-system data backup system and its method
CN103679615A (en) High-availability logistics information management system based on distributed system architecture
CN111314129B (en) High-availability architecture based on file type storage service
CN111352768A (en) Enterprise database backup system

Legal Events

Date Code Title Description
C14 Grant of patent or utility model
GR01 Patent grant
C41 Transfer of patent application or patent right or utility model
TR01 Transfer of patent right

Effective date of registration: 20160523

Address after: 201800, room 8, building 25, 2260 North Street, Wai Gang Town, Shanghai, Jiading District

Patentee after: Shanghai spades Interactive Network Technology Co., Ltd.

Address before: 2415 room 2, Gangcheng Road, Pudong New Area, Shanghai, 201204

Patentee before: Shengdong Network Technology Development (Shanghai) Co., Ltd.

CX01 Expiry of patent term
CX01 Expiry of patent term

Granted publication date: 20100721