February 18, 2013 at 3:41 am
Hi All,
Iam unable to proceed with MSDTC storage configration where it fails with the folowing error:
No disk exists in available storage. to add disks click Storage Under actions add a disk
If I do so then I receive a second error stating No disk suitable for cluster disk were found.
We have SAN storage and it is been parttioned to Quorum, msdtc , sql data and sql log folder. and Under stirage I could see only one cluster disk with all these parttion but not able to select and single partition.
Please advice, my configuration is not proceeding further.
"More Green More Oxygen !! Plant a tree today"
February 18, 2013 at 9:26 am
what do you see under "Available storage" in the Failover Cluster manager snap in?
-----------------------------------------------------------------------------------------------------------
"Ya can't make an omelette without breaking just a few eggs" 😉
February 18, 2013 at 9:47 pm
Thanks Perry, for taking this up.
When I select Storage from the failover cluster I could see only 1 disk available with 900 GB in size and if I expand that disk I could see all the parttions but not able to map these partitions while configuring MSDTC . Please find the screenshot attached.
Please do let me know what should I do? Earlier I was using starwind for storage but this is the first time we are using SAN.
"More Green More Oxygen !! Plant a tree today"
February 19, 2013 at 1:41 am
Can you supply more info about how the storage is mapped, it seems to be mapped as one large disk group. The group doesn't contain a disk small enough for the MSDTC resource, the smallest is currently 70GB.
-----------------------------------------------------------------------------------------------------------
"Ya can't make an omelette without breaking just a few eggs" 😉
February 19, 2013 at 2:45 am
It looks like you have got all your drives mapped as separate partitions on a single Windows volume.
You need to rebuild this so that each drive letter has its own Windows volume.
Cluster failover works at the Windows volume level, not at the partition level.
Original author: https://github.com/SQL-FineBuild/Common/wiki/ 1-click install and best practice configuration of SQL Server 2019, 2017 2016, 2014, 2012, 2008 R2, 2008 and 2005.
When I give food to the poor they call me a saint. When I ask why they are poor they call me a communist - Archbishop Hélder Câmara
February 26, 2013 at 10:58 pm
Thanks Perry and EdVassie,
Yes your input to have separate volume have helped me here. I was able to configure the
Active/ Active cluster. So the current structure is 2 node failover active / active cluster
Node X and Node Y.
One windows cluster
2 MSDTC and 2 SQL named instance with failover node X and Y.
One question It only take one single quorum disk. Why is this?
I have 2 public, 2 private and 5 virtual IPS.
2 for MSDTC , 2 Virtual SQL Server NW name and one for windows cluster virtual name.
"More Green More Oxygen !! Plant a tree today"
February 26, 2013 at 11:36 pm
The quorum is a single mediator, there is only 1. It can use a file share or disk but also can use neither depending on the cluster configuration.
-----------------------------------------------------------------------------------------------------------
"Ya can't make an omelette without breaking just a few eggs" 😉
Viewing 7 posts - 1 through 6 (of 6 total)
You must be logged in to reply to this topic. Login to reply