When you create a DB2 enabled Notes database from an NSF database, the DB2 enabled Notes database can require twice as much disk space as the NSF required. With ongoing use, the DB2 enabled Notes database version can grow much larger. Allot twice as much space for the DB2 enabled Notes database as you allotted for the NSF.

As databases are maintained, that is, documents are added and deleted, views are built, and DAVs are created, allow an additional two times as much space for DB2 enabled Notes databases as allowed for NSF databases. In total, allow four times as much space for each DB2 enabled Notes database as is allotted for each NSF.

Examples

Example 1 -- One mail database uses 512 MB as an NSF; therefore, you need to allow 1 GB for initial creation of the DB2 enabled Notes database. Mail files tend to be active with many inserts and deletes. The DB2 enabled Notes database is an active database; therefore, allow 2 GB for ongoing use.

Example 2 -- A reference database uses 512 MB as an NSF; therefore, allow 1 GB when you create the DB2 enabled Notes database.

Example 3 -- DB2 enabled Notes databases are stored in groups by default. Ten DB2 enabled Notes databases use the same group, DB2 tablespace, and DB2 container file. Assume there are ten mail databases, 512 MB each, and all ten are in the same DB2 group. The NSFs use 5 GB total. When you create the DB2 enabled Notes databases from the NSFs, allow 10 GB. For ongoing use, allow 20 GB.

Note Currently there are issues that make it very difficult to free up the unused space, so allow a lot of space.

For instructions about creating database replicas, see the topics Creating a cluster and Creating replicas in a cluster.

See also

Administering the Domino and DB2 environment

Glossary