/build/static/layout/Breadcrumb_cap_w.png

Best Practices Question


How long to upgrade K1000 to 7.0

12/14/2016 3377 views
We just implemented the K1000 in our environment a few months back and have not performed an upgrade yet. Looking to see an approximate window of time to upgrade from 6.4 to 7.0. Also looking for best practices as well. We host our K1000 on a VM in our environment so I would have a snapshot taken before upgrading. Thanks! 
0 Comments   [ + ] Show comments

Comments


All Answers

2
We are on a physical appliance and I believe the upgrade took about 2 hours. Longer than normal that's for sure.
Answered 12/14/2016 by: troyr
Yellow Belt

2
it really depends on the size of your database, the usage etc.
Since also backend updates are made there will be one or more reboots.

My experience sais: beween 30min and 3hr everything is possible.

Create a full backup and store it outside of the appliance is always the first step.
Then if you have the ressources, take it out of production (move it into an internal network where no agent is able to connect it anymore etc)
This will speed it up a bit.
Answered 12/14/2016 by: Nico_K
Red Belt

2
I try the automatic upgrade, but my k1000 cannot identify the update, so i download the update an try to apply manual, but after 24 hours nothing happen, then i download the de complete k1000 v7 virtual machine and try to restore the DB but i receive the message in the logs about the versión of the DB is not compatible, any ideas to fix?
Answered 12/17/2016 by: paulhdez
White Belt

Don't be a Stranger!

Sign up today to participate, stay informed, earn points and establish a reputation for yourself!

Sign up! or login

Share

 
This website uses cookies. By continuing to use this site and/or clicking the "Accept" button you are providing consent Quest Software and its affiliates do NOT sell the Personal Data you provide to us either when you register on our websites or when you do business with us. For more information about our Privacy Policy and our data protection efforts, please visit GDPR-HQ