Cluster 2008 R2

We are receiving cluster failure always with the below error..please let me know the solution to this
These servers are virtual and cluster configured.
Cluster IP address resource 'IP Address 10.x.x.x cannot be brought online because a duplicate IP address '10.1x.x.x' was detected on the network. Please ensure all IP addresses are unique.

Ping the IP address in question to see if it is live. Perform an nslookup on it to try and obtain the host name and ultimately located where the registration is.
Ensure your cluster resource does indeed have a unique IP. Ensure that any DHCP scopes exclude these IPs from their range (if they fall within the ranges - which is usually better to avoid).
Regards,
Mark Broadbent
Contact me through twitter |
blog | sqlcloud
Please click "Propose as answer" if a post solves your problem
or/and vote the post up if it's been helpful.
Want professional SQL Server High Availability Training? Click here

Similar Messages

MSDTC Service Interrupted due to Low Disk Space in MSDTC Log drive (Cluster 2008)

Hi,
I am working on SQL Cluster 2008 along with MSDTC service configured for the purpose of Distributed transactions.
I was looking into cluster logs and found that there is fail over happened of MSDTC service. I have analyzed the event viewer logs and found the MSDTC service interrupted at particular time and same was restored automatically. Below is the
details of MSDTC logs captured:
Event ID: 4103, Source MSDTC Client 2
Description: Service: MSDTC$d02c9ba0-70c4-4b72-994c-30170ab14f2d is still running. Attempt to cleanup the service has failed.
I have gone through the Health status of server and found the cause of Service interrupt is due to high disk space utilization. I have verified the MSDTC log file but haven't found any error which indicates any issue from MSDTC service end.
Generally MSDTC log consuming 4 MB space and currently there is 5 GB disk space is allocated to MSDTC service.
I am still struggling to find the RCA... Please help on same.

Hi,
Event ID 4103 — Microsoft Distributed Transaction Coordinator Service Startup.
You may try restart MSDTC service and then check the result. To restart MSDTC:
Click Start, and then click Run.
Type comexp.msc, and then click OK. If the User Account Control dialog box appears, confirm that the action it displays is what you want, and then click Continue.
Click Services.
In the Services pane, right-click Distributed Transaction Coordinator, and then click Restart.
The system stops and then restarts MSDTC.
To alternatively stop and restart MSDTC:
Click Start, and then click Command Prompt.
At the command prompt, type net stop msdtc, and then press ENTER.
At the command prompt, type net start msdtc, and then press ENTER.
For more information please refer to following MS articles:
Event ID 4103 — Microsoft Distributed Transaction Coordinator Service Startup
http://technet.microsoft.com/en-us/library/cc774406(v=ws.10).aspx
Lawrence
TechNet Community Support

Failover Cluster 2008 R2 - VM lose connectivity after live migration

Hello,
I have a Failover Cluster with 3 server nodes running. I have 2 VMs running in one the the host without problems, but when I do a live migration of the VM to another host the VM lose network connectivity, for example if I leave a ping running, the ping command
has 2 response, and 3 packets lost, then 1 response again, then 4 packets lost again, and so on... If I live migrate the VM to the original host, everything goes OK again.
The same bihavior is for the 2 VMs, but I do a test with a new VM and with that new VM everything Works fine, I can live migrate it to every host.
Any advice?
Cristian L Ruiz

Hi Cristian Ruiz,
What your current host nic settings now, from you description it seems you are using the incorrect network nic design. If you are using iSCSI storage it need use the dedicate
network in cluster.
If your NIC teaming is iconfigured in switch independent + dynamic, please try to disable VMQ on VM Setting for narrow down the issue area.
More information:
VMQ Deep Dive, 1 of 3
http://blogs.technet.com/b/networking/archive/2013/09/10/vmq-deep-dive-1-of-3.aspx
I’m glad to be of help to you!
We
are trying to better understand customer views on social support experience, so your participation in this
interview project would be greatly appreciated if you have time.
Thanks for helping make community forums a great place.
Hi!
thank you for your reply!
Yes, We are using iSCSI storage, but it has its own NICs for that (2 independant NIcs just to connect the server with the storage) and they are configured to not use those NICs to cluster communication. The team configuration is just for the LAN connectivity.
The NIC teaming is configured using BACS4 software from a DELL server and in Smart Load Balancing and Failover (as you can see here
http://www.micronova.com.ar/cap01.jpg). The link you passed is for Windows Server 2012 and we are running Windows Server 2008 R2, BUT as you can see in the following capture the NICs has that feature disabled
( http://www.micronova.com.ar/cap02.jpg ).
One test that I'm thinking to do is to remove teaming configuration and test just with one independant NIC for LAN connection. But, I do not know if you think another choice.
Thanks in advance.
Cristian L Ruiz
Sorry, another choice I'm thinking too is to update the driver versión. But the server is in production and I need to take a downtime window for test that.
Cristian L Ruiz

SQL Cluster 2008 RTM related issue- One of the Node is automatically disabiling the Agent XP's. However, all SQL Services are running

Hi All,
Please help. I am having a Prodution SQL 2008 RTM Cluster with two nodes-where node 1 works without any problem.However, if i failover to node 2-Agent xp's are disabled automatically. When i verify the SQL Services are node 2 are running fine.
Checked Agent.out file which did not give much info than below:
2012-09-09 08:00:12 - + [162] Internal request (from SetJobNextRunDate [reason: schedule will not run again]) to deactivate schedule 47
2012-09-15 06:50:30 - ? [131] SQLSERVERAGENT service stopping due to a stop request from a user, process, or the OS...
2012-09-15 06:50:41 - ? [098] SQLServerAgent terminated (normally)
I have verified that hardware and software of both nodes are identical. Still ,this issue persists always.
Please let me know the solution for this. it really pressurise on Production having one node active and other not active.
Harithasri

sp_configure 'show advanced options', 1;
GO
RECONFIGURE;
GO
sp_configure 'Agent XPs', 1;
GO
RECONFIGURE
GO
Are the SQL Agent running under the same accounts?
Best Regards,Uri Dimant SQL Server MVP,
http://sqlblog.com/blogs/uri_dimant/
MS SQL optimization: MS SQL Development and Optimization
MS SQL Blog:
Large scale of database and data cleansing
MS SQL Consultants:
Improves MS SQL Database Performance

SQL Cluster 2008 R2 Geocluster configuration with 2 VIP

Hi All,
If anyone has configure 2008 R2 Geo-cluster accross database center in different subnet. I'm interested to know whether is it possible we can cofigure cluster with 2 VIP and both VIP in different subnet e.g primarary DC VIP
is 10.20.x.x and secondary DC VIP 10.144.x.x.
Please help me

Multiple virtual IPs are not supported in SQL Server 2008. The only approach you can go with is implementing a stretched VLAN across the data centers
Edwin Sarmiento SQL Server MVP | Microsoft Certified Master
Blog |
Twitter | LinkedIn
SQL Server High Availability and Disaster Recover Deep Dive Course

SQL cluster 2008 R2 migration to new Hardware in VM

Hi,
We have a task to migrate existing Physical SQL Cluster DB to new Hardware but in VM. (cannot argue with the client)
hence our plan is to install new Cluster in VM with same Windows and SQL version i.e Win 2K8 R2 ENT w/SP and SQL 2K8
R2 STD w/SP and use SQL mirroring option for the DB to migrate on the new Server (keeping the downtime to as low as possible and advantage of bringing the old server online in case of any issues..)
Below points are for a single instance, couple of DB to migrate:
Keep the physical production server running
In-Parallel build New SQL Cluster in VM (keep same version windows/sql)
Keep Same drive letter for Quorum, MSDTC, DATA, LOG & Backup
Keep the same Instance Name, SQL Network Name can be different (will be changed to old network name once the PROD is shutdown)
Check all logins windows and SQL to be same on both the clusters
Copy all the jobs, SSIS packages etc.. .create the location folder as per current server on the VM SQL Cluster
Perform full backup of old cluster company-db databases or use the existing latest backup (full, differential, transaction)
Restore databases in the new cluster with no recovery so additional log file or differential backup can be restored
Create SQL Mirroring for the Database and select the principal server (old cluster) and the mirror server (new VM cluster)
Choose mirroring without witness ( no auto failover as we don’t need the old server later)
Start the mirroring – (hopefully everything synchronized and working)
During the downtime –
Stop the application/ client connection – if possible
Failover the DB through Mirroring option
Once the mirrored server becomes Principal and data is accessible – stop the mirroring
Now the new VM SQL Cluster DB is online
Shutdown the old cluster company-db (Node1 & Node2)
Come back to VM SQL Cluster and change the Network name to the old server network name (so that client connections are not affected)
Check if the DNS entries are updated with correct name and IP address
Delete DNS entries for old company-db on DNS Servers if not deleted, delete the old server SQL network name in computer object
Stop SQL Resources on the new VM SQL Cluster (take it offline all the resources)
Bring online the SQL Resource and make sure the SQL resources are online and new network name is reachable
Wait till you see machine name company-db in active directly (AD) and DNS server will have entry for company-db
Verify connectivity for company-db from outside.
If things are not going as per the plan then shut down the new VM cluster
Revert back the DNS settings
Power up the Old SQL Server
The DB will show “restoring mode” – use command to make it online “RESTORE DATABASE (dbname) WITH RECOVERY”
Check the DB
Start using the OLD server again
Troubleshoot the failed scenario ;)
Need to know if the above steps are okay, and any consideration once the new VM SQL Cluster is online.
Kindly let me know if there anything else to transfer apart from the logins, jobs, folder location etc.. !!
Many Thanks

Hello,
Well if you don’t change the instance name (name = ABC) then its OK.
Try the following resources about transferring SQL Server logins:
http://support.microsoft.com/kb/918992/en-us
http://www.mssqltips.com/sqlservertip/2081/transfer-sql-server-jobs-task-and-transfer-sql-server-logins-task-in-ssis/
Hope this helps.
Regards,
Alberto Morillo
SQLCoffee.com

In Failover Cluster 2008 mailbox2 server network status Unavailable (down).

Hi
I am new here, & hope i can get some help for the below issue
let me keep it simple scenario
i have 2 mailbox server ( mbx01 & mbx02)
2 cashub Server ( cshb1-cshb2) all running on hyper-v. last week due to some maintenance in data center i have to bring down all the production environment, once the thing are fixed in DC , i started all the server and found out that my exchange node 2 database
are failed.
In exchange 2010 failover cluster node ( node2 ) is down network status unavailable. due to by exchange node2 database are failed.
also i cannot access the file share witness directory from any of the above server.
can any body assist me on this please
thank you

Make sure both the DAG members have access to the witness directory. Check the location and make sure you have access. Open the DAG properties from Node2 and try to update the witness server and witness directory. Check the firewall/antivirus of the witness
server. Try disabling antivirus and firewall. If witness server is not online your databases will go offline. Pleae check
this
Get-DatabaseAvailabilityGroup -Identity DAG -Status | fl name,servers,witnessserver,witnessdirectory,alternatewitnessserver,alternatewitnessdirectory,operationalservers,primaryactivemanager,witnessshareinuse
Thanks, MAS
Please mark as helpful if you find my comment helpful or as an answer if it does answer your question. That will encourage me - and others - to take time out to help you.

MSDTC set up in SQL Server 2008 failover cluster

Hi Guys,
I am in the process of setting up failover cluster using SQL Server 2008 (64Bit) Enterprise on Windows Server 2008 R2 (64Bit) I have completed almost all the works but I got few questions regarding MSDTC configuration whether the MSDTC disk should
be assigned from SAN or it should be local to the disk , Separate disk for each nodes in the cluter or 1 disk to be used across all the servers for MSDTC in windows fail over cluster.
With regards, Gopinath.

Hi Gopinath,
Please review the following similar blogs to get more details about configuring MDTC and pros & cons of different options.
How to Configure Multiple Instances of Distributed Transaction Coordinator (DTC) on a Windows Server Failover Cluster 2008
http://blogs.technet.com/b/askcore/archive/2009/02/18/how-to-configure-multiple-instances-of-distributed-transaction-coordinator-dtc-on-a-windows-server-failover-cluster-2008.aspx
How to configure DTC for SQL Server in a Windows 2008 cluster
http://blogs.msdn.com/b/cindygross/archive/2009/02/22/how-to-configure-dtc-for-sql-server-in-a-windows-2008-cluster.aspx
Thanks,
Lydia Zhang
Lydia Zhang
TechNet Community Support

SQL 2008 R2 SP1 Cluster SAN Migration

Dears,
I am doubting about procedure and steps that must be followed while doing SAN Migration for my cluster 2008 R2 SP1 SQL.
For me, I already did cluster Quorum SAN Migration, but I am doubting about all remaining steps such:
Some one told me about disk signatures, what should I do for this?
What are steps for MSDTC migration?
How to Migrate SQL Instance?
What about Master and other system databases?
What about Apps Database, logs, and temps?
What about below commands: FOR WHAT IT IS NEEDED?
ALTER DATABASE
msdb
MODIFY FILE ( NAME = MSDBData,
FILENAME = '
H:\MSSQL10_50.MSSQLSERVER\MSSQL\DATA\
MSDBData.mdf' )
ALTER DATABASE
msdb
MODIFY FILE ( NAME = MSDBLog,
FILENAME = '
H:\MSSQL10_50.MSSQLSERVER\MSSQL\DATA\
MSDBLog.ldf' )
SELECT name, physical_name AS CurrentLocation, state_desc
FROM sys.master_files WHERE database_id = DB_ID(N'msdb');
ALTER DATABASE
model
MODIFY FILE ( NAME = modeldev,
FILENAME = '
H:\MSSQL10_50.MSSQLSERVER\MSSQL\DATA\
model.mdf' )
ALTER DATABASE
model
MODIFY FILE ( NAME =
modellog,
FILENAME = '
H:\MSSQL10_50.MSSQLSERVER\MSSQL\DATA\
modellog.ldf' )
Please help on this coz I am afraid about my information!

Some one told me about disk signatures, what should I do for this?
If you can present in disks from both SANs at the same time then this shouldn't be an issue. At a high-level you can add the new disks in and remove the old ones from the cluster when you're finished with them. The disks are just seen as new disks...not swapped
ones.
What are steps for MSDTC migration?
- Personally I've simply deleted and re-created the MSDTC, there might be a nicer way to do this, but re-creating it works.
How to Migrate SQL Instance?
- You mean elements that are on a SAN attached drive that aren't part of the cluster? You can stop the instance and copy the files (use
xcopy to preserve permissions), Then swap the drive letters around & restart the instance.
What about Master and other system databases?
For system databases I would
- bring the new disk into the cluster, give it a temporary drive letter, make sure sql server has a dependency on it (look at how the current drives are setup)
- stop the services
- copy the folders/files to the new drive using xcopy preserving permissions
- give the current drive an unused drive letter (via cluster manager)
change the new drive letter to match the original drive (via cluster manager)
- remove the old drive (remove dependencies before doing this)
- bring the server online
What about Apps Database, logs, and temps?
-You can do this 'online' while the sql server is running, just bring the new disk into the cluster and following the Microsoft recommended approach outlined
here
What about below commands: FOR WHAT IT IS NEEDED?
- that's for msdb and model, you'll have already handled those databases with the other system dbs.

Confirm no support for MSSQL 2008 before reverting to older EM version

Before I resort to installing EM Grid Control (11.1.0.1), I want to confirm that I have correctly read that EM12C does NOT support monitoring of MSSQL 2008. I understand that MSSQL 2008 R2 is certified with EM12C but, it appears that monitoring the original MSSQL 2008 is not.
Also, I'm a bit nervous about using EM Grid Control since it appears to have been a one-and-only version. Would I be smarter to go back to one of the EM10 versions?
This will be a new install, not an upgrade, so I hate to start out with an outdated EM tool but, I have to be able to monitor MSSQL 2008.
TIA,
Jeri

I have received a response from MOS to my original SR which confirms that EM12C is not certified for monitoring MSSQL 2008. For those who may possibly be interested in clarification of other OS and/or MSSQL versions with various flavors of EM, I've included below the full SR response details:
"The 12cR1 and 12cR2 Cloud Control are only certified to monitor two versions of Microsoft SQL Server : 2005 and 2008 R2
The 12cR2 is certified with these 3 Windows OS versions : 7,2008 R2,2003 on 64-bit platform where as the 12cR2 is certified with 4 versions of Windows OS version: 7,2008 R2,2008,2003
The 11g Grid Control is certified to monitor 7 versions of Microsoft SQL Server (including 2008) : 2008 R2 Cluster,2008 R2,2008 Cluster,2008,2005 Cluster,2005,2000
Also 11g Grid Control certified with 4 versions of Windows platform : 7,2008,2003 R2,2003"
The analyst who provided this information was also kind enough to open another SR on my behalf which will hopefully yield the answer to my other question- whether deploying 11g Grid Control is the best option for my environment or whether one of the EM10 versions might be a better choice. Unless someone else here is interested in that answer too, I won't update this post further with that information.
Thanks, Jeri

Cluster Resource IP Conflict

Hi,
I have 2 node windows cluster 2008 R2 Cluster resources are offline due to Cluster resource Ip conflict.
Windows
has detected Ip address conflict
Another
computer on this network has the same IP address as this computer. Contact your network administrator for help resolving this issue. More details are available in the Windows system event log.
Checked and found that Cluster resources ip address getting conflict with node 1. how can it be conflicting with itself?
Kindly let me know how to fix this issue.
Regards,
Sridharan. M

Hi Murat Demirkiran,
Thanks for the above infoirmation.
I have same issue in one my my cluster server. I have a two node server. as you said above i have 3 different IP address for node 1, node 2 and Cluster name. My issues
is that resource 1 ip address is conflict with Node 2 server.(Resource 1 ip address is conflict with the ip address of node 2 (showing the mac ID of node 2).
Please help me on this please
Salesh.C

MSSQL2012 active/passive cluster convert to active/active cluster

Good day.
We have 2-node active/passive MSSQL2012 cluster (on Win 2008 R2). One "default" instance.
We want convert to active-active, (multi-instance).
As I understand, one SQL instance (existing) will run on 1 cluster node and the second (new) instance on the 2 cluster node.
I have some questions:
- we have cluster virtual name and ip address for existing MSSQL instance, for the second MSSQL instance we need to create another name and ip ?
- for second MSSQL instance we can create 2 separate cluster disks (for DB and LOGS) ?
- for second MSSQL instance we can create another DTC instance and bind it to the second MSSQL instance ?
- we can use existing physical LAN connectors on our servers (data and heartbeat) or we need to add new LAN adaptors ?
- quorum disk is the same for all instances ?
Sorry for my bad English.

I have some questions:
- we have cluster virtual name and ip address for existing MSSQL instance, for the second MSSQL instance we need to create another name and ip ?
Yes that would be required.
- for second MSSQL instance we can create 2 separate cluster disks (for DB and LOGS) ?
Yes it will be in different resource group and you can have different disk for them.
- for second MSSQL instance we can create another DTC instance and bind it to the second MSSQL instance ?
Same MSDTC can be used for multiple instance.
http://blogs.technet.com/b/askcore/archive/2009/02/18/how-to-configure-multiple-instances-of-distributed-transaction-coordinator-dtc-on-a-windows-server-failover-cluster-2008.aspx
- we can use existing physical LAN connectors on our servers (data and heartbeat) or we need to add new LAN adaptors ?
Best to ask network team
- quorum disk is the same for all instances ?
Quorum is for windows cluster not for SQL server so Yes its same for all instances
Sorry for my bad English.
Please mark this reply as the answer or vote as helpful, as appropriate, to make it useful for other readers

Print migration - after migration not able to put spool to cluster drive

Hello
I am performing a migration from standalone server 2008 to 2 node printer cluster 2008.
All my spool are configured to D drive in cluster - when i migrate the printers from standalone server to cluster printer server, Spools are not able to load in D drive (data drive in cluster) its residing in c drive it self in cluster node. In standalone
server all spool are residing in c drive. Can any expert let me know how to solve this!!
regards
Prasad S

Hi Prasad S,
Based on your description, I understand you want to migrate a standalone printer server to a clustered print server. However, the Spool can’t be loaded. Would you please
let me know whether use resource kit utilities (such as Print Migrator tool) to help you automate the migration or migrate manually?
Please refer to the following KB and check if can help you.
How to Set up a Print Spooler on Microsoft Cluster Server
How to Migrate a Printer Server to a Server Cluster
If anything I misunderstand or any update, please don’t hesitate to let me know.
Hope this helps.
Best regards,
Justin Gu

EHP4 on MSCS 2008 - PHASE KX_CPYORG - Instance number conflict

Hello Experts,
Need some help on EHP4 on MSCS 2008.
We are Installing EHP4 on ECC 6.0 Windows 2008 - MSCS cluster 2008 environment and facing a problem while instllation Step EXTRACTION and PHASE KX_CPYORG. We have successfully installed on Sandbox and Dev regions, but now as our QAS is a Cluster environment we believe it is causing the problem.
Below is the error log from E:\usr\sap\<SID>\EHPI\abap\log KX_CPYORG.txt
1 ETQ201 Entering upgrade-phase "KX_CPYORG" ("20101113145523")
2 ETQ367 Connect variables are set for standard instance access
4 ETQ399 System-nr = '41', GwService = 'sapgw41'
4 ETQ399 Environment variables:
4 ETQ399   dbs_mss_schema=meq
4 ETQ399   auth_shadow_upgrade=0
4 ETQ399 Set environment for standard connect:
4 ETQ399 ENV: dbs_mss_schema=meq
4 ETQ399 ENV: auth_shadow_upgrade=0
4 ETQ399 Set RFC variables for standard connect:
4 ETQ399 System-nr = '41', GwService = 'sapgw41'
4 ETQ399 Set tool parameters for standard connect:
4 ETQ399   default TPPARAM: DEFAULT.TPP
1 ETQ206 Executing pre-phase DB specific actions.
Some details of our system
- The ASCS instance number is installaed on the Cluster and no. is 40
- The Central Instance is installed on a separate standalone VM Server with Instance number 41.
- The EHPI is triggered on the Central instance on the VM.
- Error is throwing exactly after the step accepting the profiles (All three).
Also with this error the SAPup is completely failing and stopping the Installation with the below error.
======================================================
Unable to execute the SDT request ABAP operation revoke-extract on hostname chgva-sap-meq instance 41
Unable to determine if a revoke of the ABAP upgrade request ABAP is possible
Cannot check for revoke possibility
Tool died unexpectedly with
FATAL ERROR: Inconsistent system number in profile '41' != '40'
======================================================
Any suggestions/solutions in resolving the issue are appreciated.
Thanks
Ajay

Hi,
It looks like there is some problem in reading profiles. Are all profiles present in profile directory (including ASCS and CI) ?
Also, make sure that while you select the system number of shadow instance then it should not be 40 and 41.
Thanks
Sunny

SCOM 2012 SP1 SQL Server 2008 R2 Clustering Monitoring?

We have a new print management system that was setup using SQL server 2008 R2 clustering. Right now we have SQL MP (monitoring)(discover) 6.3.173.1. They had a failover occur a week ago and SCOM didnt throw any alerts. As a temporary
fix, I found some correlated events and setup a monitor for those events on the servers. However, the system owner wants to know if there is a MP that will monitor for a SQL cluster failover event. I have looked and looked and cant seem to find
anything that gives a whole lot of detail on this.
Thanks
EFD
Warm Fuzzies!

Yes, you can monitor SQL Cluster 2008 using SCOM 2012 SP1. but you need to install SQL MP and Windows Cluster MP and Enable proxy Agent on physical nodes.
You can refer below link {it's same for SCOM 2012}
http://blogs.technet.com/b/birojitn/archive/2010/04/14/sql-server-2008-cluster-monitoring.aspx
Please remember, if you see a post that helped you please click "Vote As Helpful" and if it answered your question, please click "Mark As Answer"
Mai Ali | My blog: Technical | Twitter:
Mai Ali

Cluster 2008 R2

Similar Messages

Maybe you are looking for