1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
|
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8" />
<title>Recovery Procedures</title>
<link rel="stylesheet" href="gettingStarted.css" type="text/css" />
<meta name="generator" content="DocBook XSL Stylesheets V1.73.2" />
<link rel="start" href="index.html" title="Getting Started with Berkeley DB Transaction Processing" />
<link rel="up" href="filemanagement.html" title="Chapter 5. Managing DB Files" />
<link rel="prev" href="backuprestore.html" title="Backup Procedures" />
<link rel="next" href="architectrecovery.html" title="Designing Your Application for Recovery" />
</head>
<body>
<div xmlns="" class="navheader">
<div class="libver">
<p>Library Version 11.2.5.3</p>
</div>
<table width="100%" summary="Navigation header">
<tr>
<th colspan="3" align="center">Recovery Procedures</th>
</tr>
<tr>
<td width="20%" align="left"><a accesskey="p" href="backuprestore.html">Prev</a> </td>
<th width="60%" align="center">Chapter 5. Managing DB Files</th>
<td width="20%" align="right"> <a accesskey="n" href="architectrecovery.html">Next</a></td>
</tr>
</table>
<hr />
</div>
<div class="sect1" lang="en" xml:lang="en">
<div class="titlepage">
<div>
<div>
<h2 class="title" style="clear: both"><a id="recovery"></a>Recovery Procedures</h2>
</div>
</div>
</div>
<div class="toc">
<dl>
<dt>
<span class="sect2">
<a href="recovery.html#normalrecovery">Normal Recovery</a>
</span>
</dt>
<dt>
<span class="sect2">
<a href="recovery.html#catastrophicrecovery">Catastrophic Recovery</a>
</span>
</dt>
</dl>
</div>
<p>
DB supports two types of recovery:
</p>
<div class="itemizedlist">
<ul type="disc">
<li>
<p>
Normal recovery, which is run when your environment is
opened upon application startup, examines only those
log records needed to bring the databases to a consistent
state since the last checkpoint. Normal recovery
starts with any logs used by any transactions active at
the time of the last checkpoint, and examines all logs
from then to the current logs.
</p>
</li>
<li>
<p>
Catastrophic recovery, which is performed in the same
way that normal recovery is except that it examines
all available log files. You use catastrophic recovery
to restore your databases from a previously created backup.
</p>
</li>
</ul>
</div>
<p>
Of these two, normal recovery should be considered a routine
matter; in fact you should run normal
recovery whenever you start up your application.
</p>
<p>
Catastrophic recovery is run whenever you have lost or
corrupted your database files and you want to restore from a
backup. You also run catastrophic recovery when
you create a hot backup
(see <a class="xref" href="hotfailover.html" title="Using Hot Failovers">Using Hot Failovers</a> for more information).
</p>
<div class="sect2" lang="en" xml:lang="en">
<div class="titlepage">
<div>
<div>
<h3 class="title"><a id="normalrecovery"></a>Normal Recovery</h3>
</div>
</div>
</div>
<p>
Normal recovery examines the contents of your environment's
log files, and uses this information to ensure that your
database files are consistent relative to the
information contained in the log files.
</p>
<p>
Normal recovery also recreates your environment's region files.
This has the desired effect of clearing any unreleased locks
that your application may have held at the time of an
unclean application shutdown.
</p>
<p>
Normal recovery is run only against those log files created
since the time of your last checkpoint. For this reason,
your recovery time is dependent on how much data has been
written since the last checkpoint, and therefore on how
much log file information there is to examine. If you run
checkpoints infrequently, then normal recovery can
take a relatively long time.
</p>
<div class="note" style="margin-left: 0.5in; margin-right: 0.5in;">
<h3 class="title">Note</h3>
<p>
You should run normal recovery every
time you perform application startup.
</p>
</div>
<p>
To run normal recovery:
</p>
<div class="itemizedlist">
<ul type="disc">
<li>
<p>
Make sure all your environment handles are closed.
</p>
</li>
<li>
<p>
Normal recovery <span class="emphasis"><em>must
be</em></span> single-threaded.
</p>
</li>
<li>
<p>
Specify <code class="literal">true</code> to
<code class="methodname">EnvironmentConfig.setRunRecovery()</code>
when you open your environment.
</p>
</li>
</ul>
</div>
<p>
You can also run recovery by pausing or shutting down your
application and using the <span class="command"><strong>db_recover</strong></span>
command line utility.
</p>
<p>
For example:
</p>
<pre class="programlisting">package db.txn;
import com.sleepycat.db.DatabaseException;
import com.sleepycat.db.Environment;
import com.sleepycat.db.EnvironmentConfig;
import java.io.File;
import java.io.FileNotFoundException;
...
Environment myEnv = null;
try {
EnvironmentConfig myEnvConfig = new EnvironmentConfig();
myEnvConfig.setInitializeCache(true);
myEnvConfig.setInitializeLocking(true);
myEnvConfig.setInitializeLogging(true);
myEnvConfig.setTransactional(true);
// Run normal recovery
myEnvConfig.setRunRecovery(true);
myEnv = new Environment(new File("/my/env/home"),
myEnvConfig);
// All other operations are identical from here. Notice, however,
// that we have not created any other threads of control before
// recovery is complete. You want to run recovery for
// the first thread in your application that opens an environment,
// but not for any subsequent threads.
} catch (DatabaseException de) {
// Exception handling goes here
} catch (FileNotFoundException fnfe) {
// Exception handling goes here
}</pre>
</div>
<div class="sect2" lang="en" xml:lang="en">
<div class="titlepage">
<div>
<div>
<h3 class="title"><a id="catastrophicrecovery"></a>Catastrophic Recovery</h3>
</div>
</div>
</div>
<p>
Use catastrophic recovery when you are
recovering your databases from a previously created backup.
Note that to restore your databases from a previous backup, you
should copy the backup to a new environment directory, and
then run catastrophic recovery. Failure to do so can lead to
the internal database structures being out of sync with your log files.
</p>
<p>
Catastrophic recovery must be run single-threaded.
</p>
<p>
To run catastrophic recovery:
</p>
<div class="itemizedlist">
<ul type="disc">
<li>
<p>
Shutdown all database operations.
</p>
</li>
<li>
<p>
Restore the backup to an empty directory.
</p>
</li>
<li>
<p>
Specify <code class="literal">true</code> to
<code class="methodname">EnvironmentConfig.setRunRecoveryFatal()</code>
when you open your environment. This environment
open must be single-threaded.
</p>
</li>
</ul>
</div>
<p>
You can also run recovery by pausing or shutting down your
application and using the <span class="command"><strong>db_recover</strong></span>
command line utility with the the <code class="literal">-c</code> option.
</p>
<p>
Note that catastrophic recovery examines every available
log file — not just those log files created since the
last checkpoint as is the case for normal recovery. For this reason,
catastrophic recovery is likely to take longer than does
normal recovery.
</p>
<p>
For example:
</p>
<pre class="programlisting">package db.txn;
import com.sleepycat.db.DatabaseException;
import com.sleepycat.db.Environment;
import com.sleepycat.db.EnvironmentConfig;
import java.io.File;
import java.io.FileNotFoundException;
...
Environment myEnv = null;
try {
EnvironmentConfig myEnvConfig = new EnvironmentConfig();
myEnvConfig.setInitializeCache(true);
myEnvConfig.setInitializeLocking(true);
myEnvConfig.setInitializeLogging(true);
myEnvConfig.setTransactional(true);
// Run catastrophic recovery
<strong class="userinput"><code>myEnvConfig.setRunFatalRecovery(true);</code></strong>
myEnv = new Environment(new File("/my/env/home"),
myEnvConfig);
} catch (DatabaseException de) {
// Exception handling goes here
} catch (FileNotFoundException fnfe) {
// Exception handling goes here
}</pre>
</div>
</div>
<div class="navfooter">
<hr />
<table width="100%" summary="Navigation footer">
<tr>
<td width="40%" align="left"><a accesskey="p" href="backuprestore.html">Prev</a> </td>
<td width="20%" align="center">
<a accesskey="u" href="filemanagement.html">Up</a>
</td>
<td width="40%" align="right"> <a accesskey="n" href="architectrecovery.html">Next</a></td>
</tr>
<tr>
<td width="40%" align="left" valign="top">Backup Procedures </td>
<td width="20%" align="center">
<a accesskey="h" href="index.html">Home</a>
</td>
<td width="40%" align="right" valign="top"> Designing Your Application for Recovery</td>
</tr>
</table>
</div>
</body>
</html>
|
