# QAD Progress OpenEdge Database Maintenance Checklist > Source: https://netray.co/tools/qad-openedge-database-maintenance-checklist > Publisher: Netray (netray.co), AI and integration engineering for ERP and manufacturing systems. > Section: Free Tools ## Short answer Daily, weekly, monthly, pre-upgrade and disaster recovery tasks for on-prem QAD databases on Progress OpenEdge, with the utility to use for each. ## Category other-erp ## Erp QAD ## Audience - Progress DBA - QAD administrator - IT operations ## Tool **Kind:** checklist **Groups:** #### 1. Daily **Items:** **Text:** Run an online backup with probkup online to disk and copy it off the server **Critical:** true **Text:** Verify the backup with prorest -vp (partial) and run -vf (full) on a regular schedule **Critical:** true **Text:** Confirm after-imaging is enabled and AI extents are being archived (AI File Management: rfutil dbname -C aiarchiver enable, with -aiarcdir set at broker startup) **Critical:** true Check the database log file (.lg) for errors, warnings and abnormal shutdowns Check promon for long-running transactions and the lock table high water mark Check AppServer and WebSpeed brokers (asbman, wtbman on 11.x; PASOE on 12.x) and the QAD .NET UI or web services #### 2. Weekly **Items:** Capture proutil -C dbanalys (or tabanalys and idxanalys) output and keep it to track growth Review table scatter factor and index utilization from the analysis output **Text:** Check before-image (BI) file size and look for abnormal growth from long transactions **Critical:** true Check buffer hit ratio and lock table use in promon against -B and -L Check free space in each storage area with prostrct statistics #### 3. Monthly or quarterly **Items:** Run proutil -C idxcompact online for indexes with low utilization Schedule proutil -C idxbuild in a maintenance window for indexes that need a full rebuild Plan a dump and load for tables with high scatter or after large purges Review startup parameters in the .pf files (-B, -L, -n, -spin) against observed use Add extents with prostrct add before areas reach their last fixed extent Truncate the BI file with proutil -C truncate bi only during planned downtime #### 4. Before a QAD patch or upgrade **Items:** **Text:** Take a full offline backup and verify it **Critical:** true Run proutil -C holder to confirm no process holds the database before offline work Record table record counts before the change Load schema changes (.df delta) through the Data Dictionary or Data Administration tool on a test copy first Compare record counts and run dbanalys after the change Disable and re-enable after-imaging as required for offline utilities, then take a new baseline backup #### 5. Disaster recovery **Items:** **Text:** Restore the latest backup to a separate server with prorest **Critical:** true **Text:** Roll forward archived AI files with rfutil -C roll forward **Critical:** true Start the restored database, connect QAD and check recent transactions Document restore and roll-forward times against your recovery time objective Keep the procedure, scripts and passwords where the on-call team can reach them **Scoring Note:** Critical items protect recoverability: a verified backup, working after-imaging, a tested restore and control of BI growth. ## Content **Intro:** This checklist lists the routine DBA tasks for on-prem QAD Enterprise Edition and Standard Edition databases on Progress OpenEdge 10.2B to 12.x, with the Progress utility for each. It is grouped by frequency, plus pre-upgrade and disaster recovery tasks. **Sections:** #### How to use it **Body:** Use the daily and weekly groups as a run book and the monthly group as a maintenance window plan. Script the checks you can (probkup, prorest -vp, dbanalys, log scans) and keep their output, because trends tell you more than any single run. Tick items in the tool and export to PDF as evidence for auditors or IT management. QAD installs typically have several databases (qaddb, admin and help databases, sometimes custom ones), so repeat the list per database. #### The utilities behind each item **Body:** probkup online backs up a running database; prorest -vp and -vf verify a backup without restoring it. rfutil manages after-imaging: aimage begin enables it, the AI archiver copies full extents, and roll forward applies them to a restored backup. proutil runs analysis (dbanalys, tabanalys, idxanalys), index work (idxbuild offline, idxcompact online), truncate bi and holder. prostrct add and statistics manage extents and show area use. promon shows activity, locks, buffers and transactions. Check the exact qualifiers in the OpenEdge Database Management guide for your release. **Bullets:** - Backup: probkup, prorest. - Recovery: rfutil. - Analysis and repair: proutil. - Structure: prostrct; monitoring: promon. #### Worked example: BI file growth **Body:** A user runs a large report with a transaction open overnight, and the BI file grows by several GB. promon shows the oldest active transaction and the user behind it. The fix is to end that session and correct the program, not to truncate the BI while the database runs: truncate bi needs the database offline. Daily checks of the log and BI size catch this before the disk fills. #### Version differences and gotchas **Body:** OpenEdge 12 removed the classic AppServer and WebSpeed brokers in favour of PASOE, so asbman and wtbman checks apply to 11.x and earlier. After-imaging must be planned around offline utilities; some operations require AI to be disabled and a new backup taken afterwards. idxbuild needs the database offline and enough temp disk. A backup that has never been restored is not a backup: test restores at least quarterly. **Cta:** If you want your team to ask QAD questions in plain English on your own servers, we can build that on top of a database you already maintain this way. **Faq:** #### How do I back up a QAD Progress database while users are working? **Answer:** Use probkup online with the database name and target file, for example probkup online qaddb /backup/qaddb.bak. It takes a consistent backup while users stay connected. Combine it with after-imaging so you can roll forward from the backup to the point of failure, and verify each backup with prorest -vp. #### What is after-imaging in OpenEdge and why does QAD need it? **Answer:** After-imaging writes every committed change to AI extents. With a backup plus archived AI files you can restore and roll forward to just before a failure, instead of losing everything since the last backup. Enable it with rfutil aimage begin after a backup, and use the AI archiver so full extents are copied away automatically. #### When should I rebuild indexes on a QAD database? **Answer:** When idxanalys shows low utilization or after large purges and archives. idxcompact runs online and is the first step for fragmented indexes. A full proutil idxbuild needs downtime and temp space, so schedule it in a maintenance window. Always back up first and record timings so the next window is planned accurately. #### Can I truncate the BI file while QAD is running? **Answer:** No. proutil -C truncate bi requires the database to be shut down. If the BI file is growing, find the cause first: usually a long-running transaction visible in promon. After a planned shutdown you can truncate it and review the BI cluster size and transaction handling in the programs involved. ## Search terms qad database maintenance, openedge dba checklist, progress probkup online, openedge after imaging, proutil idxbuild, qad support, qad upgrade --- Talk to an engineer: https://netray.co/contact?intent=erp_ai | Machine catalog: https://netray.co/agent/catalog.json