CN101963928A - System and method of database full backup - Google Patents
System and method of database full backup Download PDFInfo
- Publication number
- CN101963928A CN101963928A CN2009100551836A CN200910055183A CN101963928A CN 101963928 A CN101963928 A CN 101963928A CN 2009100551836 A CN2009100551836 A CN 2009100551836A CN 200910055183 A CN200910055183 A CN 200910055183A CN 101963928 A CN101963928 A CN 101963928A
- Authority
- CN
- China
- Prior art keywords
- backup
- database
- address
- data
- script
- 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
Abstract
The invention provides a system of database full backup, comprising a one-city database, a first different-city database, a second different-city database, an off-line magnetic tape unit, a finance/bank safety protection system, a local telecommunication machine room and a local Netcom machine room, wherein, the local telecommunication machine room comprises at least one host which is connected with an input end and a display end, and is connected with at least one remote machine through a network; and in addition, the host also comprises an environment variable module and a backup list module, wherein, the environment variable module stores public variable, an IP address, a port and a control document, and the backup list module stores a backup list, a backup document, a backup script and a cancel script. The invention can be widely applied in various database backup systems, simultaneously adopts backup and cancels various backup data selectively, can lead the backup system to have higher flexibility and operability, and realizes the optimizing configuration of resources.
Description
Technical field
The present invention relates to a kind of database full-volume standby system, relate in particular to system and the method thereof of carrying out backup separately and cancellation separately in a kind of database full-volume standby system.
Background technology
Loss of data all is a bad dream 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 that relates to large database, 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.
Summary of the invention
The object of the present invention is to provide a kind of safe, database full-volume standby system and method efficiently, it mainly utilizes existing MySQL data base management system (DBMS), and is compatible with in the oracle database management system.
The technical scheme that enterprise-level database backup system provided by the present invention is taked is as follows:
The invention provides a kind of database full-volume standby system, comprising: with city database 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;
Wherein, the local telecommunication machine room comprises at least one main frame 40, and described main frame 40 is connected with input end 49 and display end 48, and connects at least one remote machine 10 by network.
Above-mentioned database full-volume standby system, wherein, described main frame includes environmental variance module 47 and backup list module 46, described environmental variance module 47 storage public variables, IP address, port and control documents, described backup list module 46 storage backup tabulations, backup file and backup script and cancellation script.
Above-mentioned database full-volume standby system, wherein, described remote machine 10 is single main frame.
Above-mentioned database full-volume standby system, wherein, described remote machine 10 is group of server.
Above-mentioned database full-volume standby system, wherein, described remote machine 10 is a network connection port, and further is connected on multiple host or the data server by described port.
Above-mentioned database full-volume standby system is characterized in that, 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;
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.
The present invention also provides a kind of database full-volume backup method, and wherein, described backup method comprises selectivity execution backup process or cancellation process, in order to back up the backup process of the selected partial data of selected partial data or cancellation.
Above-mentioned database full-volume backup method, wherein, described backup process and cancellation process are selected Oracle pattern or MySQL pattern according to the type of remote machine 10 from concrete data back up method.
Above-mentioned database full-volume backup method, wherein, described backup process specifically comprises the steps:
Step 400, backup process begins;
Step 401 is set public variable;
Step 402 is obtained independent backup list;
Step 403 judges whether independent backup list is empty;
Step 405 reads the instruction of the row of first in the tabulation;
Step 406 is obtained IP address and port numbers from delegation's instruction of backup list;
Step 407 judges whether the 2nd IP address is empty;
Step 408 judges whether an IP address and the 2nd IP address equate;
Step 412 is removed temporary file;
Step 413 reads the delegation in the control documents;
Step 414 is obtained the backup variable;
Step 415 is by setting up telecommunication;
Step 416 obtains type of backup;
Step 418, the output environment variable is to backup script in the Mysql backup;
Step 419, output MySQL backup script;
Step 420, the output environment variable is to backup script in the Oracle backup;
Step 421, output Oracle backup script;
Step 422, the backup information that output is being carried out;
Step 423 is carried out backup;
Step 424 is judged backup instances;
Step 425 reads next line, and is circulated to step 413;
Step 426 is upgraded backup procedure information for finishing, and exports display end to;
Step 427, backup process finishes.
Above-mentioned database full-volume backup method, wherein, described cancellation process specifically comprises the steps:
Step 503 judges whether the row of cancellation backup list is empty;
Step 504 is obtained IP address and port from the cancellation backup list;
Step 505 judges whether the 2nd IP address is empty;
Step 506 judges whether an IP address and the 2nd IP address equate;
Step 510 reads the delegation in the public environment variable;
Step 511 judges whether the public environment row of variables that is read is empty;
Step 512 obtains variable from the row that reads;
Step 513 judges whether remote machine exists;
Step 515 is obtained the remote machine type;
Step 516 is obtained the PID of backup process;
Step 525 judges whether next line is empty;
Enterprise-level database backup system of the present invention and method can provide a kind of data calamity of macroscopic view to be equipped with the erection method of system, and it has stronger conformability, can be widely used in the various database backup systems, in the different database as Oracle and MySQL framework.And pass through the foundation of the standby system of its 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.Simultaneously, optionally adopt backup and cancel various Backup Datas, can make standby system have greater flexibility and operability, and realize distributing rationally of resource.
Description of drawings
Fig. 1 is the construction module figure of database backup system of the present invention;
Fig. 2 is the main process flow diagram of database backup system of the present invention;
Fig. 3 is the MySQL backup process flow diagram of database backup system of the present invention;
Fig. 4 is the Oracle backup process flow diagram of database backup system of the present invention;
Fig. 5 is the execution module figure of database full-volume standby system of the present invention;
Fig. 6 is the independent backup process flow diagram of database full-volume standby system of the present invention;
Fig. 7 is the independent cancellation process flow diagram of database full-volume standby system of the present invention.
Embodiment
As shown in Figure 1, be a kind of preferred network architecture module map of database backup system of the present invention.Database backup system of the present invention 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 invention adopted, comprise following each step:
Step 101, initial parameter is set, and comprises MySQL backup parameter and Oracle backup parameter.
Step 103 generates the total parameter of backup control documents.
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 122 imports the MySQL backup script.
Step 123 is carried out the MySQL backup script.
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.
As shown in Figure 3, be the MySQL backup process flow diagram of database backup system of the present invention, it specifically comprises the steps:
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 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 211 is created backup directory.If backup directory is created failure, enter step 212; Otherwise, enter step 213.
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 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.
As shown in Figure 4, the Oracle backup process flow diagram for database backup system of the present invention specifically comprises the steps.
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 313 is because the input parameter inspection is invalid, so behind the output error message, enter step 330.
Step 315 is transmitted described backup file.
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 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.
Referring to accompanying drawing 5, be the execution module figure of database full-volume standby system of the present invention.Described concrete execution module system, for separate unit main frame 40, it includes environmental variance module 47, be used to store the public variable of setting, read variable, especially storing IP address and port, and preserve control documents etc., also comprise backup list module 46, be used for storage backup tabulation, backup file and backup script and cancellation script etc.In addition, main frame 40 also is connected with input end 49, in order to import extraneous instruction, in order to optionally to carry out adjustable non-full dose data backup.And display end 48, be used for display environment variable module 47 and backup list module 46 and carrying out the various error messages that concrete backup or cancellation process produce.Simultaneously, input end 49 and display end 48 have constituted management end jointly, can realize the various concrete operations for the main frame backup procedure.
As shown in Figure 6, be the backup process flow diagram of database full-volume standby system of the present invention.It has comprised following steps:
Step 400, the beginning step, backup process begins.
Step 401 is set public variable.
Step 402 is obtained independent backup list, promptly requiredly carries out the tabulation of independent backed up data, when selecting entirely, then is set at full backup.
Step 403 judges whether independent backup list is empty.When independent backup list is sky, then enter step 404; If when backup list is not empty separately, enter step 405.
Step 404, the error message of inciting somebody to action " backup list is for empty separately " is back to display end, and directly enters step 427.
Step 405 reads the row of first in the tabulation, the significant first row instruction that maybe can read.
Step 406 is obtained IP address and port numbers from delegation's instruction of backup list.
Step 407 judges whether the 2nd IP address is empty.If the 2nd IP address non-NULL then enters step 408; If the 2nd IP address is empty, then enter step 411.
Step 408 judges whether an IP address and the 2nd IP address equate.As the unequal step 409 that then enters, as equating then to enter step 410.
Step 409, be appended to the 2nd IP address, port configuration information in the control documents after, enter step 411.
Step 410, append port in the interim character string after, enter step 411.
Step 411 is an IP address with the 2nd IP address setting.
Step 412 is removed temporary file.
Step 413 reads the delegation in the control documents.If control documents is empty, then directly enter step 427; If control documents is not empty, then enter step 414.
Step 414 from the row of the control documents that reads, is obtained the backup variable, as IP address, port information etc.
Step 415 by setting up telecommunication, judges whether remote machine is normal.If set up communication failure, then be designated unusually, and enter step 424; Communicate by letter successfully if set up, be designated normal, progressive as step 416.
Step 416 obtains type of backup, by the information of input equipment input.
Step 417 is judged the type of backup of importing, and is that the Mysql backup then enters step 418 as the input type of backup; As to import type of backup be that Oracle backup then enters step 420.
Step 418, the output environment variable is to backup script in the Mysql backup.
Step 419, output MySQL backup script.
Step 420, the output environment variable is to backup script in the Oracle backup.
Step 421, output Oracle backup script.
Step 422, the backup information that output is being carried out.
Step 423 is carried out backup.
Step 424 is judged backup instances, checks whether the next line in the control documents is empty, if next behavior sky then enters step 426; If next line is not empty, then enter step 425.
Step 425 reads next line, and enters step 413, realizes a circulation.
Step 426 is upgraded backup procedure information for finishing, and exports display end to, and enters step 427.
Step 427, flow process finishes.
As shown in Figure 7, the independent cancellation process flow diagram for database full-volume standby system of the present invention specifically comprises the steps:
Step 500 is cancelled flow process separately and is begun.
Step 501 obtains the public environment variable.
Step 502 generates the cancellation backup list.
Step 503 judges whether the row of cancellation backup list is empty.If empty, then enter step 526; If be not empty, then enter step 504
Step 504 is obtained IP address and port from the cancellation backup list.
Step 505 judges whether the 2nd IP address is empty.If the 2nd IP address non-NULL then enters step 506; If the 2nd IP address is empty, then enter step 509.
Step 506 judges whether an IP address and the 2nd IP address equate.As the unequal step 507 that then enters, as equating then to enter step 508.
Step 507 is appended to the 2nd IP address, port configuration information in the control documents.
Step 508 is appended port in interim character string.
Step 509 is an IP address with the 2nd IP address setting.
Step 510 reads the delegation in the public environment variable.If read success, then enter step 511; If read failure, then return step 503 once more.
Step 511 judges whether the public environment row of variables that is read is empty.If what read is null, then enter step 526; If the capable non-NULL that reads then enters step 526.
Step 512 obtains variable from the row that reads.
Step 513 judges whether remote machine exists.If remote machine does not exist, then enter step 514; If remote machine exists, then enter step 515.
Step 514 to the display end output error message, is informed that remote machine does not exist, and is directly entered step 526.
Step 515 is obtained the remote machine type, and then judges and should adopt MySQL pattern or Oracle pattern.
Step 516 after selecting to adopt the MySQL pattern, is obtained the PID (process indications) of backup process.
Step 519 after selecting to adopt the Oracle pattern, is obtained backup process PID (process indications).
Step 525 is judged, when next line is sky, enters step 526; When next line is not sky, then enter step 511, circulate.
By two kinds of above-mentioned flow processs, realized in the Database Backup process the operation of indivedual Backup Datas, comprise only operating part data backup or the backup of cancellation partial data.And when carrying out, can also select suitable data storehouse pattern and call corresponding script, realize the optimization backup process or the cancellation process of data according to the type of remote machine by original environmental variance that is provided with and backup list.
Above-mentioned, only be preferred embodiment of the present invention, and be not intended to limit the scope of the invention; 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 scope of the present invention.
Claims (10)
1. a database full-volume standby 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);
Wherein, the local telecommunication machine room comprises at least one main frame (40), and described main frame (40) is connected with input end (49) and display end (48), and connects at least one remote machine (10) by network.
2. database full-volume standby system as claimed in claim 1, it is characterized in that, described main frame includes environmental variance module (47) and backup list module (46), described environmental variance module (47) storage public variable, IP address, port and control documents, described backup list module (46) storage backup tabulation, backup file and backup script and cancellation script.
3. database full-volume standby system as claimed in claim 1 is characterized in that, described remote machine (10) is single main frame.
4. database full-volume standby system as claimed in claim 1 is characterized in that, described remote machine (10) is a group of server.
5. database full-volume standby system as claimed in claim 1 is characterized in that, described remote machine (10) is a network connection port, and further is connected on multiple host or the data server by described port.
6. database full-volume standby system as claimed in claim 1 is characterized in that, 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 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.
7. as any described database full-volume backup method among the claim 1-6, it is characterized in that, described backup method comprises selectivity execution backup process or cancellation process, in order to back up the backup process of the selected partial data of selected partial data or cancellation.
8. database full-volume backup method as claimed in claim 7 is characterized in that, described backup process and cancellation process are selected Oracle pattern or MySQL pattern according to the type of remote machine (10) from concrete data back up method.
9. database full-volume backup method as claimed in claim 8 is characterized in that described backup process specifically comprises the steps:
Step 400, backup process begins;
Step 401 is set public variable;
Step 402 is obtained independent backup list;
Step 403 judges whether independent backup list is empty;
Step 405 reads the instruction of the row of first in the tabulation;
Step 406 is obtained IP address and port numbers from delegation's instruction of backup list;
Step 407 judges whether the 2nd IP address is empty;
Step 408 judges whether an IP address and the 2nd IP address equate;
Step 412 is removed temporary file;
Step 413 reads the delegation in the control documents;
Step 414 is obtained the backup variable;
Step 415 is by setting up telecommunication;
Step 416 obtains type of backup;
Step 418, the output environment variable is to backup script in the Mysql backup;
Step 419, output MySQL backup script;
Step 420, the output environment variable is to backup script in the Oracle backup;
Step 421, output Oracle backup script;
Step 422, the backup information that output is being carried out;
Step 423 is carried out backup;
Step 424 is judged backup instances;
Step 425 reads next line, and is circulated to step 413;
Step 426 is upgraded backup procedure information for finishing, and exports display end to;
Step 427, backup process finishes.
10. database full-volume backup method as claimed in claim 8 is characterized in that, described cancellation process specifically comprises the steps:
Step 500, the cancellation process begins;
Step 501 obtains the public environment variable;
Step 502 generates the cancellation backup list;
Step 503 judges whether the row of cancellation backup list is empty;
Step 504 is obtained IP address and port from the cancellation backup list;
Step 505 judges whether the 2nd IP address is empty;
Step 506 judges whether an IP address and the 2nd IP address equate;
Step 510 reads the delegation in the public environment variable;
Step 511 judges whether the public environment row of variables that is read is empty;
Step 512 obtains variable from the row that reads;
Step 513 judges whether remote machine exists;
Step 515 is obtained the remote machine type;
Step 516 is obtained the PID of backup process;
Step 517, the script of generation cancellation process;
Step 518, the script of execution cancellation process;
Step 523, the data that is produced in the removing backup procedure, backup file etc.;
Step 525 judges whether next line is empty;
Step 526, the cancellation process finishes.
Priority Applications (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CN2009100551836A CN101963928A (en) | 2009-07-22 | 2009-07-22 | System and method of database full backup |
Applications Claiming Priority (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CN2009100551836A CN101963928A (en) | 2009-07-22 | 2009-07-22 | System and method of database full backup |
Publications (1)
Publication Number | Publication Date |
---|---|
CN101963928A true CN101963928A (en) | 2011-02-02 |
Family
ID=43516805
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
CN2009100551836A Pending CN101963928A (en) | 2009-07-22 | 2009-07-22 | System and method of database full backup |
Country Status (1)
Country | Link |
---|---|
CN (1) | CN101963928A (en) |
Cited By (7)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN102110031A (en) * | 2011-02-23 | 2011-06-29 | 宇龙计算机通信科技(深圳)有限公司 | Android system-based application program backup and recovery method |
CN102662793A (en) * | 2012-03-07 | 2012-09-12 | 江苏引跑网络科技有限公司 | Hot backup and recovery method of distributed database with guarantee of data consistency |
CN103678592A (en) * | 2013-12-12 | 2014-03-26 | 浪潮(北京)电子信息产业有限公司 | Data backup method and system |
CN107590030A (en) * | 2017-09-29 | 2018-01-16 | 郑州云海信息技术有限公司 | A kind of method, apparatus and system of data recording on tape backup |
CN107957920A (en) * | 2017-10-31 | 2018-04-24 | 清远恒成智道信息科技有限公司 | Database backup system |
CN109062727A (en) * | 2018-06-20 | 2018-12-21 | 平安科技(深圳)有限公司 | A kind of data synchronous system and method |
CN113328880A (en) * | 2021-05-24 | 2021-08-31 | 江苏云从曦和人工智能有限公司 | Method, system, medium and apparatus for deployment of distributed cluster system |
-
2009
- 2009-07-22 CN CN2009100551836A patent/CN101963928A/en active Pending
Non-Patent Citations (2)
Title |
---|
无: "企业级开源数据库灾备体系", 《HTTP://WWW.03964.COM/READ/74061E94F8AEF9EF06934615.HTML》 * |
杨凯: "银联数据异地灾难备份架构设计探讨", 《中国金融电脑》 * |
Cited By (9)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN102110031A (en) * | 2011-02-23 | 2011-06-29 | 宇龙计算机通信科技(深圳)有限公司 | Android system-based application program backup and recovery method |
CN102662793A (en) * | 2012-03-07 | 2012-09-12 | 江苏引跑网络科技有限公司 | Hot backup and recovery method of distributed database with guarantee of data consistency |
CN103678592A (en) * | 2013-12-12 | 2014-03-26 | 浪潮(北京)电子信息产业有限公司 | Data backup method and system |
CN103678592B (en) * | 2013-12-12 | 2018-01-09 | 浪潮(北京)电子信息产业有限公司 | A kind of data back up method and system |
CN107590030A (en) * | 2017-09-29 | 2018-01-16 | 郑州云海信息技术有限公司 | A kind of method, apparatus and system of data recording on tape backup |
CN107957920A (en) * | 2017-10-31 | 2018-04-24 | 清远恒成智道信息科技有限公司 | Database backup system |
CN109062727A (en) * | 2018-06-20 | 2018-12-21 | 平安科技(深圳)有限公司 | A kind of data synchronous system and method |
CN109062727B (en) * | 2018-06-20 | 2023-04-14 | 平安科技(深圳)有限公司 | Data synchronization system and method |
CN113328880A (en) * | 2021-05-24 | 2021-08-31 | 江苏云从曦和人工智能有限公司 | Method, system, medium and apparatus for deployment of distributed cluster system |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
CN101923498A (en) | Database full-volume automatic backup system and method | |
CN101963928A (en) | System and method of database full backup | |
US7934116B2 (en) | Disaster recover/continuity of business adaptive solution framework | |
CN105843182B (en) | A kind of power scheduling accident prediction system and method based on OMS | |
CN104081353B (en) | Balancing dynamic load in scalable environment | |
CN104081354B (en) | Subregion is managed in scalable environment | |
CN101957783A (en) | Database offsite backup system and method | |
CN104809510A (en) | Building method of ticket pool middleware for providing ticket support, ticket purchasing and ticket locking methods | |
CN101923497A (en) | Enterprise-level database backup system and method | |
CN101763347A (en) | GIS (Geographical Information System) interface platform as well as network GIS management system and management method | |
CN104252485A (en) | Database management platform | |
CN101930431A (en) | Database backup information clearing system and method | |
CN102316131A (en) | Intelligent backing up of cloud platform system | |
CN101996094A (en) | Method and system for managing distributed resources | |
CN114237810A (en) | Cloud computing platform based on BIM integrated delivery mode | |
CN201532631U (en) | Database remote backup system | |
CN104199955A (en) | Information management system and information management method | |
CN109739691A (en) | DB Backup and restoration methods, device, terminal device and storage medium | |
CN201508546U (en) | Enterprise-level database backup system | |
CN201503584U (en) | Database total automatic backup system | |
KR20080079713A (en) | System and its method for managing tender information of construction company to accept a bid of construction work | |
CN201532630U (en) | Database full backup system | |
CN102289506A (en) | Mail system backup method | |
Gray et al. | Distributed computer systems: Four case studies | |
CN112734507A (en) | House lease distribution method, distribution system and storage medium based on block chain |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
C06 | Publication | ||
PB01 | Publication | ||
C10 | Entry into substantive examination | ||
SE01 | Entry into force of request for substantive examination | ||
C02 | Deemed withdrawal of patent application after publication (patent law 2001) | ||
WD01 | Invention patent application deemed withdrawn after publication |
Application publication date: 20110202 |