Hi all,
I've set up log shipping between two SQL 2012 servers in No Recovery mode.
In the secondary server, all the DBs are in Restoring status.
Now I want to learn the process to fail-over to the secondary server if the primary is unexpectedly down and cannot be accessible.
Thanks for your help,
DESCRIPTION: The operating system returned the error '32(The process cannot access the file because it is being used by another process.)' while attempting 'DeleteFile' on '\\mls-storage1\backup\sql4_backup\SQL4\UNI_MOUN1309\LOG\SQL4_UNI_MOUN1309_LOG_20110705_210005.trn'
at 'storage.cpp'(875).
I use Ola Hallengren's backup scripts; he suggested I inquire to the forums. I am particularly puzzled why the 'storage.cpp' mention since the log backup script is a SQL script.
Thank you, Tom
Hi,
I have a huge database which needs to be added to the availability group.
The documented way to perform this issue is BACKUP and RESTORE - in huge databases it consumes a lot of time.
Is there another way to have a database copy and to add it to availability group.
I have tried DETACH and ATTACH but couldn't add it to the avaliability group.
Please advise.
Regards, Asi Pesa
Hello,
As our domain changed, I have to move my own test virtual machines from one domain to another, and updated the server name, now when I tried to install new cluster, I got below error:
Node [NewServerName] appears to be a member of a cluster. It is either a member of an existing cluster or the node was not cleaned up after being evicted from a cluster. If you are sure this is not a member of a cluster run the Remove-ClusterNode cmdlet with the –Force parameter to clean up the cluster information from the node and then try to add it to the cluster again. The cluster node is already a member of the cluster.
When I tried to run Remove-ClusterNode [NewServerName]-force
Remove-ClusterNode : The cluster service is not running. Make sure that the service is running on all nodes in the
cluster.
There are no more endpoints available from the endpoint mapper
At line:1 char:1
+ Remove-ClusterNode SYDCO-VALZ-1a.sand.wtg.zone -force
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : ConnectionError: (:) [Remove-ClusterNode], ClusterCmdletException
+ FullyQualifiedErrorId : ClusterEndpointNotRegistered,Microsoft.FailoverClusters.PowerShell.RemoveClusterNodeComm
So I Ran Start-Cluster, but got different error:
WARNING: You do not have administrative privileges on the server '[OldServerName]'.So How can I remove all the old cluster information so I can start new installation?
Thanks,
Albert
There are 34 share-point databases we are planning to migrate from 2008 R2 to 2012 Always on.
Existing 2008 R2 environment is standalone. No HA/DR setup. But we are planning for HA/DR setup at 2012 environment.
Here is the 2012 Always On Setup: (TEST ENVIRONMENT)
DATACENTER1 (Main)
1. ServerSHARP1 ->Primary Replica ->Sync
2. ServerSHARP2 ->Secondary Replica ->SYNC
Datacenter (DR)
3.ServerSHARPDR ->This is another replica at DR location. ->Async
Always ON Group: AG_SHAREP_GP
Listener: sharp123
FQDN: sharp123.abc.com
My requirement is all 32 databases should participate in HA but i don't want DR, then i want remaining 2 database should participate in HA and DR because those 2 databases are very important.
STEPS i performed till now:
1. I moved (Copied) all 34 databases to ServerSHARP1
2.Added all 32 DB (except 2 dbs) databases to AG_SHAREP_GP.
3.Tested fail-over between ServerSHARP1 and ServerSHARP2 and everything is working fine and able to connect with listener/FQDN.
Now i stuck up at configuring those 2 database? how to setup these two databases for HA and DR?
Does these two databases require another AG Group,Listener and FQDN (for application access)? or can i use same?
either case how can i give connection string in application server? as we know that application server can't understand multiple FQDNS.
Please help me.
Dear All,
I am trying to setup a 2-Node SQL 2008 Cluster on Windows 2008R2 (64-bit) using the sliptstream (SP3). I am getting the following error in the end:
The cluster resource 'SQL Server' could not be brought online. Error: The group or resource is not in the correct state to perform the requested operation. (Exception from HRESULT: 0x8007139F)
When I check the SQL Server log, I see the following:
The SQL Server Network Interface library could not register the Service Principal Name (SPN) for the SQL Server service. Error: 0x2098, state: 15. Failure to register an SPN may cause integrated authentication to fall back to NTLM instead of Kerberos. This
is an informational message. Further action is only required if Kerberos authentication is required by authentication
Below is the output of setspn command that suggests SPN is registered:
D:>setspn -L <Domain Name>\<Service Account Name>
Registered ServicePrincipalNames for CN=<Service Account Name>,OU=Services Accounts,DC=<Domain Name>,DC=<Suffix of Domain Name>
Can you please guide me how to resolve this issue?
Regards,
Hello
I think theres something I'm missing about AG listeners. My test config is 1 SharePoint WFE & 2 SQL servers configured in an AAG.
WFE, SQL1 & SQL2 servers are all on the same subnet.
On the WFE, I configured an alias called SP15 to be used for the SQL servers. If I failover from SQL1 to SQL2 I just need to change where the alias is pointing on the WFE. So why do I need a listener? This works fine, albeit manually.
I have read on some posts that an automatic failover process is possible. This sounds ideal. How can I add a 2nd IP address to the listener when both SQL servers are on the same subnet? The GUI doesn't seem to allow this.
TIA
Dermot C
I have an active passive cluster on my primary Data center in NY and have a DR Active / passive SQL Cluster in TX. These are two separate clusters in the same domain using the same SQL server credentials.
Both clusters host an active / passive SQL instance. Lets call it SQLNY(Primary) and SQLTX (DR). I want to enable always On Availability group within
the two SQL Instances SQLNY and SQLTX. The listener will be SQLAG which will be used by the Application to connect to the SQL instance.
Is there a practical way to implement this? This will not only give me instant fail over within the NY (Primary) but also give me the flexibility to fail
over to TX.
I am using SQL 2014 Enterprise Edition on both clusters.
Any help will be much appreciated..
I have an active passive cluster on my primary Data center in NY and have a DR Active / passive SQL Cluster in TX. These are two separate clusters in the same domain using the same SQL server credentials.
Both clusters host an active / passive SQL instance. Lets call it SQLNY(Primary) and SQLTX (DR). I want to enable always On Availability group within
the two SQL Instances SQLNY and SQLTX. The listener will be SQLAG which will be used by the Application to connect to the SQL instance.
Is there a practical way to implement this? This will not only give me instant fail over within the NY (Primary) but also give me the flexibility to fail
over to TX.
I am using SQL 2014 Enterprise Edition on both clusters.
Any help will be much appreciated..
I have a situation where I have two servers in SQL Server 2012 R2 AlwaysOn Availability Group. One is primary and the other one being secondary. I am only running SharePoint Database on it.
Problem: I have run out of space on the primary server and about to run out of space at the secondary server. I have tried shrinking database transaction log files, but it returns an error that it cannot be shrunk as the database is in the AlwaysOn Availability Group.
Questions:
1. Several forums suggest that databases need to taken out of AlwaysOn Availability Group in order for the shrinking to work properply? is that correct? if so, what is procedure, I would appreciate step by step guidance. Thanks.
2. Would it have any impact on the database if it is taken out of availability group and then added back?
Hello,
I have to install several AG on a cluster for a whole SharePoint production farm, it's a nice to have (1 AG for Search database, 1 AG for Profil database, 1 AG for Content database, 1 for applicatif, etc...)
We have 2 Front End load balanced, 1 application server and 3 SQL HADR: 2 nodes on synchrone (sql 2014 enterprise licence) and the 3rd asynchrone (standard licence).
The SharePoint farm is configured with the SQL Alias on the primary node, then if there is a failover on node 1, I must move the sql Alias to the second node manualy, unless I'd configured this Alias to point on the AG listener of the availabitity group in order to use the automatic failover. But as we have several AG, should I create one listener per each AG ?
And wich AG listener should I have to configure on the SQL Alias then ?
Thanks for your responses.
Hello Everyone,
I have a web server that is on our DMZ subnet and I have a sql 2014 database server with Always on Availability Groups that is on our internal domain subnet. The failover cluster is on the internal domain subnet as well. I am trying to connect a web application, that is working off the .net 2.0 framework, to an SQL Server 2014 database using the Always on Availability Group Listener. The connection strings works perfect with the named instance of the sql server but when I try to use the Availability Group listener it timed out. I did some research online and was led to believe that increasing the connection time would resolve it. I did that and got a different error pertaining to a successful connection but an error occurred during the login process (Provider: TCP Provider, error: 0 - The specified network name is no longer available.) I just want to connect to an Availability Group Listener on the domain subnet. I have rules in the firewall to allow all services for the IP of the Listener. I switch back to the named instance of the same server and it works flawlessly. I have also connected to the Listener while running the application on the same subnet as the sql server without an issue. I have tried the IP instead of the Listeners name and still received the same error on the DMZ subnet. I'm at a cross roads. Do I continue to pursue this or do I try and convert the application to a later version of .net and hope that helps. Any information is valued and appreciated.
I'm running on Windows Server 2012 R2 on all servers.
The Web Server is using IIS 8.5
All Physical Machines except the replicas and webserver are virtual machines.
All Static IPs involved.
As mentioned all SQL Servers are 2014.
Thank you,
Mark
Hi, wondering if anyone have the same experience, after backing up the databases on node 1, i can check last backup time on that node, and it says the time i ran that backup. When i check the same on the other node (node 2) I get an older time, not the last time that database was backed up, even though the database is replicated.
This will be a problem since our monitoring system (ms system center operations manager, scom) is creating an alarm when it sees that backups on node 2 are older than 3 days..
Any suggestions, or am I doing something wrong?
Thanks in advance.
Hello all,
First off thank you all for your patience as I am not a DB Guy. I am an Infrastructure Engineer.
I have been given a problem to find a solution for and I'd love to get your input on this.
My client has on a physical server (A), the following:
1. MS SQL Server 2008R2
2. MS SQL Server (Reporting Server)
The data base is backed up fully daily to another physical server (B).
What the client would like to do is:
1. Backup just the Raw SQL Data with Tables and Views to Server B every 10 mins
Point to be noted is, there isn't any dedicated storage (NAS or SAN) just local disk storage on the server.
The reason for this is they want to run reports against this data every 10-15 mins...
How and what do I need to do to facilitate this? Can someone please point me in the right direction please...
Thank you so much for your time!
Thank you,
Jainesh.
I have Configured always on Availability groups between Server 1 Primary Replica(Active), server 2 Secondary Replica(Passive) on top of WCFS...
Listener Name: AGListner( CLIENTS/APPLICATIONS connect using this Name)
Testing Scenario 1(on Virtual Servers):
I have turned network down on Server 1(primary) , then secondary server (Passive ) one came ONLINE and this is now the primary and i was able to connect to AGListner...COOL
Testing Scenario 2(on Virtual Servers):
now When i try to SHUTDOWN/POWER OFF PRIMARY(current Active server),failover happened to Secondary successfully but lost cluster and lost AGListner and was not able to connect ....now applications which are trying to connect using AGListenr name will loose all connections
so, my question is does AlwaysOn Availability does not support Server SHUTDOWN/POWER OFF?or is there a way to resolve this? or am i doing wrong somewhere?
Please let me know
Good Day all,
I want to redirect the logshipping primary backup folder to another drive, could some one suggest me how to change the configurations steps to move the primary logship folder to another location within the same server!
Thank you'
K