[ExchangeList] Re: Exchange 2003 to 2007 Via backup Exec

Hey all…

 

The transfer is going extremely well.

Considering that this is my first win2K8/Exch2K7 install/upgrade.

 

I did miss a couple of things during the install and move.

I wish I would have turned on circular logging.

I believe the move would be going a little faster otherwise but… That’s water under the bridge at this point.

 

Is there a simple way to move the store to another drive on the server. 

I overlooked the install location during setup.

 

Just curious.

 

Thank you in advance.

 

From: exchangelist-bounce@xxxxxxxxxxxxx [mailto:exchangelist-bounce@xxxxxxxxxxxxx] On Behalf Of Michael B. Smith
Sent: Friday, September 05, 2008 10:45 AM
To: exchangelist@xxxxxxxxxxxxx
Subject: [ExchangeList] Re: Exchange 2003 to 2007 Via backup Exec

 

Yeppers.

 

Regards,

 

Michael B. Smith

MCITP:SA,EMA/MCSE/Exchange MVP

http://TheEssentialExchange.com

 

From: exchangelist-bounce@xxxxxxxxxxxxx [mailto:exchangelist-bounce@xxxxxxxxxxxxx] On Behalf Of John Parker
Sent: Friday, September 05, 2008 7:20 AM
To: exchangelist@xxxxxxxxxxxxx
Subject: [ExchangeList] Re: Exchange 2003 to 2007 Via backup Exec

 

I am assuming that after all is said and done, an IP change will not hurt anything since everything is done via FQDN’s. yes?

 

Thank you

 

From: exchangelist-bounce@xxxxxxxxxxxxx [mailto:exchangelist-bounce@xxxxxxxxxxxxx] On Behalf Of Michael B. Smith
Sent: Thursday, September 04, 2008 8:55 PM
To: exchangelist@xxxxxxxxxxxxx
Subject: [ExchangeList] Re: Exchange 2003 to 2007 Via backup Exec

 

If the old server is up, and the new server is up, then Outlook will automatically redirect the old server to the new profile. Magic.

 

Once all users are redirected (or the most significant percentage of same), then you can shut off the old server.

 

Regards,

 

Michael B. Smith

MCITP:SA,EMA/MCSE/Exchange MVP

http://TheEssentialExchange.com

 

From: exchangelist-bounce@xxxxxxxxxxxxx [mailto:exchangelist-bounce@xxxxxxxxxxxxx] On Behalf Of John Parker
Sent: Thursday, September 04, 2008 9:52 PM
To: exchangelist@xxxxxxxxxxxxx
Subject: [ExchangeList] Re: Exchange 2003 to 2007 Via backup Exec

 

Alright…

 

I am convinced.

Iwill admit to being a bit skiddish.  The server has been very interesting as of late and last week, we almost lost it all.  We had some corruption in the store and… well it was a very long 46 hours working on it.  I am an admin.  I work with exchange every day, but I do not install it every day.  So please forgive my naïveté.

 

N00b query…

 

So… once the move is complete…  The use’s outlook 200/2003/2007 will recognize the move?  I was under the impression that I would have to touch all of the workstations and reset the email server within outlook.

 

From: exchangelist-bounce@xxxxxxxxxxxxx [mailto:exchangelist-bounce@xxxxxxxxxxxxx] On Behalf Of Michael B. Smith
Sent: Thursday, September 04, 2008 8:45 PM
To: exchangelist@xxxxxxxxxxxxx
Subject: [ExchangeList] Re: Exchange 2003 to 2007 Via backup Exec

 

<shudder>

 

I’ve done at least 40 2003 -> 2007 upgrades. Several dozens.

 

As Rick says, and as I say – don’t do it that way! You are causing yourself pain.

 

Regards,

 

Michael B. Smith

MCITP:SA,EMA/MCSE/Exchange MVP

http://TheEssentialExchange.com

 

From: exchangelist-bounce@xxxxxxxxxxxxx [mailto:exchangelist-bounce@xxxxxxxxxxxxx] On Behalf Of Rick Boza
Sent: Thursday, September 04, 2008 9:33 PM
To: exchangelist@xxxxxxxxxxxxx
Subject: [ExchangeList] Re: Exchange 2003 to 2007 Via backup Exec

 

I'm sorry, move mailboxes bail?  Wait, you mean fail?  That's not how a move mailbox works.

The move is a copy -> delete function, not a delete ->move.  So in the event a move of a mailbox should fail, it reverts back to the original server, and you can clean it up and try again.  Users are none the wiser.

So you start moving mailboxes.  Outlook automatically detects the move the next time the user starts up, and no need to touch desktops or modify clients.  If a move fails, Outlook still sees it on the old server.

There's no halfway functional server at all - even if some moves fail, both servers are fully functional.

Also, renaming the server to the old server name is more likely to cause problems than solve them - what's the planned process?
backup data
retire server
clear AD of Exchnge, including hacking your way through ADSIEdit
Install new server with old server name
restore data
Hope the identical host name doesn't have any sort of other odd problems, such as GUIDs and AD records...?

And so, assuming the process I just outlined (may have missed a step, but at the high level, I think it's about right) how is this less risky than a move mailbox approach?

Oh yes, and there is no renaming the Exchange server after the server has been restored - once Exchange is installed, that server name is what you named it originally, it isn't renamed.  There is no rename process.

So, just to be clear, if your consultant is recommending this approach, I suggest a new consultant.  Michael has recommended a smooth, pain-free solution, I've done the same (and I've done more than a few migrations, I can't speak for Michael's migration experience but his knowledge is top shelf) and your consultant has (presumably) recommended a path that is unsupported, difficult, and likely to fail. 

Sorry to sound blunt, but the approach you appear to be headed down is the definition of risky.

On Thu, Sep 4, 2008 at 9:04 PM, John Parker <jp@xxxxxxxxxxxxxx> wrote:

My Question is this.  Why is it risky?

 

We intend to rename the server afterwards to the old server name once the mailboxes are on the new box.  Why is this risky since it leaves the old server intact.  Whereas, if the move mailboxes bail, I have a halfway functional server. And am forced to do a restore.  The old server has been somewhat unstable and I do not want to take a chance with losing data.

From: exchangelist-bounce@xxxxxxxxxxxxx [mailto:exchangelist-bounce@xxxxxxxxxxxxx] On Behalf Of Rick Boza
Sent: Thursday, September 04, 2008 7:43 PM
To: exchangelist@xxxxxxxxxxxxx
Subject: [ExchangeList] Re: Exchange 2003 to 2007 Via backup Exec

 

Could not agree more - this sounds like a much more riskly approach as well as potential for significant user impact.  Best method nearly all the time is to move the mailboxes and avoid pain for both the users AND for you.

On Thu, Sep 4, 2008 at 7:42 PM, Michael B. Smith <michael@xxxxxxxxxxxxxxxxxxxxxxxx> wrote:

I would absolutely not do it this way.

 

I would do a move-mailbox from old-server to new-server and then properly remove the old server.

 

CAN you do it the other way? Sure. But you'll have to touch every single user desktop to update the MAPI profile.

 

Regards,

 

Michael B. Smith

MCITP:SA,EMA/MCSE/Exchange MVP

http://TheEssentialExchange.com

 

From: exchangelist-bounce@xxxxxxxxxxxxx [mailto:exchangelist-bounce@xxxxxxxxxxxxx] On Behalf Of John Parker
Sent: Thursday, September 04, 2008 7:39 PM
To: exchangelist@xxxxxxxxxxxxx
Subject: [ExchangeList] Exchange 2003 to 2007 Via backup Exec

 

Hey all...

We currently have a 2003 server standard running exchange 2003 Enterprise.
It is on it's last leg and we are replacing it.

We are getting our new server in tomorrow.
I will be installing Server 2008 64bit and Exchange 2007 Std.

Once all of this is installed I intend to restore the individual exchange 2003 mailboxes to the 2007 machine from backup exec 11d.
Also, to make things go faster, I am also running the backup to disk using a backup to disk folder I created.

my consultant sources say that this will work.
 
So... My intention is to shut down the smtp service and then perform a backup.
Once Backup is complete, then I assume that I install a Backup exec agent on the 2007 box and then restore the individual mail boxes.

I am also assuming that I will need to go to the new server afterwards and reconnect the mail boxes?
Or can I use the "Recreate user accounts and mailboxes" feature within Backup Exec?
 
Am I correct in this ideology?
 
 
Thank you for your help in this.

THE INFORMATION CONTAINED IN THIS EMAIL MESSAGE AND IN ANY ACCOMPANYING ATTACHMENT IS A

CONFIDENTIAL AND PRIVILEGED COMMUNICATION.  IT IS INTENDED ONLY FOR THE USE OF THE INTENDED

RECIPIENT OR RECIPIENTS.  IF YOU ARE NOT THE INTENDED RECIPIENT OR THE EMPLOYEE OR AGENT

RESPONSIBLE TO DELIVER THIS EMAIL TO THE INTENDED RECIPIENT, YOU ARE HEREBY NOTIFIED THAT ANY

DISCLOSURE, COPYING OR DISTRIBUTION OF THE CONTENTS OF THIS TRANSMISSION IS STRICTLY

PROHIBITED.  IF YOU HAVE RECEIVED THIS EMAIL IN ERROR, PLEASE NOTIFY US IMMEDIATELY BY PHONE.

THE INFORMATION CONTAINED IN THIS EMAIL MESSAGE AND IN ANY ACCOMPANYING ATTACHMENT IS A

CONFIDENTIAL AND PRIVILEGED COMMUNICATION.  IT IS INTENDED ONLY FOR THE USE OF THE INTENDED

RECIPIENT OR RECIPIENTS.  IF YOU ARE NOT THE INTENDED RECIPIENT OR THE EMPLOYEE OR AGENT

RESPONSIBLE TO DELIVER THIS EMAIL TO THE INTENDED RECIPIENT, YOU ARE HEREBY NOTIFIED THAT ANY

DISCLOSURE, COPYING OR DISTRIBUTION OF THE CONTENTS OF THIS TRANSMISSION IS STRICTLY

PROHIBITED.  IF YOU HAVE RECEIVED THIS EMAIL IN ERROR, PLEASE NOTIFY US IMMEDIATELY BY PHONE.

Other related posts: