|Publication number||US5842222 A|
|Application number||US 08/725,803|
|Publication date||Nov 24, 1998|
|Filing date||Oct 4, 1996|
|Priority date||Oct 4, 1996|
|Publication number||08725803, 725803, US 5842222 A, US 5842222A, US-A-5842222, US5842222 A, US5842222A|
|Inventors||Chun-Ching Lin, Yi-Hsin Chan, Hung-Chieh Hsu, Shih-Yung Lo|
|Original Assignee||Taiwan Semiconductor Manufacturing Company, Ltd.|
|Export Citation||BiBTeX, EndNote, RefMan|
|Patent Citations (7), Referenced by (36), Classifications (10), Legal Events (4)|
|External Links: USPTO, USPTO Assignment, Espacenet|
1. Field of Invention
This invention relates to production information systems and in particular to providing a means to increase availability during database maintenance.
2. Description of Related Art
It is critical to provide high availability for production information systems that are used to control production processes including the logging of production transactions. It is inevitable that a certain amount of time is necessary for maintenance of the associated databases, but it is important to keep this at a minimum. An important function in any database system is to maintain a backup database so that if anything goes wrong with the primary database the system can be switched over to the backup. Keeping this backup database updated efficiently is important to providing high availability. In U.S. Pat. No. 5,381,545 (Baker et al.) a log is used for the incremental changes to the backup database since the last full backup was made. Periodically the log is applied to the backup database bringing it up to the level of the primary database. In U.S. Pat. No. 4,686,620 (Ng) a method for generating a backup copy of a database is described. Updates to the main database is summarized in a bit map on a page basis. When the next backup copy is made, only the pages that have changed are applied to the backup database.
In both these references attempts are made to reduce the demands on the availability of the primary system by minimizing the amount of data that needs to be updated in between the full backup of the primary database. Another important aspect of maximizing system availability is to perform database maintenance processes on a backup database away from the primary system and database. Important database maintenance functions include archiving and deleting data, backup data to tape and database conversion and can require considerable amount of time to perform.
A dual machine production information system, having a primary and secondary sides with primary and secondary data bases, is enhanced to provide improved availability by adding a third database for backup and database maintenance. The backup database is up dated daily by applying the incremental changes stored in the transaction log. This brings the backup database up to date with respect to the primary database once each day. Besides providing backup to the primary and secondary databases, the backup database provides a means to perform all database maintenance off line away from the production activity that use the primary and secondary databases. Maintenance activity such as data deletion, archiving and backing up to tape are performed using the backup database.
Periodically a database conversion is done using a temporary data base to minimize the effects on the production use of the system. The backup database being first to be converted is used by the primary and secondary systems while the primary and secondary databases are being converted. The backup database files are converted to the temporary database after which the backup database is deleted, and then the converted files in the temporary database are copied to the backup database. Next the secondary system is shut down and the backup database is assigned to the secondary system. The secondary system is brought up using the backup database, and the secondary database is deleted. Upon deletion of the files in the secondary database, the converted files from the temporary database are copied to the secondary database. Once this is accomplished both the primary and secondary systems are shut down, and the backup data base is assigned to the primary system. The primary system is brought back up using the backup database, and the primary database is deleted. Then the converted files contained in the temporary database are copied to the primary database. At this point all the databases are converted and synchronized. The systems are once more shut down and brought back up with the system using the primary database once again.
This invention will be described with reference to the accompanying drawings, wherein:
FIG. 1 is a schematic of the dual machine production information system of the invention, and
FIG. 2 is a flow diagram of the database conversion process, and
FIG. 3 is a continuation of the flow diagram of the database conversion process, and
FIG. 4 is a flow diagram showing the daily update of the backup database, and
FIG. 5 is a flow diagram showing the maintenance process.
Shown in FIG. 1 is a dual machine structure having primary and secondary sides and running a production information system. Each side contains a file server 1 and 2, a task communicator 3 and 4, and a transaction log 5 and 6. A primary database 7 is connected to the file server 1 on the primary side, and a secondary database 8 is connected to the file server 2 on the secondary side. A primary transaction log 5 is connected to the file server 1 on the primary side, and is used to maintain a log of incremental changes to the primary database 7. The secondary transaction log 6 is maintained as a backup to the primary transaction log 5 and is updated after the primary transaction log 5. The primary transaction log 5 is used by the daily backup process 9 to update the backup database 10. The task communicator 3 on the primary side communicates with the task communicator on the secondary side 4 and allows the production information system running on the primary file server 1 to communicate with the secondary database 8 and the transaction log 6 on the secondary side.
Periodically a conversion process is applied to all the data bases to facilitate re-establishing a clean and synchronized set of databases. Shown in FIG. 2 is the database conversion process which utilizes the backup database 10 to minimize down time of the production information system as the conversion process takes place. A temporary database is established using spare disk space and the backup database is converted to the temporary database 20. Then the backup data base files are deleted 21 and the converted files in the temporary database are copied to the backup database 22. Then the primary transaction log is applied to both the temporary database and the backup database 23 to bring these databases up to date with the most recent changes to the primary database. Next the secondary production information system is shut down 24 while maintaining the secondary database 25. The backup database is assigned to the secondary system and the secondary transaction log file is renamed as *.OLD 26. The secondary system is restarted 27. The secondary database files are deleted 28, and the converted files in the temporary database are copied to the secondary database 29. Then the secondary and temporary databases are further updated by applying the transaction log 30.
Referring to FIG. 3, both the primary and secondary system are shutdown 40 while maintaining the primary database 41. The backup database is assigned to the primary system 42 and the secondary database is assigned to the secondary system 43. Next the primary and secondary systems are restarted 44 while the primary database files are deleted 45. Then the converted files in the temporary database are copied to the primary database 46, and the primary transaction log is applied to the primary data base 47 to include the latest changes on the primary database. The primary and secondary databases are once again shut down 48, and the primary data base is assigned to the primary system 49. Once again the primary transaction log is applied to the primary database 50 to capture the latest data. All the primary and secondary transaction files are renamed 51, and the primary system is brought up using the primary database 52. The secondary system is brought up using the secondary database 53, and the conversion process is complete.
In FIG. 4 is shown the procedure of daily backup 9 of the backup database 10. The transaction log is closed 60 and a new transaction log is opened 61. The daily backup process is started 62 where the transaction log that was just closed is applied to the backup database 63. This brings the backup database up to the same level as the primary database 64 minus any differences logged into the newly opened transaction log 61.
In FIG. 5 is shown the process for archiving data. This process uses the backup database 10 freeing the primary 7 and secondary 8 databases to be used with the primary and secondary systems to do production work. The archiving process includes processes like mark lots for archive, copy archive lots, backup archive directory files and delete archive lots. The logical name of the files contained in the backup database is set to point to the backup database 70. Then the files in the backup database are accessed locally 72 and the appropriate archival procedure is applied to the data 73.
While the invention has been particularly shown and described with reference to preferred embodiments thereof, it will be understood by those skilled in the art that various changes in form and details may be made without departing from the spirit and scope of the invention.
|Cited Patent||Filing date||Publication date||Applicant||Title|
|US4686620 *||Jul 26, 1984||Aug 11, 1987||American Telephone And Telegraph Company, At&T Bell Laboratories||Database backup method|
|US5170480 *||Sep 25, 1989||Dec 8, 1992||International Business Machines Corporation||Concurrently applying redo records to backup database in a log sequence using single queue server per queue at a time|
|US5182705 *||Aug 11, 1989||Jan 26, 1993||Itt Corporation||Computer system and method for work management|
|US5381545 *||May 28, 1992||Jan 10, 1995||International Business Machines Corporation||Data backup and recovery in a data processing system|
|US5548750 *||Dec 8, 1993||Aug 20, 1996||Telefonaktiebolaget Lm Ericsson||System for taking backup in a data base|
|US5592660 *||Jul 13, 1992||Jan 7, 1997||Fujitsu Limited||Database management system to alternately perform retrieval process and updating process|
|US5640561 *||Jun 6, 1995||Jun 17, 1997||International Business Machines Corporation||Computerized method and system for replicating a database using log records|
|Citing Patent||Filing date||Publication date||Applicant||Title|
|US6014674 *||Nov 13, 1997||Jan 11, 2000||Sybase, Inc.||Method for maintaining log compatibility in database systems|
|US6023707 *||Dec 30, 1997||Feb 8, 2000||Fujitsu Limited||On-line database duplication with incorporation of concurrent database updates|
|US6185615 *||Feb 25, 2000||Feb 6, 2001||Sun Microsystems, Inc.||Method and system for consolidating related partial operations into a transaction log|
|US6349373 *||Feb 20, 1998||Feb 19, 2002||Eastman Kodak Company||Digital image management system having method for managing images according to image groups|
|US6397307 *||Feb 23, 1999||May 28, 2002||Legato Systems, Inc.||Method and system for mirroring and archiving mass storage|
|US6408314||Jul 6, 1999||Jun 18, 2002||Synscort Incorporated||Method of performing a high-performance sort which gains efficiency by reading input file blocks sequentially|
|US6415300||Jul 6, 1999||Jul 2, 2002||Syncsort Incorporated||Method of performing a high-performance backup which gains efficiency by reading input file blocks sequentially|
|US6553401||Jul 9, 1999||Apr 22, 2003||Ncr Corporation||System for implementing a high volume availability server cluster including both sharing volume of a mass storage on a local site and mirroring a shared volume on a remote site|
|US6615244||Nov 28, 1998||Sep 2, 2003||Tara C Singhal||Internet based archive system for personal computers|
|US6820097 *||Jan 16, 2002||Nov 16, 2004||Sepaton, Inc.||System and method for cross-platform update propagation|
|US7039661 *||Dec 29, 2003||May 2, 2006||Veritas Operating Corporation||Coordinated dirty block tracking|
|US7177886||Feb 7, 2003||Feb 13, 2007||International Business Machines Corporation||Apparatus and method for coordinating logical data replication with highly available data replication|
|US7222141 *||Dec 20, 2002||May 22, 2007||International Business Machine Corporation||System and method for synchronizing data in multiple databases|
|US7359925 *||Sep 28, 1998||Apr 15, 2008||Canon Kabushiki Kaisha||Database system, its control method, and information processing apparatus|
|US7487188||Jul 25, 2005||Feb 3, 2009||Computer Associates Think, Inc.||System and method for providing increased database fault tolerance|
|US7606841||May 2, 2006||Oct 20, 2009||Symantec Operating Corporation||Coordinated dirty block tracking|
|US8170994||May 1, 2012||Symantec Corporation||Techniques for virtual archiving|
|US9213609 *||Dec 16, 2003||Dec 15, 2015||Hewlett-Packard Development Company, L.P.||Persistent memory device for backup process checkpoint states|
|US9235580||Apr 30, 2012||Jan 12, 2016||Symantec Corporation||Techniques for virtual archiving|
|US20010050088 *||Mar 14, 2001||Dec 13, 2001||Gary Leeds||Method for prevention/rehabilitation customization|
|US20020083084 *||Sep 28, 1998||Jun 27, 2002||Mitsumasa Sugiyama||Database system, its control method, and information processing apparatus|
|US20020152227 *||Jan 16, 2002||Oct 17, 2002||Alexander Winokur||System and method for cross-platform update propagation|
|US20030131025 *||Dec 20, 2002||Jul 10, 2003||Zondervan Quinton Yves||System and method for synchronizing data in multiple databases|
|US20040139127 *||Jul 31, 2003||Jul 15, 2004||Lech Pofelski||Backup system and method of generating a checkpoint for a database|
|US20050033638 *||Aug 8, 2003||Feb 10, 2005||Toni-Diane Donnet||System and method for advertising compliance|
|US20050044231 *||Aug 8, 2003||Feb 24, 2005||Boris Apotovsky||Client/supplier communication and performance management system|
|US20050132250 *||Dec 16, 2003||Jun 16, 2005||Hewlett-Packard Development Company, L.P.||Persistent memory device for backup process checkpoint states|
|US20060053183 *||Jul 25, 2005||Mar 9, 2006||Eaton Kenneth W||System and method for providing increased database fault tolerance|
|US20090089523 *||Oct 31, 2007||Apr 2, 2009||Symantec Corporation||Techniques for virtual archiving|
|US20090094426 *||Jan 22, 2008||Apr 9, 2009||Hirokazu Ikeda||Storage system|
|US20140214263 *||Jan 23, 2014||Jul 31, 2014||Airbus Operations (Sas)||Method, device and computer program for assisting the maintenance of an aircraft system using a diagnostic assistance tool and experience feedback data|
|US20150213036 *||Apr 10, 2015||Jul 30, 2015||Delphix Corporation||Datacenter Workflow Automation Scenarios Using Virtual Databases|
|CN100390747C||Feb 20, 2006||May 28, 2008||南京联创科技股份有限公司||Soft co-standby method based on memory database in whole-process real time system|
|EP2042993A1 *||Sep 29, 2008||Apr 1, 2009||Symantec Corporation||Techniques for virtual archiving|
|WO2006028689A2 *||Aug 19, 2005||Mar 16, 2006||Computer Associates Think, Inc.||System and method for providing increased database fault tolerance|
|WO2006028689A3 *||Aug 19, 2005||Mar 29, 2007||Computer Ass Think Inc||System and method for providing increased database fault tolerance|
|U.S. Classification||707/646, 707/E17.005, 707/661, 707/999.202, 707/648, 707/802|
|Cooperative Classification||Y10S707/99953, G06F17/30368|
|Oct 4, 1996||AS||Assignment|
Owner name: TAIWAN SEMICONDUCTOR MANUFACTURING COMPANY, LTD.,
Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:LIN, CHUN-CHING;CHAN, YI-HSIN;HSU, HUNG-CHIEH;AND OTHERS;REEL/FRAME:008263/0722
Effective date: 19960828
|Feb 28, 2002||FPAY||Fee payment|
Year of fee payment: 4
|Apr 28, 2006||FPAY||Fee payment|
Year of fee payment: 8
|May 3, 2010||FPAY||Fee payment|
Year of fee payment: 12