VM upgrade vs replacement?

  • 1
  • Question
  • Updated 5 years ago
  • Answered
Considering that I originally started out on a HiveManager 3.4 VM, and have been doing just upgrades since, would now be a good time to export my config, download a fresh VM(and go 64bit?) and import my configuration into the new HM 6.0r2?
Photo of Dave Brown

Dave Brown

  • 15 Posts
  • 1 Reply Like

Posted 5 years ago

  • 1
Photo of Crowdie

Crowdie, Champ

  • 972 Posts
  • 272 Reply Likes
I have a customer in almost the same situation and we are going to move to the 64-bit VM when we upgrade from 5.1r5 to 6.0r2. With the number of clients we are currently supporting the 3 GB memory limit on the 32-bit VM is becoming an issue and the new Application Visibility and Control functionality in 6.0r2 will increase the demands on the CPU and memory.
Photo of Dave Brown

Dave Brown

  • 15 Posts
  • 1 Reply Like
I'm sure I could get away with just upgrading, but my hunch is that the upgrade just updates the HiveManager code and doesn't do anything with the underlying OS in the Virtual Appliance. Its probably time for a fresh VM.
Photo of Andrew Garcia

Andrew Garcia, Official Rep

  • 368 Posts
  • 120 Reply Likes
You are correct that the upgrade will not address the settings of the underlying VM. We have provided specific instructions in the release notes for upgrading the 32-bit HiveManager VM, which needs an additional processor, memory, and a change to the JVM settings. Release Notes

However, depending on the size your installation, you may well find the 64-bit platform to be a better long term solution.

To migrate, you will need to take a full backup (for upgrades) of your existing server. If you have multiple VHMs, use the root admin to do this (rather than a per VHM process). Then you can restore the resulting file into the new server.

However, you will need to contact support so they can reset your entitlement key so it can be reapplied to the new server.
Photo of Adam Conway

Adam Conway

  • 101 Posts
  • 55 Reply Likes
I, personally, did this recently. I abandoned my VM instance and moved my devices to a fresh instance in the cloud - not because I had any problems, but just to see what the experience was like to start fresh with a new network. Given that I am a product guy, that is a good idea... that said, I found unanticipated benefits. Knowing the product better now I reorganized all of my networks, cleaned up a bunch of old, unused configs and ended up using a lot more features.

To me it was worth it, just for that.
Photo of Dave Brown

Dave Brown

  • 15 Posts
  • 1 Reply Like
I finally had time to do this weekend and it went very well. I contacted support on Friday to have them unregister my licenses, did an upgrade backup of my database, imported the OVA into vSphere, fired it up, re-IP'd it, pasted in my serials and restored the backup. Everything is working fine so far and I'm on a fresh 64bit VM now.
Photo of Anjanesh Babu

Anjanesh Babu

  • 68 Posts
  • 7 Reply Likes
Replaced vm. Apart from not being able to increase RAM beyond 4GB on the old 32 bit vm , it would be simply cleaner to re deploy in terms of space for expansion and scalability on the 64 bit platform.

Backed up database, exported certificates and key for a good measure and carried out the install using the IMG file instead of an OVF.

Shutdown down the old vm reused the same ip addresses and everything is now working - including the ssl certificates for the domain name.

Did not even have to reenter the license keys - it was all there when the database import finished.
Unbelievably simple.

Edit - thanks to Adam Black on another thread, just found out that the TFTP service on the new Hivemanager is not turned on by default . This needs to be manually flipped on.
Photo of Crowdie

Crowdie, Champ

  • 972 Posts
  • 272 Reply Likes
If you need more than 3 GB of memory for HiveManager then you should be running a 64 bit version as 32 bit operating systems have "technical issues" when they attempt to address more than 3 GB of memory.

I am not sure if the 32 bit HiveManager images support PAE (physical address extension), which allows 32 bit operating systems to address 36 bit physical addresses. Aerohive Support may be able to advise.