Jerry Seinfield
asked on
expertise from Storage, Exchange, VMware experts
Hello Experts,
I decided to open this question, because I've been dealing with a problematic client who is running into multiple performance issues.
Performance issues can be caused by storage, network, VMware issues. Every SME for each area has indicated that everything looks fine, however sometimes DBs are reseeding, the host where Exchange VMs resides on lost access to datastore, and so on.
This is the third client that I have running this type of issues, and all of them have something in common. They were using mountpoints to place DBs, logs
In one of my clients, My recommendation was to use one single db per virtual disk and same per logs. Then present these virtual disks to each Exchange VMs, and the performance improved 90 %
The problematic clients basically does not want to change the use of mount points, because basically they statement was:
All pieces are separate Volumes, they just are mounted in the Same Mount Point
Can someone from the storage team, VMware and exchange teams provide your thoughts?
Any article that state the use of mount points is not recommended?
Best practices to place DBs and logs for Exchange 2013
Please, I need the feedback from different SME, one for Exchange, VMware and Storage
Our infrastructure below
Exchange 2013 CU8. Windows 2012 R2 standard edition. All are vms running on multiple VMware host 5.5
5 MBX servers in a DAG. 3 MBX servers on site 1, 2 MBX site on site 2
2 CAS servers behind a F5
2 Edge servers in the DMZ network
Storage
Net App
XIO
V7000
I decided to open this question, because I've been dealing with a problematic client who is running into multiple performance issues.
Performance issues can be caused by storage, network, VMware issues. Every SME for each area has indicated that everything looks fine, however sometimes DBs are reseeding, the host where Exchange VMs resides on lost access to datastore, and so on.
This is the third client that I have running this type of issues, and all of them have something in common. They were using mountpoints to place DBs, logs
In one of my clients, My recommendation was to use one single db per virtual disk and same per logs. Then present these virtual disks to each Exchange VMs, and the performance improved 90 %
The problematic clients basically does not want to change the use of mount points, because basically they statement was:
All pieces are separate Volumes, they just are mounted in the Same Mount Point
Can someone from the storage team, VMware and exchange teams provide your thoughts?
Any article that state the use of mount points is not recommended?
Best practices to place DBs and logs for Exchange 2013
Please, I need the feedback from different SME, one for Exchange, VMware and Storage
Our infrastructure below
Exchange 2013 CU8. Windows 2012 R2 standard edition. All are vms running on multiple VMware host 5.5
5 MBX servers in a DAG. 3 MBX servers on site 1, 2 MBX site on site 2
2 CAS servers behind a F5
2 Edge servers in the DMZ network
Storage
Net App
XIO
V7000
Last Comment
How is the storage configured ?
ASKER CERTIFIED SOLUTION
THIS SOLUTION IS ONLY AVAILABLE TO MEMBERS.
View this solution by signing up for a free trial.
Members can start a 7-Day free trial and enjoy unlimited access to the platform.
Exchange
Exchange is the server side of a collaborative application product that is part of the Microsoft Server infrastructure. Exchange's major features include email, calendaring, contacts and tasks, support for mobile and web-based access to information, and support for data storage.
213K
Questions
--
Followers
--
Top Experts
Get a personalized solution from industry experts
TRUSTED BY
ASKER