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

Transaction log backup failure types that break the chain

October 9, 2018, 2:08 pm
$
0
0

I am creating some alert monitors and need to fill a particular hole:  I need to know when a particular transaction log backup actually breaks the restore chain.  Knowing this will allow me to create a monitor that ignores trn backup failures that do not break the restore chain, since I already have a monitor that alerts me based on the number of successful tlog backups in a given hour, I need to know immediately when any given backup failure breaks the restore chain.

My tlogs backup every 15 minutes, so minor failures every now and then that do not break the chain are not as critical, but a broken chain requires immediate action.  Is there a list of failure result types that do and do not break the restore chain?  This would be a tremendous help.  With this info I could know at a glance that my restore capability remains intact even if a network or other hiccup causes a tlog backup to fail.

↧
Search

SQL 2014 Always On

October 9, 2018, 11:51 pm
$
0
0

Hi,

In SQL 2014 Always On availability group, with 2 nodes cluster.

If we assigned a SQL Login with permission to a Database from the Primary replica (for AlwaysOn database), the SQL Login permission will not be replicated to the Secondary replica, is this correct?

What if we set up a Windows Authentication Login permission to DB, will it be replicated? 

Does this apply to all Databases in SQL HA cluster, regardless the DB is set for AlwaysOn or not?

Thank you

↧
↧

DR via DAG AlwaysOn. One of two DCs goes down.

October 10, 2018, 2:08 am
$
0
0

Hi All,

I have two distributed AG in two DCs, AG1 and AG2. DAG is working in asynchronous data movement mode.

In MS DAG manual I found this: "only manual failover is supported for a distributed availability group". But in this case what is the procedure of disaster recowering  if DC1 with primary AG1 unexpectedly goes down? I can't start manual failover and have just read-only AG2. How can I switch the secondary AG to primary?

↧

SQL Always-On - backup fails on secondary node

October 10, 2018, 3:03 am
$
0
0

Hi,

We've a SQL Server 2016 cluster Always-On running on Windows Server 2016.

Current situation:

- SQL1 (Secondary node)

- SQL2 (is currently Primary node & backup job running fine on this node) 

Backup preference option is: Prefer Secondary

When a failover happens, SQL1 takes the lead and becomes Primary but all backup jobs fail subsequently even the backup preference is Secondary.

Can someone explain why the backups fail on the secondary node SQL2 (when it becomes secondary) where it contains all the backup history (full, differential and log)?

I appreciate your help.

Thanks,

AB

AB

↧

SQL Server Standard with 3 nodes.... temporarily

October 10, 2018, 12:44 pm
$
0
0

Hey everyone, I'm trying to migrate all of our SQL services to a new network infrastructure, including new vlans and IP addresses. I have a 2012R2 Windows Active/Passive cluster with SQL 2014 Standard. The cluster holds 5 SQL instances, all of which need to be re-IP'd and migrated.

I'm trying to do this in phases and with as little impact as possible. One of the methods I was testing out was to build 2 new nodes, so C and D nodes, add them into the cluster, install SQL, move services to the new nodes, and then slide out the old A and B nodes.

Technically, this works, I can set up the stretch cluster and the C/D nodes are added in fine. However, I get the error when installing SQL on node C that SQL standard can only have 2 nodes at once. Is there any way around this? I've tried removing the B node from the possible cluster owners and install SQL on the C node, but same error. Eventually, I'll come back to having 2 nodes in the cluster, I just need to add in a 3rd node temporarily so I can remove the others.

I'm already thinking of a plan B to do this migration, but I wanted to throw this out there in case anyone had any thoughts around this.

Thanks in advance! Appreciate the help..

↧
↧

LISTERNER issue in SQL 2016 BASIC AVAILIBILITY GROUP

October 10, 2018, 1:16 pm
$
0
0

Should two IP addresses be set to the listener in the basic AG?

In our proejct, 

The BAG is set up on two physical servers (one primary and another?

the primary and secondaary server are in two subnets.

This is asked as the BAG is operating well and BAG can be failover manually.

But, there are the error for two servers in WSFC.  Event Id is 1069 for both servers. 

What would be the cause of this ID? How to fix?

thanks

John

↧

SqlServerWriter missing when Enable AlwaysOn Availability Groups

October 11, 2018, 6:37 am
$
0
0

Hey People,

i´m searching for many hours a problem and i´m at the end now.

I have a two node Failover Cluster with Availability Groups. The OS is Windows Server 2016 with Sql Server 2016, all System are up to date.

Two Instances are allready configured with AG and everything is fine. SqlServerWriter is still running if i show it in Powershell with "VSSADMIN LIST WRITERS"

Now is the thing i dont unterstand. I´ve created my two Instances on each server and want to use the AG Feature. For This i go to SQL Server Configuration Manager and mark the "Enable AlwaysOn Availability Groups" at this moment the "SQL Server Writer" dissapear and im not able to perform my backups anymore. Reinstall doenst help, at the same point the VSS Writer dissapear all the time.

If i delete the Instance or disable the Services of this Instance it appears again - Verry confused about that

I´m useing for each instance different Service Accounts

I´m think about an missings Securithy Right. But which one ? Any ideas ?

Thank you Guys!



↧

Always ON -2016 or latest

October 12, 2018, 12:40 am
$
0
0

Hi 

I need info 

1) How always on working ? all query going to primary server then replicate to other secondary server.

2) what is the delay or down time,  In case of node failure?

3) supporting linux version ?

Thanks 

↧
Search

Reg:Issue in disabling the Log Shipping Configuration...

October 12, 2018, 8:02 am
$
0
0

Hi Experts,

in one of my client environment,

Logshipping has been enabled between Primary and Secondary servers.

but unfortunately secondary server has been crashed.so i need to disable the log shipping configuration in primary server .

when i disable the check box in Primary server as shown in below pic,

it tries to  delete  the log shipping related jobs  in seconadry server which is not existis currently.

Here my requirement is that ,is  there  any method to disable the log shipping configuration even though there is not valid conncetion between Primary and Secondary Servers.

Thanks In Advance.




↧
↧

Database location for SQL Server FCI

October 16, 2018, 11:50 am
$
0
0

On Azure I created a SQL Server Failover Cluster using Windows Server 2016 and SQL Server.  Everything is working great.  When I log in via management studio, I see that databases are created in the S:\SQLDB\MSSQL13.MSSQLSERVER\MSSQL\DATA\ directory.

I need to modify my SQL Scripts to create new databases.  S: does not appear to be a drive that I can see.  Also, I see no databases in the cluster shared storage.  Where are these databases and what location should i refer to in my scripts for new databases?

Mitch

↧

Need your opinion on Hyper V Cluster and SQL

September 5, 2018, 8:52 pm
$
0
0

Hello, I have been given the task of creating a Hyper V cluster and some app servers. 

I have a 3 node hyper V clustered together and connected to SAN Switch for Storage.

Now for the VM part i have some concerns, Need to have 2 node SQL Cluster as VM, i think i have to go with VHD sets but do i have to create the drives as fixed or dynamic? 

The SAN is all SSDs FYI 

Say i need 1 TB of data, 500 for Log and 500 for Temp files, do i have to create all of them as fixed size disks? If yes will there be any issues when doing live migrations? I hope not, since its a CSV , but your opinion please.

We do need always on and here is what I did so far. Added storage LUN to the hyper v cluster and made them as csv Created couple of shared storage for data and log files for the Sql vm from the cluster manager onto the csv created earlier.

Now my understanding is that both the SQL should see the shared VHD set available to them right? Or I am missing something?

I am doing a lot of research on this as well and all of your feedback and guidance is very much appreciated. Thank you

ferouze

↧

SQL 2014 AlwaysOn Databases

October 16, 2018, 11:53 pm
$
0
0

Hi,

We try to set up Login permission for a x2 nodes SQL 2014 AlwaysOn Availability Group.

  • Listener: sqlListern
  • Primary Replica: SQL1
  • Secondary Replica: SQL2

Create a Windows Login and assigned sysadmin permission on both SQL server.

- The Windows Login can access SQL Instance of the sqlListener & primary replica via SMSS.

- However, the Windows Login cannot access the Secondary replica. (double check and the sysadmin permission has been assigned).

Not entire sure how to set up Login permission for SQL 2014 AlwaysOn AG. please shed some lights what is missing, thankyou

↧

Multiple Instances and AlwaysOn Availability Groups

April 23, 2013, 2:34 pm
$
0
0

Hi,

I have 2 SQL Servers: A & B
Each has 2 instances and each instance is part of an database AlwaysOn Availability Group

Server A - instance 1, AlwaysOn Group1 & instance2, AlwaysOn Grroup2
Server B- instance 1, AlwaysOn Group 1 & instance2, AlwaysOn Grroup2

I configured 2 AlwaysOn groups, which worked for a brief amount of time:

Server A - had instance 1 (primary) and instance 2 (secondary)
Server B - had instance 1 (secondary) and instance 2 (primary)

However after a few minutes, Server A instance 1 (secondary) changed to the not synchronized state and I'm struggling to add Server A instance 1 as a replica in AlwaysOnGroup1

Can someone tell me if I'm doing something wrong? Can I have 2 instances participating in separate AlwaysOn Database Availability Groups on the same server?

I'm wondering maybe the configuration is failing because one server holds a primary and the other a secondary - perhaps each server should hold only a primary or secondary?

Thanks

↧
↧

Differential Backup (But Specify Differential Base)

October 18, 2018, 8:50 am
$
0
0
Suppose that we have the following (daily) full database backups that ran in the following order on Server1:

F1   F2   F3   F4   F5

Now, F1 has been restored on Server2 and Server1's database activity has been stopped.

Is it possible to run a differential database backup on Server1, but specify F1 as the differential base, rather than having F5 be the differential base, and then restore this differential backup on Server2? (if F5 is used as the differential base, then the changes from F2-F4 won't be picked up).

Thank you for any help.
↧

Backup error

October 18, 2018, 10:54 am
$
0
0

Hi Team,

We are using olahallengren maintenance scripts for backups.

These are working fine from past few days.

But today we got errors for Full and Log backup jobs, like

Msg 207, Level 16, State 1, Line 1
Invalid column name 'modified_extent_page_count'.
Msg 208, Level 16, State 1, Procedure DatabaseBackup, Line 1761 [Batch Start Line 0]
Invalid object name 'sys.dm_db_log_stats'.

↧
Search

SQL Server on Hyper-V security concern

October 18, 2018, 6:50 pm
$
0
0

Hi,

I am setting up a new SQL Server on the Windows Server 2012 Hyper-V.
But I'm thinking how do I secure that SQL Server in case the vm is stopped, removed, or the virtual disk is deleted?
Is it a good idea to put the production database server on the Hyper-V?
Thanks for help.

Jason

↧

SQL Server AG - Some databases stuck at recovering on secondary nodes after any of these secondary nodes are restarted

October 18, 2018, 5:37 pm
$
0
0
I have an 2017 SQL Server on Windows 2016 boxes.  When rebooting the secondary nodes while their Replica Role is Secondary, some of the databases in this AG groups are showing Synchronizing after rebooted.  They remain Synchronizing for days.  I checked the logs and didn't see any errors.  The affected databases are random.  To resolve this, i just restart the SQL Server Services and all the databases in the same AG group become synchronizing again.  Sometimes, i have to restart the SQL Server Services multiple times.  I am not sure what is causing this problem or where to look at.  I check the database log, system log, and didn't see any thing related to why they are not synchronizing.  I was wondering is this a bug?
↧
↧

No more failover w/o dataloss in sql 2017 cu11?

October 19, 2018, 12:23 am
$
0
0

good day

We have standard sql2017 cu9  and read-scale configuration of availability groups (cluster type=none). we can manualy failover AG to secondary node by demoting primary node and failover to secondary.

but after we applied CU11 we get an error

Cannot failover an availability replica for availability group 'ag1' since it has CLUSTER_TYPE = NONE. Only force failover is supported in this version of SQL Server.

according to manual we try to use ALTERAVAILABILITYGROUP ag1 FORCE_FAILOVER_ALLOW_DATA_LOSS;

but in this case secondary replica becomes not syncronizing and it need to be resumed manualy.

Is this a bug or there will be no more smooth failover?

↧

SQL Server AG - Some databases stuck at synchronizing on secondary nodes after any of these secondary nodes are restarted

October 18, 2018, 5:37 pm
$
0
0

I have an 2017 SQL Server on Windows 2016 boxes.  When rebooting the secondary nodes while their Replica Role is Secondary, some of the databases in this AG groups are showing Synchronizing after rebooted.  They remain Synchronizing for days.  I checked the logs and didn't see any errors.  The affected databases are random.  To resolve this, i just restart the SQL Server Services and all the databases in the same AG group become synchronizing again.  Sometimes, i have to restart the SQL Server Services multiple times.  I am not sure what is causing this problem or where to look at.  I check the database log, system log, and didn't see any thing related to why they are not synchronizing.  I was wondering is this a bug?

Updated:

1) System are patched with the latest CU 11 as of today.

2) The secondary nodes are in Synchronous-commit mode

↧

SQL server 2017 always on: Manually fail over from primary node to secondary node--- never successed

October 19, 2018, 11:06 am
$
0
0

Here is error message when I do from wizard or T-sql(ALTER AVAILABILITY GROUP group1 FORCE_FAILOVER_ALLOW_DATA_LOSS;)

Failed to bring availability group 'group1' online.  The operation timed out. If this is a Windows Server Failover Clustering (WSFC) availability group, verify that the local WSFC node is online. Then verify that the availability group resource exists in the WSFC cluster. If the problem persists, you might need to drop the availability group and create it again.

I checked Failover cluster manager and all online and green I checked Cluster events: no error log showup.

Any idea what happened? It failed again and again yesterday: "Server name" under "cluster core resources" offline yesterday.

Today, everything back online. Then I tried to manually fail over. Still failure and get those messages.

I try to reboot primary node: failover didn't happen. After primary restarted, I checked: everything is green(good) and no failover happened. 

Any help?Thanks



↧
Viewing all 4532 articles
Browse latest View live
Search
<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>