We value your feedback.
Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!
Course Of The Month
1 day, 20 hours left to enrollBecome a Premium Member and unlock a new, free course in leading technologies each month.
Solved
Using SAN in Exchange 2010 DAG
Posted on 2012-12-27
I am in process of installing Exchange 2010 SP2. I want to create the DAG in mailbox servers I have two servers with these roles. But I am confusing that Do I have to create separate volumes for each member server in DAG or I have to have on volume shared between them. How DAG works with SAN in place. I know that as Best practice I should have two separate volume for Database and Logs. But my question is do I have to use shared volume or separate volumes in each server.
[X]
Welcome to Experts Exchange
Add your voice to the tech community where 5M+ people just like you are talking about what matters.
- Help others & share knowledge
- Earn cash & points
- Learn & ask questions
3-
2
- +1
7 Comments
NO, you no need to use shared volume or separate volume in each server.
or also refer this
http://exchangeserverpro.com/exchange-server-2010-database-availability-group-installation-step-by-step
or also refer this
http://exchangeserverpro.com/exchange-server-2010-database-availability-group-installation-step-by-step
Active 7 days ago
Exchange 2010 does not support shared volumes/lun/storage anymore. you will need to assign a separate storage space for each dag member this would mean, obviously, that you will be using x times the storage of the SAN where x is your number of nodes
Thank you but I think still I can use my SAN to attach volumes in both servers. I think it should fine since they are separate volumes in each servers. Am I right ?
Active 7 days ago
no you are not right. volumes should not be shared each server should see only its own volumes
Yes I understand it shouldn't be shared. As I said since they separated I mean they should be unique volume for each server.
Active 7 days ago
yes they should be separated and of course you can put then on the SAN if that is the question.
Separate LUNs on a SAN is fine. The only issue is the SAN is a single point of failure. If your SAN goes down then you could lose all of your mail. Microsoft's recommendation is to use independent JBODs. So if a JBOD goes down that it won't impact the other JBOD arrays.
In my environment, I am using multiple SANs accross two sites in a four Exchange server DAG configuration. If possible, you should have at least one DAG instance off site.
If you don't have this ability and only have the one SAN then, depending on the SAN, you need to make sure each Exchange DAG LUN sets are defined on a different group of disks. Some newer SANs that leverage storage virtualization can stripe multiple LUNs accross the same group of disks. Impeding performance for competing LUNs as well as potentially creating a single point of failure for all LUNs shared accross the same set of disks. However, there are typically capabilities that virtualization SANs may have to limit the drive failure risk, but either way you should be aware of these type of potential issues.
In my environment, I am using multiple SANs accross two sites in a four Exchange server DAG configuration. If possible, you should have at least one DAG instance off site.
If you don't have this ability and only have the one SAN then, depending on the SAN, you need to make sure each Exchange DAG LUN sets are defined on a different group of disks. Some newer SANs that leverage storage virtualization can stripe multiple LUNs accross the same group of disks. Impeding performance for competing LUNs as well as potentially creating a single point of failure for all LUNs shared accross the same set of disks. However, there are typically capabilities that virtualization SANs may have to limit the drive failure risk, but either way you should be aware of these type of potential issues.
Featured Post
Everything you need to know about backup and disaster recovery with AWS, for FREE!
Question has a verified solution.
If you are experiencing a similar issue, please ask a related question
After hours on line I found a solution which pointed to the inherited Active Directory permissions . You have to give/allow permissions to the "Exchange trusted subsystem" for the user in the Active Directory...
This article will help to fix the below errors for MS Exchange Server 2013
I. Certificate error "name on the security certificate is invalid or does not match the name of the site"
II. Out of Office not working
III. Make Internal URLs and Externa…
In this video we show how to create an Accepted Domain in Exchange 2013. We show this process by using the Exchange Admin Center.
Log into Exchange Admin Center.: First we need to log into the Exchange Admin Center.
Navigate to the Mail Flow >> Ac…
A short tutorial showing how to set up an email signature in Outlook on the Web (previously known as OWA).
For free email signatures designs, visit https://www.mail-signatures.com/articles/signature-templates/?sts=6651
If you want to manage em…
Suggested Courses
Course of the Month1 day, 20 hours left to enroll
Earn Certification
MTA Server Fundamentals Exam 98-365
$59.00$53.10
717 members asked questions and received personalized solutions in the past 7 days.
Join the community of 500,000 technology professionals and ask your questions.