Video Screencast Help
Archiving and eDiscovery Community Blog

A sheet to help perform an upgrade from EV7.5 to 8.0SP2

Created: 26 Aug 2009 • Updated: 29 May 2014 • 3 comments
GertjanA's picture
+3 3 Votes
Login to vote

Hello everyone,

As you are aware, upgrading a larger environment of EV-servers can be a little confusing.
I've done upgrades from 6 to 7, from 7 to 7.5 and now from 7.5 to 8.0

My environment is pretty large.
9 Journal Archiving servers
15 Mailbox Archving servers
4 Discovery Accelerator servers.

The attached sheet will only show updating EV, not DA.

The sheet consists of 2 pages.
Page 1 is the Pre-Upgrade steps.
Page 2 is the actual upgrade steps.

In the sheet, you will see a red line with the word Sync at the end at several steps.
This indicates that if you perform an upgrade with multiple people (each one doing a server (or 8 ;-)) that is the point where everyone has to wait for the others to reach that point before continuing.

I made the sheet having 3 servers.
1 EV-server being the first installed server, called Directory Server.
2 EV-servers, one being a Journal Archiving server, one being a Mailbox Archiving server. There is no real difference between those, but it is to indicate a multiple-server environment.

I compiled the sheet using experience, the update/upgrade documents, and 'lessons learned'.

Do comment if you feel steps are missing or in the wrong order!



Comments 3 CommentsJump to latest comment

Silvershare's picture

Hi GertjanA

Thank you very much for this file, looks amazing...

Login to vote
PJuster's picture


I would strongly recommend taking SQL backups and EV server system state backups around step 35, when all vault store databases have successfully upgraded.  If you had a server fail before taking a backup you would have to go back to step 1 after recovering the system.

I would also recommend putting  the whole environment in read only at the start, so when you bring everything back online your still in read only mode, crucial for another backup after the upgrade.  But his allows for a certain level of safety and  testing without adding/archiving data to an evironment that could still be rolled back if the worst happened.  I have heard of customers upgrading one vault store partition fine but then have an issue with another and if you have archived data into one and then have to roll back this is alot of extra work.

If you feel this is a solution please mark it as such. TIA Paul

Login to vote
GertjanA's picture

Hi Paul,

The script has 2 tabs. The first is called Prep-1.
In there, it specifically states to make backups, and to put the tasks in read-only mode (step 1).
I made this a seperate step, as this is something we do end of the day before actually performing the upgrade.

I added step 35b (make backup SQL, Data, Indexes etc)

Thank you, Gertjan, MCSE, MCITP,MCTS, SCS, STS

Login to vote