You are here: Advanced Features > Defragment > Defragmentation Configuration

Defragmentation Configuration

You can configure the defragmentation processes for your needs. This topic discusses the available configuration options.

First you need to configure which database file to defragment. See "Original Database And Backup"

It's also recommended to use the db4o database configuration for the defragmentation process. This ensures that all low level settings which influence the database-file layout are used. See "Database Configuration"

When you defragment large database you should configure a commit-frequency to speed up the defragmentation process. See "Commit Frequency"

If you have refractored your classes you might want to remove old meta data. This is possible with the class filters. See "Class Filter" 

By default the backup file isn't deleted after a successful defragmentation. You can change that. See "Delete The Backup"

You can force a database update before defragmenting the database-file. See "Upgrade Database File"

You can disable the read-only more the for backup file. See "Disable Read Only Mode"

If you want to have different storage implementation for the old database file and the new defragmented database file you can configure a separate storage. See "Configure Storage for Backup File"

You can change the id-mapping implementation for the defragmentation-process. See "Configure IDMapping"