Home > Microsoft Exchange Tips > Exchange Server Administration Tips > Move that ever-growing Exchange 2000 database
Exchange Tips:
EMAIL THIS
 TIPS & NEWSLETTERS TOPICS 

EXCHANGE SERVER ADMINISTRATION TIPS

Move that ever-growing Exchange 2000 database


Robert Shahon
06.01.2003
Rating: --- (out of 5)


Digg This!    StumbleUpon Toolbar StumbleUpon    Bookmark with Delicious Del.icio.us   


This tip was submitted to the SearchWin2000.com tip exchange by member Robert Shahon. Please let other users know how useful it is by rating it below.


You may have found yourself in a situation that many Exchange admins have come up against: low disk space on your Exchange drive. Sometimes the planning does not necessarily fit the result of a few years of usage -- especially when the upper management insists on using Exchange as its filing cabinet. When this happens, you need to add a larger disk to your Exchange server to accomodate the database size.

Since Exchange 2000 Server does not come with the the Performance Optimizer program (Perfwiz.exe) that is included with previous versions of Exchange, this tip explains how to move log files or database files in Exchange 2000 from one disk to another.

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

To move log files:

  1. Start Exchange System Manager.
  2. Locate the Administrative Group.
  3. Open the properties on the Storage Group for which you want to change log file paths.
  4. On the General tab, change the Transaction Log Location by clicking Browse, and then specifying a new drive or directory location for the log files.

To move databases:

  1. Start Exchange System Manager.
  2. Locate the Administrative Group.
  3. Under the Storage Group, click the Mailbox or Public Folder Store that you want to change.
  4. Open the properties on that store, and click the Database tab.
  5. Choose a new location for the databases by clicking Browse and specifying a new drive or directory location for the database files.

    With the databases, you can choose to move the Exchange database (.edb file), Exchange streaming database (.stm file) or both. If the databases are still mounted, you will 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?

  6. Click Yes to dismount the database automatically and move the location.
  7. When you finish moving the databases, remount the databases manually.
  8. You can move the log files and database files to any directory that you want to create. When you move logs and database files, you may want to create the ExchsrvrMdbdata file structure for consistency reasons, but you are not required to do so.
  9. You must grant the following default permissions to the new Mdbdata directory 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

    You may also need to grant the following permissions to the root drive that contains the new Mdbdata directory: System: Full Control.

During the process of moving log files and database files, your store is temporarily dismounted, which makes it inaccessible to your users until the process is completed. Moving log files or database files invalidates all existing incremental and differential backups, so I recommend that you make a full backup after these changes.

Note: In the compiliation of this tip, I referred to Microsoft Knowledge Base article 270693 and permissions info I received from a Microsoft support person on the Exchange newsgroup. All other information is based on my own experience.

Rate this Tip
To rate tips, you must be a member of SearchExchange.com.
Register now to start rating these tips. Log in if you are already a member.


Submit a Tip




Digg This!    StumbleUpon Toolbar StumbleUpon    Bookmark with Delicious Del.icio.us   


RELATED CONTENT
Exchange Server Administration Tips
Top 5 Exchange mobile tips of 2008
What are the pros and cons of a hosted Exchange Server deployment?
Top 10 Microsoft Exchange Server tips of 2008
Database changes that enhance Exchange Server 2007 fault tolerance
How continuous replication methods affect Exchange 2007 log shipping
Analyzing Exchange ActiveSync data from .CSV report files
How to run Exchange Management Shell cmdlets in Exchange Server 2007
Eliminate .PST file use for secure email retention in Exchange 2007
Exchange Server 2007 log shipping and continuous replication
Benefits of backing up Exchange Server with Microsoft's DPM 2007

Microsoft Exchange Server Database Management
Database changes that enhance Exchange Server 2007 fault tolerance
Microsoft Exchange Server 2003 database recovery methods
Creating disk space for an Exchange Server 2003 priv1.edb database
Why boot an Exchange server from a storage area network (SAN)?
DetachPipe: Outlook add-in tool saves and restores email attachments
How to calculate white space in an Exchange streaming (.STM) file
An affordable Exchange Server database backup software option for SMBs
Solve server problems with the Exchange Troubleshooting Assistant tool
iSCSI SAN storage for Microsoft Exchange -- 5 tips in 5 minutes
Is an Exchange 2003 offline defrag needed prior to moving databases?

Microsoft Exchange 2000 Server
How to move Exchange 2000 to new server hardware
Error 1053: Exchange System Attendant service could not start
Solve server problems with the Exchange Troubleshooting Assistant tool
Move mailboxes to Exchange 2007 after Windows upgrade
Third-party tools that modify NDRs for oversized email
IP address changes for an Exchange 2000 recovery server
Exchange Server 2003 tips and tricks -- 7 tips in 7 minutes
How to enable Exchange Server public folder logging
Deciphering an 0xc103798a Exchange Server setup error code
Exchange Server error message: 'A non-delivery report with a status code of 5.4.0 was generated for recipient'
Microsoft Exchange 2000 Server Research

RELATED GLOSSARY TERMS
Terms from Whatis.com − the technology online dictionary
E2K  (SearchExchange.com)

RELATED RESOURCES
2020software.com, trial software downloads for accounting software, ERP software, CRM software and business software systems
Search Bitpipe.com for the latest white papers and business webcasts
Whatis.com, the online computer dictionary

DISCLAIMER: Our Tips Exchange is a forum for you to share technical advice and expertise with your peers and to learn from other enterprise IT professionals. TechTarget provides the infrastructure to facilitate this sharing of information. However, we cannot guarantee the accuracy or validity of the material submitted. You agree that your use of the Ask The Expert services and your reliance on any questions, answers, information or other materials received through this Web site is at your own risk.



Email Server Solutions: Exchange 2007, Exchange 2003, Exchange 2000, SharePoint
HomeNewsTopicsITKnowledge ExchangeTipsAsk the ExpertsMultimediaWhite PapersIT Downloads
About Us  |  Contact Us  |  For Advertisers  |  For Business Partners  |  Site Index  |  RSS
SEARCH 
TechTarget provides enterprise IT professionals with the information they need to perform their jobs - from developing strategy, to making cost-effective IT purchase decisions and managing their organizations' IT projects - with its network of technology-specific Web sites, events and magazines.

TechTarget Corporate Web Site  |  Media Kits  |  Site Map




All Rights Reserved, Copyright 2004 - 2009, TechTarget | Read our Privacy Policy
  TechTarget - The IT Media ROI Experts