Database vacuum? Help

[silve66]

So we have a new phone system and minimal training on it.... We've been receiving this lately. How do you restart this so it will perform a full vacuum? We have already rebooted phone system and doing so causes our phones to not work, the IPOCC server doesn't fail over to secondary like it's supposed to... How do we restart this device without causing other issues

Thanks for any help - we have a lot more questions

06/09/16 01:00:11 AM It is now 231 days since the last full database vacuum. The recorder will perform a full vacuum the next time it is restarted. This may take some time. To postpone this to the following reboot, clear the setting on the System Settings > Server page. You MUST restart the recorder and allow it to vacuum the database at least once every 240 days.
06/09/16 01:00:11 AM Purged 1806KB of old log files. Now 421458MB free.

[mnorst]

It sounds like you may be mixing some of the equipment and have multiple things occurring across different systems.

To the Contact Recorder error message, this is actually a component of IP Office not IPOCC so support in this sub-forum may be limited. I can say that I had the same error and the support ticket resolution is that this is non-impacting in IPO versions 9.0 and 9.1 per SOLN271910. https://support.avaya.com/ext/index?...&id=SOLN271910

That said, you should be able to restart the Contact Recorder itself via the maintenance webpage without restarting the entire linux box, however if you restart the linux box your phones will most likely fail back to the secondary IPO as the primary is rebooting. IPOCC doesn't have failover capabilities that I know of in the 9.1 line and only attaches to the primary server.

Hope that helps!

[silve66]

Thanks MNORST... It sounds like it's a feature implemented by AVAYA which has no use for us, although we can't remove either.


Great - Get daily alerts for a problem that really isn't a problem! Now how to explain this to my boss who also receives these alerts!

[tdaway]

Am also finding it difficult to explain this to customer who is also receives these alerts. Someone said to me the 'full database vacuum' process simply involves stopping Contact Recorder then starting it in Web manager. tried this but did not see any change. Mine is now saying:

"It is now 425 days since the last full database vacuum. The recorder will perform a full vacuum the next time it is restarted. This may take some time. To postpone this to the following reboot, clear the setting on the System Settings > Server page. You MUST restart the recorder and allow it to vacuum the database at least once every 240 days."

And customer is now asking if this has any impact on ACR operation.

[dunfo]

Hi - I have exactly the same issue. Restarting Contact Recorder in the Application Server doesnt solve it. Also, we tried to disable the vacuum process but after a restart the option was selected again. There is an option to use Shell Command is to vacuum the Contact Store DB but still trying to find out what that is.

[akilmister]

Contact Recorder does not actually support the DB vacuum feature (at least not yet anyway).
Although there is no way to supress this alert the good news is that there is no technical impact to the product features and performance.

[tdaway]

Thanks for the comforting words