I saw a post a couple of weeks ago that an upgrade package was on the way. Is there an expected availability date yet? We are currently using 2.2, is it Ok if we wait until the upgrade is available rather than install an new appliance?
We are still working on some documentation from the changes that were made in this patch update. The update should be out within the next few days and a post will be made to the communities forum once released.
Here are temporary links to download the Usage Meter version 2.3.2 files. Note that these will be available on the ftpsite for roughly 48 hours or when capacity needs to be freed up on the ftpsite.
Release notes for version 2.3.2 (including upgrade steps)
In place upgrade file from version 2.2 to 2.3.2
Full OVA for new appliance installation
Thread will be updated again when the normal download site is functioning again.
Hello, I've just tried in-place upgrade of 2.2.0 to 2.3.2 according to 2.3.2 release notes, but no collected samples were migrated after pressing "Migrate Version 2.2 Data" button in webapp. The migration successfully populated Manage Page settings, but all reports now contain only samples that were newly collected after the upgrade. Is migration of historic data from 2.2.0 to 2.3.2 unsupported or do I miss something? At the end of migration, appliance log contains "db.V22To23Migrator$: Migrating samples" from which I guess that the migration of historic samples should work?
* Migrating Manage Page information
* Collecting license, host, and VM information from vCenter server(s)
* Starting: Collecting but not saving samples
* Ending: Collecting but not saving samples
* Migrating samples
Martin, sorry about the trouble. Are you interested in getting into this with us, via WebEx? We would like to know what happened. Sometime in the next couple of hours, perhaps?
I am also experiencing the same issue as Martin. The company and licensing information migrate successfully, but the samples do not migrate. I see the same status in the Support page. I am migrating from v2.2 to 2.3.2 using the in-place upgrade script.
We've had the same issue. The upgrade goes to the "Migrating Samples" and never actually seems import them.
Looking through the postegres database logs, I see:
Postgres still lists the "um22" database as existing and taking 2GB of disk.
I'm hoping that I'll be able to resume the import later?
I believe that the current expected function is that the data migration should be done immediately, not delayed.
If you wait and migrate later, it will not merge the current 2.3.2 data with old 2.2.0 data. It will probably dump the current DB and transfer data ... so you will have a gap in data from when the upgrade was done until the data migration was completed.
This is why it's critical to migrate immediately, or revert in case of failure.
Jon, new info: We have decided to change the migrator to deal with the situation where collections are made between the time the VM is patched and the migration is successfully run. We will preserve those collections made during that time. Should be ready in a day or two.