Configuring database storage for Db2
Db2 supports a variety of both traditional and software-defined storage types. You define your storage types during database provisioning.
The preceding diagram illustrates the storage configuration options for Db2.
Mandatory storage:
- System Data - shared (RWX) volume for Db2 metadata
- Data - non-shared (RWO) volume for database storage
- Backup - shared (RWX) volume for database backups
- Activelogs - non-shared (RWO) volume for transactional logs
- Tempts - non-shared (RWO) volume for temporary tablespaces
- Archivelogs - non-shared (RWO) volume for archive logs
- Auditlogs - shared (RWX) volume for audit logs
For a full listing of supported storage types, see Storage requirements.
Notes:
- When provisioning the database, for user data (the main database data), select ReadWriteOnce (RWO) access mode for your storage.
- Select 4K sector size during provisioning if your storage supports 4K (this setting is mandatory for Portworx). Db2 also supports 4K for OpenShift® Data Foundation.
- Appropriate host-attached SAN storage is usually the better performing option for OLTP workloads. For a comparison of NAS versus SAN storage, see Storage technologies for IBM Db2 Warehouse.
- For more information about configuring dynamic provisioning for NFS storage for testing, see the External Storage topic in the
kubernetes-incubator
repository on GitHub. - For more information about configuring a hostPath for data storage, see HostPathVolumeSource in the Red Hat® OpenShift documentation.
Attention: Starting with IBM Cloud Pak® for Data 4.6.0, support for hostPath is deprecated and will be discontinued in a
future release.