Exchange Mail Store Moves

Is there a higher risk in moving an exchange store database and log files to a new location vs moving the mailboxes 1 by 1?

We've been moving mailboxes 1sy 2sy moves with low risk.  We've never moved an entire mail store database before along with the trans logs.  Is this common practices?  Recommended?  Supported?  Any best practice tips?
It will be moved from 1 of our Exchange servers over to our new SAN.
ncvadfAsked:
Who is Participating?

Improve company productivity with a Business Account.Sign Up

x
 
Exchange_GeekConnect With a Mentor Commented:
Well, it is not supported - also high risk involved in it - since what you are thinking of in exchange terms is called fork-lifting exchange database - now you need to get facts clear that your users have certain attributes which are associated with your source server - if you tend to move the database (keep in mind the store will mount as long as both servers are part of same Exchange organization and administration group) across servers - you will find all the mailboxes in disconnected state - since the active directory (in other words users - mailboxes) does not know that database has been moved to the new server since all you have moved are database files (EDB + STM) and few log files (which wont be required since you would be dismounting the stores first hence, stores would be in good shape).

hope this clears your doubt.

0
 
Exchange_GeekCommented:
Are you stating that you want to move mailboxes between servers being safe versus moving an entire store (database and log files) ??

0
 
ncvadfAuthor Commented:
No......we've been moving mailboxes.......taking a long time.....I am asking if a database move is the best way to go.....Is it a higher risk, supported, etc?
0
Creating Active Directory Users from a Text File

If your organization has a need to mass-create AD user accounts, watch this video to see how its done without the need for scripting or other unnecessary complexities.

 
ncvadfAuthor Commented:
Sorry, but can you re-explain that.......perhaps more than 1 long run-on awkward sentence.....I got most of it.
0
 
Exchange_GeekCommented:
Ping me at v-9tshah@passport.com to clear your Q and Ans
0
 
Exchange_GeekCommented:
Sorry i just went on typing ;)

In short Microsoft does not support fork-lifting (the method which you are thinking of)

Also, the reason why it is never suggested to perform this method is. Active directory users information are never updated since you are now moving the database to another store. This means that the attributes which point to old server will not get updated since you are not using the traditional Exchange method of move mailbox.

Isn't this a short and sweet answer :)
0
 
ncvadfAuthor Commented:
Thanks.......this is the info I was looking for.....We will continue witht the 1sy 2sy mailbox moves over to the SAN.  We have 2 exchange servers.........only 1 of them is now pointed (iSCSI target) over to the SAN.  Therefore, the mail stores moving from that server over to the SAN are not really moving to a different server.......just a new local storage point.

However........all-in-all, we will continue with the mailbox moves, not the mail stores.

Thanks for the info !!
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.