Upgrading a S&S 5.3.0 failover cluster to 5.3.7

Hi!
we need to upgrade our S&S to 5.3.7. Currently we have S&S and DMM 5.3.0 in failover cluster.
In pre-prod, were we have no cluster, just a single DMM and a single S&S, we upgraded the S&S easily.
But when facing the procedure for upgrading the S&S in the Failover cluster, after reading the official Cisco docs, we have few doubts:
1) We know that we'll need to break the cluster, reverting to standalones, before upgrading, but, since we just need to upgrade the S&S to 5.3.7 (DMM remains 5.3.0), is it enough if we break only the S&S cluster and revert to standalones, while keeping the DMM failover cluster with no changes?
2) Once we have upgraded the active/primary, I don't understand point 4 of the upgrading procedure, where it says “Reimage the secondary DMM and Show and Share appliances. Install the same software release that you upgraded the primary appliances to.”?
What does “REIMAGE” mean? does it mean that we'll need to install the secondary unit from zero to 5.3.7 and then, when both are 5.3.7, re-do the failover cluster? Isn't it enough to break the cluster, upgrade each member to 5.3.7, and then re-do the cluster again? or does it mean that the secondary unit will be unusable after breaking the cluster?
Does any of you know any more specific guide (or your own experience) of upgrading a failover cluster?
many thanks from Spain,
DAVID

The Skype extension for Firefox has a long history of being problematic in Firefox. Various older version of that extension have been "blocklisted" by Mozilla from time to time due to causing a high number of Firefox crashes in the last 3 or 4 years. <br />
http://kb.mozillazine.org/Problematic_extensions
You don't need that Skype extension in Firefox to be able to use Skype '''or''' to use Firefox.

Similar Messages

Upgrading from SQL Server 2012 Standard to SQL Server 2014 Standard Failover Cluster

Goal: To upgrade my default instance from SQL Server 2012 to SQL Server 2014 in a failover cluster.
Given:
1) Operating System Windows 2012 R2
2) 2 Virtual Machines in a cluster with SQL Server as a Guest Cluster resource. The two VMS are called APPS08 and APPS09. They are our development environment that is setup similar to our production environment.
Problem: When running the SQL Server 2014 upgrade, I started on the VM that was not running the instance. I then moved onto upgrading on the node that was running the instance. As soon as the install attempt to failover the running instance
an install error occurred that it could not failover. After many install attempts I consistently received the error
The SQL Server Failover cluster instance name 'Dev01'
already exists as a cluster resource. Opening Failover cluster manager there is no record of a DEV01.
New Strategy: Create a SQLCluster called DEV07. At the end of the Install I get 'Resource for instance 'MSSQLSERVER' should not exists. Neither I nor my Windows 2012 guy understand what Resource the install may be referring to.
We do not see anything out of the ordinary.
Any suggestions as to what Resource may be seeing the default instance would be greatly appreciated.

Hi PSCSQLDBA,
As your description, you want to upgrade the default instance in SQL Server cluster.
>> 'SQL Server failover cluster instance name 'Dev01' already exists as cluster resource'
This error could occur when there is a previously used instance name which may not be removed completely.
To work around the issue, please use one of the ways below.
1. At command prompt, type Cluster res. This command will list you all the resources including orphan resources. To delete the orphan resource, type Cluster res <resource name>/delete.
For more information about the process, please refer to the article:
http://gemanjyothisqlserver.blogspot.in/2012/12/sql-2008r22012-cluster-installation.html
2. Delete DNS entries, and force a replication of DNS to the other DNS servers.
For more information about the process, please refer to the article:
http://jon.netdork.net/2011/06/07/failed-cluster-install-and-name-already-exists/#solution
>> 'Resource for instance 'MSSQLSERVER' should not exist'
This error could occur when you already have MSSQLSERVER as a resource in the cluster, which may not be removed completely. To work around the issue, you could rebuild the SQL Server cluster node.
Regards,
Michelle Li

Can I upgrade Server 2012R2 Standard to 2012R2 Datacenter while in a failover cluster?

I would like to know if it is supported to upgrade my Server 2012R2 Standard to 2012R2 Datacenter while in a failover cluster. I have a 3 node cluster all running Server 2012R2 standard with only a few VM's running on them at this time.
-Jim

Should be no problem. There are no technical differences between Standard and Datacenter. The difference is in the licensing.
I would evict a node, upgrade it, and add it back in. Rinse and repeat.
. : | : . : | : . tim

Cannot migrate VM in VMM but can in Failover Cluster Manager network adapters network optimization warning

I have a 4 node Server 2012 R2 Hyper-V Cluster and manage it with VMM 2012 R2. I just upgraded the cluster from 2012 RTM to 2012 R2 last week which meant pulling 2 nodes out of the existing cluster, creating the new R2 cluster, running the copy
cluster roles wizard since the VHDs are stored on CSVs, and then added the other 2 nodes after installing R2 on them, back into the cluster. After upgrading the cluster I am unable to migrate some VMs from one node to another. When trying to do
a live migration, I get the following notifications under the Rating Explanation tab:
Warning: There currently are not network adapters with network optimization available on host Node7.
Error: Configuration issues related to the virtual machine VM1 prevent deployment and must be resolved before deployment can continue.
I get this error for 3 out of the 4 nodes in the cluster. I do not get this error for Node10 and I can live migrate to that node in VMM. It has a green check for Network optimization. The others do not. These errors only affect
VMM. In the Failover Cluster Manager, I can live migrate any VM to any node in the cluster without any issues. In the old 2012 RTM cluster I used to get the warning but I could still migrate the VMs anywhere I wanted to. I've checked the network
adapter settings in VMM on VM1 and they are the same as VM2 which can migrate to any host in VMM. I then checked the network adapter settings of the VMs from the Failover Cluster Manager and VM1 under Hardware Acceleration has "Enable virtual machine
queue" and Enable IPsec task offloading" checked. I unchecked those 2 boxes refreshed the VMs, refreshed the cluster, rebooted the VM and refreshed again but I still could not live migrate VM1. Why is this an issue now but it wasn't before
running on the new cluster? How do I resolve the issue? VMM is useless if I can't migrate all my VMs with it.

I checked the settings on the physical nics on each node and here is what I found:
Node7: Virtual machine queue is not listed (Cannot live migrate problem VM's to this node in VMM)
Node8: Virtual machine queue is not listed (Cannot live migrate problem VM's to this node in VMM)
Node9: Virtual machine queue is listed and enabled (Cannot live migrate problem VM's to this node in VMM)Node10: Virtual machine queue is listed and enabled (Live Migration works on all VMs in VMM)
From Hyper-V or the Failover Cluster manager I can see in the network adapter settings of the VMs under Hardware Acceleration that these two settings are checked "Enable virtual machine queue" and Enable IPsec task offloading". I unchecked those
2 boxes, refreshed the VMs, refreshed the cluster, rebooted the VM and refreshed again but I still cannot live migrate the problem VMs.
It seems to me that if I could adjust those VM settings from VMM that it might fix the problem. Why isn't that an option to do so in VMM?
Do I have to rebuild the VMM server with a new DB and then before adding the Hyper-V cluster uncheck those two settings on the VM's from Hyper-V manager? That would be a lot of unnecessary work but I don't know what else to do at this point.

SQL 2012 Failover Cluster to 2014

Hi,
we have recently purchased SQL 2014 std edition with SA (VLSC), one of our guy downloaded SQL 2012 instead of 2014 by mistake and installed as failover cluster. I wanted to ask whether should I upgrade to SQL 2014 or uninstall SQL 2012 and install 2014 fresh.
In 2014, secondary server used for failover support does not need to be separately licensed for sql server as long as it is truly passive and primary SQL server is covered with active SA.
We have installed 2012 in other fashion, 4 cores on primary and 4 cores on secondary, now we just want to assign 8 cores to primary and 8 to secondary to get 2014 benefit. Is it possible using upgrade or a fresh install is required.
I Appreciate inputs from experts.

Hello,
You can upgrade the cluster using the instructions provided on the following article.
https://msdn.microsoft.com/en-us/library/ms191295.aspx
I cannot provide you answers about questions related to licensing. For licensing questions, please call Microsoft Licensing at 1-800-426-9400, Monday through Friday,
6:00 A.M. to 6:00 P.M. (Pacific Time) to speak directly to a Microsoft licensing specialist. You can also visit the following site for more information and support on licensing issues:
http://www.microsoft.com/licensing/mla/default.aspx
Hope this helps.
Regards,
Alberto Morillo
SQLCoffee.com

Guest two node Failover Cluster with SAS HBA and Windows 2012 R1

Hi all, i have two IBM x3560 brand new servers with V3700 IBM Storage. The Servers are connected to the storage through four SAS HBA adabters (two HBA's on each server). I want to create a two node guest Fileserver Failover Cluster. I can present the
LUN's to the guest machines, but when i 'm running the cluster creation wizard it can't see any disk. I can see the disks on disk management console. Is there any way to achive this (the cluster creation) using my SAS HBA presented
disks, or i have to use iSCSI to present the disks to my cluster?
Thank you in advance, George

Hi all, i have two IBM x3560 brand new servers with V3700 IBM Storage. The Servers are connected to the storage through four SAS HBA adabters (two HBA's on each server). I want to create a two node guest Fileserver Failover Cluster. I can present the
LUN's to the guest machines, but when i 'm running the cluster creation wizard it can't see any disk. I can see the disks on disk management console. Is there any way to achive this (the cluster creation) using my SAS HBA presented
disks, or i have to use iSCSI to present the disks to my cluster?
Thank you in advance, George
1) Update to R2 and use shared VHDX which is a better way to go. See:
Shared VHDX
http://blogs.technet.com/b/storageserver/archive/2013/11/25/shared-vhdx-files-my-favorite-new-feature-in-windows-server-2012-r2.aspx
Clustering
Options
http://blogs.technet.com/b/josebda/archive/2013/07/31/windows-server-2012-r2-storage-step-by-step-with-storage-spaces-smb-scale-out-and-shared-vhdx-virtual.aspx
2) If you want to stick with non-R2 (which is a BAD idea b/c tons of reasons) you can spawn an iSCSI target on top of your storage, make it clustered and make it provide LUs to your guest VMs. See:
iSCSI Target in Failover
http://technet.microsoft.com/en-us/library/gg232632(v=ws.10).aspx
iSCSI Target Failover Step-by-Step
http://techontip.wordpress.com/2011/05/03/microsoft-iscsi-target-cluster-building-walkthrough/
3) Use third-party software providing clustered storage (active-active) out-of-box.
I would strongly recommend to upgrade to R2 and use shared VHDX.
StarWind VSAN [Virtual SAN] clusters Hyper-V without SAS, Fibre Channel, SMB 3.0 or iSCSI, uses Ethernet to mirror internally mounted SATA disks between hosts.

2008R2 to 2012R2 = Failover Cluster Manager not found ..gray out feature.

Hello everyone,
I just upgraded from our Hyper-V host running Windows Server 2008R2 to 2012R2,
I didn't get any errors during the upgrade and everything looked fine except that the failover cluster manager is no longer exist ..I went to add it from the server manager and found that the feature already exist but it is grayed out, I can not remove it and
add it again!
how to get the failover manager cluster working again ?
Thanks
Misbah

ok, the fix seems simple,
I needed to go from server manager and select remove role/features and then re-add it.
going to add roles/feature will not allow me to remove any feature ..it is just for adding features.

Good device to put Instance root directory on a SQL Server 2012 Always On Failover Cluster ?

Hello, I'm currently testing SQL Server 2012 AlwaysOn Failover Cluster.
I wonder if I installed it correctly : I installed the software on both server with the instance root directory set to a directory on a cluster shared module.
The reason why I'm not sure is because, when I wanted to upgrade from SP1 to SP2, I wanted to do it first on the passive node, but it failed for most of the components it had to upgrade. So I first upgraded the active node then failover and upgraded the
newly active node.
I installed SQL Server this way because our system admins don't like us to install in on C:\ for their own reasons (maybe backup, or something ...)
I'm pretty sure there is something wrong. What's your point ?
Thanks in advance.

>I wonder if I installed it correctly : I installed the software on both server with the instance root directory set to a directory on a cluster shared module.
Nope.
SQL Server 2012 and earlier don't support data files on CSV volumes (SQL 2014 does).
And for any version of SQL Server the SQL Server instance directory should not be on a clustered disk. The Installation is local to each node, so should be on a non-clustered disk. It may be supported to put the instances in different locations
on the same clustered disk, but I wouldn't recommend it.
Installing the SQL Binaries on C:\ is fine. If you have another local volume you can also install them there.
David
David http://blogs.msdn.com/b/dbrowne/

RBS Licensing on a SQL Server Standard 2012 Failover Cluster

I am planning to implement a Sharepoint 2013 installation which is primarily to be used for Document Storage. We are considering using Sharepoint RBS with Filestream with SQL 2012 Standard and as far as I can see on our non-production environments this works
without any issue - i.e. we enable filestream and RBS with Sharepoint and SQL and everything works as expected on our non production systems. In non production we have single SQL Server nodes.
However, in production we have planned to have a 2 node SQL 2012 Standard failover cluster.
On this page, it indicates
"To run RBS on a remote server, you must be running SQL Server 2008 R2 Enterprise on the server that is running SQL Server where the
metadata is stored in the database."
My question is : Am I entitled to use RBS with Filestream on a SQL 2012 Standard Failover Cluster, or is SQL Enterprise required.
If enterprise is required, we will have to remove the RBS. I have reviewed the links below, but cannot see a definitive answer from a licensing perspective
http://social.technet.microsoft.com/Forums/en-US/76e86936-b7ee-4571-aa02-f45b80867515/which-edition-for-sql-server-2008-r2-with-sharepoint-2010-no-foundation?forum=sharepointadminprevious
http://social.msdn.microsoft.com/Forums/sqlserver/en-US/2b04979f-c619-48a4-b0e4-3add00345fb0/sql-server-2008-edition-comparisons-in-terms-of-high-availability-rbs?forum=sqldisasterrecovery

Hi antrimcoaster,
Indeed, in Microsoft official document, all SQL editions (Express, Standard, Enterprise…) of SQL Server 2008 and SQL Server 2008R2 support RBS (Remote Blob Store), however, as your post, if you run RBS on a remote server, we recommend you use Enterprise
version especially you want to deploy Remote BLOB Storage with SQL Server 2012 in Production environment. Usually, Enterprise edition is more for mirroring, supporting more RAM/CPU, and custom RBS providers and multiple nodes cluster.
If you had setup and configured RBS successfully with SQL Server 2012 standard, and now you need to want to upgrade to SQL Server 2012 Enterprise, I recommend you reconfigure your blob store, you can review the following similar article.
https://community.dynamics.com/ax/b/axdilip/archive/2012/10/22/configuring-and-implementing-sharepoint-2010-rbs-remote-blob-storage-with-sql-server-2012-part-1.aspx
In addition, for more detailed information regarding to the license issue, please call 1-800-426-9400, Monday through Friday, 6:00 A.M. to 6:00 P.M. (Pacific Time) to speak directly to a Microsoft licensing specialist. For international customers, please
use the Guide to Worldwide Microsoft Licensing Sites to find contact information in your locations.
Thanks,
Sofiya Li
If you have any feedback on our support, please click
here.
Sofiya Li
TechNet Community Support

Reporting Services as a generic service in a failover cluster group?

There is some confusion on whether or not Microsoft will support a Reporting Services deployment on a failover cluster using scale-out, and adding the Reporting Services service as a generic service in a cluster group to achieve active-passive high
availability.
A deployment like this is described by Lukasz Pawlowski (Program Manager on the Reporting Services team) in this blog article
http://blogs.msdn.com/b/lukaszp/archive/2009/10/28/high-availability-frequently-asked-questions-about-failover-clustering-and-reporting-services.aspx. There it is stated that it can be done, and what needs to be considered when doing such a deployment.
This article (http://technet.microsoft.com/en-us/library/bb630402.aspx) on the other hand states: "Failover clustering is supported only for the report server database; you
cannot run the Report Server service as part of a failover cluster."
This is somewhat confusing to me. Can I expect to receive support from Microsoft for a setup like this?
Best Regards,
Peter Wretmo

Hi Peter,
Thanks for your posting.
As Lukasz said in the
blog, failover clustering with SSRS is possible. However, during the failover there is some time during which users will receive errors when accessing SSRS since the network names will resolve to a computer where the SSRS service is in the process of starting.
Besides, there are several considerations and manual steps involved on your part before configuring the failover clustering with SSRS service:
Impact on other applications that share the SQL Server. One common idea is to put SSRS in the same cluster group as SQL Server. If SQL Server is hosting multiple application databases, other than just the SSRS databases, a failure in SSRS may cause
a significant failover impact to the entire environment.
SSRS fails over independently of SQL Server.
If SSRS is running, it is going to do work on behalf of the overall deployment so it will be Active. To make SSRS Passive is to stop the SSRS service on all passive cluster nodes.
So, SSRS is designed to achieve High Availability through the Scale-Out deployment. Though a failover clustered SSRS deployment is achievable, it is not the best option for achieving High Availability with Reporting Services.
Regards,
Mike Yin
If you have any feedback on our support, please click
here
Mike Yin
TechNet Community Support

Difference between scalable and failover cluster

Difference between scalable and fail over cluster

A scalable cluster is usually associated with HPC clusters but some might argue that Oracle RAC is this type of cluster. Where the workload can be divided up and sent to many compute nodes. Usually used for a vectored workload.
A failover cluster is where a standby system or systems are available to take the workload when needed. Usually used for scalar workloads.

Install Guide - SQL Server 2014, Failover Cluster, Windows 2012 R2 Server Core

I am looking for anyone who has a guide with notes about an installation of a two node, multi subnet failover cluster for SQL Server 2014 on Server Core edition

Hi KamarasJaranger,
According to your description, you want configure a SQL Server 2014 Multi-Subnet failover Cluster on Windows Server 2012 R2. Below are the whole steps for the configuration. For the detailed steps about the configuration, please download
and refer to the
PDF file.
1.Add Required Windows Features (.NET Framework 3.5 Features, Failover Clustering and Multipath I/O).
2.Discover target portals.
3.Connect targets and configuring Multipathing.
4.Initialize and format the Disks.
5.Verify the Storage Replication Process.
6.Run the Failover Cluster Validation Wizard.
7.Create the Windows Server 2012 R2 Multi-Subnet Cluster.
8.Tune Cluster Heartbeat Settings.
9.Install SQL Server 2014 on a Multi-Subnet Failover Cluster.
10.Add a Node on a SQL Server 2014 Multi-Subnet Cluster.
11.Tune the SQL Server 2014 Failover Clustered Instance DNS Settings.
12.Test application connectivity.
Regards,
Michelle Li

Mounted Volume not shwoing up with Windows 2012 R2 failover cluster

Hi
We configured some drives as mounted volumes and configured it with Failover cluster. But it's not showing up the mounted volume details with Cluster Manager, it's showing the details as seen below
Expect support from someone to correct this issue
Thanks in advance
LMS

Hi LMS,
Are you doubt about the disk shown as GUID? Cluster Mount point Disk is showing as a Volume GUID in server 2012 R2 Failover Cluster I creating a mountpoint inside the cluster
and had the same behavior, instead of mount point name we had the volume GUI after volume label, that must by design.
How to configure volume mount points on a Microsoft Cluster Server
http://support.microsoft.com/kb/280297
I’m glad to be of help to you!
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Support, contact [email protected]

The Cluster Service function call 'ClusterResourceControl' failed with error code '1008(An attempt was made to reference a token that does not exist.)' while verifying the file path. Verify that your failover cluster is configured properly.

I am experiencing this error with one of our cluster environment. Can anyone help me in this issue.
The Cluster Service function call 'ClusterResourceControl' failed with error code '1008(An attempt was made to reference a token that does not exist.)' while verifying the file path. Verify that your failover cluster is configured properly.
Thanks,
Venu S.
Venugopal S ----------------------------------------------------------- Please click the Mark as Answer button if a post solves your problem!

Hi Venu S,
Based on my research, you might encounter a known issue, please try the hotfix in this KB:
http://support.microsoft.com/kb/928385
Meanwhile since there is less information about this issue, before further investigation, please provide us the following information:
The version of Windows Server you are using
The result of SELECT @@VERSION
The scenario when you get this error
If anything is unclear, please let me know.
Regards,
Tom Li

Very Strange Network Issue With Two Guests on 2012 R2 Hyper-V Failover Cluster

Hi all. We're having a odd issue with two guests on our 2012 R2 failover cluster.
In a nutshell, if we shutdown a particular server (I'll call it Server A) another totally different server (Server B) on the same node loses it's network connectivity to the domain. If we start server A back up, network connectivity returns on server B.
At first I thought server A might be running a service that was somehow linked to server B, so I decided to disable server A's NIC. Interestingly, that had no affect on server B's connectivity.
The next step I tried was pausing server A and again, no adverse affect on server B's connectivity.
Next step was to live migrate server A to another node. This action did
cause server B to lose its network connection.
One other clue is that if I ping server B from either of the Hyper-V hosts in the cluster, I never lose network connection to server B.
So I would suspect this is some network issue on the cluster, but I'm kind of at a loss where to go from here.
Has anyone seen this behavior before or does anyone have any troubleshooting suggestions I can try?
Thanks!
George Moore

Hi Sir,
I'v never seen this before .
>>Next step was to live migrate server A to another node. This action did
cause server B to lose its network connection.
They are connecting to same virtual switch ?
First please run cluster validation to check if there is any error .
If it is ok , please try the following items for troubleshooting :
1. shutdown serverA serverB
2. then add another virtual NIC for serverB
3. start server B check if the issue happens to both "old" and "new" virtual NIC .
In addition , you can live migrate both A and B to another node , then try to live migrate A to the original node .
If the issue persists , I would suggest you to remove that virtual switch on both nodes then re-create them .
Best Regards,
Elton Ji
If it is not the answer please unmark it to continue
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact [email protected] .

Upgrading a S&S 5.3.0 failover cluster to 5.3.7

Similar Messages

Maybe you are looking for