cancel
Showing results for 
Search instead for 
Did you mean: 

Upgrading EV from 7.5 to 9

Gilly-Bhoy
Level 6
Partner

Hi All,

Have to upgrade an EV7.5 installtion to version 9.

I know I have to go to 8.0.4 first but are there any other things to watch out for?

I don't know what SP is currently installed for 7.5 and I cannot see how to determine this?

Any help would be greatly appreciated.

Thanks in advance.

Gilly

1 ACCEPTED SOLUTION

Accepted Solutions

JesusWept3
Level 6
Partner Accredited Certified

If you're upgrading EV2007 to EV8 to EV9 it doesn't matter about the service packs, only CA and DA require specific upgrade paths in that regard

For instance with EV you could do

EV2007 SP2 -> EV8 SP3 -> EV9 base
or EV2007 SP3 -> EV8 SP2 -> EV9 SP2
or EV2007 SP5 -> EV8 SP5 -> EV9 SP1

But based on the current releases its best to do
EV2007 -> EV8 SP5 -> EV9 SP2

The first thing I would do if i were you is to read up on the Late Breaking News for EV9 SP2
This will describe any issues that have been found, any hotfixes that have been released and known issues that still exist, look through them and make sure none of the known issues will heavily affect you

http://www.symantec.com/business/support/index?page=content&id=TECH147778

I wrote a fairly high level over view of the upgrade process here for a user who wanted to do EV6 -> EV9
https://www-secure.symantec.com/connect/forums/upgrading-ev6-ev9#comment-5553601

I would definitely suggest if you could running it through a lab environment first so you can understand the new Vault Store Groups and the new OSIS sharing model, because one of those choices you make when upgrading to EV8 can only be changed at the very beginning, once its set theres no going back so be very very very careful.

Also something that could possibly derail your upgrade from EV8 to EV9 is a known issue of painfully slow Vault Store upgrades if you have millions of items in the JournalArchive/JournalUpdate/JournalDelete tables.

Another thing to note is the backup procedures have changed, if you used the "Immediately After Archive" option in EV that doesn't wait for items to be backed up, note that EV now monitors those items to make sure the Archive Bit has been removed from the files.

In other words, in EV2007 you may have archived millions of items and never cared about backups
But now it will just fill the JournalArchive table with each item archived, so if you don't have good backups or you don't use the ignoreArchiveBitTrigger.txt file, then you will get alerts that you have x thousand of items awaiting backup.

I wrote about the changes to this as well, here:
https://www-secure.symantec.com/connect/articles/changes-backup-procedures-enterprise-vault-8

Last but not least: To check your version, the easiest way is to open the Vault Admin Console, right click Enterprise Vault on the very top left of your MMC tree and go to About Enterprise Vault and it will show you there what SP level you're on.

 

https://www.linkedin.com/in/alex-allen-turl-07370146

View solution in original post

8 REPLIES 8

Gonz
Level 5
Employee

To determine what it is the current SP installed, in the Enterprise Vault Server open the registry and navigate to:

HKLM\SOFTWARE\KVS\ENTERPRISE VAULT\INSTALL

Check the value of version as per technote:

http://www.symantec.com/business/support/index?page=content&id=TECH39258

Apart from that: read the installation notes of each service pack. It is important and will give you all the tips required for a smooth installation / upgrade process.

JesusWept3
Level 6
Partner Accredited Certified

If you're upgrading EV2007 to EV8 to EV9 it doesn't matter about the service packs, only CA and DA require specific upgrade paths in that regard

For instance with EV you could do

EV2007 SP2 -> EV8 SP3 -> EV9 base
or EV2007 SP3 -> EV8 SP2 -> EV9 SP2
or EV2007 SP5 -> EV8 SP5 -> EV9 SP1

But based on the current releases its best to do
EV2007 -> EV8 SP5 -> EV9 SP2

The first thing I would do if i were you is to read up on the Late Breaking News for EV9 SP2
This will describe any issues that have been found, any hotfixes that have been released and known issues that still exist, look through them and make sure none of the known issues will heavily affect you

http://www.symantec.com/business/support/index?page=content&id=TECH147778

I wrote a fairly high level over view of the upgrade process here for a user who wanted to do EV6 -> EV9
https://www-secure.symantec.com/connect/forums/upgrading-ev6-ev9#comment-5553601

I would definitely suggest if you could running it through a lab environment first so you can understand the new Vault Store Groups and the new OSIS sharing model, because one of those choices you make when upgrading to EV8 can only be changed at the very beginning, once its set theres no going back so be very very very careful.

Also something that could possibly derail your upgrade from EV8 to EV9 is a known issue of painfully slow Vault Store upgrades if you have millions of items in the JournalArchive/JournalUpdate/JournalDelete tables.

Another thing to note is the backup procedures have changed, if you used the "Immediately After Archive" option in EV that doesn't wait for items to be backed up, note that EV now monitors those items to make sure the Archive Bit has been removed from the files.

In other words, in EV2007 you may have archived millions of items and never cared about backups
But now it will just fill the JournalArchive table with each item archived, so if you don't have good backups or you don't use the ignoreArchiveBitTrigger.txt file, then you will get alerts that you have x thousand of items awaiting backup.

I wrote about the changes to this as well, here:
https://www-secure.symantec.com/connect/articles/changes-backup-procedures-enterprise-vault-8

Last but not least: To check your version, the easiest way is to open the Vault Admin Console, right click Enterprise Vault on the very top left of your MMC tree and go to About Enterprise Vault and it will show you there what SP level you're on.

 

https://www.linkedin.com/in/alex-allen-turl-07370146

jim_leggett
Level 6
Employee Accredited Certified

Is available in case your interested.

Gilly-Bhoy
Level 6
Partner

Thanks for all the info!

I might be ok in the sense that the client is only running FSA.

Does that help?

I am planning to perform the upgrade in one day. Is this unwise? I read somewhere that I would have to wait for "processing" to complete after the upgrade to V8 before I went to V9? Is this correct?

 

Thanks again,

Gilly

GertjanA
Moderator
Moderator
Partner    VIP    Accredited Certified

Hello Gilly,

What I would do is wait a week before upgrading 8 to 9. But, if you want to do it in 1 go, what I would do then is to set the tasks in report mode. (doubleclick a task, check the 'report mode' checkbox,restart task) That gives EV the time to empty the MSMQ's, and will not add new items.

When the queues are empty, you can upgrade 7.5 to 8 to 9.

When going to 8, yo need to do some steps, like defining the 'cache location', and create the fingerprint database.

Do that first before going to 9.

Regards. Gertjan

Gilly-Bhoy
Level 6
Partner

Thanks, How long before the upgrade should I look at doing something like that?

Would the day before the upgrade suffice? Thus allowing the tasks to run the night before the upgrade in report mode.

JesusWept3
Level 6
Partner Accredited Certified

to be honest, its called best practice, but honestly i find it a bit aimless, just make sure your Storage Archive/Restore queues are cleared and you can upgrade at will

https://www.linkedin.com/in/alex-allen-turl-07370146

GertjanA
Moderator
Moderator
Partner    VIP    Accredited Certified

It might be aimless, but prevents weird events when the upgraded services are starting.

To make the upgrade as smooth as possible, and to prevent events flooding eventlog, which makes it hard to see 'real' (upgrade related) events, I have found this helps go an upgrade more smooth. How long the tasks are set in report mode, is up to you. I would do it the night before (around 17:00), then started upgrades at 09:00 the following day. Make sure the backups are in sync.

Regards. Gertjan