About allocating more memory before database defragmentation
The database defragmentation process may require more memory to run successfully. This section provides the procedure to allocate more memory to the database cache using the -ch option before database defragmentation.
Note:
The information that is published in this section is based on the tests that were performed in Veritas Lab in a controlled environment with expert users. These can only be used as guidelines and should not be used as 100% accurate benchmarks.
Note:
The database defragmentation process requires the available disk space to be double the current database size.
To allocate more memory to database cache
- Backup the existing OpsCenter database.
- Modify the memory settings to allocate more memory to the database cache.
The following table shows an example scenario where the OpsCenter database size is 48 GB. It lists the original memory settings that you need to modify to the new settings before database defragmentation so that there are no performance issues during the defragmentation.
Example scenario: OpsCenter database size = 48 GB
Original memory settings
Modified memory settings (to allocate more memory to database cache)
Memory allocated for the OpsCenter database process = 24 GB
Memory allocated for the OpsCenter database process = 39 GB
Memory allocated for the OpsCenter GUI process = 4 GB
Memory allocated for the OpsCenter GUI process = 1 GB
Memory allocated for the OpsCenter Server process = 12 GB
Memory allocated for the OpsCenter Server process = 1 GB
Memory allocated for the Operating System = 8 GB
Memory allocated for the Operating System = 8 GB
- Restart OpsCenter services.
- Defragment the OpsCenter database.
- Revert to the original memory settings.