• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 93
  • Last Modified:

How do I change the default drive where new exchange 2016 database are created?

How do I change the default drive where new exchange 2016 database are created? The current default is the C:\ drive and it runs out of space when someone makes a mistake and creates a database on it.
0
masterofall
Asked:
masterofall
1 Solution
 
Valentina PerezExchange ServersCommented:
Hi,

You need to use the Move-DatabasePath command:

https://technet.microsoft.com/es-es/library/bb124742(v=exchg.160).aspx

Regards
Valentina
0
 
yo_beeDirector of Information TechnologyCommented:
When creating a new DB you have the option to point it to any local drive.   I think you are asking for a similar issue.  When creating a new DB you should check your system resources prior to doing this/
0
 
Muhammad AsifSenior Solutions ArchitectCommented:
Hi,

You can move the mailbox database from C drive to any other drive with the help of given below article:
https://practical365.com/exchange-server/moving-an-exchange-server-2016-mailbox-database/
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.

 
yo_beeDirector of Information TechnologyCommented:
I was in the process of editing my comment when Muhammad posted, but is your question for future DB's or because you are constantly running out of space due to log growth?  If that is the case you need to move the DB and use Muhammad's suggestion.
0
 
masterofallAuthor Commented:
This is for future Dbs.  The issue that I am trying to solve is the create process defaults to the C: drive, I need it to default to another drive. (I know to specify the drive at creation and I know move database after creation.)
0
 
yo_beeDirector of Information TechnologyCommented:
You can change it, but there is a chance that you will run into the same situation as your environment grows. So I recommend that prior to creating a new DB that you assess your current available space and plan accordingly. This should not be done blindly.
0
 
MAS (MVE)EE Solution GuideCommented:
Hi masterofall,
Please move your current DB to other drive. Please do it on non-working hours as it requires downtime.
Move-Databasepath -Identity "DatabaseName" –EdbFilepath "D:\Newlocation\DBname.edb" –LogFolderpath "D:\Newlocation"

Open in new window


Please change log folder path.
Open EAC-->Servers-->Servers-->Double server name--> transport  logs--> Change locations here as well.
Capture2.png
I suggest you create a drive with minimum 200GB (Increase it depends on number users and transaction) and move logs to that drive. i.e. you have to use below command if you use a different drive for logs.
Move-Databasepath -Identity "DatabaseName" –EdbFilepath "D:\NewlocationforDB\DBname.edb" –LogFolderpath "E:\NewlocationforLogs"

Open in new window


Hope it helps.
0
 
RoninCommented:
You can use the Scripting agent cmdlet extension agent in Exchange 2013 to insert your own scripting logic into the execution of Exchange cmdlets. Using the Scripting agent, you can add conditions, override values, and set up reporting.
https://technet.microsoft.com/en-us/library/dd335054(v=exchg.150).aspx
0
 
masterofallAuthor Commented:
I did not get an answer how to change the default from C: to something else.  However, I moved the location of the Exchange log files to a drive that is reserved for log files.
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.

Join & Write a Comment

Featured Post

Improve Your Query Performance Tuning

In this FREE six-day email course, you'll learn from Janis Griffin, Database Performance Evangelist. She'll teach 12 steps that you can use to optimize your queries as much as possible and see measurable results in your work. Get started today!

Tackle projects and never again get stuck behind a technical roadblock.
Join Now