Hi Folks,
Cluster validation step has failed due to the IP configuration validation ,
how can identity and How to resolve duplicate IP's
Can you suggest your views on this.
PFA
↧
how to resolve duplicate IP's in cluster configuration?
↧
"HadrLogCapture" messages in SQL Server Log
HI
After activating AlwaysOn High Availibility Groups in SQL Server 2012 R2 and adding databases at the availibilitygroup, SQL Server started genereting lots of messages in the SQL Server Logs.
Some example Messages are: "DbId (1466) log capture is rescheduled with partner generation: 45, log consumer id: 9828",
"HadrLogCapture::BuildMsgBodyForSend - DbId [2535]->[1807D374-DA55-4CAC-A831-AA3C3A8B8EC4] Send From saved msg - LogBlockId (0x000221e800000010)"
Is there is a possibility to stop generating these messages?↧
↧
Always on Availability groups using static SQL Tcp Port
Hi, I have 2 SQL 2012 servers in my DMZ and I have assigned SQL to run on a static TCP Port. I would like to setup Always On availability groups on the servers but I cannot get the failover to work with the static TCP port. It works fine with dynamic ports.
When the failover is initiated it attempts to connect to the secondary replica with out using the static port, can someone tell me how to setup the availability group using static tcp ports.
Thanks,
↧
Perform Forced Manual Failover of Availability Group (SQL Server 2012) and WSFC (Windows Server Failover Cluster)
I have a scenario with the three nodes with server 2012 standard, each running an instance of SQL Server 2012 enterprise, participate in asingle Windows Server Fail-over Cluster (WSFC) that spans two data centers.
If the nodes in the primary data center are unavailable due to data center outage. Then how I can able to access node in the WSFC (Windows Server Fail-over Cluster) in the secondary disaster recovery data center automatically with some script.
- I want to write script that can be able to check primary data center by pinging some IP after every 5 or 10 minutes.
- If that IP is unable to respond then script can be able to Perform Forced Manual Fail-over of Availability Group (SQL Server) and WSFC (Windows Server Fail-over Cluster)
Can you please guide me for script writing for automatic fail-over in case of primary data-center outage?
↧
Time-out issue Alwayson SQL 2012 Cluster
Currently I'm working on a large deployment of a SharePoint 2013 environment (stretched farm over 2 DC's). We are using a SQL 2012 alwayson multisubnet cluster (each DC has 1 SQL node). During the installation of SharePoint we encountered several connection time-out errors from the SQL environment. (Exception calling "Open" with "0" argument(s): "Connection Timeout Expired. The timeout period elapsed during the post-login phase. The connection could have timed out while waiting for server to complete the login process and respond;)
Steps we follow for SharePoint installation are:
Steps to configure SharePoint 2013 on an AlwaysOn Availability group:
1>Create SharePoint databases (with the PowerShell script)
- Configure a SQL alias for a consistent SQL instance name.
- Create farm on SQL instance/replica 1 (one of the SQL nodes), creating all databases needed (service-apps & web-apps). -->
we are connected directly to 1 SQL node and not connecting to the cluster. Installation server is in same DC as the SQL node.
- Stop SharePoint so databases remain static during migration to an AlwaysOn cluster.
2>Move database to AlwaysOn high-availability group.
- Restore all the DBs onto SQL replica 2 (with NORECOVERY).
- Create AlwaysOn availability group, or use existing
- Join the replica 2 databases to availability group.
- Create listener.
3>Migrate SharePoint onto AlwaysOn on cluster
- Make all SharePoint DB MultiSubnetFailover aware with PowerShell Cmdlet
- Reconfigure SQL alias for new listener àat this point the SharePoint farm is connecting to the SQL cluster (listener of AlwaysOn availability group of the SQL Instance), but we never reached this point so far.
- Restart SharePoint services with updated alias.
Event errors and SQL log errors that I found:
Date,Source,Severity,Message,Category,Event,User,Computer
09/18/2014 07:34:59,Microsoft-Windows-FailoverClustering,Error,Cluster network name resource 'SPAG_CU8000001105' failed registration of one or more associated DNS name(s) for the following reason:<nl/>DNS bad key.<nl/>.<nl/><nl/>Ensure
that the network adapters associated with dependent IP address resources are configured with at least one accessible DNS server.,(19),1196,NT AUTHORITY\SYSTEM,CU8000000015
09/18/2014 07:34:59,MSSQL$SPAG,Information,The Service Broker endpoint is in disabled or stopped state.,(2),9666,,CU8000000015
09/18/2014 07:34:52,Microsoft-Windows-FailoverClustering,Error,Cluster network name resource 'SPWMAG_CU8000002105' failed registration of one or more associated DNS name(s) for the following reason:<nl/>DNS bad key.<nl/>.<nl/><nl/>Ensure
that the network adapters associated with dependent IP address resources are configured with at least one accessible DNS server.,(19),1196,NT AUTHORITY\SYSTEM,CU8000000015
09/18/2014 07:34:52,MSSQL$SPWMAG,Information,The Service Broker endpoint is in disabled or stopped state.,(2),9666,,CU8000000015
09/18/2014 07:34:47,Service Control Manager,Information,The WMI Performance Adapter service entered the running state.,(0),7036,,CU8000000015
09/18/2014 07:32:41,Microsoft-Windows-FailoverClustering,Error,Cluster network name resource 'SPSDAG_CU8000003105' failed registration of one or more associated DNS name(s) for the following reason:<nl/>DNS bad key.<nl/>.<nl/><nl/>Ensure
that the network adapters associated with dependent IP address resources are configured with at least one accessible DNS server.,(19),1196,NT AUTHORITY\SYSTEM,CU8000000015
09/18/2014 07:32:41,MSSQL$SPSDAG,Information,The Service Broker endpoint is in disabled or stopped state.,(2),9666,,CU8000000015
09/18/2014 07:31:09,PowerShell,Information,Engine state is changed from Available to Stopped. <nl/><nl/>Details: <nl/> NewEngineState=Stopped<nl/> PreviousEngineState=Available<nl/><nl/> SequenceNumber=61464<nl/><nl/> HostName=OpsMgr
PowerShell Host<nl/> HostVersion=7.0.5000.0<nl/> HostId=32012185-8d9a-41c2-be56-91929c02f1e8<nl/> EngineVersion=4.0<nl/> RunspaceId=af176e01-185d-4574-ab9b-0fd745178d29<nl/> PipelineId=<nl/> CommandName=<nl/> CommandType=<nl/> ScriptName=<nl/> CommandPath=<nl/> CommandLine=,(4),403,,CU8000000015
We are not allow to update/write in the DNS for the multisubnet cluster IP registration, so I think that explains the "failed registration" error. But can this explains our time-out errors during the SharePoint installation? For the installation we are connection directly to 1 SQL node and not to the SQL cluster.
Any help is appreciated!
Ronald Bruinsma - Independent SharePoint Consultant - iDocs.info - The Netherlands -- Please don't forget to propose this post as an answer or mark it as helpful if it did help you. Thanks.
↧
↧
automatic failover not working on SQL 2012 Always on
Hello Frenz,
I have a SQL Always on environment with 02 Nodes, the Failover is not happening automatically when one server is down with the following error,
"network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server) (.Net SqlClient Data Provider)"
Kindly someone help.
Note: The Node which is available is in Synchornizing state, but when both the Nodes are available its working fine.
↧
Disaster Recovery ALWAYSON
How do I achieve disaster recovery in the following scenario
WINDOWS 2012
MSSQL 2012 ENT
SiteA win2012wsfc_PROD with 2 nodes with DB1,DB2, here am able to achieve HA
SiteB win2012wsfc_DR with 2 nodes, I need to replicate DB1,DB2 on DR site
Besides Log shipping & SAN based replication, can we achieve this in any other way.
1. In the Availability Group can we configure, SiteB win2012wsfc_DR [ can a node be add in multi cluster]
2. Any other options
Thanks
Cleto
↧
Time-out issue Always on SQL 2012 Cluster
Currently I'm working on a large deployment of a SharePoint 2013 environment (stretched farm over 2 DC's). We are using a SQL 2012 alwayson multisubnet cluster (each DC has 1 SQL node). During the installation of SharePoint we encountered several connection time-out errors from the SQL environment. (Exception calling "Open" with "0" argument(s): "Connection Timeout Expired. The timeout period elapsed during the post-login phase. The connection could have timed out while waiting for server to complete the login process and respond;)
Steps we follow for SharePoint installation are:
Steps to configure SharePoint 2013 on an AlwaysOn Availability group:
1>Create SharePoint databases (with the PowerShell script)
- Configure a SQL alias for a consistent SQL instance name.
- Create farm on SQL instance/replica 1 (one of the SQL nodes), creating all databases needed (service-apps & web-apps). -->
we are connected directly to 1 SQL node and not connecting to the cluster. Installation server is in same DC as the SQL node.
- Stop SharePoint so databases remain static during migration to an AlwaysOn cluster.
2>Move database to AlwaysOn high-availability group.
- Restore all the DBs onto SQL replica 2 (with NORECOVERY).
- Create AlwaysOn availability group, or use existing
- Join the replica 2 databases to availability group.
- Create listener.
3>Migrate SharePoint onto AlwaysOn on cluster
- Make all SharePoint DB MultiSubnetFailover aware with PowerShell Cmdlet
- Reconfigure SQL alias for new listener àat this point the SharePoint farm is connecting to the SQL cluster (listener of AlwaysOn availability group of the SQL Instance), but we never reached this point so far.
- Restart SharePoint services with updated alias.
Event errors and SQL log errors that I found:
Date,Source,Severity,Message,Category,Event,User,Computer
09/18/2014 07:34:59,Microsoft-Windows-FailoverClustering,Error,Cluster network name resource 'SPAG_CU8000001105' failed registration of one or more associated DNS name(s) for the following reason:<nl/>DNS bad key.<nl/>.<nl/><nl/>Ensure
that the network adapters associated with dependent IP address resources are configured with at least one accessible DNS server.,(19),1196,NT AUTHORITY\SYSTEM,CU8000000015
09/18/2014 07:34:59,MSSQL$SPAG,Information,The Service Broker endpoint is in disabled or stopped state.,(2),9666,,CU8000000015
09/18/2014 07:34:52,Microsoft-Windows-FailoverClustering,Error,Cluster network name resource 'SPWMAG_CU8000002105' failed registration of one or more associated DNS name(s) for the following reason:<nl/>DNS bad key.<nl/>.<nl/><nl/>Ensure
that the network adapters associated with dependent IP address resources are configured with at least one accessible DNS server.,(19),1196,NT AUTHORITY\SYSTEM,CU8000000015
09/18/2014 07:34:52,MSSQL$SPWMAG,Information,The Service Broker endpoint is in disabled or stopped state.,(2),9666,,CU8000000015
09/18/2014 07:34:47,Service Control Manager,Information,The WMI Performance Adapter service entered the running state.,(0),7036,,CU8000000015
09/18/2014 07:32:41,Microsoft-Windows-FailoverClustering,Error,Cluster network name resource 'SPSDAG_CU8000003105' failed registration of one or more associated DNS name(s) for the following reason:<nl/>DNS bad key.<nl/>.<nl/><nl/>Ensure
that the network adapters associated with dependent IP address resources are configured with at least one accessible DNS server.,(19),1196,NT AUTHORITY\SYSTEM,CU8000000015
09/18/2014 07:32:41,MSSQL$SPSDAG,Information,The Service Broker endpoint is in disabled or stopped state.,(2),9666,,CU8000000015
09/18/2014 07:31:09,PowerShell,Information,Engine state is changed from Available to Stopped. <nl/><nl/>Details: <nl/> NewEngineState=Stopped<nl/> PreviousEngineState=Available<nl/><nl/> SequenceNumber=61464<nl/><nl/> HostName=OpsMgr
PowerShell Host<nl/> HostVersion=7.0.5000.0<nl/> HostId=32012185-8d9a-41c2-be56-91929c02f1e8<nl/> EngineVersion=4.0<nl/> RunspaceId=af176e01-185d-4574-ab9b-0fd745178d29<nl/> PipelineId=<nl/> CommandName=<nl/> CommandType=<nl/> ScriptName=<nl/> CommandPath=<nl/> CommandLine=,(4),403,,CU8000000015
We are not allow to update/write in the DNS for the multisubnet cluster IP registration, so I think that explains the "failed registration" error. But can this explains our time-out errors during the SharePoint installation? For the installation we are connection directly to 1 SQL node and not to the SQL cluster.
Any help is appreciated!
Ronald Bruinsma - Independent SharePoint Consultant - iDocs.info - The Netherlands -- Please don't forget to propose this post as an answer or mark it as helpful if it did help you. Thanks.
↧
Always on Database is in Reverting / In recovery mode after failback from 1 replica to other replica
We have Always on set up and I have failback replica from one to other and after that status of Database is in Reverting / In recovery mode. Is there any way to bring db online?
Rahul
↧
↧
Server Requirements - Always On in a single server? - Needs clustering even one server on another Data Center?
Hello:
I have been asking this questions to different forums and got different responses, so I wanted to know if asking to "Microsoft" will give me some good directions. (All in SQL Server 2012, including the OS)
Question 1.- Always On "HAS" to be configured on a WSFC node? How about in a Single SQL Server. (NO Clustering)?.
Question 2.- What about our mirroring processes configured and running in single servers, do we have to have WSFC installed before we can upgrade them to Always On?.
Question 3.- In a case I have WSFC, and configure Always On, can my second or third replica reside in a single SQL Server? (No WSFC). What if I can not have Clustering in a DR Data Center? or I do have only VM's on the DR Center?
Any help will be greatly appreciated.
Thanks
Oscar Campanini
↧
Seeing error 1196 in system event log referencing the availability group name (not the listener name)
We successfully created an availability group with a listener and tested multiple failovers and everything is working fine however in the windows system event log we see entries for error 1196 referencing the availability group name (not the listener name).
Any suggestions?
Laura
↧
SQL2012 System Databases Restore on a different environment
So While I was playing around I wondered if it was possible for me to setup a similar version of SQL 2012 on a different environment and restore it quickly.
Master Env
SQL 2012 - 3 databases , 2 SSIS packages , 2 Sql Agent jobs and 1 report.
The idea would be to copy this on another Server altogether.
Slave Env
So the first thing I thought was the system database should go across before all else. Now it states that both versions have to be the same which I confirmed using;
Use Master
Go
SELECT
SERVERPROPERTY
('ProductVersion ')ASProductVersion,
SERVERPROPERTY
('ProductLevel')ASProductLevel,
SERVERPROPERTY
('ResourceVersion')ASResourceVersion,
SERVERPROPERTY
('ResourceLastUpdateDateTime')ASResourceLastUpdateDateTime,
SERVERPROPERTY
('Collation')ASCollation;
Both showing the same. Having backed up both system databases on both sides the restoring of the model and msdb databases where straight forward.
The master was a different ball game and is one I still cant get past
1. Stopped the SQL SERVER on the Slave Env
2. Open Command shell
3. Net Start MSSQLServer /m”SQLCMD”
4. sqlcmd -S. -E
5. RESTORE DATABASE master FROM DISK = 'D:\SQL\Backups\master.bak' WITH REPLACE
Go
what this will do is restore the master database from the live to the slave and this is where the problems begin because once you do that restart the SQL server and get out of single user mode you cant logon .
Question
Assuming the Master has different windows logons to the Slave is there any way once this restore has been done to negate this or do you create a user straight after the restore?
Also with ReportingServices and Integrated Services are they straight forward Db restores ?
Any Help one this would be great!!
As I really want to know how quickly I can jump from one environment to another.
↧
How to sync logins and passwords between the instances in Always ON availability groups
We have a 3 node cluster with Node 1 being Primary, Node 2 being secondary and Node 3 is DR as well as read-only secondary. If Node 1 is having issues then we will switch the primary to any other node.
We have a process to copy logins between all 3 instances using SQL agent job. This process use sp_help_revlogin to copy all the logins from primary at a given point in time. This will not help if instance is failed over to node 2 or 3 before this job runs.
If some one changes the password in primary and when the instance is failed over to node 2 or 3, they will not be able to connect because the password is not replicated.
Can some one suggest a way to replicate the changes to logins to other secondary instances in availability groups?
Thanks in advance.
↧
↧
Always-On Node2 Server performace is very slow
I have two node Always-On Configured (sync & Automatic) SQL serves. Node 1 Performance is very good however as soon as failover happens on Node 2 the performace becomes very slow.
Both the server configurations are same.What could be the reason for degradation of the performance of the server?
Thanks!!
↧
What is HADR SEEDING TEST database in High availability server?
Hi All,
Our servers belongs to HA. Now, we could see a db like "HADR SEEDING TEST" has been created in our server.We don't know when was it created. How is it getting created and what is it? Will it make any error if we drop this db?
Thanks,
Julie
↧
log file space is not getting freed up even after log backup happened in log shipping
Log shipping is configured in my environment & sec. db is in restoring mode.
There is one db issue whose log space is not free even after log backup. everything is OK. log backup is also happend at regular interval & log is also applied on sec databases. then why log size of database on PROD is remain same as it cause a issue, when i checked in sys.databases then log_reuse_wait _desc column shows "replication" but replication is not configured.
I fired checkpoint also but no luck.
what is the reason why log is not getting freed.
↧
SQL cluster - all nodes in same subnet - intermittent connectivity issues
I have a handful of 2 node SQL 2008 R2 clusters. The nodes and cluster IP addresses all reside in the same subnet. Periodically we have issues where the active node in of one cluster cannot ping the active node of another cluster and cannot ping the cluster IP; but can ping the standby node IP. For example, NODE_A1, NODE_A2 are in CLUSTER_A; suppose NODE_A2 is active. NODE_B1 is the active node in CLUSTER_B; it can ping NODE_A1, but not the active NODE_A2 and not CLUSTER_A. By clearing the ARP table on NODE_B1 sometimes the ping responds to NODE_A2 and CLUSTER_A will be restored, but only temporarily. All these devices are connected to the same physical network switch.
I was wondering if having all the IP's, which can have the same MAC addresses behind them, on the same subnet may be causing issues with MAC tables not updating in a timely fashion? Is it considered a best practice to use different subnets? I'm more experienced with Exchange clusters where a dedicated heartbeat subnet is used for server to server communication, and the cluster IP would be on a different and user accessible subnet.
↧
↧
Consider costs when implementing SQL server cluster.
Hi,
I had this question on an interview and i would like to have your opinion.
When designing a cluster environment (Windows cluster i.c.m with SQL cluster). It is never Available/Available but Available/Not Available.
How can i work cost effective and use the unavailable node. So this machine doesn't do nothing. Without performance degredation?
Maybe use 2012 "Always on availability"?
Are there any other answers?
Kind regards,
Andre
↧
SQL Server DTS packages migration
How to move DTS packages from SQL Server 2000 to SQL server 2008 version
can you plz provide me step by step procedure
if i migrated DTS packages by using of save as option what will happen, is it working properly
and i had migrated DTS packages from sql 2000 to sql 2008 version but while i'm click to open the DTS i got below error
ERROR:Managing DTS packages in SQL Server Management Studio requires the SQL Server 2000 Data Transformation Services (DTS) runtime. To install the DTS runtime, on your SQL Server 2008 R2 installation media, locate and run the Windows Installer package for SQL Server 2005 Backward Compatibility (SQLServer2005_BC*.msi). You can also download the DTS runtime from the SQL Server Feature Pack page on the Microsoft Download Center. (Microsoft.SqlServer.DtsObjectExplorerUI)
Kamal
↧
Always On - async mode - Failover and failback check list
Hi All,
Our production is configured with Always On in Async mode with DR.
We are planning to do a failover and failback on the Availability Groups in weekend.
Apart from the time consuming to do a failover and failback, does anyone having complete checklist on what all has to be checked at the time of failover and failback?
Thanks in advance!
↧