Just wondering if anyone has any problem running their mailbox databases on JBOD with Outlook Cached Mode disabled.  We have many people logging into different workstations throughout the day and use a fast user switching product for this.  However, we don't normally cache Outlook data files.  Mailbox size ranges from MBs to a few GBs and we have a couple hundred users connected per MBX server currently during peak.  We are migrating from Exchange 2007 SAN storage to new servers with local disk. 

I'm not looking for advice on my particular situation, just wondering if anyone has encountered performance issues with Exchange 2013 JBOD and non-cached mode in their environments.

Thanks!

Hi,

From an Exchange perspective, JBOD means having both the database and its associated logs stored on a single disk. To deploy on JBOD, you must deploy a minimum of three highly available database copies.

Utilizing a single disk is a single point of failure, because when the disk fails, the database copy residing on that disk is lost. Having a minimum of three database copies ensures fault tolerance by having two additional copies in the event that one copy (or one disk) fails. However, placement of three highly available database copies, as well as the use of lagged database copies, can affect storage design.

For detailed information about the Exchange 2013 storage configuration options, please refer to:

https://technet.microsoft.com/en-us/library/ee832792%28v=exchg.150%29.aspx?f=255&MSPPError=-2147217396

Regards,

Hi Winnie,

Thanks for taking the time to reply!  We do have planned 3 mailbox servers for three database copies for fault tolerance.  What I am really concerned about is the performance, particularly with non-cached mode in Outlook.  Just wondering if anyone runs their clients in non-cached mode (terminal servers maybe?) and if they have run into any performance issues.

Thanks!