Adding SQL Cluster to MARS

What is the best way to add the physical servers and SQL server instances to MARS?
As a bit of background we have a SQL cluster with 3 physical servers and each one has an ip address. There are also 3 SQL instances with an associated IP address. These are similar in nature to virtual addresses. Both the physical servers and the SQL instances have their own netbios name.
Do we add both the physical servers and the SQL instances to MARS?

Hi Fredrik,
There are alot of events on the IDSSM but these events aren't appeared on MARS although IDSSM is successfully discovered by MARS. That's also happened with Cisco NAC appliance which i added it to MARS but there are no incidents for it on MARS.

Similar Messages

Disk and tempdb configuration for multiple Instances in one SQL cluster

Hi Everyone ,
I am in planing to build SQL Cluster on Blade server . Two blades are allocated for SQL. and planning to cluster those two blades. It will be windows 2012R2 and SQL 2012/2014. Initially it was plan to put most of database on one SQL instance. but
due to other requirements I will be Installing more SQL Instance on same cluster.
for now Everything will be on RAID 10 but do not have more details about storage yet that how it will get configured
256 GB Ram on Each blade server.
1) what are the Disc configuration recommendation for data and log files when each instance get added?
2) what are the Disc configuration recommendation for tempdb files when each instance get added?
3) Each Instance Tempdb file on Same drive is good practice?
Any other Best practices should follow for this setup?
Thank you ....
Please Mark As Answer if it is helpful. \\Aim To Inspire Rather to Teach A.Shah

1) what are the Disc configuration recommendation for data and log files when each instance get added?
Keep both the sql instances in diffèrent drives.read the below link for RAID levels and according to your usage you can cofigure it..
http://technet.microsoft.com/en-us/library/ms190764%28v=sql.105%29.aspx
Storage best practice.
http://technet.microsoft.com/en-us/library/cc966534.aspx
2) what are the Disc configuration recommendation for tempdb files when each instance get added?
Its good to have sepreate drive for tempdb and each instance too with correct allocation or configuration..RAID5
for data if you must, but have to keep a spare drive around for that.
Best is 10 everywhere. If that's too expensive, then 1 or 10 for log and 5 for data (and 10 for TempDB)
RAID 5 is terrible for logs because it has a high write overhead. Tran logs are write-heavy, not read-heavy.
3) Each Instance Tempdb file on Same drive is good practice?
Tempdb configuration is depends, its completelty based on your server and tempdb usage..Make sure to have equal size for all the files in tempdb, As a general rule, if the number of logical processors is less than 8, use the same number of data files
as logical processors. If the number of logical processors is greater than 8, use 8 data files and then if contention continues, increase the number of data files by multiples of 4 (up to the number of logical processors) until the contention is reduced to
acceptable levels or make changes to the workload/code.
http://www.confio.com/logicalread/sql-server-tempdb-best-practices-initial-sizing-w01/#.U7SStvFBr2k
http://msdn.microsoft.com/en-us/library/ms175527(v=sql.105).aspx
http://www.sqlskills.com/BLOGS/PAUL/post/A-SQL-Server-DBA-myth-a-day-(1230)-tempdb-should-always-have-one-data-file-per-processor-core.aspx
Raju Rasagounder Sr MSSQL DBA

Sql cluster with Always on

Hi
I have 2 sites Ho & DR
I have 2 sql servers in each site
I need to make on each site sql cluster and between the 2 sites we need to make always on
please need the steps for this scenario
MCP MCSA MCSE MCT MCTS CCNA

Hi Yasser,
According to your description, you want to setup a disaster recovery solution combining SQL Server Failover Cluster in Primary Datacenter and Availability Group on a SQL Server Failover Cluster in Secondary Datacenter. Assume that, in the Primary DataCenter,
SQL_PV is the FCI instance and CLP_1 and CLP_2 are the two nodes. In the Secondary DataCenter, SQL_SV is the FCI instance and CLS_1 and CLS_2 are the two nodes as the screenshot below shows.
To achieve the goal, you could follow the steps below:
1.Add two nodes CLS_1 and CLS_2 from secondary datacenter into the existing
Windows Server Failover Cluster(WSFC). Please note that all nodes for an availability group must exist on a single WSFC within the same Active Directory domain, even between datacenters.
2.Configure Shared Storage for both CLS_1 and CLS_2 nodes.
3.Install FCI instance of SQL 2012 Enterprise edition using "New SQL Server Failover Cluster Installation" and join the other secondary node using Add node to a SQL Server failover Cluster.
4.Enable Always on Availability Group on newly installed FCI.
5.Define the possible owner for each SQL Server FCI as the following:
a. Go to "SQL Server" services on the Cluster instance under SQL_PV group and go to SQL Properties. Under Advanced Policies, choose only CLP_1 and CLP_2 as possible owner for SQL_PV.
b. Go to "SQL Server" services on the Cluster instance under SQL_SV group and go to SQL Properties. Under Advanced Policies, choose only CLS_1 and CLS_2 as possible owner for SQL_SV.
For more information about the process, please refer to Scenario 2 in the article:
http://www.mssqltips.com/sqlservertip/3150/adding-sql-server-alwayson-availability-groups-to-existing-failover-clusters/
Regards,
Michelle Li
If you have any feedback on our support, please click
here.

SQL cluster 2008 R2 migration to new Hardware in VM

Hi,
We have a task to migrate existing Physical SQL Cluster DB to new Hardware but in VM. (cannot argue with the client)
hence our plan is to install new Cluster in VM with same Windows and SQL version i.e Win 2K8 R2 ENT w/SP and SQL 2K8
R2 STD w/SP and use SQL mirroring option for the DB to migrate on the new Server (keeping the downtime to as low as possible and advantage of bringing the old server online in case of any issues..)
Below points are for a single instance, couple of DB to migrate:
Keep the physical production server running
In-Parallel build New SQL Cluster in VM (keep same version windows/sql)
Keep Same drive letter for Quorum, MSDTC, DATA, LOG & Backup
Keep the same Instance Name, SQL Network Name can be different (will be changed to old network name once the PROD is shutdown)
Check all logins windows and SQL to be same on both the clusters
Copy all the jobs, SSIS packages etc.. .create the location folder as per current server on the VM SQL Cluster
Perform full backup of old cluster company-db databases or use the existing latest backup (full, differential, transaction)
Restore databases in the new cluster with no recovery so additional log file or differential backup can be restored
Create SQL Mirroring for the Database and select the principal server (old cluster) and the mirror server (new VM cluster)
Choose mirroring without witness ( no auto failover as we don’t need the old server later)
Start the mirroring – (hopefully everything synchronized and working)
During the downtime –
Stop the application/ client connection – if possible
Failover the DB through Mirroring option
Once the mirrored server becomes Principal and data is accessible – stop the mirroring
Now the new VM SQL Cluster DB is online
Shutdown the old cluster company-db (Node1 & Node2)
Come back to VM SQL Cluster and change the Network name to the old server network name (so that client connections are not affected)
Check if the DNS entries are updated with correct name and IP address
Delete DNS entries for old company-db on DNS Servers if not deleted, delete the old server SQL network name in computer object
Stop SQL Resources on the new VM SQL Cluster (take it offline all the resources)
Bring online the SQL Resource and make sure the SQL resources are online and new network name is reachable
Wait till you see machine name company-db in active directly (AD) and DNS server will have entry for company-db
Verify connectivity for company-db from outside.
If things are not going as per the plan then shut down the new VM cluster
Revert back the DNS settings
Power up the Old SQL Server
The DB will show “restoring mode” – use command to make it online “RESTORE DATABASE (dbname) WITH RECOVERY”
Check the DB
Start using the OLD server again
Troubleshoot the failed scenario ;)
Need to know if the above steps are okay, and any consideration once the new VM SQL Cluster is online.
Kindly let me know if there anything else to transfer apart from the logins, jobs, folder location etc.. !!
Many Thanks

Hello,
Well if you don’t change the instance name (name = ABC) then its OK.
Try the following resources about transferring SQL Server logins:
http://support.microsoft.com/kb/918992/en-us
http://www.mssqltips.com/sqlservertip/2081/transfer-sql-server-jobs-task-and-transfer-sql-server-logins-task-in-ssis/
Hope this helps.
Regards,
Alberto Morillo
SQLCoffee.com

An error occurred while adding the Cluster to the list

Hello,
I've installed the HFM 9.3.1 client on a Windows Server 2003 machine and now I'm attempting to configure it. I get all the way to the Server/Cluster Registration and when I try to add my one and only HFM application server to the list I'm present with this error.
"An error occurred while adding the Cluster to the list".
I don't see anything of use in the config tool log and as a result, I'm stuck. The odd thing is that not more than 10 minutes previously I added just finished installing the HFM client on another Windows Server 2003 machine and it installed / configured perfectly.
What am I missing?
Thanks!

You may have a DNS error of sorts. From a command line on the server which presents the error, ping the servername you are trying to reach. Do not use the cluster name, but instead use the server name or IP address. If you successfully reach it, use this in the registration utility. Once the server has been reached, it will return the cluster's name. If you cannot reach it using ping, focus on the underlying DNS problem.
--Chris

Sharepoint 2010 farm Sql cluster

hello,
i have sharepoint farm with 3 server ( Web front , Sql , search server )
can i make sql cluster to sql with 3 sql server or it be must before begin install sharepoint farm
thanks
Nour

Your question isn't very clear but i think i understand.
You have an existing farm with a single SQL server.
You want to upgrade your single SQL server to a clustered SQL installation.
Doing so is not easy, you can't upgrade a single server SQL install to a clustered install as far as I know. You'd need to re-build the SQL server as a single node cluster and add the new servers to make the full cluster before moving the SharePoint databases
over.
In addition you'd need to use SQL Aliases to point to the new clustered SQL address. If you've already used them then that's great, if not you'd need to use the old, single server, address as the Alias address and point it to the cluster.
In short: You can do it later but it's quite tricky and best done before you install SharePoint.

SQL Cluster - Unable to obtain IP Address from System Center IP Pool

Hi everyone,
we are trying to deploy a SQL cluster into a windows azure pack tenant cloud.
Our azure pack environment contains:
- 4X Hyper-V server in a failover cluster
- 1X SCVMM server
- multiple WAP server
Steps we have done:
-   Windows failover cluster is installed and configured successfully
-   Quorum disk was configured successfully
-   SQL server 2014 installation (via static IP) is successfully. But routing between the VMs is not possible.
-   SQL server 2014 installation (via DHCP) fails at the end of the installation with following error:
       -> We used DHCP to obtain an IP from the scvmm IP pool.
(01) 2015-04-22 15:29:11 Slp: Running Action: cluster_ip_address_cluster_config_Cpu64
(01) 2015-04-22 15:29:11 Slp: Action Data:
(01) 2015-04-22 15:29:11 Slp:   Feature = SQL_Engine_Core_Inst_sql_engine_core_inst_Cpu64
(01) 2015-04-22 15:29:11 Slp:   Scenario = install
(01) 2015-04-22 15:29:11 Slp:   Timing = ConfigNonRC
(01) 2015-04-22 15:29:11 Slp:   ConfigObjectType = Microsoft.SqlServer.Configuration.ClusterConfiguration.ClusterIPAddressPrivateConfigObject
(01) 2015-04-22 15:29:11 Slp:   FeatureName = SQL_Engine_Core_Inst
(01) 2015-04-22 15:29:11 Slp:   FeatureCpuType = Cpu64
(01) 2015-04-22 15:29:11 Slp:   FeaturePackageId = sql_engine_core_inst
(01) 2015-04-22 15:29:11 Slp:   FeatureClusterState = CompleteFailoverCluster
(01) 2015-04-22 15:29:11 Slp: Creating IPv4 address 'SQL IP Address 1 (SQLADFS)'.
(01) 2015-04-22 15:29:11 Slp: Creating cluster resource 'SQL IP Address 1 (SQLADFS)' of type 'IP Address' in group 'SQL Server (ADFS)'
(01) 2015-04-22 15:29:11 Slp: Bringing IP address resource 'Type='IP Address' NetworkName='Cluster Network 1' Group='SQL Server (ADFS)' Resource='SQL IP Address 1 (SQLADFS)'' online
(01) 2015-04-22 15:29:11 Slp: Bringing cluster resource 'SQL IP Address 1 (SQLADFS)' online
(01) 2015-04-22 15:29:12 Slp: Prompting user if they want to retry this action due to the following failure:
(01) 2015-04-22 15:29:12 Slp: ----------------------------------------
(01) 2015-04-22 15:29:12 Slp: The following is an exception stack listing the exceptions in outermost to innermost order
(01) 2015-04-22 15:29:12 Slp: Inner exceptions are being indented
(01) 2015-04-22 15:29:12 Slp:
(01) 2015-04-22 15:29:12 Slp: Exception type: Microsoft.SqlServer.Configuration.Cluster.ResourceOnlineException
(01) 2015-04-22 15:29:12 Slp:     Message:
(01) 2015-04-22 15:29:12 Slp:         The cluster resource 'SQL IP Address 1 (SQLADFS)' could not be brought online. Error: There was a failure to call cluster code from a provider. Exception message: Generic failure
. Status code: 5023. Description: The group or resource is not in the correct state to perform the requested operation.
(01) 2015-04-22 15:29:12 Slp:         .
(01) 2015-04-22 15:29:12 Slp:     HResult : 0x86d8003a
(01) 2015-04-22 15:29:12 Slp:         FacilityCode : 1752 (6d8)
(01) 2015-04-22 15:29:12 Slp:         ErrorCode : 58 (003a)
(01) 2015-04-22 15:29:12 Slp:     Data:
(01) 2015-04-22 15:29:12 Slp:       resourceName = SQL IP Address 1 (SQLADFS)
(01) 2015-04-22 15:29:12 Slp:       errorMessage = There was a failure to call cluster code from a provider. Exception message: Generic failure . Status code: 5023. Description: The group or resource is not in the correct state
to perform the requested operation.
(01) 2015-04-22 15:29:12 Slp:       WatsonData = Microsoft.SqlServer.Configuration.Cluster.ResourceOnlineException@58
(01) 2015-04-22 15:29:12 Slp:       DisableRetry = true
(01) 2015-04-22 15:29:12 Slp:     Inner exception type: Microsoft.SqlServer.Configuration.Cluster.ClusterProviderDetailedException
(01) 2015-04-22 15:29:12 Slp:         Message:
(01) 2015-04-22 15:29:12 Slp:                 There was a failure to call cluster code from a provider. Exception message: Generic failure . Status code: 5023. Description: The
group or resource is not in the correct state to perform the requested operation.
(01) 2015-04-22 15:29:12 Slp:                 .
(01) 2015-04-22 15:29:12 Slp:         HResult : 0x86d70002
(01) 2015-04-22 15:29:12 Slp:                 FacilityCode : 1751 (6d7)
(01) 2015-04-22 15:29:12 Slp:                 ErrorCode : 2 (0002)
(01) 2015-04-22 15:29:12 Slp:         Data:
(01) 2015-04-22 15:29:12 Slp:           ExceptionMessage = Generic failure
(01) 2015-04-22 15:29:12 Slp:           StatusCode = 5023
(01) 2015-04-22 15:29:12 Slp:           Description = The group or resource is not in the correct state to perform the requested operation.
(01) 2015-04-22 15:29:12 Slp:           WatsonData = Microsoft.SqlServer.Configuration.Cluster.ClusterProviderDetailedException@2
(01) 2015-04-22 15:29:12 Slp:         Stack:
(01) 2015-04-22 15:29:12 Slp:                 at Microsoft.SqlServer.Configuration.Cluster.WmiClusterResource.Online(Int32 timeout)
(01) 2015-04-22 15:29:12 Slp:                 at Microsoft.SqlServer.Configuration.Cluster.ClusterResource.Online(Int32 timeout)
(01) 2015-04-22 15:29:12 Slp:         Inner exception type: System.Management.ManagementException
(01) 2015-04-22 15:29:12 Slp:             Message:
(01) 2015-04-22 15:29:12 Slp:                         Generic failure
(01) 2015-04-22 15:29:12 Slp:             HResult : 0x80131501
(01) 2015-04-22 15:29:12 Slp:             Data:
(01) 2015-04-22 15:29:12 Slp:               WmiErrorCode = Failed
(01) 2015-04-22 15:29:12 Slp:               WatsonData = Failed@5023
(01) 2015-04-22 15:29:12 Slp:               Description = The group or resource is not in the correct state to perform the requested operation.
(01) 2015-04-22 15:29:12 Slp:               ErrorType = 1
(01) 2015-04-22 15:29:12 Slp:               Operation = ExecMethod
(01) 2015-04-22 15:29:12 Slp:               ParameterInfo = MSCluster_Resource.Name="SQL IP Address 1 (SQLADFS)"
(01) 2015-04-22 15:29:12 Slp:               ProviderName = WinMgmt
(01) 2015-04-22 15:29:12 Slp:               StatusCode = 5023
(01) 2015-04-22 15:29:12 Slp:             Stack:
(01) 2015-04-22 15:29:12 Slp:                         at System.Management.ManagementException.ThrowWithExtendedInfo(ManagementStatus errorCode)
(01) 2015-04-22 15:29:12 Slp:                         at System.Management.ManagementObject.InvokeMethod(String methodName, ManagementBaseObject
inParameters, InvokeMethodOptions options)
(01) 2015-04-22 15:29:12 Slp:                         at Microsoft.SqlServer.Configuration.WMIInterop.Resource.BringOnline(UInt32 TimeOut)
(01) 2015-04-22 15:29:12 Slp:                         at Microsoft.SqlServer.Configuration.Cluster.WmiClusterResource.Online(Int32 timeout)
(01) 2015-04-22 15:29:12 Slp: ----------------------------------------
We have tried to reinstall the servers multiple times, without result.
Can anyone assist us in this case?
Thanks
Kind Regards
Julian

Hi Darryl,
thanks for your supply.
We don't have an DHCP in the Cloud. System Center DHCP is used for assigning IP addresses and routing inforamtion to the vms.
This works fine for assigning IP addresses to the vms.
At my current point of understanding network virtualisation with system Center, we do not have an alternative to this way of assigning IP addresses.
Kind Regards
Julian

Question on sql cluster failover behaviour

Hi Experts,
I have a doubt on SQL Cluster.
In SQL cluster, If we MOVE the group or failover the group to another node what happens to the user connections(say 100 conn's) and ongoing open transactions during failover?
Will all connections gets disconnected and open transactions gets rollbacked or the connections and txns will be moved to other node?
Could anyone shed some insight on this?
Thank you.

All connections get disconnected an ongoing transactions have to be rolled back. Its like restarting the service, just on the other node.
Bodo Michael Danitz - MCT, MCITP - free consultant - performance specialist - www.sql-server.de

SQL cluster name on a Windows Failover Cluster

Hello,
I am installing a SQL cluster (first timer) using Windows server and SQL (both 2008 R2)
Windows failover cluster is setup and functioning. I am now installing the SQL failover cluster part.
Question: What should be the "SQL server network name", should it be the same as my Windows cluster name or different name ?
Thanks for your help,
Luca

It should be different, this is known as the virtual SQL Server name in earlier versions of SQL Server failover clusters.
SQL Server Network Name —
Specify a network name for the new SQL Server failover cluster. This is the name that is used to identify your failover cluster on the network.
https://msdn.microsoft.com/en-us/library/ms179530.aspx?f=255&MSPPError=-2147217396
This will be the name used to identify your cluster on the network. This is the name that will be available on the
network for the clients to connect SQL instance.
http://www.mssqltips.com/sqlservertip/1709/install-sql-server-2008-on-a-windows-server-2008-cluster-part-3/

SCOM 2012 Reporting Components with a shared SQL cluster

Hi, we are planning to install SCOM 2012 but i am a bit confused around the reporting components.
We have a shared SQL Enterprise cluster with multiple instances which we would like to use for our OperationsMananger and OperationsManagerDW databases. However after trying a test SCOM deployment, installing the SCOM reporting components on a VM requires
a local running copy of SQL reporting services.
Is this true? It seems ludicrous to have to purchase an additional license of SQL just to run the reporting components of SCOM. We have spent a lot of money on our SQL cluster and we would like to use it. We dont want to install the SCOM reporting components
on the shared SQL cluster.
If this is true, can you tell me which license of SQL we require? Just to run SQL reporting services on a VM should just require a standard SQL license, right?
Also if we have to purchase a SQL license for this standalone VM, would you recommend having the OperationsManagerDW database on the shared SQL cluster or on the VM where the standalone instance of SQL reporting services resides.
Surely this is something that other people have an issue with? I would have thought most people would want to use a shared SQL cluster. Any help is much appreciated.

Just to add that SQL Reporting Services isn't cluster aware so the best you could do is to install stand-alone onto a node of the cluster.
To reinforce what Scott is saying, see this screenshot of the install of SCOM reporting:
http://www.systemcentersolutions.co.uk/images/easyblog_images/42/scom/CTP2/Install/SQRS9.png
Technically you can install SCOM reporting on a shared SQL Server Reporting Services instance but as Scott (and the screenshot) state - it will overwrite any existing security settings on existing reports.
Scott is also correct that SQL Server Standard Edition is included as part of the licensing cost of System Center 2012 as long as the SQL instance only runs components of System Center.
cheers
Graham
Regards Graham New System Center 2012 Blog! -
http://www.systemcentersolutions.co.uk
View OpsMgr tips and tricks at
http://systemcentersolutions.wordpress.com/
I have one SQL 2012 Server with a few instances. 1 for Scom, 1 for SCCM and 1 for Service Manager. The instance shows up as blank for reporting services on the SCOM. Do I have to install SQL on the SCOM box also? Why Can't
it see the instance on my 2012 SQL box? It is in a different instance than SCCM.

Can a SQL Cluster have many Master Secret \ SSO systems?

We are trying to build a BizTalk environment that will offer multiple BizTalk instances off one SQL cluster.
Our SQL cluster consists of 2 servers configured in an ACTIV\ACTIVE configuration and reads data from a SAN.
We have to set up 6 BizTalk instances to create 6 environments for UAT, Support, DR, etc. These BizTalk groups will contain 2 BizTalk servers each. Each instance will have a group of service accounts assigned to it ino order to separate the environments
but will still use the same SQL cluster.
We have named cluster resources for each UAT, Support, etc for the SAN so that the databses are written and read from mounted disks.
My question and confusion surrounds SSO and the clustering of the Master Secret for multiple instances.
I want to cluster the Master Secret on the existing SQL cluster as the documentation states, but I am not sure if this is correct when there are multiple BizTalk instances running off the the same SQL cluster. The nodes of the SQL cluster will have
the SSO service installed and so too will the BizTalk servers in each instance group - UAT, Support, etc. So, would this mean there is only one master secret being used for all BizTalk instances, which I feel is wrong?
Or should the master secret just exist on a bizTalk server without HA?
I want HA but not sure where the SSO and master secret should go and ensure there are no dependencies from the other BizTalk instances should the SSO service need restarting on the SQL cluster.
I have not implemented multiple instances on the same SQL cluster before so this is new and confusing. The microsoft documentation isn't too great either.
Any help and guidance would be greatly appreciated.

post Windows Server 2008 you can have multiple MS DTC instances on one cluster. So unlike previous versions (w2k3) where the recommendation was to add MSDTC to the base cluster group, you can now have one instance of MSDTC cluster resource per resource group.
In short yes if you feel that MSDTC is becoming a bottleneck in your processing. Also it would be preferred that for each of your BizTalk Environments you create at least ONE MSDTC resource per environment.
Regards.

How to migrate SQL Cluster into Virtual SQL server or Virtual SQL Cluster

Hello All,
Currently we will be attempting to migrate a SQL cluster of (2 systems) into are virtual enviroment. We have been tracking the system requirements with Vmware Consolidation Tool and IO Meter to make sure our hosts have enough resources to accomidate this. All the metrics coming back looks like it will run just fine virtulized as the cluster was just for failover purposes anyhow and not for performance purproses. With that said a few questions have come up.
1.) What is the best way to virtulize this or to convert it (P2V)
- Should we just create a new Virtual Machine and install the same version of SQL and do a manual migration to the new SQL server and leave it as 1 SQL server with HA
- Or is there a way to P2V this kind of a setup ? if so what are the steps involved?
2.) If a P2V is possible I was under the impression that you will have to use a RAW mapping for the hard disks otherwise the cluster will not work ? Can anyone speak to this? as I'm pretty sure I have clustered windows server 2008 without RAW mapping before but not with SQL

Another quick question. The Vmware SQL Clustering KB article says:
vSphere MSCS Setup Limitations
Before you set up MSCS, review the list of functionality that is not supported for this release, and any
requirements and recommendations that apply to your configuration.
The following environments and functionality are not supported for MSCS setups with this release of vSphere:
n Clustering on iSCSI, FCoE, and NFS disks.
n Mixed environments, such as configurations where one cluster node is running a different version of ESX/
ESXi than another cluster node.
n Use of MSCS in conjunction with VMware Fault Tolerance.
n Migration with VMotion of clustered virtual machines.
n N-Port ID Virtualization (NPIV)
n With native multipathing (NMP), clustering is not supported when the path policy is set to round robin.
n You must use hardware version 7 with ESX/ESXi 4.0.
Can you not do clustering if your shared storage is iSCSI ? or can you not do RAW mapping with it to create the cluster ?

Install SQL Cluster

Hi all,
Kindly what is the step by step procedue to install sql server 2012 sp1 cluster to host sharepoint 2013 databases? Knowing that the sharepoint 2013 servers (two servers) and the sql servers (two) in different zones (there is a firewall between them)
Regards,

i assume you want to Install SQL Cluster for High Availability group, please follow the link below, walk through the all steps from failover cluster to SQL Installation to configure the high Availability group.
Configure SQL Server 2012 AlwaysOn Availability Groups for SharePoint 2013
One thing make sure, you punch the hole in firewall for all the ports you used on the SQL server so that sharepoint can communicate to sql server.
Please remember to mark your question as answered &Vote helpful,if this solves/helps your problem. ****************************************************************************************** Thanks -WS MCITP(SharePoint 2010, 2013) Blog: http://wscheema.com/blog

SQL Cluster Management Pack

Hello,
I do not see a specific Management Pack for SQL Cluster... It seems to be the SQL Management Pack 6.1.400.0 and the Operating System Cluster Management Pack...6.0.6720.0 for Windows Server 2008 Cluster Management Library ...
Am I right?
Thanks,
Dom
System Center Operations Manager 2007 / System Center Configuration Manager 2007 R2 / Forefront Client Security / Forefront Identity Manager

I implemented the low-privilege setup from the SQL MP guide because on a few standalone SQL instances and one SQL 2012 cluster, not all scripts were running. The SQL cluster is a two node cluster with 2 SQL instances in and active/active config (One
instance is active on each node in the cluster). On the standalone SQL instances, the low-privilege setup is working great. On the SQL cluster it is not. Reading the latest SQL MP guide, it appears that SQL 2012 cluster are supported for
monitoring. I've made the additional configuration changes that the MP guide says is required for cluster monitoring. I am getting PowerShell script execution error messages in the OpsMgr console stating a lack of permissions. When I look
at the SQL error logs, I see that something is trying to log into the databases as NT AUTHORITY\SYSTEM and can't because access is denied. That login is not mapped to any databases - obviously. Why would these workflows be trying to execute as
NT AUTHORITY\SYSTEM and not one of the the action accounts in the SQL RunAs profiles that I've setup and deployed to the two cluster nodes?

SQL Cluster requiremnt for Lync 2013

Hi
We are are planning to deploy Lync 2013 enterprise. Planning to use SQL cluster. Would like to clarify whether we must create a sepearte sql instance for Lync 2013 or can we use an existing shared instance to create a seperate database for Lync.
We prefer 2nd approach. Is there any issues or demerits using existing shared SQL instances?
Thanks and regards,
Aboo Arif

Hi AbooArif.
This kind of question is very common. Basically here is the Microsoft Documentation about it.
Database software support in Lync Server 2013
https://technet.microsoft.com/en-us/library/gg398990.aspx
This point is the important: "If you collocate Lync Server databases with other databases, we highly recommend assessing all factors that might affect availability and performance, as well as ensuring that, if one node fails, the remaining node can
handle the load. To verify failover capabilities, we recommend testing all failover scenarios."
We can say the following: It's recommended to use a separate SQL server for Lync, however collating Lync database with other SQL databases will work, but has an high probability of present some performance problems. Many customers prefer to use this option
considering the cost of SQL licenses.
It is important to consider all the hardware requeriments for the Lync Server BackEnd role:
https://technet.microsoft.com/en-us/library/gg398835.aspx because the normal issue when customers share the SQL server with other instances is due to performance issues. Also note
that if you have multiple front end pools, these cannot share a SQL server.
PLEASE REMEMBER, if you see a post that helped you please click "Vote As Helpful" and if it answered your question please click "Mark As Answered"

Adding SQL Cluster to MARS

Similar Messages

Maybe you are looking for