[2 days left] What’s wrong with your cloud strategy? Learn why multicloud solutions matter with Nimble Storage.Register Now

x
?
Solved

Exchange 2007 to Exchange 2010 juggling act.

Posted on 2010-08-16
1
Medium Priority
?
288 Views
Last Modified: 2012-05-10
We are very excited about the new option to archive SMS on Exchange 2010, and would like to upgrade our current Exchange 2007 server.

Where we are kinda breaking the norm. is that we want to still use the same server as it's one of beefiest spec'ed systems we own.  We do have other hardware available, but nothing as powerful or with as much RAM as our current Exchange system.  I've also been told we don't have a budget for spec'ing out all new hardware at this time.

What my thoughts are....bring one of our extra systems up as a new exchange server, migrate all the primary roles to this server, and then kill off our big server.  Format, reinstall OS, and then install Exchange, again, migrate all the rolls back to our main server, and then kill off the "extra hardware" system.

I know this would have to be done over the course of a few days to a week or so to let everything sync up, and also to check for errors that might be cropping up in the event logs between each step...

My question for you guys is....is this a doable "Upgrade path" for keeping the same server running as our Exchange server in the end...

and....should our "extra hardware" system first match, with Exchange 2007, and then let our beefy system be the first Exchange 2010 system...or should the "Extra hardware" just start the Exchange 2010 upgrade?

thanks....Please ask any clarity questions you might need to ask...as I know this upgrade is a bit "out side of the box"
0
Comment
Question by:Evil_RSA
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
1 Comment
 
LVL 4

Accepted Solution

by:
a1rh0pper earned 2000 total points
ID: 33451437
We went through this recently.....may be a bit of overkill....but the path we took was as follows....

Load up a machine with ESXi free from VMWare.....use VMConvert to convert the physical to a virtual running on ESXi. This gave us an exact duplicate of the Exchange server with all data intact.

Then blow out the "big box" and install the new OS and Exchange 2010 and migrate that way.

As an alternate to VMConvert, you can also use tools like Acronis or ShadowProtect to back up the box....and then import the backup image into ESXi.
0

Featured Post

Free Tool: Subnet Calculator

The subnet calculator helps you design networks by taking an IP address and network mask and returning information such as network, broadcast address, and host range.

One of a set of tools we're offering as a way of saying thank you for being a part of the community.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

This article will help to fix the below error for MS Exchange server 2010 I. Out Of office not working II. Certificate error "name on the security certificate is invalid or does not match the name of the site" III. Make Internal URLs and External…
Know the reasons and solutions to move/import EDB to New Exchange Server. Also, find out how to recover an Exchange .edb file and to restore the file back.
In this Micro Video tutorial you will learn the basics about Database Availability Groups and How to configure one using a live Exchange Server Environment. The video tutorial explains the basics of the Exchange server Database Availability grou…
This video discusses moving either the default database or any database to a new volume.
Suggested Courses

656 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question