This text is a work in progress—highly subject to change—and may not accurately describe any released version of the Apache™ Subversion® software. Bookmarking or otherwise referring others to this page is probably not such a smart idea. Please visit for stable versions of this book.

Appendix D. The Berkeley DB Legacy Filesystem

Table of Contents

Configuring Your Berkeley DB Environment
Limitations of Berkeley DB
Architectural Limitations
Network Share Deployment
Fault Tolerance and the Need for Recovery
Maintaining Berkeley DB Repositories
Berkeley DB Recovery
Purging unused Berkeley DB logfiles
Berkeley DB Utilities

Long ago, when Subversion first learned to store versioned data, it did so using a storage layer implementation based on the Berkeley DB (BDB) transactional database system.[86] As the product matured, though, this storage layer implementation was joined by—and then outmatched by—another one, the FSFS backend which is used by the vast majority of Subversion's repositories today. In Subversion 1.8, the Subversion development community announced that the BDB-based storage layer was being officially deprecated.

This appendix presents some of the documentation about administering BDB-backed repositories featured more prominently in previous versions of this book.

[86] Okay, strictly speaking, it used XML files for starters. But that was never intended for public release.