Quantcast
Channel: Data Protector Practitioners Forum topics
Viewing all articles
Browse latest Browse all 3189

(DP) Support Tip: IDB backup fails Cannot lock the keystore, Key Store Database corrupted.

$
0
0


Problem

A Data Protector Internal DataBase backup fails...

[Normal] From: OB2BAR_POSTGRES_BAR@CM_hostname.co.com "DPIDB"  Time: 30/12/2015 12:59:31
               Completed OB2BAR Backup: CM_hostname.co.com:SMBFs:15 "IDB"
[Warning] From: OB2BAR_POSTGRES_BAR@CM_hostname.co.com "DPIDB"  Time: 30/12/2015 12:59:31
[81:526]               Cannot lock the keystore.
[Critical] From: OB2BAR_POSTGRES_BAR@CM_hostname.co.com "DPIDB"  Time: 30/12/2015 12:59:32
[81:528]               Key Store Database corrupted ==> backup aborted!
               Please run omnidbcheck to check database.

One solution that may help solve this problem

- Ensure no Data Protector sessions are in Progress
so `omnistat` says "No currently running sessions".

- Stop DP (`omnisv -stop`)

- if present, delete the "dbcheck.keystore" file.
Windows default location - \ProgramData\OmniBack\tmp

- Start DP (`omnisv -start`)


An alternative problem/solution that may help (if the above does not help)

Sometimes the DP "KMS" service is down:
    rds     : Active  [4188]
    crs     : Active  [4840]
    mmd     : Active  [4236]
    kms     : Down                               
    uiproxy : Active  [4836]
    omniinet: Active  [4732]
    Sending of traps disabled.

The solution that may help solve this problem

- Ensure no Data Protector sessions are in Progress
so `omnistat` says "No currently running sessions".

- Stop DP (`omnisv -stop`)

- if present, rename the "kms_audit.log" file.
Windows default location - :\ProgramData\OmniBack\log\server\

- Start DP (`omnisv -start`)


Viewing all articles
Browse latest Browse all 3189

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>