Database file types in more detail
This article provides technical background information on the various file types which make up a TPX Enterprise database. You will not need to know any of this for normal program administration but in some circumstances it might be useful to be aware of these details.
Database file types
The regular database files are of type:
When you manually "zip" (or backup) only the files inside the database directory ending in '.dat', '.idx', '.blb., '.dbi', you can always restore a 'clone' of this database by copying these files back from the backup (zip) archive into a directory of your choice. But preferably you should use the built-in backup function of the TPX Administrator program (described here) which automatically selects the right files for creating a zip backup archive.
The .dat files are the core of a TPX database. They contain the principal information necessary for operating a TPX database. This includes identifiers, guids, node properties, references, etc.. ('.dat' comes from 'data').
The .blb files can contain huge amounts of data which might vary in size tremendously, such as articles, images, attachments ('.blb' comes from 'blob'). Since .blb files contain the major part of the textual information in a database (articles !), it is essential to include them in a backup as well.
The .idx files are used to speed up accessing the information in the .dat and .blb files ('.idx' comes from 'index'). Although this might sound as if .idx files are not essential, you should never delete any .idx files from your database manually and always include the .idx files in your backup copies.
There is only one .dbi file and it is called 'tpx.dbi'. It contains information regarding the entire database ('.dbi' comes from 'database information') and it also should never be deleted manually, and included in any backup.
Safety copy file types
During an optimize⁄repair action (see Table management) TreePad creates 'safety copies' of all database files. The option 'create safety copies' can be found at the bottom of the table management page (in the TPX Administrator program). This option can be turned off. Although this will save disk space, it is recommended have it enabled because when a disaster happens during the optimize⁄repair action (such as a computer crash or a power failure) the halfway optimized file will probably not be totally readable. In the rare case that this happens, you can just copy the safety copy files to another directory (and the regular database files which do not yet have a safety copy), rename the safety copy files, and you have a valid copy representing the original state of your database (before the optimize action).
The following type of files are created by TPX Enterprise during a database optimize or repair action.
These are copies of .dat files. When TreePad performs an optimize or repair by default the old (non-optimized) versions of the .dat files are copied to files with the same name except ending in .dbk.
These are copies of .idx files.
These are copies of .blb files.