KACE Product Support

The time it takes depends on a few things. I personally don't have a lot of experience benchmarking this time but if others comment on their experience it would help to know what generation of box you have and size of your database.

To "monitor" the upgrade there is the udpate log that is displayed during update. You could also login to the console as the limited netdiag user and run "top" to see what's running. It makes me feel better anyway

It only took 8 or 9 minutes for our upgrade.

I dont know the generation of the box. I cant log in while it is updating to see any of the info. I purchased it last year and dont use it to its full potential. I mainly use if for inventory and software patches. The database is only 400mb.

The webpage that is displayed during the update process is refreshing every 7 minutes. But it is not changing. It seams to be hung up at:

[Wed Mar 9 7:39:58 MST 2011] [notice] check table ORG1.KBOT_LOG_DETAIL
[Wed Mar 9 7:39:43 MST 2011] [notice] optimize table ORG1.KBOT_LOG
[Wed Mar 9 7:39:38 MST 2011] [notice] check table ORG1.KBOT_LOG
[Wed Mar 9 7:39:38 MST 2011] [notice] optimize table ORG1.KBOT_LABEL_JT
[Wed Mar 9 7:39:38 MST 2011] [notice] check table ORG1.KBOT_LABEL_JT
[Wed Mar 9 7:39:38 MST 2011] [notice] optimize table ORG1.KBOT_FORM_DATA
[Wed Mar 9 7:39:38 MST 2011] [notice] check table ORG1.KBOT_FORM_DATA
[Wed Mar 9 7:39:38 MST 2011] [notice] optimize table ORG1.KBOT_FORM
[Wed Mar 9 7:39:38 MST 2011] [notice] check table ORG1.KBOT_FORM
[Wed Mar 9 7:39:38 MST 2011] [notice] optimize table ORG1.KBOT_EVENT_SCHEDULE
[Wed Mar 9 7:39:38 MST 2011] [notice] check table ORG1.KBOT_EVENT_SCHEDULE
[Wed Mar 9 7:39:38 MST 2011] [notice] optimize table ORG1.KBOT_DEPENDENCY
[Wed Mar 9 7:39:38 MST 2011] [notice] check table ORG1.KBOT_DEPENDENCY
[Wed Mar 9 7:39:38 MST 2011] [notice] optimize table ORG1.KBOT_CRON_SCHEDULE
[Wed Mar 9 7:39:38 MST 2011] [notice] check table ORG1.KBOT_CRON_SCHEDULE
[Wed Mar 9 7:39:38 MST 2011] [notice] optimize table ORG1.KBOT
[Wed Mar 9 7:39:38 MST 2011] [notice] check table ORG1.KBOT
[Wed Mar 9 7:39:38 MST 2011] [notice] optimize table ORG1.IPHONE_PROFILE_LABEL_JT
[Wed Mar 9 7:39:38 MST 2011] [notice] check table ORG1.IPHONE_PROFILE_LABEL_JT
[Wed Mar 9 7:39:38 MST 2011] [notice] optimize table ORG1.IPHONE_PROFILE
[Wed Mar 9 7:39:38 MST 2011] [notice] check table ORG1.IPHONE_PROFILE
[Wed Mar 9 7:39:38 MST 2011] [notice] optimize table ORG1.IM_CRON
[Wed Mar 9 7:39:38 MST 2011] [notice] check table ORG1.IM_CRON
[Wed Mar 9 7:39:38 MST 2011] [notice] optimize table ORG1.HD_WORK
[Wed Mar 9 7:39:38 MST 2011] [notice] check table ORG1.HD_WORK
[Wed Mar 9 7:39:38 MST 2011] [notice] optimize table ORG1.HD_TICKET_RULE
[Wed Mar 9 7:39:38 MST 2011] [notice] check table ORG1.HD_TICKET_RULE
[Wed Mar 9 7:39:38 MST 2011] [notice] optimize table ORG1.HD_TICKET_RELATED
[Wed Mar 9 7:39:38 MST 2011] [notice] check table ORG1.HD_TICKET_RELATED
[Wed Mar 9 7:39:38 MST 2011] [notice] optimize table ORG1.HD_TICKET_FILTER
[Wed Mar 9 7:39:38 MST 2011] [notice] check table ORG1.HD_TICKET_FILTER
[Wed Mar 9 7:39:38 MST 2011] [notice] optimize table ORG1.HD_TICKET_CHANGE_FIELD
[Wed Mar 9 7:39:38 MST 2011] [notice] check table ORG1.HD_TICKET_CHANGE_FIELD
+



There is no hard drive activity on the box.

Going from version 5.1.31237, it took me 8 minutes and 45 seconds from start to finish.

Kbox Size:
kbox_dbdata.gz (61.26 MB)
kbox_file.tgz (7.5 GB)

My upgrade to 5.2 was smooth, but when I upgraded to 5.1 my KBOX hung during the upgrade. I ended up having one of the techs tether in and truncate a table (I think it was one of the log tables). After that, we re-ran the update and were finished in a few minutes.

Casey

It's on a potentially very large table. 400mb is bigger than average. You could try turning off agent log retention in all ORGs before the udpate.

Turn off Agent log retention. WARNING: This will delete the copy of the client logs on the kbox. There are a lot of historical client logs on the database and if you want keep them they need to be upgraded. However, if you turn off retention then there will be less to upgrade and you will greatly reduce the time it takes to complete this long step. Note that if you are on a 1200 you need to do it separately in each Organization. If you do not turn off agent log retention then this step could take a long time. If you do turn it off (and back on) then you will only lose the agent logs that are currently stored. New logs can be generated. To see an example of what logs will be deleted go to the inventory detail of any machine and look at the log section there.

• Go to Agent settings and set Agent log retention to Turn off log retention
• Click Save
• Go to Agent settings and set Agent log retention to Save all Agent Logs
• Click Save

Turning off the logs didn't work. I had to have Kace tether in and fix the corrupt database. The update completed without issues after the db fix.