Backup internal database HP Dataprotector failes to run

imagesAt a customer site I received a notification that the job that backups the HP Dataprotector internal database (DP: IDB)had failed to run. The rest of the environment backup was successful. When the backup of the internal database does not run a backup report is not send to the administrators mailbox

The backup job for the internal database generated the following error:

[Critical] From: DBBDA@s-dp01.customer.local "[Database]: s-dp01.customer.local"  Time: 8/14/2013 7:15:48 AM
    Velocis server ob2_40:
    (Change log cycle timeout (S_BUTIMEOUT)).

[Critical] From: DBBDA@s-dp01.customer.local "[Database]: s-dp01.customer.local"  Time: 8/14/2013 7:15:48 AM
    Velocis server ob2_40:
    Backup mode not active
    (backup mode is not active (S_BUNOTACTIVE)).

[Warning] From: DBBDA@s-dp01.customer.local "[Database]: s-dp01.customer.local"  Time: 8/14/2013 7:15:49 AM
    Cannot un-lock the keystore.

[Major] From: DBBDA@s-dp01.customer.local "[Database]: s-dp01.customer.local"  Time: 8/14/2013 7:15:49 AM
    ABORTED Database HotBackup Disk Agent on s-dp01.customer.local "[Database]: s-dp01.customer.local"

The first step after a failed backup is to retry the backup job. This job end successful.
After some research I found that this behavior is accurse if the IDB backup starts too close to a Change Log recycling.

To make sure that HP Dataprotector does a retry we have to alter an configuration file.
This file is located under C:\Program Files\OmniBack, the file is called omnirc.
Add the OB2DBRETRY variable to this file with a value for the number of retry you want HP Dataprotector to perform.

OB2DBRETRY=1

Because at this site this variable is already in the file, I’ve raised the value to 3. The next morning the backup of the HP Dataprotector internal database was performed.