You can refer BPPM Troubleshooting Guide. There are some description to clean DB files.
Check ProactiveNet\pw\dbarchive - the system creates backup every week either from cron or scheduled tasks
Pn_WeeklyJob_DBArchiveSunAT0530. You could stop this and create your own script to backup to a new folder. I expect if your disk space is low you may not have a backup anyway.
Also ensure all "debug" is off as this will fill the logs\debug folder. All these files can be removed and in normal operation not files should be written to here.
This could be due to a bug in 8.5:
Knowledge Article ID: KA359337
Published date: 08/13/2012
The file system on which BPPM is installed is increasing very fast on Production Sever. Major concern is the Database of BPPM which also reside on the same drive.
LP: BMC ProactiveNet Performance Management 8.5.00
DR: BPPM Database 8.5.00
Details: Concern with the file system on which BPPM is installed. Its size is continuously increasing. Total size of File system is 199 GB and free space is 5 GB right now. Please suggest how to reduce the size. Its urgent.
1) Confirmation on incremental backup if it started with the BPPM installation or we have to run a command to execute and start it.
Ans: The database archives are performed on a regular basis. By default the ProactiveNet server performs a full db archive once per week with incremental archives once every day.
2) What is the file name which can changed for the path of incremental backup?
Ans: Go to pw\pronto\bin\dbarchive.bat then change the third argument to reflect to the new location. Once this change is saved then the next weekly archive will be written to the new location. You will need to delete the existing the db file and transaction file (pronto.log and all the contents from the incremental directory too (AA**.log)) from the pw\dbarchive directory after the next weekly archive.
The location for the incremental log files cannot be changed. Daily jobs will save these files in this location only.
3) What if disk size is full, how it will affect BPPM application?
Ans: Once disk size is full, your db will crash and not able to perform any operation on BPPM
4) Recommendation why incremental backup should be executed?
Ans: Incremental backup of the database is recommended as part of regular maintenance to provide a measure of safety against hardware failure or administrative errors.
5) How to manually kickoff a database archive?
Ans: Run command "pw database archive" from command prompt. This command archives your ProactiveServer database by storing a snapshot of the database and transaction log files in the archive directory. After completion the original transaction log is pruned.
6) If sufficient space is not present on disk to store the database archive, what else can we do to reduce the file system utilization?
Ans: You can change the path and it can be save on different location. Also make sure clean-up of old BPPM logs and dump file regularly