Verify a backup
- Last Updated: January 27, 2026
- 2 minute read
- OpenEdge
- Version 12.8
- Documentation
Immediately after backing up the database, verify that the backup does not contain any corrupted blocks. Use the Restore (PROREST) utility to verify the integrity of a full or incremental backup of a database as follows:
- Run PROREST with the Partial Verify (
-vp) parameter. With this parameter, PROREST checks the backup for bad blocks and reports whether any exist. - Run PROREST with the Full Verify (
-vf) parameter. With this parameter, PROREST compares the backup to the database block-for-block.
For more information, see Use the PROREST utility to restore a database.
proenv>probkup sourcedb3 sourcedb3.bk
OpenEdge Release 12.2 as of Fri May 22 19:02:12 EDT 2020
1464 active blocks out of 1763 blocks in sourcedb3 will be dumped. (6686)
0 BI blocks will be dumped. (6688)
The blocksize is 4096. (6994)
Backup requires an estimated 5.7 MBytes of media. (9285)
Restore would require an estimated 1464 db blocks using 5.7 MBytes of media. (9286)
Backed up 1464 db blocks in 00:00:00
Wrote a total of 44 backup blocks using 5.9 MBytes of media. (13625)
Backup complete. (3740)
proenv>prorest sourcedb3 sourcedb3.bk -vf
OpenEdge Release 12.2 as of Fri May 22 19:02:12 EDT 2020
This is a full backup of C:\OpenEdge12\WRK\sourcedb3.db. (6759)
This backup was taken Thu Sep 17 16:37:49 2020. (6760)
The blocksize is 4096. (6994)
It will require a minimum of 1763 blocks to restore. (6763)
Full verify pass started. (3752)
Verified 1464 db blocks in 00:00:01
Full verify successful. (3758)The -vp or -vf parameters do not actually restore the database. They only verify the status of the backup, notify you if there are any bad blocks, and report whether the blocks are recoverable. You must run the restore utility again (without the partial or full verify parameters) to restore the database.
When you use the -vp parameter, PROREST scans
the backup and recalculates the CRC code for each block. It then
compares the newly calculated CRC code with the CRC code stored
in the block header. If the codes do not match, PROREST marks the
block as bad and displays the following message:
|
If the backup contains error-correction blocks and a redundancy set contains only one bad block, PROREST uses the error-correction block (and the other blocks in the redundancy set) to re-create the bad block. The error-correction block is the EXCLUSIVE OR of the backup blocks in the redundancy set. When PROREST recovers the block, the following message appears:
|
If the redundancy set contains more than one bad block or if the backup does not include error-correction blocks, PROREST cannot recover the bad block and displays the following message:
|
PROREST also cannot recover a corrupted block if the error-correction block itself has a CRC check failure. In this case, the following message appears:
|
If PROREST encounters 10 unrecoverable errors during the verify pass or during the database restore, you can terminate the verify operation, as shown:
|