moving large database / stm to new storage

We are running out of space on one of your current SAN volumes for one of our
exchange servers. Our plan is to move one of our stores to a new lun attached
to the server. I have read Kb article 821915 which seems pretty
straightforward. The database we are moving is 170GB and is being moved
across disk on the same SAN.

Does ESM perform a move or copy? Wondering what the backout plan is in the
event that something happens during the move causing the process to fail? Any
gotcha's that we should prepare for before or after the procedure?

Thanks,

Chris

just move it from the ESM...

just move it from the ESM...I always make certain I've got a good, full
online backup before undertaking any such change...but it is pretty straight
forward...I've never had a problem with it...ESM just dismounts the store,
moves it, and then remounts the store...

--
Susan Conkey [MVP]

So it actually does perform a move? As in a copy first then delete old copy?

So it actually does perform a move? As in a copy first then delete old copy?
If there are any type of fiber fabric issues during the move, will it remount
the old store after error? I thought I would have to manually mount the store
after it was moved, will ESM do it for me?

Getting a good full backup is kind of difficult because i won't be able to
perform the move until late night when the backup is supposed to kick off.
But as long as i have the previous days backup I think I'll be ok.

Thanks for the quick replies, disk space is getting absorbed quickly!

Chris

Yes it is pretty fail safe.

Yes it is pretty fail safe. It copies it to the destination then re-
homes serveral attributes to point to the new server. Don't worry
about if it fails during the move as nothing gets change ie.
attributes or original database unless it has sucessfully completed
all.

The three conventional DB moves:


1. Use move Database via Exchange ESM
2. Manually move the DB and update Exchange attributes  (http://
support.microsoft.com/kb/822676)
3. Use SAN vendor software to migrate



James Chong (MVP)
MCITP | EMA; MCSE | M+, S+,
Security+, Project+, ITIL
msexchangetips.blogspot.com



y?
unt
ore


ight
e,
of
d
the
il?

I've never had any kind of fiber or network connetivity issue during a move,

I have never had any kind of fiber or network connetivity issue during a move,
but I am sure it would just stop the process and you would  need to start over...

--
Susan Conkey [MVP]

So by doing this I will definetly save myself in running out of storage by

So by doing this I will definetly save myself in running out of storage by
moving a whole database to a new lun correct?

Inline below.

Inline below.
--
Ed Crowley
MVP - Exchange


Yes.


Yes


Yes, if the move doesn't complete.  The move will fail.


If the store is mounted it will be mounted after the move.  If it isn't it
won't.


I suggest you take a special backup to a disk file or something first.

As everyone said, it is a strait forward process, and of course, you must

As everyone said, it is a strait forward process, and of course, you must
perform an online, full backup before you begin.

If you are really not comfortable about moving the database at once, you
might consider creating a new database on your new LUN, and then start
moving mailboxes from the old database to the new one. If you decide the
second way, do not move all mailboxes at once, but in a number of  phases,
so you can see how the process is advancing, and you will have ability to
try it with several test mailboxes.

http://support.microsoft.com/kb/821829 (Moving mailboxes in Exchange Server
2003)


Regards,


Vladimir Meloski

That approach is preferable if you suspect store corruption.

That approach is preferable if you suspect store corruption.  Although that
is not indicated in this thread, it's a reasonable way to move the store.
It will take longer and requires more effort, though.
--
Ed Crowley
MVP - Exchange

Thanks all for the support.

Thanks all for the support. Process went smooth as silk the databse and stm
files were moved and remounted automatically. Took all of 1 hour to complete
from start to finish.

Vladimir - I was under the impression even if you move mailboxes out of a
database, you won't reclaim and of the avaible whitespace unless you perform
and offline defrag. So in the scenario of running out of space on storage LUN
1, how would moving mailboxes to a new database on storage LUN 2 help? Just
want to make sure I am understanding database sizing correctly.

Thanks again.

chris

That is correct you will not reclaim the whitespace.

That is correct you will not reclaim the whitespace. However; MS
stance is now preferred to move ALL mailboxes to a new DB rather than
offline defragging.



James Chong (MVP)
MCITP | EMA; MCSE | M+, S+,
Security+, Project+, ITIL
msexchangetips.blogspot.com


On Mar 21, 12:22=A0pm, Chris Meehan
m
te
rm
LUN
t
that
.
ust
ou

he
hases,
to
e of
ed
n
ail?

You would move all mailboxes then just delete the EDB and STM files.

You would move all mailboxes then just delete the EDB and STM files.
Remounting the store will create new empty small ones, which would move
quickly.
--
Ed Crowley
MVP - Exchange