If I would like to relocate a database files to another faster drive in the primary replica, is it required to rebuild the whole replication ???
↧
Always on : Primary database relocation
↧
Which spn to configure when using listener
Hi all,
I am confused by a situation I am facing.
I have an availability group configured with two nodes.
If I follow the instructions below :
https://docs.microsoft.com/en-us/sql/database-engine/availability-groups/windows/listeners-client-connectivity-application-failover?view=sql-server-2017#SPNs
I need to create the spn using the listener :
setspn -s MSSQLSvc/listener.domain.com DOMAIN\gmsaAccount
setspn -s MSSQLSvc/listener.domain.com:INSTANCENAME DOMAIN\gmsaAccount
setspn -s MSSQLSvc/listener.domain.com:1433 DOMAIN\gmsaAccount
At this point my connection is not using Kerberos:
So I add the following :
SetSPN -s "MSSQLSvc/node1.domain.com:INSTANCENAME DOMAIN\gmsaAccount
SetSPN -s "MSSQLSvc/node1.domain.com:INSTANCEPORT DOMAIN\gmsaAccount
SetSPN -s "MSSQLSvc/node2.domain.com:INSTANCENAME DOMAIN\gmsaAccount
SetSPN -s "MSSQLSvc/node2.domain.com:INSTANCEPORT DOMAIN\gmsaAccount
Now it works. So I remove the spn using the listener to see what happens :
setspn -D MSSQLSvc/listener.domain.com DOMAIN\gmsaAccount
setspn -D MSSQLSvc/listener.domain.com:INSTANCENAME DOMAIN\gmsaAccount
setspn -D MSSQLSvc/listener.domain.com:1433 DOMAIN\gmsaAccount
The connection is still using Kerberos.
So now I wonder what is the point of creating the spn for the listener ?
Is it relevant ?
Thanks for your help
↧
↧
setup log shipping or replication from 2014 to 2016
Hi all,
I have an on premise VM on which SQL server 2014 standard edition running which has databases in 3 TB approx, its a prod environment which is used to run mostly analysis and report kinda query. it gets input data from third party replication tool continuously.
There is one more VM on Azure we have taken on which SQL server 2016 developer edition running. we have taken it to use it like a test environment, so that any queries we run for analysis and reporting can be executed here and tested before deploying it to prod environment.
Now point here is I want data of prod to be synced in test environment from on premise 2014 standard edition to 2016 developer edition Azure VM, what are the possible ways ?
what challenges with log shipping ?
what challenges for replication?
any other recommendations welcome
please suggest ? point here to keep in mind is we have table size up to 1 TB.
SQL Server DBA
↧
Can't rebuild(join) availability group: '10061(No connection could be made because the target machine actively refused it.)'
Hi experts,
I created an AlwaysOn Availability before but due to a 10GbE NIC driver issue(it rans 10X slower than before) I manually removed AG to keep the SAP system/SQL DB running.
I want to rebuild now and I find it always failed at "ALTER AVAILABILITY GROUP [AGTP1] JOIN;"
I have checked every steps mentioned in link below: both firewalls are disabled, both endpoint are created and enabled with the role:sysadmin, service accounts are domain admins, telnet port 5023 are ok.
I still can't get a clue, please help. Thanks.
--- errorlog ----
2019-06-10 09:45:52.57 Backup Log was backed up. Database: testdb, creation date(time): 2019/06/10(09:24:06), first LSN: 78:112:64, last LSN: 78:256:1, number of dump devices: 1, device information: (FILE=1, TYPE=DISK: {'\\DL580-1\TP1TransactionLog\testdb_20190610014552.trn'}).
This is an informational message only. No user action is required.
2019-06-10 10:00:11.83 Backup Log was backed up. Database: TP1, creation date(time): 2019/03/19(09:47:55), first LSN: 1018829:3168377:1, last LSN: 1018830:415658:1, number of dump devices: 1, device information: (FILE=1, TYPE=DISK: {'Z:\TP1TransactionLog\TP1_20190610020001.trn'}).
This is an informational message only. No user action is required.
2019-06-10 10:01:53.23 spid813 [HADR TRANSPORT] AG:[71ACF45E-FC88-4AAE-98E0-97A3C356C95E] CHadrTransport::NotifyManagerChange called
↧
Disadvantages of using 'Allow Failback' in sql cluster
Hi, we are looking into 'Allow failback' option in sql cluster as we would like sql to run on its preferred owner after patching is done. Patching is done by a different team and they don't put sql back to its original node most of the times - they have some issue currently. I would rather not touch the cluster but we are looking into the option of failback anyhow.
Prevent failback is our current default - which works well.
I wanted to know what are the disadvantages of using 'Allow Failback- Immediately' option in sql cluster, Thanks.
One scenario that i can think of is during a actual issue on the current node, sql fails over to the other good node, but then tries to fallback to the 1st bad node, which fails it to 2nd good node - How long does this cycle runs for and does SQL ends up in a failed state?
D
↧
↧
how to change HostRecordTTL value for network name 'Name: "my cluster name'
Warning "the HostRecordTTL property for network name 'Name: "cluster nmae' is set to 1200 (20 minutes). For multi-site clusters the suggested value is 300 (5 minutes)." shows in the cluster vaslidation report. how to change this cluster parameter?
the "cluster name", for exmple, cluster1 , is not listed in the outputs from get-clusterresource. off course, the paramenter of cluster cannot found from get-clusterparameter
My cluster is consist of two nodes in Server 2012 R2.
three SQL alwayson groups icreated n SQL 2016 standard on each node. These groups are Roles of the cluster and they are lsited in the ourput from get-clusterresource. But no cluster name in the ouput.
how to change HostRecordTTL value for network name 'Name: "cluster name'?
Please advise.
thansk
John
↧
SQL 2016 cluster installation fails with an IP address error
Hi Guys,
We have existing two node windows 2016 cluster, running four SQL Server 2016 instances. Now I am installing one more SQL 2016 instance on it and setup keep on failing with below error message.
Error installing SQL Server Database Engine Services Instance Features. The resource with identifier 'Type='IP Address' NetworkName='public' Group='SQL Server (XXXXX)' Resource='SQL IP Address 1 (XXXXX)'' could not be found on the cluster. Please check if it exists.Error code: 0x855D0003
Any help will be appreciated.
Thanks,
Tajinder Singh
↧
SQL 2016 AG
Hi
When the read-only routing is configured, the read requests like select * from dbo.account will go to secondary node when the application srting is also set toApplicationIntent=ReadOnly
Now what would happend when de read requests goes to the secondary node and at the same time the secondary node failed? would the read requests goes back to the primary node?
In my test enviorment I set the ApplicationIntent=ReadOnly for my ssms and then connect to my AG listener and ran select * from dbo.account and I could see that select requests goes to the secondary node but when query was running we did disconnect the secondary node nic and we can see that query has been failed
Is this expected?
Shahin
↧
Connecting to Always on Database
Hi,
I have configued SQL 2016 always and have a DB replicating but have no idea how I attach to it using the listener
Could someone please help
Thanks
↧
↧
SQL Server 2017 (Ubuntu 18.04) - managed backups to Azure config
Hi,
I'm trying to setup managed backups to Azure storage container. I've set everything according https://docs.microsoft.com/en-us/sql/relational-databases/backup-restore/enable-sql-server-managed-backup-to-microsoft-azure?view=sql-server-2017 but not working.
I've run the same setup options to another SQL2k17 running on Win2k19 - and backups are working.
Database is the same - empty one just for testing.
T-SQL backups from Linux installation to Azure works finr (SAS credentials are correct).
Regards
JD
↧
Can DBs running on different version be joined to the same AG
We are currently running SQL 2012 with AG on it.
I need to plan for upgrade to SQL 2016/2017.
For the time of the migration, is it possible to have AG connecting to DBs with same compatibility level but sitting on SQL server of different version? E.g. have the primary site with SQL 2012 and one of the secondaries on SQL 2016?
↧
CENTOS Failover Multiple Always On Availability Groups
Hello everyone.
I have a problem.
I have two CENTOS.
CENTOS 1: Installed MSSQL 2017 Standard
CENTOS 2: Installed MSSQL 2017 Standard
CENTOS 1 and CENTOS 02 configured SQL Always On Availability Groups.
I have 4 databases, I configured 4 Always On Availability Groups.
I configured Pacemaker for first group.
How do I config Pacemaker for 3 other groups?
Thanks you.
↧
Probe Ports 59999, 59998 etc.
Hi
I'm really struggling to understand the probe port part of Azure Always-on.
Where on the actual VM is this probe port set? I take it the probe port is different from the listener port?
Many thanks, I'm under pressure to actually get this working
↧
↧
SQL Server AG Authentication issue
SQL Server 2016 running on Windows Server 2012 participating in three replica availability group. All three nodes using gMSA for SQL Server services. gMSA has CONNECT to the instance and the endpoint. System's been working smoothly for over a year.
two out of three nodes behaving normally following windows patching and reboot.
third node can no longer connect to endpoints on other nodes, reporting :
Login failed for user 'domain\machine$'. Reason: Token-based server access validation failed with an infrastructure error. Login lacks Connect SQL permission. [CLIENT: <ip address>].
As I say, the sql services are running under a group managed service account and the AG's have behaved normally over the last year, which includes routine OS patching and restarts.
The computer object in the domain is not disabled nor is the SQL gMSA. The VCO is enabled.
Obvious remedy is to grand the machine account connect (instance and endpoint) on each node, but that doesn't answer they why this happened and what's going on.
I've restarted the SQL Service several times, even rebooted. SQL Server service comes back up just fine, but I can't get the primary replica on this AG to come up since it can't connect to the secondaries. Nor can I create new AGs for the same reason. I have deleted this particular AG and restored with recovery the databases to get the application back on line. If I can't figure this out then I'm left with building a new cluster node.
I'm not entirely sure I understand the error, but it seems as though the machine can't access the service account. Anyone have any suggestions?
↧
Re-create AlwaysOn Group
Hi expert,
if we recreate AlwaysOn Group with same name with old, do we need to recreate Distributed AlwaysOn Group too?
thanks for all reply
warm regard,
Urbel
↧
Suspend an Availability Database in Always On
Hi,
We have two VM with Always On installed and configured, we want to apply some changes in the replica, the plan is
- Suspend Availability Database on Primary
- Create a VM snapshot for replica
- Apply changes on replica
In case there is an issue and we need to rollback changes we need to restore a VM snapshot for replica and resume the vailability Database on Primary, is there anything I am missing ? do I need to stop the hourly Tlog backup on Primary ?
Thanks for your help and feebacks
↧
AlwaysOn enabled database property "Mirroring" options
Hi Experts
Version 2016 R2 Enterprises
I have two server always no enabled and Async mode. I did a failover and failed back between two nodes and the process and working fine
When I check with database property under "mirroring" and operating mode three options(High performance, High safety without automatic(sync) ,
High safety without automatic(async) shows in "grey colour" mode.
I understand this parameters related to Mirroring(not sure all three) and both cant enabled. I checked same properties with
normal DB and the options are same as "grey" (non enabled as a HA)
This issue raised some one check this properties whether enable DB always on or not.
Q1.Just checking with export knowledge that did we miss configuration done on alwayson" ?
Highly appreciate expert advise on this
↧
↧
SQL Server HA
Hi,
We have two SQL 2016 Std edition server and don't have shared storage, what is the method to configure HA.
Regards,
Mani
↧
Regarding Differential Backup in AlwayOn
Hi,
We are currenly using AlwayOn (SQL Server 2016 Ent) backup preference to Primary Replica.As per Microsoft Diff backup doesn't support on Secondary Replicas.
But in order to reduce load on primary we are planning to run backups in Secondary, but due to this limitation we are in big confusion and we can't avoid Diff backups.
These DB's are very critical and should run 24/7.
In this case what is the alternative?
↧
Basic availability groups when application has multiple databases
Iam currently looking into the Standard and Enterprise versions of SQL Server 2016 to see if what benefits we can get from Enterprise vs licensing costs. Iam currently looking into Basic Availability Groups and I was wondering the following:
Say I have an application which uses 4 databases. If I want to use Basic Availability Groups, then I need to create 4 groups and, preferably, 4 listeners. I would think that we can run into issues in this configuration, because these groups behave independently. For example, if 2 groups failover (lets say we have a listener for each group), then the others still run on the other server. You would think that this is not a scenario that you would encounter very often, but I have read stories that this can be possible when doing some research.
In theory this should work I think, because each DB has it's own VNN and therefore can be accessed separately, but my gut feeling says you should not use this configuration. What do you guys think?
↧