Browse Prior Art Database

Database Server Journal Backup Automation Technique

IP.com Disclosure Number: IPCOM000103971D
Original Publication Date: 1993-Feb-01
Included in the Prior Art Database: 2005-Mar-18
Document File: 2 page(s) / 59K

Publishing Venue

IBM

Related People

Duvall, KE: AUTHOR [+5]

Abstract

Disclosed is an automated method for backup of Database Server journal files to an Archive Server in a manner that does not disable the Database Server from performing other work.

This text was extracted from an ASCII text file.
This is the abbreviated version, containing approximately 52% of the total text.

Database Server Journal Backup Automation Technique

      Disclosed is an automated method for backup of Database Server
journal files to an Archive Server in a manner that does not disable
the Database Server from performing other work.

      In a distributed, multiple workstation, client/server based
backup and restore system the Database Server process is used to
track the backup activity that has taken place on the client nodes.
Information associated with every file backed up from the client node
to an Archive Server (backup data repository) is stored in the
database associated with the client node.  This information becomes
critical to the restoration of data files back into the enterprise.

      Two standard methods are employed to ensure the availability of
the data maintained by a Database Server.  The first method involves
creating backup copies of the database itself at regular intervals.
These backups provide periodic snapshot images of the databases
maintained by the Database Server.

      The second method is to track the update transactions to the
database via a journaling function.  The journal records the
transactions applied (data pages that have changed) to the database
since the last database backup.

      Due to the volatility of file systems being backed up, there is
potential for a high number of database transactions to record the
backup of files to an Archive Server.  This implies that the journal
file itself can become large as it is recording the transactions
against the...