Go Premium for a chance to win a PS4. Enter to Win

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 59
  • Last Modified:

C drive mailbox DB

Are there any risks in storing a mailbox database on the system drive. is there any official guidance and best practices from Microsoft about risks associated in such a design. I know from a SQL Server point of view its seen as bad practice to put databases on a local system drive, just wondered what if any risks existed in doing the same in exchange...
0
pma111
Asked:
pma111
  • 4
  • 4
2 Solutions
 
AmitIT ArchitectCommented:
It is good to keep your DB on separate drive. Why? As DB's size updates frequently. Imagine your DB eat up all your disk space on C:drive, which will bring your server down. Keeping DB on different drives will not impact OS functioning. Remember expanding C drive is not recommended or I will say, should not be done as chance of OS corruption is very high. I hope that answers your query.
0
 
Guy LidbetterCommented:
Hi pma111

From a performance point of view it depends if the system is physical or virtual. If physical you will generally have quite a bit of IOPS hitting the same disk your system is on and the contention would severely hit performance. If virtual, the system disk is most likely on a datastore of many disks working together so it wont really make any difference at all whether separated or on the same logical disk.

From a best practice point of view, I wouldn't do it.  I imagine you would then have the logs, pagefile, databases etc all in the same place which is an accident waiting to happen. If  the drive fills you will take the server down.

In all honesty, a system drive should be just that... a system drive. In many places I have worked they even separate the application binaries, page files, data drives, log drives etc... so only the windows files are located there.

The only possible reason I could see you wanting to do this then is that the drives are local and you have one large partition?

Regards

Guy
0
 
pma111Author Commented:
>the logs, pagefile, databases etc all in the same place which is an accident waiting to happen

Hi, can you elaborate why?
0
Simplify Active Directory Administration

Administration of Active Directory does not have to be hard.  Too often what should be a simple task is made more difficult than it needs to be.The solution?  Hyena from SystemTools Software.  With ease-of-use as well as powerful importing and bulk updating capabilities.

 
Guy LidbetterCommented:
Yes, as mentioned if the drive fills the server will go down.

The log directory will always grow, databases will grow, if you install additional software, or update windows temporary files remain etc... Miss a full backup and the log directory will continue to grow.

If you had a 2TB drive that always had 1TB free, then no problem, there is nothing stopping you. However, as I said, from a best practice point of view its not a great solution.
0
 
pma111Author Commented:
ok thanks, from a log file point of view, which exchange log are you referring to, and is there an eay way to determine where that is located?
0
 
Guy LidbetterCommented:
Yes absolutely,

The log's are the Exchange Database Transaction Logs.

Run this script in the management shell to output a CSV.

Get-MailboxDatabase | select Name, EDBFilePath, LogFolderPath | export-csv c:\temp\paths.csv -NoTypeInformation

Open in new window


The Paths provided will be the same on all server members of a Database Group.

Regards

Guy
0
 
pma111Author Commented:
Thanks Guy

So you would recommend a seperate volume for both the database and its log file?
0
 
pma111Author Commented:
Totally respect your input, but I am struggling to find anything official from Microsft on locating databases and logfiles on the system drive, have you ever come across any official best practice guidance from them on this issue? Cant seem to find anything... Would be a useful reference to have.
0
 
Guy LidbetterCommented:
Have a look at Microsoft's Technet on Understanding Storage Configuration found here:
https://technet.microsoft.com/en-us/library/ee832792(v=exchg.141).aspx

Under Best Practice for Storage Configurations is states on the "OS, System or Pagefile" table under "High availability: supported or best practice:"
"Use a dedicated array group; don't host both system LUN and data LUNs on the same array group."

Essentially saying, System Drives (OS, Exchange Binaries etc) should be kept separate from Data Drives (DB and Logs)

Regards

Guy
0

Featured Post

Windows Server 2016: All you need to know

Learn about Hyper-V features that increase functionality and usability of Microsoft Windows Server 2016. Also, throughout this eBook, you’ll find some basic PowerShell examples that will help you leverage the scripts in your environments!

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