OmniBack II 3.5 Purge Hanging

[Ashish Tripathi]

Hi Admins,
I am using OmniBack 3.5 and my problem is that the purge session which is started automatically by OmniBack at 12 PM doesn't show any activity for 5-6 hours and ultimately I have to do "omnidbutil -purge_stop" to stop it.It used to work fine earlier.Has anything gone wrong with the database?
Any help will be greatly appreciated.
Ashish Tripathi

[A. Clay Stephenson]

Ashish,

My first guess is that the database has become corrupt. I assume you have monitored the purge while it is running and see no activity.
I would check the database with omnidbcheck -extended (be patient) and if errors are reported fix it with omnidbcheck -fix.

You should probably check the size of the database with omnidbutil -extendinfo and omnidbutil -info. If you are near maximums you will need to extend the database.

If you have added new backup specifications that too could dramitically increase the purge times. Again, I would monitor a running purge session to see if the numbers are climbing -- this could be perfectly normal.

Clay

[Ashish Tripathi]

Hi,
If I do "omnidbcheck -extended" It shows me that "database check is already running".
Even though I stopped OmniBack omnisv.sh stop and killed all opened sessions then also omnidbcheck is giving same error message.
Ashish Tripathi

[A. Clay Stephenson · Accepted solution]

Ah, just what I needed to know.
See if you have a file /var/opt/omni/tmp/dbcheck.lk.

It'sd a lock file. Then do an omnisv.sh stop;
check that all omni processes are gone via ps;
then omnisv.sh -start.

I'm pretty sure you're fixed.

Clay

[A. Clay Stephenson]

Sorry Ahish,
I got ahead of myself. If you find the lock file, remove it. That's when been hanging everything. It thinks an omnidbcheck is running when it's really not.

Clay

[Ashish Tripathi]

Thanks a lot !!!!!!Yep...purge counter seems to be moving now...its slow but as long as it moves I am happy...Thanks again for u'r prompt and accurate reply.
Ashish