Networker

Re: [Networker] Upcoming MS Exchange upgrade

2009-04-01 21:52:36
Subject: Re: [Networker] Upcoming MS Exchange upgrade
From: Stan Horwitz <stan AT TEMPLE DOT EDU>
To: NETWORKER AT LISTSERV.TEMPLE DOT EDU
Date: Wed, 1 Apr 2009 21:44:43 -0400
> From: "Werth, Dave" <dave.werth AT GARMIN DOT COM>
> Reply-To: EMC NetWorker discussion <NETWORKER AT LISTSERV.TEMPLE DOT EDU>, 
> "Werth,
> Dave" <dave.werth AT GARMIN DOT COM>
> Date: Wed, 1 Apr 2009 16:00:53 -0700
> To: <NETWORKER AT LISTSERV.TEMPLE DOT EDU>
> Subject: [Networker] Upcoming MS Exchange upgrade
> 
> Folks,
> 
> In about a month we will be upgrading our MS Exchange server from 2003
> to 2007.  Being lazy I figured I'd ask if anyone on the list that is
> familiar with it had some tips to help ease the process.
> 
> Our current MS Exchange 2003 server is a standalone system running
> Windows 2K3 Server.  The new system will be running MS Exchange 2008,
> probably on Windows 2K3 but perhaps Windows 2K8.  It will consist of two
> clustered systems for the Information/Data store part of the server and
> two mirrored systems for the front end (if that sounds crazy, enlighten
> me, I'm just repeating as best I can my current understanding of how it
> goes together).
> 
> We are currently still on Networker 7.2.2 but I plan to upgrade to 7.5.?
> in the next couple of weeks (anyone think I should upgrade to a lesser
> version?)?
> 
> Do I need an additional license for Exchange for the front end system or
> is the currently license we have (NetWorker Module for Microsoft
> Exchange Server/11) sufficient or do I need additional licenses for the
> Exchange front end systems.  I assume using a 45 day evaluation license
> will get us through the 3 weeks or so we plan to use to migrate users to
> the new server.  Any problem with that assumption?  When I specify the
> Exchange Server to backup up I specify the cluster name, right?
> 
> Any other tips that would help make the process go smoothly?

You'll need one client connection for each server in that mix, so a total of
4 client connections, plus the Exchange module. If you are going to run your
old and new Exchange servers concurrently and back both of them up via
NetWorker, you'll need a second Exchange module license. If the old server
isn't going to be backed up after you put the new server into production,
you should get by with just an evaluation license, which will buy you 45
days of overlap. You only need an Exchange license to back up the Exchange
data which will always live on exactly one server at a time in your set-up.
The two front end servers are just normal client connections.

You need to be at NetWorker 7.4.4 or greater in order to get around the old
cluster licensing policy. Your plan to run 7.5.1 should be fine. If you stay
with 7.2.2, you will also need to purchase a cluster license, but you should
upgrade, so that shouldn't be an issue.

To sign off this list, send email to listserv AT listserv.temple DOT edu and 
type "signoff networker" in the body of the email. Please write to 
networker-request AT listserv.temple DOT edu if you have any problems with this 
list. You can access the archives at 
http://listserv.temple.edu/archives/networker.html or
via RSS at http://listserv.temple.edu/cgi-bin/wa?RSS&L=NETWORKER

<Prev in Thread] Current Thread [Next in Thread>