Important Notice: Our web hosting provider recently started charging us for additional visits, which was unexpected. In response, we're seeking donations. Depending on the situation, we may explore different monetization options for our Community and Expert Contributors. It's crucial to provide more returns for their expertise and offer more Expert Validated Answers or AI Validated Answers. Learn more about our hosting issue here.

After obackup is killed by using kill -9, obackup can not perform any operations right away, what went wrong?

April 26, 2017away kill Killed operations perform right wrong

0

10 Posted

After obackup is killed by using kill -9, obackup can not perform any operations right away, what went wrong?

1 Answer

0

10 Posted

First, users should never terminate obackup by ‘kill -9’. This operation abruptly interrupts EBU operations, force EBU to take relatively long time to recover from it. During the interim, attempts to run obackup will fail due to the fact that recovery process is in progress. There are entries in the log file with “Failed job XX with system table space ‘LOCKED'”, or “Inconsistent internal state”, etc. These are usually the results of kill -9. Recovery from this for user is relatively simple. Just wait. Make sure brd process is running(If not, start a normal obackup job even if it fails). Monitoring $OBK_HOME/log/brd.log file, until “Finished cleaning job XX” appears before continuing on any EBU operations.