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

SQL AlwaysOn Networking Questions

$
0
0

I'm asking these questions together so they better describe what I am trying to understand overall.

We have two next major goals for our application and data center environment: 1) implement hot/warm (Active/Passive) failover for DR and 2) implement hot/hot (Active/Active) for HA after my service application is enhanced to sync over the network in order to scale out. I'm mostly interested in scenario #1 now where the failover data center is keeping a DR replica of our primary database that we want to use R/O for reporting, invoicing etc. in the meantime when not failed over to. This is a great AlwaysOn feature.

We are Microsoft centric (Server 2008 R2 and SQL 2012 Enterprise) so I hope to use SQL AlwaysOn but am confused on how a few networking mechanisms work in practice and want to better understand the SQL AlwaysOn big picture.

I'm a full time developer and also do most of the IT and understand a fair bit of networking (for a developer) but don't configure much since we are running at an ISP where our IAAS is hosted under VMware and they mostly manage the network. Our long term goal is a multi data center, multi vendor Active/Active geo diverse configuration. We will eventually be converting to Windows Server 2012 or can sooner if required or there is some useful benefit in conjunction with AlwaysOn.

Here are my questions which mostly are asking about how certain IP and Windows Failover Cluster mechanisms work in practice with AlwaysOn.

  • Do I use DNS to map a VNN to some IP(s) or VIP that all the machines in the Availability Group listen to? How are DNS, VNN, IP(s), VIP, etc. used to make this happen?

  • After a failover, how does a client find the new machine? Is the connection broken and the client application must have retry logic, or be restarted in some poor design cases, to reconnect? I think a VNN is used here and if so would like to understand how that works before, during and after the primary machine fails.

  • Can we setup a Windows Server Failover Cluster on Windows Workgroups or must we convert all the involved OS and SQL machines to a domain based system under Active Directory? Does the DC have to be its own machine? We are a very small operation with a high real time transaction rate so setting up AD would be a a big hit on my time as I've worked in that environs before and thus far we have run with workgroups just fine.

  • How is the R/O replica database accessed before and after failover? Can it be accessed after failover and did it just become no longer R/O to applications that expected it to be? I could see someone coding a R/W test to see if they had the correct database! Iow, can/how do I specifically access/address the replica database machine for guaranteed R/O reports rather than how a R/W client might typically connect to the database not caring if they got the primary or the failover database as long as it was R/W and live?

Thanks so much, Dave


Dave


SQL Always on

$
0
0

Hello ,

i have sql server 2008 and hosting 3 databases

i have to upgrade to sql 2012 with always on .

i am not DB guy so how can i migrate the database from sql 2008 to 2012 is it kind of export or backup & restore

need any reference please regarding this process .

Regards


MCP MCSA MCSE MCT MCTS CCNA

sql and azure login time slow

$
0
0

hi

i have a SQL alwayson setup of 3 virtual machines. two sql servers and one for cluster quorum. the sql listener Works fine, but the connection login time to the sql server instanse are slow. ive tried both from the sql server it self, from another machine in my azure setup, and from "home" (fixed vpn fra "home" to the azure setup

Where should i start?

/

David

Always On technology

$
0
0

Hi,

I have one requirement to configure Always On in SQL server 2012 clustering.

Is it possible to configure ?

If so please provide the steps..

Regards,


Vinodh Selvaraj

Queries on AlwaysON

$
0
0

Hi:

I have some queries.

- Can I failover 1 database out of 'N' databases in an availability group.

- Is it possible that out of say 5 dbs in an availability group 2 are on server1 and 3 are on server 2, as in the case of mirroring.

- My client requirement is that, if one database in availability group has issues, all databases should failover to the other server... .....This is the default behavior.. Am I right...?

Thanks

Is it acceptable if I have sometimes Resent Messages/sec > 20

$
0
0

I saw that the performance count SQL Server:Availability Replica--> Resent Messages/sec should be 0, and I see that usually it is close to 0 (average is 3) but sometimes (a few times a week) I do have it close to 20. Is is acceptable? I want to set an alert to get mail when it raises so that I know something goes wrong, what value is acceptable for the alert? What does it say when it raises?

High Log Send Queue on replica. What does it mean?

$
0
0

As far as I understand Always on  synchronization, The performance counter SQL Server:Database Replica --> Log Send Queue is relevant only on the primary, which is sending the log to the replicas.How come I have very high "Log Send queue" in the Secondary replica?

Will Always-on HAS ALWAYS BE installed in a Cluster environment?

$
0
0

Hello:

I understand High availability includes Windows Cluster, But I have a simple question:

Can I Install or deploy/configure Always-on in a NON windows CLUSTER environment?.

Just have 2 servers, might be same or different data centers, of course in a Domain, can I install/configure Always On from one SQL Server instance to another SQL Server instance that DO NOT reside on a Windows Clustering nodes?. Just plain Windows boxes?.

Thanks


VSS errors preventing backups

$
0
0

Trying to use a third party backup solution to backup our SQL databases using VSS but it has not been successfull because we're experiencing vss issues. When running "vssadmin list writers" the 'SqlServerWriter' fails:
Writer name: 'SqlServerWriter'
   Writer Id: {a65faa63-5ea8-4ebc-9dbd-a0c4db26912a}
   Writer Instance Id: {548b4a35-35fa-4f2f-b8c6-f5a285f696db}
   State: [8] Failed
   Last error: Non-retryable error
When looking the event viewer for VSS errors i see two repeatedly. 
1. Event ID 8193
Volume Shadow Copy Service error: Unexpected error calling routine RegOpenKeyExW(-2147483646,SYSTEM\CurrentControlSet\Services\VSS\Diag,...).  hr = 0x80070005, Access is denied.


Operation:
   Initializing Writer

Context:
   Writer Class Id: {e8132975-6f93-4464-a53e-1050253ae220}
   Writer Name: System Writer
   Writer Instance ID: {e0c429a2-971e-491d-ad9c-3df3f8cb6ddc}
2. Event ID 8229
A VSS writer has rejected an event with error 0x800423f4, The writer experienced a non-transient error.  If the backup process is retried,
the error is likely to reoccur.
. Changes that the writer made to the writer components while handling the event will not be available to the requester. Check the event log for related events from the application hosting the VSS writer. 

Operation:
   PrepareForSnapshot Event

Context:
   Execution Context: Writer
   Writer Class Id: {a65faa63-5ea8-4ebc-9dbd-a0c4db26912a}
   Writer Name: SqlServerWriter
   Writer Instance Name: SQL Server Code-Named 'Denali' CTP2:SQLWriter
   Writer Instance ID: {548b4a35-35fa-4f2f-b8c6-f5a285f696db}
   Command Line: "C:\Program Files\Microsoft SQL Server\90\Shared\sqlwriter.exe"
   Process ID: 1852

After contacting the vendor of the backup solution, they pointed out that those are the cause of the backups failing. So far I've tried restarting the "volume shadow copy service" and the "SQL Server VSS Writer" but hasn't worked. Also I tried to re-register the VSS service buy running the script below but still no luck

cd /d %windir%\system32
net stop vss
net stop swprv
regsvr32 /s ole32.dll
regsvr32 /s oleaut32.dll
regsvr32 /s vss_ps.dll
vssvc /register
regsvr32 /s /i swprv.dll
regsvr32 /s /i eventcls.dll
regsvr32 /s es.dll
regsvr32 /s stdprov.dll
regsvr32 /s vssui.dll
regsvr32 /s msxml.dll
regsvr32 /s msxml3.dll
regsvr32 /s msxml4.dll
vssvc /register
net start swprv
net start vss

They mentioned that the server may need a reboot to resolve the issue but if there are any other suggestions I can try that will fix this I would like to know.

How to automate SQL Agent Jobs should failover to Active Node on AlwaysON setup

$
0
0

Hello Guys,

I have received a new requirment , which is Automate the Jobs enable/disable process on AlwaysON setup.

Currently i have alwaysON setup between my Node01 and Node 02 , also couples of maintenance plan

on both , now what happens is whenever the node fails , due to cluster issue( for eg from Node 01 to Node 02),

mine backup , others job keep getting failed due to Read_only state on primary , coz mine jobs are still disabled

on Node 02 , so currently i have to manually enable job on Node 02 , n then disable on node 01,

so is there any way to Automate this process , so that i doesn't have to manually enable/disable the job.

I belive you guys have got my requirement , If not then please let me know.

Your help will higly appriciated.

Thanks ,

Anish


Asandeen

Manual or Automatic failover?

$
0
0
For SQL Server (2005/2008/R2) cluster, after failover happened from one node to another, how do I tell whether it was an automatic failover or somebody failed it over manually. This would help further troubleshoot what caused the failover. Please consider both Windows Server 2003 and Windows Server 2008 scenario. Thanks.

Question on transactional Replication

$
0
0
Hi All,

In transactional replication, can I have publisher as SQL 2012 and one of subscriber as SQL 2000?

Thanks in advance.

Failover Over Cluster Windows 2012 R2 Role Gets Stop

$
0
0

I have deployed SQL server 2012 SP2 with latest updated on windows 2012 R2 with updated windows we have 2 nodes of SQL with SQL feature Always on Availability we have successfully deployed it but now we are facing the problem in windows failover is Role gets stop and we have to manually starts the role I am also attaching the snapshot of it.

Kindly see the above 2 snapshots and tell us the solution on it on urgent basis.

I will be very thanfull if u will resolve my issues on urgent basis.

Regards,

Tauseef

Is cluster environment needed in alwayson?

$
0
0

Hi All,

I have a question, can  we built 'Alwayson group' without a cluster environment? 
If we can, what are the disavantages in building it? 
Or
If we can not? Why we can not built in non-cluster environment?

I did some research in google some say we can built in standalone some say we can not, but I do not get the concrete answer. The agenda is we are planning to cut cost for clustering. Please help me to understand it.
Also Suggest me some blogs, books for the same.

Thanks


Best Regards Moug

Database in recovery

$
0
0

Our server ran out of disk space during a stored procedure process. We were able to free up some space, stopped all SQL services, restarted all SQL services and now SQL Management Studio shows the database to be in recovery.  Is there a way to monitor this to ensure progress is being made and to estimate when it might complete?

 


R2 recover from Corrupt SQL Server

$
0
0

Now i am searching any tool, which recover all over data MDF file and R2 from SQL server.

DECLARE @DBName VARCHAR(64) = 'databasename'

DECLARE @ErrorLog AS TABLE([LogDate] CHAR(24), [ProcessInfo] VARCHAR(64), [TEXT] VARCHAR(MAX))

INSERT INTO @ErrorLog
EXEC sys.xp_readerrorlog 0, 1, 'Recovery of database', @DBName

SELECT TOP 5
         [LogDate]
        ,SUBSTRING([TEXT], CHARINDEX(') is ', [TEXT]) + 4,CHARINDEX(' complete (', [TEXT]) - CHARINDEX(') is ', [TEXT]) - 4) AS PercentComplete
        ,CAST(SUBSTRING([TEXT], CHARINDEX('approximately', [TEXT]) + 13,CHARINDEX(' seconds remain', [TEXT]) - CHARINDEX('approximately', [TEXT]) - 13) AS FLOAT)/60.0 AS MinutesRemaining
        ,CAST(SUBSTRING([TEXT], CHARINDEX('approximately', [TEXT]) + 13,CHARINDEX(' seconds remain', [TEXT]) - CHARINDEX('approximately', [TEXT]) - 13) AS FLOAT)/60.0/60.0 AS HoursRemaining
        ,[TEXT]

Now I am using this : en.mdfrepair.net

Setting Up Alerts for Always on Availability Groups Failover

$
0
0

Hi Folks,

In SQL Server 2008R2 we set up alerts for Mirroring failover using WMI Alerts. As Like this.

Now we need to configure similar alerts for Always on Availability Groups(AAG) in SQL Server 2012, but it seems that there is no such WMI Alerts or any standard way to set up the alerts for getting notified for AAG Failover. Click Here

Should I manually Create a SQL Agent Job using these DMVs and schedule it at frequent Interval to get notified about any AAG failover or is there any standard way as for mirroring Failover alerts? Any suggestion or help is appreciated. 


Pranshul Gupta


What is the Command to find out the Transaction delay between Primary and Read-only instance of an ApplicationGroup listener.

$
0
0
need the sql command to find out the Transaction delay between Primary and Read-only instance of an ApplicationGroup listener. same as the Dashboard shows.

Rohit

SQL Server 2012 AlwaysON Replica Backups

$
0
0

I am using SQL Server 2012 on Windows Server 2008 R2 Core.

I have alwayson configured and running.

I have transaction log backups set to run on the replica.

They are running successfully. 

I do NOT have any transaction log backups running on the primary server, only full backups 1x a day.

The transaction log on the primary is not truncating, just keeps getting bigger and bigger.

Is this by design?  If so, I MUST run transaction log backups on Primary, which negates the performance gain of just running them on the secondary replicas.

The question is...do I have to run tlogs on the primary even if I'm doing them on the secondary to keep the log file from growing out of control?

Thanks!  Ben Jongewaard

SQL 2012 Log shipping

$
0
0

Dear all,

Please find the below query I am also facing the same issue please give the resolution as early as possible.

I'm after some help please, as I think I may have discovered a bug with SQL Log Shipping to a server that is also running SQL Reporting Services.

To try and help keep things clear, I have 4 servers, ServerA, ServerB, ServerC and ServerDR. ServerA, B and C are all within the same domain, whilst ServerDR is in a data centre offsite.

I have setup to logship several databases from ServerA (11.0.2100 - 2 node SQL cluster) to ServerDR (11.0.2100), this is working as it should and the databases are in a Standby / Read Only mode. I then setup to logship to ServerB (11.0.2100), from ServerA. This initially worked, but at certain times over night the log shipping would fail and leave the databases on ServerB in a restoring state, rather than Standby / Read Only state. I deleted logshipping and re-created the job. This runs fine through the day, but as soon as the evening comes it fails again. It seems that when the transaction backup doesn't have any data changes to apply, this is when it fails.

Log shipping is setup to restore into Standby / Read Only mode and disconnect the users.

I then tested log shipping from ServerA to ServerC and this has worked without fault over night. The only difference between ServerC and ServerDR, is that ServerB is running Reporting Services.

The logs from ServerB when the log restore fails is:

2013-12-27 15:16:05.82 * Error: Could not apply log backup file 'F:\Logshipped Files\xxxxx_20131224171511.trn' to secondary database 'Logship_xxxxx'.(Microsoft.SqlServer.Management.LogShipping) 2013-12-27 15:16:05.82 Error: An error occurred while processing the log for database 'Logship_xxxxx'. If possible, restore from backup. If a backup is not available, it might be necessary to rebuild the log. An error occurred during recovery, preventing the database 'Logship_xxxxx' (27:0) from restarting. Diagnose the recovery errors and fix them, or restore from a known good backup. If errors are not corrected or expected, contact Technical Support. RESTORE LOG is terminating abnormally. Processed 0 pages for database 'Logship_xxxxx', file 'xxxxx' on file 1. Processed 1 pages for database 'Logship_xxxxx', file 'xxxxx' on file 1.(.Net SqlClient Data Provider) 2013-12-27 15:16:05.82 Error: Could not log history/error message.(Microsoft.SqlServer.Management.LogShipping) 2013-12-27 15:16:05.82 Error: ExecuteNonQuery requires an open and available Connection. The connection's current state is closed.(System.Data) * 2013-12-27 15:16:05.82 Skipping log backup file 'F:\Logshipped Files\xxxxx_20131224173011.trn' for secondary database 'Logship_xxxxx' because the file could not be verified. 2013-12-27 15:16:05.82 * Error: Could not log history/error message.(Microsoft.SqlServer.Management.LogShipping) 2013-12-27 15:16:05.82 Error: ExecuteNonQuery requires an open and available Connection. The connection's current state is closed.(System.Data) 2013-12-27 15:16:05.82 Error: Could not apply log backup file 'F:\Logshipped Files\xxxxx_20131224174511.trn' to secondary database 'Logship_xxxxx'.(Microsoft.SqlServer.Management.LogShipping)This is a snippet and it repeats itself

I then have run Restore VerifyOnly from disk = 'D:\.....' to check the integrity of the log file it has copied. This returnsThe backup set on file 1 is valid.

If I manually apply this log with:

RESTORE LOG Logship_xxxxx

FROM DISK='F:\Logshipped Files\xxxxx_20131223193011.trn'

WITH STANDBY='F:\Logshipped Files\UNDO\UNDO_xxxxx_ARCHIVE.DAT'

This fails with the:

Processed 0 pages for database 'Logship_xxxxx', file 'xxxxx' on file 1. Processed 1 pages for database 'Logship_xxxxx', file 'xxxxx_log' on file 1. Msg 9004, Level 16, State 6, Line 1 An error occurred while processing the log for database 'Logship_xxxxx'. If possible, restore from backup. If a backup is not available, it might be necessary to rebuild the log. Msg 3013, Level 16, State 1, Line 1 RESTORE LOG is terminating abnormally. Msg 3414, Level 21, State 1, Line 1 An error occurred during recovery, preventing the database 'Logship_xxxxx' (27:0) from restarting. Diagnose the recovery errors and fix them, or restore from a known good backup. If errors are not corrected or expected, contact Technical Support.

It will then allow me to move onto the next log, which will generate the same error, but then when I hit a log with some slight data change, this applies successfully and puts the database back into Standby / Read Only.

I have also checked the SQL jobs that are running on ServerB to see if there is anything that is causing an issue and nothing coincides with the timings of the restores.

Apologies if I have missed anything, but any ideas would help a lot.

Thank you.

Viewing all 4532 articles
Browse latest View live


<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>