Solved

Best way to move exchange root installation

Posted on 2008-10-29
5
338 Views
Last Modified: 2013-11-14
We are in the process of moving our exchange server to a new storage solution.

Our current setup involves an ms cluster with the logs and exchange root install each having a lun dedicated to them. We are moving off of the current netapp box to an emc ns20. We will be keeping the iscsi and we have already moved the quorum, logs, and a single unused storage group  to the new unit with little issue. We are struggling however with how to move the root installation.

Is there an easy way to move the root installation folder to a new storage unit within exchange itself? Or is it advisable to robocopy the contents of the drive over while the services are stopped and then rotate drive letters so the new storage unit has the same drive letters?

Any insight would be helpful, thanks!
0
Comment
Question by:HunTelWebProgrammer
  • 3
  • 2
5 Comments
 
LVL 63

Expert Comment

by:SysExpert
Comment Utility
WHy ot simply move the foldes via the Exchange maanger per storage group.

There is an MS article that tells how to move all LOgs, storage groups and puublic/ private filders via the GUI, and it is quite simple


I hope this helps !
0
 
LVL 63

Expert Comment

by:SysExpert
Comment Utility
0
 
LVL 1

Author Comment

by:HunTelWebProgrammer
Comment Utility
That KB article does not exist anymore.  Do you have another one?
0
 
LVL 63

Accepted Solution

by:
SysExpert earned 500 total points
Comment Utility
I just checked it and it still exists.

How to move Exchange databases and logs in Exchange Server 2003
View products that this article applies to.
Article ID      :      821915
Last Review      :      October 25, 2007
Revision      :      2.2
For a Microsoft Exchange 2000 version of this article, see 257184 (http://support.microsoft.com/kb/257184/EN-US/).
On This Page
SUMMARY
MORE INFORMATION
To move log files
To move databases
SUMMARY
Exchange Server 2003 does not include the Performance Optimizer program (Perfwiz.exe) that is included with previous versions of Exchange Server. This article describes how to move log files or database files in Exchange Server 2003.

Back to the top
MORE INFORMATION
If you want to move log files or database files to another drive, use the following procedures.

Back to the top
To move log files
1.      Start Exchange System Manager.
2.      Click Administrative Groups.

Note If Administrative Groups does not appear, it may not be turned on. To turn on Administrative Groups, right-click Exchange Organization in Exchange System Manager, and then click Properties. Click to select the Display Administrative Groups check box.
3.      Locate the storage group where you want to change log file paths, right-click the storage group, and then click Properties.
4.      Click the General tab, click the Browse button next to the Transaction log location box, and then specify the new drive or folder location for the log files.

Back to the top
To move databases
1.      Start Exchange System Manager.
2.      Open the administrative group that contains the database that you want to change.
3.      Under Storage Group, right-click the mailbox store or the public folder store that you want to change, and then click Properties.
4.      Click the Database tab.
5.      Next to the database that you want to change, click Browse, and then specify a new drive or folder location for the files.

Notes
"      With the databases, you can decide to move the Exchange Database (.edb file), the Exchange Streaming Database (.stm file), or both.
"      If the databases are still mounted, you receive the following message:
You are about to perform the following operation(s):
- change Exchange database location
To perform the requested operation(s), the store must be temporarily dismounted which will make it inaccessible to any user.

Do you want to continue?
Click Yes to dismount the database automatically and move the location.
6.      When you finish moving the databases, remount the databases manually.
You can move the log files and database files to any folder that you want to create. When you move logs and database files, you may want to create the Exchsrvr\Mdbdata file structure for consistency reasons, but you are not obligated to do so.

You must grant the following default permissions to the new Mdbdata folder that contains the log files and database files:
"      Administrators: Full Control
"      Authenticated Users: Read and Execute, List Folder Contents, Read
"      Creator Owner: None
"      Server Operators: Modify, Read and Execute, List Folder Contents, Read, Write
"      System: Full Control
Note Only assign permissions to the Server Operators group if the Exchange server is a domain controller. Otherwise, assign permissions to the Power Users group. Only domain controllers should have permissions to the built-in Server Operators group. Stand-alone and member servers should have permissions to the built-in Power Users group.

You may also have to grant the following permissions to the root drive that contains the new Mdbdata folder:
"      System: Full Control
During the process of moving log files and database files, your store is temporarily dismounted. Because the store is temporarily dismounted, it is inaccessible to your users until the process is completed. Moving log files or database files invalidates all existing incremental and differential backups; therefore, make a full backup after these changes.

Do not delete or rename the Old MDBdata Folder path after you move the Exchange database. If you want to delete the old MDBdata folder, make sure that the following working directory parameter in the registry points to the new location:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\MSExchangeIS\ParametersSystem
Value name: Working Directory
Value type: REG_SZ
Value data: C:\Program Files\Exchsrvr\Mdbdata
For more information, click the following article number to view the article in the Microsoft Knowledge Base:
298415 (http://support.microsoft.com/kb/298415/) Messages that have attachments are not delivered as expected, and Event ID 12003 and 327 messages are logged in Exchange 2000 Server and in Exchange Server 2003

Back to the top
APPLIES TO
"      Microsoft Exchange Server 2003 Enterprise Edition
"      Microsoft Exchange Server 2003 Standard Edition

Back to the top
Keywords:
      kbinfo KB821915
0
 
LVL 1

Author Closing Comment

by:HunTelWebProgrammer
Comment Utility
I asked a silly question, your answer was 100% correct. Thanks!
0

Featured Post

Find Ransomware Secrets With All-Source Analysis

Ransomware has become a major concern for organizations; its prevalence has grown due to past successes achieved by threat actors. While each ransomware variant is different, we’ve seen some common tactics and trends used among the authors of the malware.

Join & Write a Comment

We are happy to announce a brand new addition to our line of acclaimed email signature management products – CodeTwo Email Signatures for Office 365.
Not sure what the best email signature size is? Are you worried about email signature image size? Follow this best practice guide.
In this video we show how to create a Shared Mailbox in Exchange 2013. We show this process by using the Exchange Admin Center. Log into Exchange Admin Center.: First we need to log into the Exchange Admin Center. Navigate to the Recipients >> Sha…
In this video we show how to create a Resource Mailbox in Exchange 2013. We show this process by using the Exchange Admin Center. Log into Exchange Admin Center.: Navigate to the Recipients >> Resources tab.: "Recipients" is our default selection …

744 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question

Need Help in Real-Time?

Connect with top rated Experts

18 Experts available now in Live!

Get 1:1 Help Now