Absent Member.
Absent Member.
558 views

Upgrade ESM 4.5 SP2 to 5.2

Jump to solution

Hi,

I'm currently dealing with a project where I have to upgrade an instance of ESM 4.5 SP2, to ESM 5.2. I have noticed the upgrade procedure of 4.5 SP2 to 5.0 SP2, but can it be upgraded directly to 5.2? If it's not possible, maybe a full reinstall would be a good idea. Could you please help me with a reinstall strategy? Besides from moving packages, what else can be done to migrare most of the settings/data from the first appliance?

I must also specify that the current ESM is on a VMware environment, and that I'm no ArcSight expert. Still learning.

Thanks,

Paul

Labels (1)
Tags (3)
0 Likes
1 Solution

Accepted Solutions
Admiral
Admiral

Being given you are working on a virtualized environment, you can take a snapshot of your system and try to upgrade as many times as necessary to make it work properly ( I'm assuming that oracle is also virtualized, if not be careful because your DB will also be upgraded ).

Working with packages is possible but indeed you will have to re-register all your connectors and loose all your data so it's up to you to see if it's suiting your needs or not.

If your production DB is not virtualized and if you don't care about your data, you could  follow this procedure :

* setup a new 4.5 install on a VM for the DB and ESM ( doesn't need to be big, we will not store data in it) .

* export your current content with export_system_tables

* import it in the fresh virtualized instance with import_system_tables. 

* take a snapshot of your new virtualized DB and ESM

* try to conduct the upgrade on this new virtualized environment

* when the upgrade is successfull, use export_system_tables on the 5.2 environment

* You should now have a full export of your content ready for 5.2 version and you can now make a fresh 5.2 install on your production system and import the content.  Thanks to that your content should be strictly identical to the original one and the connectors should still work properly.  Just be aware that all the data you collected before are not going to be available anymore.

HTH

Gaetan

View solution in original post

0 Likes
7 Replies
Fleet Admiral
Fleet Admiral

Hi Paul,

I don't want to disappoint you but depending on how your system is setup and the amount of content in it. Doing a re-install  and migrating content and making sure everything including connectors continue to work, could be a complex job and therefore you should seek specialised skills for it.

If you want to start a new empty system then it would be much easier, the install/admin guide will give you all you need to stand up a new system.

Upgrading from 4.5 has to be done to 5 and then you can upgrade to 5.2. This upgrade is also a little delicate as there are risks due to some major changes made in the schema. I would suggest seeking specialised skills for this too.

Vini

0 Likes
Admiral
Admiral

Being given you are working on a virtualized environment, you can take a snapshot of your system and try to upgrade as many times as necessary to make it work properly ( I'm assuming that oracle is also virtualized, if not be careful because your DB will also be upgraded ).

Working with packages is possible but indeed you will have to re-register all your connectors and loose all your data so it's up to you to see if it's suiting your needs or not.

If your production DB is not virtualized and if you don't care about your data, you could  follow this procedure :

* setup a new 4.5 install on a VM for the DB and ESM ( doesn't need to be big, we will not store data in it) .

* export your current content with export_system_tables

* import it in the fresh virtualized instance with import_system_tables. 

* take a snapshot of your new virtualized DB and ESM

* try to conduct the upgrade on this new virtualized environment

* when the upgrade is successfull, use export_system_tables on the 5.2 environment

* You should now have a full export of your content ready for 5.2 version and you can now make a fresh 5.2 install on your production system and import the content.  Thanks to that your content should be strictly identical to the original one and the connectors should still work properly.  Just be aware that all the data you collected before are not going to be available anymore.

HTH

Gaetan

View solution in original post

0 Likes
Absent Member.
Absent Member.

Hi Vini, hi Gaetan,

Thanks for the helpful answer. The decision was made not to upgrade, but to do a reinstall. The client has done the same procedure before: exported all packages, reinstalled all components, and imported them back.

Now, I do not know if the same procedure applies for switching from version 4.5 to version 5.2, due to the database schema changes. Could you detail the steps or issues that could appear due to this db change?

Also, there is no problem if the connectors will not function for a specific timeframe.

My concern now is regarding the steps necessary to do the reinstallation, and if the packages can be imported. Could you please help me with this?

Thanks,

Paul

P.S. I'm simulation the upgrade in my virtual environment. The data loss was also applicable when doing a reinstall from older versions to version 4.5?

0 Likes
Admiral
Admiral

If all your systems are virtualized, I don't understand why you don't want to at least try to upgrade.   Doing a fresh install will also take quite a lot of time ( new install + export/import packages + connectors registration ) and you will definitely loose all your data which includes all data you have been collecting in your trends.

If you still want to use a fresh install and import packages, be careful anyway because being able to import a package from 4.5 to 5.2 ( did not test it but it will probably work ) doesn't mean the content will be fully compatible between both versions so you could have some damaged content at the end.

PS answer : if you do a fresh install you will always loose your data because you are rebuilding the DB from scratch.  I also implies that you will not be able to access to your archived data ( zipped files ) anymore.

0 Likes
Absent Member.
Absent Member.

Hi GCA,

Thanks for the info. An upgrade would be most suitable, but still the clients wants a reinstall, because this is how he has done all migrations.

The data is not important. The most important for him are the packages.

Now, a friend suggested that, if we are doing a reinstall, maybe we could switch directly to version 6.0, not 5.3. What is your opinion regarding this?

From what I understand, the packages should not be dependent on the backend database. Of course, I will be testing it locally before doing the reinstall. What is your recomandation regarding this reinstall?

Thanks,

Paul

0 Likes
Admiral
Admiral

Assuming your OS is RHEL 6.2 64 bits you can try to use ESM 6.0c.  As far as I have seen it's possible to import packages coming from 5.0 sp2 on that version.  You will also have to re-register your connectors.

Also worth mentioning I experienced issues during ESM6.0c install.  I suggest you do the install locally in command line only with X Window stopped ( init 3 ).

HTH

Gaetan

0 Likes
Absent Member.
Absent Member.

Thanks alot for the helpful tips! I had also problems installing 6.0c locally, so I'll go with console only also. Thanks again,

Paul

0 Likes
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.