Salesforce

How to verify a backup file is the same after it is copied to a new system / location?

« Go Back

Information

 
TitleHow to verify a backup file is the same after it is copied to a new system / location?
URL Namehow-to-verify-a-backup-file-is-the-same-after-it-is-copied-to-a-new-system-location
Article Number000114574
EnvironmentProduct: Progress
Product: OpenEdge
Version: All supported versions
OS: All supported platforms
Other: Verifying backup file.
Question/Problem Description
How to verify a backup is good after transfer of the database backup file to a file server?
How to verify a backup is good after transfer of the database backup file to a cloud vault?
Steps to Reproduce
Clarifying Information
Error Message
Defect Number
Enhancement Number
Cause
Resolution
Prorest with the "-vf" parameter compares the contents of the backup block with the corresponding database block to see if they match.
So long as the database hasn't changed and neither the database nor the database backup file were damaged in a uniform way the prorest -vf should be able to see a difference in the backup file if it does not match the database.

Example


To check the backup file sports.bak against the sports database use:

prorest sports sports.bak -vf

If the target system does not have an OpenEdge installation or does not have access to the source database, then an alternative is needed.

It is common for many products to need to verify that the source version of a file matches a copy of the file after download / copy.
Many use a checksum utility to calculate the MD5 or similar checksum value.
The same tool is used to validate the checksum of the file after it has been copied.

If the two match, then it is reasonably safe to believe there was no error during the copy operation and the copy is the same as the source.
Most operating systems have some form of checksum calculation tool.

NOTE: It is important to use a checksum tool with the same version of the algorithm to validate the file(s) or the results can be different.
Workaround
Notes

References to Other Documentation:
Progress Article(s):
 Considerations when upgrading from OpenEdge 11 to a later OpenEdge 11 version.
 
Keyword Phrase
Last Modified Date12/18/2023 7:13 PM

Powered by