hi all ,
i have created SQL 2014 cluster using CSV and i am trying to to backup and restore for the database to the new SQL Server and i am facing the below error :
any idea ?
↧
Restore Database Error
↧
SQL Alert 1480 Not firing for a Particular database
All,
I set up an Alert for Message Id 19406 to be alerted whenever the Failover/FailBack on our AAG happens. I also setup an Alert for Message ID 1480 when a particular database's role changes. I need this Alert to work since I have to enable TRUSTWORTHY on some of the databases that are on the nodes (Secondary when the Failover happens and Primary when the Failback happens). I created this Alert by selecting the Database Name while configuring the Alert.
The Alert for MessageID 19406 fires as expected and we get a total of 12 alerts (per Failover & Failback). Unfortunately, the alert for Message ID 1480 does not seem to happen for the particular database. Instead I get one email for every database in the AAG.
I'm not sure if this is how it is supposed to work. I cannot even specify the database name in the Message Text area since I have more than one database for which I need to change the TRUSTWORTHY setting. I was hoping to run a Job via the Alert to enable the TRUSTWORTHY setting.
Please kindly share your experiences!!
Thanks.
rgn
USE [msdb] GO EXEC msdb.dbo.sp_update_alert @name=N'AvailabilityGroupRoleChange-1480', @message_id=1480, @severity=0, @enabled=0, @delay_between_responses=0, @include_event_description_in=1, @database_name=N'NorthWind', @notification_message=N'Database Role Changed', @event_description_keyword=N'', @performance_condition=N'', @wmi_namespace=N'', @wmi_query=N'', @job_id=N'00000000-0000-0000-0000-000000000000' GO EXEC msdb.dbo.sp_update_notification @alert_name=N'AvailabilityGroupRoleChange-1480', @operator_name=N'DBAsGroup', @notification_method = 1 GO EXEC msdb.dbo.sp_update_alert @name=N'AAG-StateChange-19406', @message_id=19406, @severity=0, @enabled=1, @delay_between_responses=0, @include_event_description_in=1, @database_name=N'', @notification_message=N'State of the AAG Changed. Failover/Failback is currently in progress', @event_description_keyword=N'', @performance_condition=N'', @wmi_namespace=N'', @wmi_query=N'', @job_id=N'00000000-0000-0000-0000-000000000000' GO EXEC msdb.dbo.sp_update_notification @alert_name=N'AAG-StateChange-19406', @operator_name=N'DBAsGroup', @notification_method = 1 GO
↧
↧
What else need I in order to test Always On??
Hi all of you,
My goal is simple: test Always On features in my test environment...
I've tried in my Sql Server 2012 running in my Windows 7 Ultimate Pro OS unsuccessfully.
Now, after being featured a full Windows Server 2012 DataCenter 180 days trial period (DC, DNS, DHCP and son) and having installed Sql Server 2016 CTP3 I receive this message:..
Any input would be greatly appreciated!!
↧
Windows Server Failover Cluster, failover cluster instances and Always On HA, in a nutshell: everything
Hi all of you,
My goal is trying to grasp all the knowledge as well as all the ins and outs behind one Always On HA along with Failover Cluster Instances atmosphere. At home.
Before proceeding, could you please be so kind to tell me if I've got all the pieces needed for that??
- Machine 1 (Architecture: x64.). It runs Windows 7 Ultimate Pro OS and runs 4 instances: Sql2k8Express, Sql2k8 R2 and Sql2k12 (Enterprise Evaluation 180 day, solid state disk, 16 Gb RAM and so on, good one. This machine runs a Domain Controller based on Windows Server 2012 DataCenter Evaluation 180 days in my VM VirtualBox platform along with one Sql2k16 CTP3 Evaluation Edition.
- Machine 2 (MacBook), up to the moment only using NAT internet connection for consuming internet data. This one goes on your own way. In a future I would like to attach to my virtualized Windows Server 2012 domain controller. No worries up to the moment.
- Machine 3 (Architecture x32). It does runs Windows 7 Ultimate Pro OS connected beatifully to the former virtualized 2012 domain controller. Runs a couple of Sql instances, Sql2k8 and Sql2k5.
- Machine 4 (Architecture x64), runs a Windows 7 Pro, no Sql Server instances installed, only MongoDb server.
Having in mind the aforementioned facts, can I deploy one Failover Cluster Instance from Machine 1 (VirtualBox one) adding as second node, Machine 3?
Must be a 2008/2012 server? I mean, the second node.
I don't know if I've been sufficiently clear on my request, let me know…
Thanks in advance for any input/advices provided
↧
AlwaysOn issues with System Policies and Replica States
Hi all,
When testing the system policies, some of them fail on the secondary but all succeed on the primary. EG AlwaysOnAgReplicasConnectionHealthPolicy is one that fails. The dashboard shows no errors on Primary or Secondary. If I failover, the new secondary fails the same policies but the new primary is fine and all succeed.
The system fails over and back - manually and automatically - all fine.
I'm wondering if the policies are meant to be evaluated on the secondary?
The other "anomaly" is that the Primary replica has a role of "unknown" when looking at SSMS on the Secondary. Again this reverses after failover.
Am hoping that either this is expected behaviour or someone can help me understand what's wrong. Thanks in advance.
Paul
↧
↧
Migrating an Existing Availability group to a new datacenter Availabitiy group
need to migrate a cluster with an AG dtabases to new data center cluster with AG.
I was wondering if is possible to do mirroring on top of the AG configuration? or what other options could be to migrate a cluster that has 3 nodes and setup the ag databases to a new datacenter.
↧
SQL 2012 - FCI number of cluster nodes supported for edition failed
Hi,
I have encountered issue by add a node to SQL cluster
Server 2012 R2 Datacenter version
SQL 2012 Enterprise edition
Error Status>
number of cluster nodes supported for edition - failed
I have failed to bypass with Setup /SkipRules=Cluster_VerifyForErrors /Action=AddNode
↧
backup and restore at the same time
SQL Server 2008 R2
i don't see a "general discussion" thread and this is the closest i think.
i just have a general question: if my backup window is from 8am to 10am, and i do a restore within that backup window, what will happen? assuming we're talking only of a single database, ACME.
i'm comparing because with Oracle RMAN, it pukes when i do a restore while the backup is going on. it would complain of unable to find some archive logs.
↧
Log shipping from a 2008 r2 SP2 server to a 2008 r2 SP3 CLUSTER
Hello guys,
We have recently configured one database to be replicated with log shipping in production, using SQL Server 2008 R2.
We have up and running more than 150 database replicas without any problems. But now, when we try to configure the new replica in a new server environment we have experiencing one error:
The log shipping is configured from a 2008 r2 SP2 server to a 2008 r2 SP3CLUSTER (the only difference compared with our other replicas)
1 – the LS backup works Ok in the primary
2 – the LS Copy works OK and successfully copy the files from the primary to the secondary
3 – the LS Restore restores one, two or three trn files, and than it fails:
Restored log backup file. Secondary DB: 'xxxyyyy _mirror', File: 'P:\ xxxyyyy _TLogs_Mirror_LS\xxxyyyy\ xxxyyyy _20151120163351.trn'
The restore operation was successful. Secondary Database: ' xxxyyyy _mirror', Number of log backup files restored: 1
The next job execution:
*** Error: An error occurred while processing the log for database ' xxxyyyy _mirror'. If possible, restore from backup. If a backup is not available, it might be necessary to rebuild the log.
RESTORE LOG is terminating abnormally.
Processed 0 pages for database xxxyyyy _mirror', file 'Vitacare2k6_Dev' on file 1.
Processed 1 pages for database ' xxxyyyy _mirror', file 'Vitacare2k6_Dev_log' on file 1.(.Net SqlClient Data Provider) ***
And the the database gets Suspect.
4 – the files (MDFs, LDFs and TRNs) are in an Clustered Disk shared by the cluster nodes.
5 - I tried to restore the TRNs in the same full backup from the cluster my PC and I get no errors.
Can you guys provide me any guidance on where I could troubleshoot this further, I would greatly appreciate it.
Thanks for your time and input.
Rafael
-----------------------
↧
↧
Cross-Cluster migration of alwayson availability groups issue from Windows 2008 to 2012
Hello team,
We are using attached white paper document for cross cluster always on availability group migration (HERE) and testing the suggested set of steps in our environment which is four node (Lets say Nodes 1, 2, 3, 4) windows 2008 cluster environment and as per requirement we have created another new destination windows 2012 cluster which is also having four nodes (Nodes 5, 6, 7, 8) .
Configuration of Source and Destination
WSFC cluster | Windows | SQL Server |
Source cluster | Windows Server 2008 R2 Enterprise. | SQL Server 2012 RTM (Enterprise) |
Destination cluster | Windows Server 2012 R2 Datacenter. | SQL Server 2012 SP1 (Enterprise) |
As per document we have executed below steps
- Creatednew testAG on primary replica (Node 1) in windows 2008 cluster environment and added test database to that AG with 1 secondary replica (Node 2 with synchronous commit). So there are two replicas in TestAG now (Node 1 & 2)
- Changed the HADR ClusterContext to windows 2008 cluster for Node 5 & 6 of destination cluster (Windows 2012 cluster).
- Added node 5 & 6 as secondary replicas of TestAG. Node 5 has been configured as synchronous commit replica whereas an asynchronous commit for node 6
- Then deleted the listener and set the TestAG to OFFLINE
- We tried to create new AG with same name on destination cluster node 5 but we were unable to add the test database (already synchronized ) to this new TestAG as that database is in restoring mode (so not accessible to add in AG)
As per my understanding we have followed all the steps in same fashion in which it has been described in the white paper. We require your kind support in removing this hurdle or you can advise any alternate method by which we can migrate our database between these two hardware set with minimum downtime.
Thanks a lot
↧
Always On Virtual Labs
Getting below error while working on Microsoft Virtual Lab:
https://technet.microsoft.com/en-us/virtuallabs
System Name : SQL Two
"unable to save the alwayson high availability settings return code 0x80070046"
Getting above error while enabling Always on Availability group from SQL Server Configuration Manager.
↧
unable to see the database disk to add as server name dependencies
hi all
i have create sql cluster and i need to add the Database disk as dependencies of cluster resource Server Name and i am not able to see the disk
any suggestion
↧
Always on - Changing shared folder
Hi
I've created always on between 2 servers, during initial setup it was required to have a shared network folder for always on .
Now I got request for removing existing file system and to create a new one. I need to do changes in sql server to point to new folder but not sure its impact on services and how/where to assign new shared folder
Thanks
DBA
↧
↧
SQL Server 2008R2 Cluster Standard Edition REPORTING SERVICES
Hi Team,
We are aware the Reporting Services is not a cluster aware and will not work in PASSIVE node of SQLSERVER 2008R2 STANDARD EDITION Active/Passive Cluster.
To avoid the ENTERPRISE EDITION COST, I tried to find workaround with STANDARD Edition so that we can also use the Reports in PASSIVE node (IN CASE OF ACTIVE NODE IS DOWN or FAILOVER to PASSIVE node.)
Steps configured to Access Reports from Passive Node(Standard Edition)
Prerequisite: Install SQL Standard Edition Named Instance(SQLBNamed) on the Passive node.
INCASE OF Failover from Active to Passive Node:
1) Open Reporting Services configuration Manager in Passive Node and Connect NamedInstance(SQLBNamed).
2) Configure the Web Service URL Virtual Directory toReportServer (This is same as ActiveNode URL) and Add the SQLServerVirtualIP in Advanced Report Server WebService Site identification.
3) Configure the Report Server Database with Existing Report server database of Default Instance(SQLVirtualIP).
4) Configure the Report Manager URL Virtual Directory asReports (This is same as ActiveNode URL) and Add the SQLServerVirtualIP in Advance Report Manager Site identification.
5) Restore the Encryption Key of Active Node.
6) Connect SSMS with SQL Virtual IP and Delete the Active Node reference from SQL Server ReportServer Database. Query Listed Below:
Use ReportServer
go
Delete from ReportServer.dbo.keys where MachineName = 'SQL-A'
-- SQL-A here is Active Node.
8) Browse the Reports using same Virtual IP (http://SQLVirtualIP/Reports).
9) Take The Encryption Key backup if Failback is planned.
INCASE of Failback from Passive Node to Active
1) Open Reporting Services configuration Manager in Active Node and Connect Default Instance.
2) Restore the Encryption Key of Passive Node.
3) Connect SSMS with SQL Virtual IP and Delete the Passive Node reference from SQL Server ReportServer Database. Query Listed Below:
4) Delete the Passive Node reference from SQL Virtual IP. Query Listed Below:
Use ReportServer
go
Delete from ReportServer.dbo.keys where MachineName = 'SQL-B'
-- SQL-B here is PassiveNode.
5) Browse the Reports using same Virtual IP (http://SQLVirtualIP/Reports).
6) Take The Encryption Key backup if Failover is planned.
Please provide your opinion if the above solution is supported by MS.
Regards
↧
HA with multiple subnet cluster
Hi,
I have two nodes in the cluster the network for both are 192.168.1.0/24 and 192.168.2.0./24. And the server's IP 192.168.1.2 and 192.168.2.2.
When I finished creating cluster for both nodes the wizard told me I have two IPs I can use for failover which I set to 192.168.1.250 and 192.168.2.250 because they both in different networks.
Both nodes are set to be able to write and read. The question is which IP should I use to access the cluster? Because I've tried to use one of them but when the cluster change node, the IP is unreachable which I believe because the current active node were changed.
Or my cluster configuration is wrong?
Thanks in advance.
↧
Cluster Validation - Unsigned Drivers for all Microsoft Drivers
Hi,
I configured failover cluster on 2 nodes. when i ran validation test, it showed warning that there are unsigned drivers. These drivers are all supposedly signed by Microsoft.
It seems like it is just missing a validation cert from Microsoft but i compared it to another cluster that doesn't have these warnings, and the certs were the same.
Any other clue what is causing this? I ran sigverif and nothing returned unsigned.
Thanks, LJ
↧
Delay in Data synchronizing to secondary replica in AlwaysOn
Hi,
I have configured SQL Server 2014 AlwaysOn setup in Asynchronous mode for database having 1.5 TB size.
After some time i found that there is 4 hrs delay in data between primary and secondary replica located across data center.
I checked in AlwaysOn DashBoard on primary replica, it is showing following information :-
Estimated Data Loss (Time) = 03:04 hrs
Log Send Queue Size (KB) = 71275013
Log Sent Rate (KB/Sec) = 4658
So Data sync delay is due to log is not transferring to secondary replica with sufficient rate.
Can anyone help me to figure out exact reason of low log sent rate ?
Mark As Answer If My Reply Is Helpful<br/> Thanks<br/> Neeraj Bhandari (MCTS - Sql Server 2008)
↧
↧
How to create multiple availability groups with same listener in SQL Always on??
Hi Friends,
Recently we configured always on and created availability group with listener. Now i want to create two more availability groups with same listener.
Please let me know is there any way to create multiple availability groups with single listener??
Thanks,
Hari
↧
Always on Failed Primary role changed to Resolving
Guys I have an issue in always on.
I got an alert like
The lease between availability group 'AG_NAME' and the Windows Server Failover Cluster has expired. A connectivity issue occurred between the instance of SQL Server and the Windows Server Failover Cluster. To determine whether the availability group is failing
over correctly, check the corresponding availability group resource in the Windows Server Failover Cluster.
Then another alert like
DESCRIPTION: The availability group database "Database_Name" is changing roles from "PRIMARY" to "RESOLVING" because the mirroring session or availability group failed over due to role synchronization. This is an informational
message only. No user action is required.
Please I need the RCA of this problem.
Note : I don't have automatic failover.
↧
SQL Server 2008 R2 Log Shipping
HI All,
WE have configured Log Shipping on our SQL Server 2008 R2 server from PR to DR. Now we are planning to Mock DR Drill. For this our app team are considering following Scenario.
1) They want to do some read write operations on the DR Slave server to test app functionality and DR Data. For this do we need to Break log shipping and after app team does their testing We have to re-enable the log shipping. Please suggest us follwoing
1) steps to cancel the Log shipping in proper way
2) if we shutdown DR server and take a file system backup and start SQL Server on slave server and stop log shipping jobs and enable databases to recovery mode and after app team completes their activity again shutdown the DR instance and restore earlier taken cold backup of file system and bring up the instance and enabling log shipping job would work? Please suggest.
or do we have any better solution in this case?
Regards,
Varun
↧