Gecko [ 122.154.134.11 ]

Name	Size	Permission
admin.html	3.28 KB	-rw-r--r--
app.html	16.29 KB	-rw-r--r--
archival.html	9.52 KB	-rw-r--r--
atomicity.html	4.19 KB	-rw-r--r--
checkpoint.html	4.7 KB	-rw-r--r--
cursor.html	4.99 KB	-rw-r--r--
data_open.html	5.89 KB	-rw-r--r--
deadlock.html	5.78 KB	-rw-r--r--
env_open.html	6.53 KB	-rw-r--r--
fail.html	4.98 KB	-rw-r--r--
faq.html	7.8 KB	-rw-r--r--
filesys.html	4.22 KB	-rw-r--r--
hotfail.html	5.51 KB	-rw-r--r--
inc.html	6.1 KB	-rw-r--r--
intro.html	2.72 KB	-rw-r--r--
logfile.html	3.57 KB	-rw-r--r--
nested.html	4.19 KB	-rw-r--r--
put.html	10.51 KB	-rw-r--r--
read.html	7.93 KB	-rw-r--r--
reclimit.html	9.7 KB	-rw-r--r--
recovery.html	6.42 KB	-rw-r--r--
term.html	4.09 KB	-rw-r--r--
throughput.html	7.14 KB	-rw-r--r--
transapp.cs	10.34 KB	-rw-r--r--
tune.html	10.76 KB	-rw-r--r--
why.html	2.49 KB	-rw-r--r--
writetest.cs	2.32 KB	-rw-r--r--

Code Editor : archival.html

<html>
<head>
<title>Berkeley DB Reference Guide: Database and log file archival</title>
<meta name="description" content="Berkeley DB: An embedded database programmatic toolkit.">
<meta name="keywords" content="embedded,database,programmatic,toolkit,btree,hash,hashing,transaction,transactions,locking,logging,access method,access methods,Java,C,C++">
</head>
<body bgcolor=white>
<a name="2"></a><a name="3"></a>
<table width="100%"><tr valign=top>
<td><dl><dt>Berkeley DB Reference Guide:<dd>Berkeley DB Transactional Data Store Applications</dl></td>
<td align=right><a href="../transapp/checkpoint.html"><img src="../../images/prev.gif" alt="Prev"></a><a href="../toc.html"><img src="../../images/ref.gif" alt="Ref"></a><a href="../transapp/logfile.html"><img src="../../images/next.gif" alt="Next"></a>
</td></tr></table>
Database and log file archival
The third component of the administrative infrastructure, archival for
catastrophic recovery, concerns the recoverability of the database in
the face of catastrophic failure. Recovery after catastrophic failure
is intended to minimize data loss when physical hardware has been
destroyed -- for example, loss of a disk that contains databases or log
files. Although the application may still experience data loss in this
case, it is possible to minimize it.
First, you may want to periodically create snapshots (that is, backups)
of your databases to make it possible to recover from catastrophic
failure. These snapshots are either a standard backup, which creates a
consistent picture of the databases as of a single instant in time; or
an on-line backup (also known as a hot backup), which creates
a consistent picture of the databases as of an unspecified instant
during the period of time when the snapshot was made. The advantage of
a hot backup is that applications may continue to read and write the
databases while the snapshot is being taken. The disadvantage of a hot
backup is that more information must be archived, and recovery based on
a hot backup is to an unspecified time between the start of the backup
and when the backup is completed.
Second, after taking a snapshot, you should periodically archive the
log files being created in the environment. It is often helpful to
think of database archival in terms of full and incremental filesystem
backups. A snapshot is a full backup, whereas the periodic archival of
the current log files is an incremental backup. For example, it might
be reasonable to take a full snapshot of a database environment weekly
or monthly, and archive additional log files daily. Using both the
snapshot and the log files, a catastrophic crash at any time can be
recovered to the time of the most recent log archival; a time long after
the original snapshot.
To create a standard backup of your database that can be used to recover
from catastrophic failure, take the following steps:
<ol>
<li>Commit or abort all ongoing transactions.
<li>Stop writing your databases until the backup has completed. Read-only
operations are permitted, but no write operations and no filesystem
operations may be performed (for example, the <a href="../../api_c/env_remove.html">DB_ENV-&gt;remove</a> and
<a href="../../api_c/db_open.html">DB-&gt;open</a> methods may not be called).
<li>Force an environment checkpoint (see <a href="../../utility/db_checkpoint.html">db_checkpoint</a> for more
information).
<li>Run <a href="../../utility/db_archive.html">db_archive</a> -s to identify all the database data
files, and copy them to a backup device such as CD-ROM, alternate disk,
or tape.
If the database files are stored in a separate directory from the other
Berkeley DB files, it may be simpler to archive the directory itself instead
of the individual files (see <a href="../../api_c/env_set_data_dir.html">DB_ENV-&gt;set_data_dir</a> for additional
information). Note: if any of the database files did not have
an open <a href="../../api_c/db_class.html">DB</a> handle during the lifetime of the current log files,
<a href="../../utility/db_archive.html">db_archive</a> will not list them in its output! This is another
reason it may be simpler to use a separate database file directory and
archive the entire directory instead of archiving only the files listed
by <a href="../../utility/db_archive.html">db_archive</a>.
<li>Run <a href="../../utility/db_archive.html">db_archive</a> -l to identify all the log files,
and copy the last one (that is, the one with the highest number) to a
backup device such as CD-ROM, alternate disk, or tape.
</ol>
<a name="4"></a>
To create a hot backup of your database that can be used to
recover from catastrophic failure, take the following steps:
<ol>
<li>Archive your databases, as described in the previous step #4.
You do not have to halt ongoing transactions or force a checkpoint. As
this is a hot backup, and the databases may be modified during the copy,
the utility you use to copy the databases must read database pages
atomically (as described by <a href="../../ref/transapp/reclimit.html">Berkeley DB recoverability</a>).
<li>Archive all of the log files. The order of these two operations
is required, and the database files must be archived before the
log files. This means that if the database files and log files are in
the same directory, you cannot simply archive the directory; you must
make sure that the correct order of archival is maintained.
To archive your log files, run the <a href="../../utility/db_archive.html">db_archive</a> utility using
the -l option to identify all the database log files, and
copy them to your backup media. If the database log files are stored
in a separate directory from the other database files, it may be simpler
to archive the directory itself instead of the individual files (see
the <a href="../../api_c/env_set_lg_dir.html">DB_ENV-&gt;set_lg_dir</a> method for more information).
</ol>
To minimize the archival space needed for log files when doing a hot
backup, run db_archive to identify those log files which are not in use.
Log files which are not in use do not need to be included when creating
a hot backup, and you can discard them or move them aside for use with
previous backups (whichever is appropriate), before beginning the hot
backup.
After completing one of these two sets of steps, the database
environment can be recovered from catastrophic failure (see
<a href="recovery.html">Recovery procedures</a> for more information).
For an example of a hot backup implementation in the Berkeley DB distribution,
see the source code for the <a href="../../utility/db_hotbackup.html">db_hotbackup</a> utility.
To update either a hot or cold backup so that recovery from catastrophic
failure is possible to a new point in time, repeat step #2 under the
hot backup instructions and archive all of the log files in the
database environment. Each time both the database and log files are
copied to backup media, you may discard all previous database snapshots
and saved log files. Archiving additional log files does not allow you
to discard either previous database snapshots or log files. Generally,
updating a backup must be integrated with the application's log file
removal procedures.
The time to restore from catastrophic failure is a function of the
number of log records that have been written since the snapshot was
originally created. Perhaps more importantly, the more separate pieces
of backup media you use, the more likely it is that you will have a
problem reading from one of them. For these reasons, it is often best
to make snapshots on a regular basis.
Obviously, the reliability of your archive media will affect the safety
of your data. For archival safety, ensure that you have multiple copies
of your database backups, verify that your archival media is error-free
and readable, and that copies of your backups are stored offsite!
The functionality provided by the <a href="../../utility/db_archive.html">db_archive</a> utility is also
available directly from the Berkeley DB library. The following code fragment
prints out a list of log and database files that need to be archived:
<blockquote><pre>void
log_archlist(DB_ENV *dbenv)
{
	int ret;
	char **begin, **list;

	/* Get the list of database files. */
	if ((ret = dbenv-&gt;log_archive(dbenv,
	 &list, DB_ARCH_ABS | DB_ARCH_DATA)) != 0) {
		dbenv-&gt;err(dbenv, ret, "DB_ENV-&gt;log_archive: DB_ARCH_DATA");
		exit (1);
	}
	if (list != NULL) {
		for (begin = list; *list != NULL; ++list)
			printf("database file: %s\n", *list);
		free (begin);
	}

	/* Get the list of log files. */
	if ((ret = dbenv-&gt;log_archive(dbenv,
	 &list, DB_ARCH_ABS | DB_ARCH_LOG)) != 0) {
		dbenv-&gt;err(dbenv, ret, "DB_ENV-&gt;log_archive: DB_ARCH_LOG");
		exit (1);
	}
	if (list != NULL) {
		for (begin = list; *list != NULL; ++list)
			printf("log file: %s\n", *list);
		free (begin);
	}
}</pre></blockquote>
<table width="100%"><tr><td> </td><td align=right><a href="../transapp/checkpoint.html"><img src="../../images/prev.gif" alt="Prev"></a><a href="../toc.html"><img src="../../images/ref.gif" alt="Ref"></a><a href="../transapp/logfile.html"><img src="../../images/next.gif" alt="Next"></a>
</td></tr></table>
Copyright (c) 1996,2008 Oracle. All rights reserved.
</body>
</html>

${this.title}

Code Editor : archival.html