Verification fails when there are existing files left behind by a previous verification process. This can happen when the verification process in interrupted unexpectedly, otherwise the verification process cleans up after itself.
Update the verification process:
[x] Check to see if files where left behind by a previous verification.
[x] Check to see if the local server is running. This could indicate the previous verification process is not complete.
[x] If the local server is not running, and there are existing database files, initialize the environment (delete the existing files).
[x] If the local server is running and there are existing files, the chances are the previous verification has not completed ... send an alert notification. This likely indicates there is something wrong with the verification schedule. Most likely, database verification schedules have been discretely setup for individual databases and there is not enough time between them, or there are duplicate verification schedules. This can easily be avoided by using the recommended configuration ./backup.sh -s -v all which will verify the most recent backup of each database in sequence.
Verification fails when there are existing files left behind by a previous verification process. This can happen when the verification process in interrupted unexpectedly, otherwise the verification process cleans up after itself.
Update the verification process:
./backup.sh -s -v allwhich will verify the most recent backup of each database in sequence.