Quantcast
Channel: SQL Server High Availability and Disaster Recovery forum
Viewing all 4532 articles
Browse latest View live

Can't remove IP?!?!? What the ..

$
0
0
Hi,

I am using SQL2014 with HA/AG groups and was adding an extra listener when I used the incorrect IP address. 

I had thought the 'remove' button would work, but it does not. Also I tried deleting it manually:

[quote]
delete from sys.availability_group_listener_ip_addresses where listener_id = '26d37cdb-5a6f-43a0-ab0c-f4343eeac0f2' 

delete from sys.availability_group_listeners where group_id = '6B060505-CDDC-44B6-A9AD-38FC6AD4A7AA'[/quote]

Ad hoc updates to system catalogs are not allowed.

I attached an image.

How can I remove the invalid IP?

qeqw


SQL Always On Backups

$
0
0

Hi,

SQL Always On

Backups taken on a replicas will not show up in the MSDB database backup tables of the primary server (or other replicas), as they don’t share an MSDB database.

Then where can i find the backup/SQL Jobs and so on information?

Mixing SQL2008R2 and SQL2012

$
0
0

Hello!!

I have a cluster environment two nodes windows 2008 R2 Enterprise, with 4 instances  SQL2008R2, my question is can I install one instance more of SQL2012 ?..thanks a lot

SQL 2008R2 Failover Cluster without File Share

$
0
0

We are looking to set up a failover cluster for our SQL 2008R2 database. To accomplish this, we have 2 servers, both equipped with Fusion I/O cards that will both have identical copies of our production databases on them.

From everything I've read, we're supposed to set the servers up so they are both pulling the databases from a shared file storage of some sort. We intended to have both servers simply run the databases from their respective Fusion I/O cards rather than from a file share.

Clustering seems to be the correct choice for a high availability SQL setup, given the "LooksAlive" and "isAlive" checks it makes, but if the shared storage is a requirement, we may need to consider an alternative solution.

Given that we only really need the HeartBeat network functionality and don't need any shared storage, can we still use a Failover Cluster for SQL?

Replication Validation is being failed on AlwaysOn

$
0
0

Hi All,

When executed below query on distribution database receiving 2nd below error. Please suggest if you faced same kind of issue.

----------

USE distribution;

GO

DECLARE @redirected_publisher sysname;

EXEC sys.sp_validate_replica_hosts_as_publishers

@original_publisher = 'VLDBATEAM',

@publisher_db = 'TD_AO11',

@redirected_publisher = 'RIMDNS';

---------

OLE DB provider "SQLNCLI11" for linked server "[EBD1AA94-995E-4C5C-888F-39119E0B39C9]" returned message "Login timeout expired".
OLE DB provider "SQLNCLI11" for linked server "[EBD1AA94-995E-4C5C-888F-39119E0B39C9]" returned message "A network-related or instance-specific error has occurred while establishing a connection to SQL Server. Server is not found or not accessible. Check if instance name is correct and if SQL Server is configured to allow remote connections. For more information see SQL Server Books Online.".
Msg 21892, Level 16, State 1, Procedure sp_hadr_validate_replica_hosts_as_publishers, Line 60
Unable to query sys.availability_replicas at the availability group primary associated with virtual network name 'RIMDNS' for the server names of the member replicas: error = 2, error message = Error 2, Level 16, State 1, Message: Named Pipes Provider: Could not open a connection to SQL Server [2]. .',

Please let me know if you want me to share any more details on this issue.


Grateful to your time and support. Regards, Shiva

SQL Server Log Shipping 14420, 14421 False Error Message

$
0
0
I have set up log shipping on a SQL 2014 server to copy data from a primary to a secondary server. This is all working correctly backing up, copying and restoring however the alerting which is configured to run to the secondary server is reporting that the last backup time is the time of the initial backup full before log shipping starts. This is the information that is reported when I query the msdb.dbo.log_shipping_monitor_primary table. Consequently when the monitoring alert runs, it reports:


Msg 14420, Level 16, State 1, Procedure sp_check_log_shipping_monitor_alert, Line 61
The log shipping primary database XXXXXXX.xxxxxxx has backup threshold of 60 minutes and has not performed a backup log operation for 1120 minutes. Check agent log and logshipping monitor information.


SQL server was originally installed before the server was renamed to its current name however I have renamed the instance and all queries of the database (e.g. SELECT @@SERVERNAME) return the correct servername.

Not able to Failover AG

$
0
0

Hi All,

Could not able to connect secondary replica below is the error message I am getting when I tried to failover. Please suggest

TITLE: Connect to Server
------------------------------

Cannot connect to VLDBATEAM.

------------------------------
ADDITIONAL INFORMATION:

The secondary replica that you selected to become the new primary replica does not belong to the specified availability group. A possible explanation is that the replica has not been joined the availability group.  (Microsoft.SqlServer.Management.HadrTasks)

------------------------------
BUTTONS:

OK
------------------------------



Grateful to your time and support. Regards, Shiva

Compatible Development Platforms?

$
0
0

As understood, AlwaysOn Availability Groups supports multi-subnet failover as long as the application in question supports:
SQL Native Client 11.0 ODBC
ADO.NET with .NET Framework 4.0 (Update 4.0.3)
Microsoft JDBC driver 4.0 for SQL Server
and the app was developed on:
.Net 3.5 SP1 or higher
(resourse = http://www.mattmasson.com/2012/03/alwayson-multi-subnet-failover-and-ssis/)
This particular article has been a valuable resource for testing databases and their new or old supporting apps.
I've devised a comfortable mix of "supported" & "unsupported" listeners, depending on whether apps were created
on platforms that support "multi-subnet failover = true".

I have one app that was developed on Microsoft Dynamics NAV 2009 SP1.
I haven't found any articles that mention the Microsoft Dynamics NAV 2009 SP1 platform and AOAG in the same sentence.
I guessing that it doesn't support multi-subnet failover ?


JDA


Find errors in AlwaysOn synching

$
0
0

Hi folks,

We've just started using AlwaysOn High Availability and run into a wierd issue. I have 1 particular database that is not syncing data to the secondary replica. But when i look at all the dashboards, everything is green, they all say synchronised - but if I query the data they are not.

The database has additional sql transactional 1 way replication a different server which i was wondering if was causing any problems, but it's working ok,

I'm just wondering if there's any other more detailed logs i can check to see why the data is not flowing. The availability dashboard and it's event log all says ok.

Thanks

Merge Replication in AlwayOn

$
0
0

Hi All,

Merge replication on AlwayOn is configured, working fine on Original Publisher.

When failover to possible publisher data is not being replicated.

Replication Monitor Error:

Message: Validation failed for the publisher 'RIMDNS' with error 21879 severity 16 message 'Unable to query the redirected server 'RIMDNS' for original publisher 'UNITEDKINGDOM' and publisher database 'TD_AO11' to determine the name of the remote server; Error 2, Error message 'Error 2, Level 16, State 1, Message: Named Pipes Provider: Could not open a connection to SQL Server [2]. '.  '.
Stack:    at Microsoft.SqlServer.Replication.SnapshotGenerationAgent.GetHadrRedirectedPublisherProcessResult(SqlDataReader dataReader)
   at Microsoft.SqlServer.Replication.AgentCore.ExecuteWithOptionalResults(CommandSetupDelegate commandSetupDelegate, ProcessResultsDelegate processResultsDelegate, Int32 queryTimeout, CommandBehavior commandBehavior)
   at Microsoft.SqlServer.Replication.AgentCore.ExecuteWithOptionalResults(CommandSetupDelegate commandSetupDelegate, ProcessResultsDelegate processResultsDelegate)
   at Microsoft.SqlServer.Replication.SnapshotGenerationAgent.GetHadrRedirectedPublisher()
   at Microsoft.SqlServer.Replication.SnapshotGenerationAgent.InternalRun()
   at Microsoft.SqlServer.Replication.AgentCore.Run() (Source: MSSQL_REPL, Error number: MSSQL_REPL54172)

Please Suggest.


Grateful to your time and support. Regards, Shiva

SQL Server 2012, SSMS won't show bak files or even folders, using enterprise admin account?

$
0
0

I'm working on a newly installed windows 2012 R2 server which has SQL Server 2012 and SSMS installed on it. What has been odd is that when I open the "restore database" dialog, in the "Select Backup Devices", "Locate Backup File" dialog, only the immediate folders off of the root of the E: drive are visible. E: is where sql server data and backup files are stored.

The account I am logged in with is supposed to have Enterprise Admin rights. How is can I not see these folders and files? The files are certainly there and are visible to me on that login with windows explorer. I am able to backup via SSMS without issue. When I look at the folder's permissions everything seems normal. If I add "Everyone" to that folder's permissions the folders and files become visible. The SQL Server service is running on the NT Service\MSSQLSERVER account, which is normal for my other installations of sql server. Can anyone suggest what the issue is?

AlwaysOn Availability Groups - Downlod hotfixes

$
0
0

Friend

    I'm doing a certification process using AlwaysOn, and was using the link below, and on the lower 90 hotfix, and instead of downloading one by one, and then upgrade one by one updates, is there any way to make it more faster or practical, or unfortunately have to do this one by one, so the download as the update?


  This rollup contains the latest version of the Windows system files that are updated after the release of SP1.
  Hotfixes that are included in this update rollup

https://support.microsoft.com/pt-br/kb/2775511

           

"Select backup devices" hangs after clicking Add button

$
0
0

I'm trying to restore a database using SSMS GUI. In "Select backup devices" window if I click the Add button there the window and the whole process hangs like it will never work.

I tried to clear backup history, but that didn't solve it.

I tried with a couple of other databases, but same thing.

It was working fine!

Any advice please!

Log Shipping - Log file truncation

$
0
0

Hello,

I have log shipping setting up on my production going to my DR server with every 15 min of Tlog backup , but after doing some online searches about this I still cannot figure out why the transaction log file of the database does not reduce\truncate? It keeps growing. I made sure there are no active or open transactions. Is there any way to check the transactions open during the tlog backup happend? But still the log file is 70gb and does not truncate after the 15 min log backups..

I did a lot of searching about this, but could not find a solution, please help me on this.

Thanks

AJ

add more datafile to Log Shipping, Mirroring, Always on

$
0
0

Hi export ,

can you explain what will happen to secondary nodes if you add a data file to primary server

1. for log shipping /mirroring / Transactional

environment 1

folders, mount points location are both identical in both nodes

Environment 2

folders, mount points location are both NOT identical in both nodes. different locations.

2. How does it happen to Always On environment.

can any one help me or send me  important Tech notes for this.

thanks

Ashwan


Undo an applied transaction log ?

$
0
0

USE [master]
RESTORE DATABASE [EmployeeRecovered] FROM  DISK = N'D:\Backups\Normal\EmployeeFULL.BAK' WITH  FILE = 1,  
MOVE N'Employee' TO N'D:\MSSQL\DATA\EmployeeRecovered1.mdf',  
MOVE N'Employee_log' TO N'D:\MSSQL\LOG\EmployeeRecovered1_log.ldf',  
NOUNLOAD,  STATS = 5, NORECOVERY
GO

RESTORE LOG [EmployeeRecovered] FROM  DISK = N'D:\Backups\Normal\TranBackup1.trn' WITH  FILE = 1,  STANDBY = N'D:\Backups\Normal\EmployeeStandby.BAK',  NOUNLOAD,  STATS = 10
GO

RESTORE LOG [EmployeeRecovered] FROM  DISK = N'D:\Backups\Normal\TranBackup2.trn' WITH  FILE = 1,  STANDBY = N'D:\Backups\Normal\EmployeeStandby.BAK',  NOUNLOAD,  STATS = 10
GO

now I realze the recovery point is somewhere in TranBackup2.trn and need to go back to the state where only TranBackup1.trn is applied.

How can i do this ?


SQL Server evaluation edition

$
0
0

Experts,

What I understand is that there is a restriction of upgrading a SQL server 2012 cluster from evaluation edition to licensed standard editon.

Is there a similar limiation for upgrade from evaluation editon to licensed enterprise edition. Is no , can you please provide a link for the upgrade process.


Installtion & Configuration

$
0
0

Hello Experts,

I am about to install a new failover SQL-Server environment (win 2012 \SQL 2008 Sp4) and after going to installation we found out that storage designed to map to over the number of drive letter alphabetic and was looking for your experience for which is more practical and best practice to follow , follow MS advised in this article  https://support.microsoft.com/en-us/kb/947021?wa=wsignin1.0 or go with the straightforward scenario and adjust the storage design to be less than number of alphabetic  characters.

Thanks 

AlwaysOn Estimated Recovery Time (seconds)

$
0
0

Hi All,

Estimated Recovery Time (seconds) is not matching with actual fail-over recovery time. Is the two process different? Normal Redo catch-up and during a time of failover recovery?

Estimated Recovery Time (seconds)  -> 7000
Redo Queue Size -> 12 GB
Normal Redo Catch-up -> 2-3 hours
Manual Failover Redo Catch-up -> 2-3 minutes and database was online and accessible

We saw this behavior in non-prod VM machines and identified the process and fixed it which was generating huge REDO. But the recovery time number (7000 seconds) was a concern if we get such a real time scenario in production. So we tried a manual fail-over repro-ing the REDO scenario, but the secondary came online Synchronized and was accessible within 2-3 minutes.

Thanks,

-SreejitG

Availability Group Listener - Targeting Incorrect Node

$
0
0

Hi Guys,

We have a multi-subnet cluster and trying to add a listener but the following error keeps popping up:

Msg 19456, Level 16, State 0, Line 1

None of the IP addresses configured for the availability group listener can be hosted by the server 'XXXXXXXX'

The cluster node referenced in the error is not an owner for any of the IP address ranges selected for the listener. How can I prevent the creation of the listener from targeting this new server? This node was recently joined to the cluster. Validation of the cluster is fine.

Any ideas where to look?

Viewing all 4532 articles
Browse latest View live