- Community Home
- >
- Storage
- >
- HPE Nimble Storage
- >
- Application Integration
- >
- Re: Exchange 2016: One big volume for all database...
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Forums
Discussions
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Community
Resources
Forums
Blogs
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО12-08-2017 02:51 PM
тАО12-08-2017 02:51 PM
Exchange 2016: One big volume for all databases or one volume for each database?
I'm going back and forth with my decision here. What do you guys recommend?
When designing the Exchange storage infrastructure to host my database VMDK files, should I put all of my VMDKs in one big Nimble volume or should I create one volume for each VMDK?
I don't want to end up having to replicate or rebuild a huge multi-TB volume but would that ever even be an issue?
Another related question ... should I create a separate VMDK for each database or should I put multiple or even all of my databases in a single VMDK? As of right now, I'm looking at about 30-40 databases per server and I have 3 servers in my DAG. Each database will be about 400 GB and will host between 80-100 users. That doesn't include the tlog VMDK and I'm not quite sure how to handle the archive databases. This will be my first time using the archive feature of Exchange.
Any helpful information or even links to blogs or whitepapers would be appreciated. I'm having a hard time finding a good source of information on how to set up the SAN portion of Exchange.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО12-09-2017 03:00 PM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО12-11-2017 10:15 AM
тАО12-11-2017 10:15 AM
Re: Exchange 2016: One big volume for all databases or one volume for each database?
Thank you for that. There's a lot of good info there.
That example you posted ... that's extremely detailed ... I can't believe they're comfortable using twelve 1.2 TB databases, though! I can't imagine how long the reseed time would be with that.
Hopefully I can find a few documents dealing with VMware and VMDKs in there.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО12-13-2017 07:53 AM
тАО12-13-2017 07:53 AM
Re: Exchange 2016: One big volume for all databases or one volume for each database?
Personally I would not use VMDK's to store Exchange Databases on unless you have some in guest Exchange backup solution.
I would do in guest iSCSI and create actual volumes and give it to the Exchange server. This is what I do for our current Exchange 2010 enviroment and what I plan to do next year when we move to Exchange 2016. The boot drive and "D:\" drive are on VMDK's but the log and DB drives are in guest iSCSI volumes.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО12-14-2017 12:52 PM
тАО12-14-2017 12:52 PM
Re: Exchange 2016: One big volume for all databases or one volume for each database?
I'm going to use VEEAM to back up my Exchange environment so I have to use VMDKs. From what I understand, VEEAM doesn't support any in-guest mounted solution. so I'm stuck using VMDKs.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО01-17-2018 01:21 PM
тАО01-17-2018 01:21 PM
Re: Exchange 2016: One big volume for all databases or one volume for each database?
That is correct, Veeam doesn't backup iSCSI connected volumes. It is also a pain for when contractors come in to assist as they have to figure out where all those iSCSI connects go. I have been in some environments where those connections can cause all sorts of issues. There are loads of write ups from VMware about virtualizing exchange. Cross reference those with the storage docs and you should be covered.