diff options
| author | Lorry Tar Creator <lorry-tar-importer@baserock.org> | 2015-02-17 17:25:57 +0000 |
|---|---|---|
| committer | <> | 2015-03-17 16:26:24 +0000 |
| commit | 780b92ada9afcf1d58085a83a0b9e6bc982203d1 (patch) | |
| tree | 598f8b9fa431b228d29897e798de4ac0c1d3d970 /docs/programmer_reference/am_upgrade.html | |
| parent | 7a2660ba9cc2dc03a69ddfcfd95369395cc87444 (diff) | |
| download | berkeleydb-master.tar.gz | |
Diffstat (limited to 'docs/programmer_reference/am_upgrade.html')
| -rw-r--r-- | docs/programmer_reference/am_upgrade.html | 81 |
1 files changed, 43 insertions, 38 deletions
diff --git a/docs/programmer_reference/am_upgrade.html b/docs/programmer_reference/am_upgrade.html index 7366891f..9e08741f 100644 --- a/docs/programmer_reference/am_upgrade.html +++ b/docs/programmer_reference/am_upgrade.html @@ -14,7 +14,7 @@ <body> <div xmlns="" class="navheader"> <div class="libver"> - <p>Library Version 11.2.5.3</p> + <p>Library Version 12.1.6.1</p> </div> <table width="100%" summary="Navigation header"> <tr> @@ -22,9 +22,7 @@ </tr> <tr> <td width="20%" align="left"><a accesskey="p" href="am_truncate.html">Prev</a> </td> - <th width="60%" align="center">Chapter 3. - Access Method Operations - </th> + <th width="60%" align="center">Chapter 3. Access Method Operations </th> <td width="20%" align="right"> <a accesskey="n" href="am_verify.html">Next</a></td> </tr> </table> @@ -38,41 +36,47 @@ </div> </div> </div> + <p> + When upgrading to a new release of Berkeley DB, it may be + necessary to upgrade the on-disk format of already-created + database files. <span class="bold"><strong>Berkeley DB database + upgrades are done in place, and so are potentially + destructive.</strong></span> This means that if the system + crashes during the upgrade procedure, or if the upgrade + procedure runs out of disk space, the databases may be left in + an inconsistent and unrecoverable state. To guard against + failure, the procedures outlined in the <a href="../upgrading/upgrade_process.html" class="olink">Upgrading Berkeley DB installations</a> chapter of + the Berkeley DB Installation and Build Guide should be carefully followed. If you are + not performing catastrophic archival as part of your + application upgrade process, you should at least copy your + database to archival media, verify that your archival media is + error-free and readable, and that copies of your backups are + stored offsite! + </p> <p> - - When upgrading to a new release of Berkeley DB, it may be necessary to - upgrade the on-disk format of already-created database files. - <span class="bold"><strong>Berkeley DB database upgrades are done in place, - and so are potentially destructive.</strong></span> This means that if - the system crashes during the upgrade - procedure, or if the upgrade procedure runs out of disk space, the - databases may be left in an inconsistent and unrecoverable state. To guard - against failure, the procedures outlined in the <a href="../upgrading/upgrade_process.html" class="olink">Upgrading Berkeley DB installations</a> chapter of the - Berkeley DB Installation and Build Guide should be carefully followed. If you are not performing - catastrophic archival as part of your application upgrade process, you - should at least copy your database to archival media, verify that your - archival media is error-free and readable, and that copies of your backups - are stored offsite! -</p> + The actual database upgrade is done using the <a href="../api_reference/C/dbupgrade.html" class="olink">DB->upgrade()</a> + method, or by dumping the database using the old version of + the Berkeley DB software and reloading it using the current + version. + </p> <p> - The actual database upgrade is done using the <a href="../api_reference/C/dbupgrade.html" class="olink">DB->upgrade()</a> method, or by - dumping the database using the old version of the Berkeley DB software - and reloading it using the current version.</p> - <p>After an - upgrade, Berkeley DB applications must be recompiled to use the new - Berkeley DB library before they can access an upgraded database. - <span class="bold"><strong>There is no guarantee that applications compiled - against previous releases of Berkeley DB will work correctly with - an upgraded database format. Nor is there any guarantee that - applications compiled against - newer releases of Berkeley DB will work correctly with the previous - database format.</strong></span> We do guarantee that any archived database may - be upgraded using a current Berkeley DB software release and the - <a href="../api_reference/C/dbupgrade.html" class="olink">DB->upgrade()</a> method, and there is no need to step-wise upgrade the database - using intermediate releases of Berkeley DB. Sites should consider - archiving appropriate copies of their application or application sources if - they may need to access archived databases without first upgrading them. -</p> + After an upgrade, Berkeley DB applications must be + recompiled to use the new Berkeley DB library before they can + access an upgraded database. <span class="bold"><strong>There is no + guarantee that applications compiled against previous + releases of Berkeley DB will work correctly with an + upgraded database format. Nor is there any guarantee that + applications compiled against newer releases of Berkeley + DB will work correctly with the previous database + format.</strong></span> We do guarantee that any archived + database may be upgraded using a current Berkeley DB software + release and the <a href="../api_reference/C/dbupgrade.html" class="olink">DB->upgrade()</a> method, and there is no need to + step-wise upgrade the database using intermediate releases of + Berkeley DB. Sites should consider archiving appropriate + copies of their application or application sources if they may + need to access archived databases without first upgrading + them. + </p> </div> <div class="navfooter"> <hr /> @@ -89,7 +93,8 @@ <td width="20%" align="center"> <a accesskey="h" href="index.html">Home</a> </td> - <td width="40%" align="right" valign="top"> Database verification and salvage</td> + <td width="40%" align="right" valign="top"> Database verification and + salvage</td> </tr> </table> </div> |