Do you wonder if your IT business is truly profitable or if you should raise your prices? Learn how to calculate your overhead burden using our free interactive tool and use it to determine the right price for your IT services. Start calculating Now!
Using SAN in Exchange 2010 DAG
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.
Do more with
EXPERT OFFICE® is a registered trademark of EXPERTS EXCHANGE®
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
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 ?
Yes I understand it shouldn't be shared. As I said since they separated I mean they should be unique volume for each server.
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.
Premium Content
You need an Expert Office subscription to comment.Start Free Trial