cancel
Showing results for 
Search instead for 
Did you mean: 

EV upgrade from 5.0 to 2007

stlm1
Level 3
I'm new to EV and have just been assigned to research how to get us moved from EV 5.0 (Exch2003, x86 W2K3 SP1 environment) to EV 2007 (on an x64 box / W2K3 SP1, with Exchange 2007). I'm trying to figure out the correct upgrade path and have just started reading through Admin manuals, compatabilty charts, install and upgrade instructions.  So far the only initial conclusion I have found is that I need to follow the path of 5.0 to 6.0, 6.0 to 7.0, and 7.0 to 2007, but could use as much help / advice that could be offered.  Has anyone else out there completed this type of multi-version upgrade and can offer an outline for upgrade?  Thanks!  
1 ACCEPTED SOLUTION

Accepted Solutions

Shawn_Waggoner
Level 4
Partner Accredited Certified

I have just finished an upgrade just like the one you described, except we did not use 64bit HW. We went from EV 5.0 on and older server to 2007 SP3 on new hardware/SAN.

 

The process I used which worked well, was to upgrade sequentially, like you described, to 2007 on the old server. We were running Server 2000 on the old box and 2003 Standard on the new. You will have to upgrade Outlook and maybe one or two other components on the way to make sure they are compatable with the newer version. 

 

Once you get the Old server to EV 2007, I would build the new server, just not config EV. You will need to stop the EV services on the old server and then copy (Robocopy works well) the indexes, shopping and vault store data to the new server. If these are SAN volumes and they can just be reattached, great. The trick is making the data is in the SAME locations as before. So if your Indexes were on a E:\ drive, the index location should E:\

 

One important note on the sequential upgrade, backup your EV databases before each step. Back them up now before you begin, upgrade to 6, test and back them up again. Rinse and repeat. This way if you need to stop and go back, you have a clean DB to go to. I highly stress you test in between upgrades to make everything is working.

 

Once the old server is on EV 2007 and all the data has been copied/migrated to the new server, rename the old server and shut it down. I also like to disable the EV services from starting on the old server before shutting it down. Rename the new server the old server name (the CNAME or Vault alias should still point to the old name and work fine). Now the NEW server has the old name and IP and the vault alias still points to it. (I know simply updating the alias CNAME entry should fix this, but I have seen where 5.0 still embeds the physical hostname in the config in SQL and the recovery fails - I prefer to play it safe and rename the server and keep the CNAME as is.) Make sure all the data is available in the correct locations and run the EV config util.

 

Select create a new site, enter the VSA credentials and then on the next screen enter the SQL server (this needs to be the same SQL server as before). It will recognize the EV server as the old one and automatically start the recovery process and restore all the settings, policies, tasks and services on the new server.

 

At this point you should have everything up and running on the hardware.

 

In a nutshell, you are upgrading the EV first then walking through doing a DR/recovery on the new hardware.

 

I have done this a couple of times now and it works very well.

 

Hope this was helpful!  

View solution in original post

6 REPLIES 6

Shawn_Waggoner
Level 4
Partner Accredited Certified

I have just finished an upgrade just like the one you described, except we did not use 64bit HW. We went from EV 5.0 on and older server to 2007 SP3 on new hardware/SAN.

 

The process I used which worked well, was to upgrade sequentially, like you described, to 2007 on the old server. We were running Server 2000 on the old box and 2003 Standard on the new. You will have to upgrade Outlook and maybe one or two other components on the way to make sure they are compatable with the newer version. 

 

Once you get the Old server to EV 2007, I would build the new server, just not config EV. You will need to stop the EV services on the old server and then copy (Robocopy works well) the indexes, shopping and vault store data to the new server. If these are SAN volumes and they can just be reattached, great. The trick is making the data is in the SAME locations as before. So if your Indexes were on a E:\ drive, the index location should E:\

 

One important note on the sequential upgrade, backup your EV databases before each step. Back them up now before you begin, upgrade to 6, test and back them up again. Rinse and repeat. This way if you need to stop and go back, you have a clean DB to go to. I highly stress you test in between upgrades to make everything is working.

 

Once the old server is on EV 2007 and all the data has been copied/migrated to the new server, rename the old server and shut it down. I also like to disable the EV services from starting on the old server before shutting it down. Rename the new server the old server name (the CNAME or Vault alias should still point to the old name and work fine). Now the NEW server has the old name and IP and the vault alias still points to it. (I know simply updating the alias CNAME entry should fix this, but I have seen where 5.0 still embeds the physical hostname in the config in SQL and the recovery fails - I prefer to play it safe and rename the server and keep the CNAME as is.) Make sure all the data is available in the correct locations and run the EV config util.

 

Select create a new site, enter the VSA credentials and then on the next screen enter the SQL server (this needs to be the same SQL server as before). It will recognize the EV server as the old one and automatically start the recovery process and restore all the settings, policies, tasks and services on the new server.

 

At this point you should have everything up and running on the hardware.

 

In a nutshell, you are upgrading the EV first then walking through doing a DR/recovery on the new hardware.

 

I have done this a couple of times now and it works very well.

 

Hope this was helpful!  

stlm1
Level 3

Thank you Shawn, that is very helpful. 

 

So the indexes remain unchanged through the version upgrades and they don't need to be rebuilt?

Shawn_Waggoner
Level 4
Partner Accredited Certified

That's correct. Any changes or background upgrades are handled on the old server before migrating. When you go to the new server, you are basically 'recovering' EV onto the new hardware. No changes to the indexes are needed.

 

Just want to stress that the locations/paths need to be the same for the indexes and vault stores/partitions.

Jeffrey_Lynch
Level 4
Partner

hmm, one important question, did you have any unstructured archives??

stlm1
Level 3
If there are unstructured archives then those would need to be converted to structured after upgrading to version 6.0?  And if that is true, then once they are converted to structured archives, the rest of the upgrade could continue as described by Shawn?  Is that true?  Thanks. 

TonySterling
Moderator
Moderator
Partner    VIP    Accredited Certified

Yes, that looks good. 

 

Thanks Shawn for sharing your info!