Re: information store location
- From: "Dave Nickason [SBS MVP]" <gwdibble@xxxxxxxxxxxxxxxxxxxxxx>
- Date: Thu, 4 May 2006 19:17:23 -0400
Sounds good to me. I don't see any reason to migrate away from SBS unless
you're near the CAL limit, and there are some really obvious financial
reasons not to migrate. Not only that, but at some point you'll have the
new version of SBS and Centro to consider. It seems that for an
SBS-oriented business, one or the other of those would be the logical
migration path from SBS 2003 rather than to WS03 and the separate Server
apps.
http://www.microsoft.com/presspass/features/2005/sep05/09-06Infrastructure.mspx
BTW, don't disregard Al's good advice about the space on C prior to
upgrading.
"lesticia" <lesticia@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:4B6C6171-222F-4BF6-AEB9-250FB895302D@xxxxxxxxxxxxxxxx
thanks so much for the in depth reply. i'm looking into upgrading to
sbs2003
for now because it looks like it will be easier than migrating to 2003
standard. i figure the sbs2003 will give me a year or 2 of breathing room
and give me a chance to complete my mcsa. then i think i will be in a
better
position to migrate to standard server. what do you think of that plan?
"Dave Nickason [SBS MVP]" wrote:
You can do this either before or after the upgrade. I recommend planning
the upgrade for a time when you can avoid all changes for a period of a
week
or more before and after. You'll want to make sure the system you're
upgrading is perfectly stable before beginning the upgrade. After the
upgrade, you may be troubleshooting and repairing minor issues, plus
again
you'll want to be sure the system is stable before changing it in any
way.
Read the KB I posted carefully, and follow the steps exactly and in
order.
You don't move anything yourself - just create the directory you want to
move the data to. In other words, create an MDBDATA directory in any
path
you choose. The target directories need to exist when you click Browse
in
step 4 of the log move and step 5 of the database move. If you follow
the
exact steps in the KB, Exchange will move everything itself.
So back up. Create the MDBDATA where you want the data to end up. Set
the
permissions on the target directory as indicated in the KB article. Move
the logs, then the databases, both per the instructions in the KB. Back
up
again to a different tape. And that's it - you're finished. The log
move
will only take a couple of minutes. The database move will take longer
depending on the size of the databases. You should be in great shape if
you
allow an hour for the whole thing, plus how ever long the backups take.
May 9 is Patch Tuesday. I would consider moving the databases as soon as
possible after your next full backup of Exchange. Then do the upgrade
this
weekend and install the Tuesday patches next weekend. Or, do Exchange as
soon as possible, then the patches, then the upgrade next weekend.
My point is, if something doesn't work out well, you don't want to be in
the
position where you moved the logs and databases, installed the Tuesday
patches, and upgraded to SBS 2003. Now Exchange is acting up and you
have
no idea which of the three changes are the cause. You want to break that
down into three discrete steps, pausing in between to make sure the
system
is stable and error free before moving on to the next step. The order is
less important than the planning, and the monitoring between the steps.
"lesticia" <lesticia@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:5ADAAD71-3B9C-4598-A3B2-AC1E27E70A9A@xxxxxxxxxxxxxxxx
That's great -- looks like I can move it in 2000 too. That leads to a
couple
more questions. What exact folders do I need to move to move the
mailbox
store? Would it be better to move the mailbox store before the upgrade
to
2003? Or does it matter if I do it after the upgrade? Thanks so much!
"Dave Nickason [SBS MVP]" wrote:
Sure, you can move it using this procedure. I recommend keeping the
paths
as close to default as possible. In other words, if the default path
is
C:\Exchsrvr\MDBDATA, consider moving the databases to a path like
E:\Exchsrvr\MDBDATA.
XADM: How to Move Exchange Databases and Logs in Exchange 2000 Server
http://support.microsoft.com/default.aspx?scid=kb;en-us;257184
"lesticia" <lesticia@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:B50FCC60-5E88-4094-B408-F4F3FBBD6B6D@xxxxxxxxxxxxxxxx
I am looking at upgrading SBS 2000 to SBS 2003. Can I move the
information
store to a different drive on the same server? I want to take
advantage
of
being able to raise the store limit to 75 gb but the current drive
it's
on
has very little free space.
.
- References:
- Re: information store location
- From: Dave Nickason [SBS MVP]
- Re: information store location
- From: Dave Nickason [SBS MVP]
- Re: information store location
- From: lesticia
- Re: information store location
- Prev by Date: Re: Companyweb won't work after installing ISA
- Next by Date: Adding Local Admin Accounts Using GPOs
- Previous by thread: Re: information store location
- Next by thread: Re: information store location
- Index(es):
Relevant Pages
|
