Pau Lo
asked on
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...
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
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.
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.
ASKER
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?
Yes absolutely,
The log's are the Exchange Database Transaction Logs.
Run this script in the management shell to output a CSV.
The Paths provided will be the same on all server members of a Database Group.
Regards
Guy
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 -NoTypeInformationThe Paths provided will be the same on all server members of a Database Group.
Regards
Guy
ASKER
Thanks Guy
So you would recommend a seperate volume for both the database and its log file?
So you would recommend a seperate volume for both the database and its log file?
ASKER
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.
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
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
ASKER
Hi, can you elaborate why?