IMPORTANT: Before proceeding with any update Turbonomic strongly recommends that you prepare a full backup.

The installation procedure will check whether you have adequate disk space, but to save time, you may wish to perform a quick check before proceeding. To check the disk space usage on your server, SSH into the Turbonomic instance asroot(default password isvmturbo) and issue the command: "df -kh" (no quotes).Make sure you have at least 5GB of disk space left. Some upgrades may require more disk space; the actual amount is mainly dependent on the size of your database, and it's the space available to the database partition that is usually the determining factor. If you have a large installation and a large database, at least 15GB is a more reasonable estimate.

Perform a snapshot of the VM. This will provide a reliable restore point if you have any issues during the upgrade.

Restart your instance.

Updates may take some time to complete depending on the size of your topology and database.

PLEASE DO NOT RESTART the Turbonomic VM during this process if the UI is not responding!

Offline updates are required if your Turbonomic instanceis not connected to the internet. If it has an Internet connection, even through a configured proxy, it's simpler to do an update, as described at

To determine the architecture/version of your Turbonomic Server, go to (or Help -> About) or in the Admin tab -> Maintenance then Software Updates -> About, you will see a detailed output of your Turbonomic Server version.

NOTE: The current default OS isCentOS.

6.3.6

New Version Link: If you would like to upgrade to the newest release 6.3.5 (release notes), download the offline update zip file from one of the below links.

NOTE: If you see "The file selected is too large!" after selecting "Upload", follow the instructions here to increase the limit.

Updates occur in stages. The software itself is updated immediately, as are certain configuration changes. Some updates, however, require significant restructuring of your database files. This can take many hours, depending on the size of your topology and how much data is retained in your database. To maintain the data integrity and avoid potential issues, startup of the system is halted till the database restructuring is complete. Until this process is complete, login to the instance is also disabled. Please do not restart the server during this time.

Hi Matt - That's a good idea. We'll look into the update naming to see if we can make this more intuitive/include the version numbering.

OVA availability lag is actually 'by design' in the sense that we recommend our newer customers deploy initially using our GA-1 release and reserve newer GA releases and features for those customers who really need them. OVA's are generally consumed by new users , but of course as an existing customer you're free to update from a pre-5.5 instance at any time and we don't limit customers ability to update these)

Hence the latest OVA is currently 5.4 with the 5.5 OVA due to become available when 5.6 release ships (ETA June 2016)

Check on the Status/Progress of an ONLINE Update brings me to a page that says "Access to this place or content is restricted. If you think this is a mistake, please contact your administrator or the person who directed you here." I am logged in on both pages. Please advise.

Hi Alan, I check on our forum permissions and I noticed that you did not have proper access to all of our customer forums. I've made the correction on our end and you should have access to that page now.

Even i'm facing similar issue "Access to this place or content is restricted. If you think this is a mistake, please contact your administrator or the person who directed you here." Please grant me access. I need to perform an update to version 6.3.8.

Can you confirm the version information from your current installation? You can obtain this by clicking on the "VMTurbo" logo at the top of this update page and screen grabbing the contents of the popup that appears..

It looks like you are trying to apply the Redhat version of the update, did you deploy VMTurbo application components onto your own RHEL VM? If not, and you are using the default VMTurbo supplied pre-packaged VM, you should choose the "OpenSuse" package from above. They also should be below the limit and should update.

Check on the Status/Progress of an ONLINE Update brings me to a page that says "Access to this place or content is restricted. If you think this is a mistake, please contact your administrator or the person who directed you here." I am logged in on both pages. Please advise.

what i'm looking for is whether direct upgrade from 5.5.7 to 5.6.4 is supported via offline update.

And, if for example, i upgrade from 5.5.5 to 5.5.7 right now, how long should I wait for the update process to fully complete (my understanding is there are background update processes that take hours even after the GUI comes back up?) before proceeding to the 5.6.7 update?

You can certainly update to 5.6 from 5.5 with an offline update just follow the instructions above. Also depending on the size of the environment the update can take anywhere from 30 mins to 1 hour to fully finish and data to reappear in the user interface. After your wait when you log back in click the gear wheel in the upper right and then about to check to make sure the instance is running on the latest version (or the version you updated to

You will have to go through a two-step process: Migrate 5.8 openSuSE to 5.8 CentOS; then update 5.8 CentOS to 6.0 CentOS. Turbonomic Support has plenty of experience doing this; please contact them for assistance.

Hi William, you will need to migrate your data from your current SUSE to a new 5.x version running on CentOS and then perform the 6.0 upgrade as per the above. I would recommend contacting Turbonomic support for guidance but the process will look like the below (very high level):

Upgrade your current SUSE based Turbo to the latest available / supported version (v5.9.1)

Deploy a new Turbo instance running on 5.8 (or latest available OVA at the time) and ensure it is upgraded to the same version as the current running Turbonomic server (e.g. SUSE based)

Perform full backup on the original SUSE instance and restore the backup on the new instance (Support can provide details)

Once you confirmed the new instance is working fine, perform the upgrade to 6.0

Decommission the original Turbonomic server

Again, the above is high-level and for details steps (such as when to take snapshots, applying the licenses, etc) can be provided by Turbonomic Support.

Just tried to install the latest update, getting the error that the file is too large and that the maximum size is 1 GB . . . which I fixed by updating the update.js file to contain a higher value. However, once I completed the upload, nothing appeared to happen. All I get is this blank box:

In release notes for 6.1.6 - Can you be specific about the following Know Issue, specifically is there a version of vCenter this occurs on, also how do we ensure no data loss for the patch upgrade:

• For vCenter environments, upgrades to the latest version of Turbonomic include changes to how the system tracks discovered entities. As a result, you might see a loss of historical data, and you will need to reconfigure placement policies on clusters that are discovered by the impacted vCenter targets