We are trying to setup a Windows Server 2003 Cluster with 2 systems and a DAV. We intend to install SQL 2005 on this Cluster. We purchased a DAV with 3 physical disk arrays as follows.
73GB RAID 1 (our plan is to use this to store sql transaction logs)
146GB RAID 1 (sql backups, temp database & other temp files)
420GB RAID 10 (sql databases)
Now as we are setting all this up we find out we need a shared physical drive on the DAV to store the Quorom. It is my understanding we cannot partition the physical drives and use one of the partitions to store the Quorum because when you create the resource for the Quorum the resource is the phsyical disk not the partition.
So my question is, is it in our best interest to buy a seperate physical disk for the Quorom?
My next question is, with regards to the MSDTC, is it in our best interest to buy a seperate physical disk for the MSDTC or can we store it on the 146GB RAID 1 and still use the drive for its original purpose?
I'm just starting to work with AlwaysOn Availability and WSFC.
I have in my environment (in Azure) a DC, WSFC and to SQL instances, so I have 3 nodes in my Failover Cluster:
WSFC SQL1 SQL2
If I simulate failure by shutting down one of the SQL boxes my Availability group seamlessly fails over to the other SQL instance - which is great.
However, I'm starting to look into the workings of the Quorum, my envt has the default settings and when I shutdown both of my SQL servers I expected the Cluster itself to go offline as 2 out of the 3 votes will be negative, but the Cluster is still up - Screenshot below when SQL1 and SQL2 are shutdown:
Going through the Wizard (but not changing anything) it shows following config:
Today we installed on MS Cluster (W2k3) and SQL Server 2000 a MSDTC Service. The installation was succesfull, but wenn we try to move the group, then it failed. Because we have only 2 Disks on the cluster one for the Quorum, the other for the Sql Server. We installed the MSDTC as a Resource on the Quorum Disk. The other Thing, wenn we start the firts node all is running on the first node, but we cannot move. Wenn we start the second node all is running on the second node, but we cannot move the Group which contain the Msdtc resource.
More often than not, I typically don't touch DTC on clusters anymore; however on a project where the vendor states that it's required. So a couple things here.
1) Do you really need DTC per instance or one for all? 2) Should DTC be in its own resource group or within the instance's group? 2a) If in it's own resource group, how do you tie an instance to an outside resource group? tmMappingSet right?
Is it possible to install and configure the MSDTC resource in a SQL Server 2000 cluster after SQL is installed and running?
When I recently went through a rebuild of my cluster, I forgot to install the resource before installing SQL Server. Now, if I install and bring online the MSDTC resource the SQL disk groups will not fail over correctly. The SQL Server resource will not come online.
Thanks in advance for any help. I would really like to avoid rebuilding again.
I'm just a newbie with clustering. We've got a 64-bit A-P cluster running with Sql25k 64-bit too. Each node own two local network adapters. One of them (the one currently is Active) own three IP and the another one only one.
Why? From CLUADMIN I see as one of these three is set as Cluster IP Address in Active Resources. So I see the following configuration for the Active node:
Adapter 1: IP public for Active Directory Adapter2: IP1 (reserved or ???????) IP2 (used as SQL IP Address 1 in Active Resources) IP3 (used as Cluster IP Address in Active Resources)
Passive node:
Adapter 1: IP public for Active Directory Adapter2: IP (only have one ???)
Is this correct/necessary? Does anyone have similar configuration?
In reading material on the quorum drive on a sql server cluster in mentions this is the drive the logs are written to. Is this referring to sql log files that are dumped by a process or scheduled job, or some other log files?
I'm trying to install a server cluster to implement an SQL Server 2005 cluster. No other services (I think this is important).
I've a dual SCSI channel Smart Array with 4 disks configured in a 400Gb RAID 5.
I do not need to move different resource groups from one node to the other, I need only one group with all the resources IP, Network name, MSDTC, and SQL Server..., when a node fails, all services should failover to the other node.
Is it possible to have only one physical disk (RAID 5) for Quorum disk and shared disk?
It would be the following configuration:
[Groups] Cluster Group IP Address Network Name Physical disk (used for quorum and shared storage) Distributed Transaction Coordinator SQL Server SQL Server Agent Generic Service (SQL Server Fulltext)
The other option would be having a 1 physical disk Raid 0 for Quorum (146Gb wasted) and another physical disk Raid 5 (3 disk) for Shared Storage, but this schema will have a a flaw point that if Quorum disk fails, the cluster fails....
I've the quorum disk of my cluster on win2003 full and I cannot use The cluster administrator because the Service Cluster cannot going up.
Obviously the shared disk (included Quorum) and MSDTC are not visible and I'm wondering if is possible to solve the problem without rebuild the cluster.
I am trying to setup clustering for SQL 2005. I initially want to setup a 2 node cluster in Active/Active Configuration.
I am trying to understand the Quorum disk in SQL 2005. As I understand the quorum disk is a shared resource. How is this resource configured? Would I need to have an iSCSI or fibrechannel connection from each of the nodes to the shared disk?
As well, does each node have a separate data drive? Or do all the nodes use only the shared storage?
I have a windows 2012 cluster environment that consists of two SQL servers nodes with Quorum disk configured as witness.
Manual failover between nodes is working fine, however the sql instance virtual is not seeing the Quorum disk.
Moreover the Quorum disk has the same number as another cluster storage disk, is that considered a problem?
When I move the SQL instance from a node to anohter, should the Quorum Disk change ownership as well to that destination node ? if it is not changing ownership what would be the problem??
I am trying to setup a test cluster and am having an issue. When I try to create the resource of a physical disk it takes both the drive e: and drive q: and doesn't seperate them into two physical disks as resources. This means when I try to associate the quorum disk it links the to physcial disk resource of drive e and q. Then when I try to install SQL2k5 I get the warning about installing SQL on the quorum disk. Am I missing something? Is there a way to seperate e and q onto two physical disk resources so I can specifically associate the quorum to q and the sql to e or should I be setting the quorum disk to a majority node set? Thanks in advance.
During the installation of Adding node to a SQL Server failover cluster(On passive node) getting error like.. The MOF compiler could not connect with the WMI server. This is either because of a semantic error such as an incompatibility with the existing WMI repository or an actual error such as the failure of the WMI server to start.We run the below commands but didn’t get any resolution & got the same above error .
1<sup>st</sup> Method…
1. Open console command (Run->CMD with administrator privileges).
2. net stop winmgmt
3. Rename folder %windir%System32WbemRepository to other one, for backup purposes (for example _Repository).
I am in the process of moving databases from a SQL 2005 Standard version to a 2-node 2014 cluster.All of my 2005 databases back up successfully.They all restore without issue except for one database that has a full text catalog. I get this message
Msg 7610, Level 16, State 1, Line 2 Access is denied to "fileStoragedataMSSQLSERVERFullTextCatalog", or the path is invalid. Msg 3156, Level 16, State 50, Line 2 File 'sysft_FTCatalog' cannot be restored to 'fileStoragedataMSSQLSERVERFullTextCatalog'. Use WITH MOVE to identify a valid location for the file. Msg 3119, Level 16, State 1, Line 2 Problems were identified while planning for the RESTORE statement. Previous messages provide details. Msg 3013, Level 16, State 1, Line 2 RESTORE DATABASE is terminating abnormally.
[code]....
I went as far as giving the folder full access to everyone temporarily and received the same error.
Can I build a cluster by adding the cluster service, then the SQL instances, then add the other nodes and their passive SQL instances?I would lean to building the cluster first, the add the SQL instances.
Trying to locate information on MSDTC. Is this "needed" to run SQL Server? That is, if this part of the installation is deleted, will SQL Server still function? Also, does anyone know if this is a crucial tool needed by Veritas Volume Manager or Windows Disk Manager?
If anyone knows of a link to this information, I'd appreciate it. My searches come up with lots on information on MSDTC, but nothing that answers my specific questions.
When i do a BEGIN TRAN to a SQL server sitting on Windows 2003 Server from a SQL Server Sitting on Windows 2000 Server, the Transaction hangs and if I try o kill it the Transaction is in ROLLBACK State.
I tried setting the Properties for the MSDTC and restarted the Windows 2003 Server but in vain
I keep getting this error on my application server...what does it mean?The description for Event ID ( 0 ) in Source ( ODBC ) cannot be found.The local computer may not have the necessary registry information ormessage DLL files to display messages from a remote computer. Thefollowing information is part of the event: Failed to enlist in DTC:SQL state 37000, native error 8501, error message [Microsoft][ODBC SQLServer Driver][SQL Server]MSDTC on server 'PROSQL' is unavailable..any help would be appreciated...thanks-Jim
I'm using msde. On the little icon in task tray, you have under currentservice, a choice of mssqlserver, and another choice is msdtc. What ismsdtc? And what is sqlserver agent?
The resource msdtc is down. Every time, it works pretty well , after we restart the servers(node1 and node2). But, about half a hour later, the problem is there. We reintalled msdtc. It didn't work out too. msdtc and sql server is on a cluster. Can anyone help me out?
I am running SQl 7.0 (SP4) on Windows XP Professional (SP2). Whenever I try an insert/update type of activity, the System returns the following message :
Server: Msg 8501, Level 16, State 3, Line 2 MSDTC on server 'SERVER' is unavailable.
However, all the required services including MSDTC are running on the System.
I have following script which i am planning to run to drop all non-clustered primary keys on a database and then created as clustered. I am using someone else's script so don't know how to modify this. Some of primary key columns are used in references in other tables.
is there anyway i can drop the existing primary keys and using their original script then create again as clustered including restoring all foreign and reference keys and unique or no unique.
DECLARE @table NVARCHAR(512), @tablename NVARCHAR(512), @sql NVARCHAR(MAX), @sql2 NVARCHAR(MAX), @sql3 NVARCHAR(MAX), @column NVARCHAR(MAX); DECLARE @indexname NVARCHAR(512); SELECT name As 'Table'
We are planning to change all IPs of PRODUCTION Failover Cluster Setup. In my cluster setup ... we have 2 Physical Nodes with windows-2008, Roles are MSDTC and SQL-2008R2.
IP change for:
1. Both Nodes(Physical) 2. MSDTC 3. SQL Server 4. windows Cluster
So Almost... All IPs are going to change.
Im DBA here, I need to take care of SQL cluster and MSDTC. But I haven't performed this activity before.So I'm worrying about Impacts and consequences of this change. steps how should I perform this activity.
I have a class that use a TransactionScope object for make make two operations into a database. The problem is that in a computer works well but in another I receive a error message: "MSDTC is not running in .SQLEXPRESS". I had watched the services in the computer and the "Microsoft Distributed Transaction Coordinator" is running. Does somebody know what is happening? Thankyou and sorry for my English.
I am selectively insert data from serverA databaseX to serverB databaseX. (serverA is linked server on B.)
I could insert parent and child tables. But get error when insert to grand-child tables: Server: Msg 8501, Level 16, State 3, Line1 MSDTC on server B is unavailable.
Don't think I need to turn on MSDTC on B. But I could copy and paste from source A server to target B server. Confusing on some table could insert while others with error....
