/build/static/layout/Breadcrumb_cap_w.png

K1000 10.0 Upgrade

Is anyone else experiencing long upgrade times or upgrade failures with their K1000 virtual appliance when upgrading from 9.1 to 10.0?  Ours seems to be upgrading for 6 hours and we are going to let it sit overnight. Anyone else experience this?


3 Comments   [ + ] Show comments
  • Please give us more information about your environment. Is this a Virtual appliance?
    if so, Hyper-V or VMware. What is the host the virtual appliance it is running on?

    Please do not reboot the appliance if you have not received a upgrade completion message.
    If rebooted during an upgrade can corrupt OS and/or database.
    Call support if the upgrade as not completed. - KevinG 4 years ago
    • It's on VMware ESXi 6.7 . The host is an HP Blade Center. We took a snap shot of it before the upgrade so we are reverting back to that for now. We let it sit for 14 hours. Since this is a prod environment we will have to stand up a fresh 10 environment and probably migrate data over since we cant be down during the day as KACE support hours aren't available when the upgrade is done. - dnitschke 4 years ago
  • Was there any message on the VM console before reverting to the snapshot? If it should happen again, you may want to let support take a look at the logs before reverting to a snapshot. - KevinG 4 years ago
    • There was nothing on the console. We have quest support on the line now. Tried explaining to him that we let it sit for 14 hours over the weekend but he doesnt seem to care and is refusing to connect into the system to see whats going on. At this point i'm pretty upset since we are doing the same exact thing that we did before and my tech is wasting his evening on this. - dnitschke 4 years ago
  • Just did mine this morning and it took about an hour. It is a Hyper-V VM.

    The only issue I had was that it appeared to be complete but I could not login. I had to go to the VM console and check the display which also appeared to be at the normal text login prompt. After a couple of times trying to login via FQDN I resorted to IP and was able to login and accept the T+Cs.

    Then the VM rebooted one more time and then I was able to login using FQDN again. - JordanNolan 4 years ago

Answers (3)

Posted by: acid8k 4 years ago
Yellow Belt
1

no, the appliance update was quick, like 1 hr without problems

Posted by: kaluaabyss 4 years ago
White Belt
1

Was it stuck on 'starting mysql' following the OS package updates and prior to the db upgrade?

We had to backup and restore to a new virtual appliance and then upgrade to resolve that issue.

https://support.quest.com/kb/119863/how-to-migrate-database-between-multiple-smas-k1000s-


If your not on the most recent 9.1 version, support can provide you older virtual appliances if you open a ticket. (Have to backup and restore onto same exact version)

Posted by: Hobbsy 4 years ago
Red Belt
0

Check the main KACE console, I carried out an update today which took over 4 hours, eventually on checking the main console the system was sat waiting for keys to be hit or passwords to be entered, which resolved the issues and completed the upgrade 

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