Will SCCM 2012 R2 , SCOM 2012 R2 and SCDPM R2 2012 support SQL 2012 AlwaysOn Availability Group ?

Hi,
It is listed here:
http://technet.microsoft.com/en-us/library/dn281933.aspx
Configuration Manager 2012 r2 and DPM 2012 r2 does not support AlwaysOn.
regards,
Jörgen
-- My System Center blog ccmexec.com -- Twitter
@ccmexec

Similar Messages

2012 SQL AlwaysOn Availability Group - JDBC re-connection not happening in case of Multisubnet failover

Hi There,
Having some problem with MultiSubNet AG failover re-connection using SQL JDBC driver 4. Details given below.
SETUP:
We have a three node 2012 Windows Server Cluster, on top it we have 2012 SQL Sever AlwaysOn Availability Group.
Two nodes are in one subnet and other in a different subnet to make this as a multisubnet AlwaysOn AG.
An AG Listener is configured with a DNS name and two VIP assigned (For two subnet) to it. We were able to failover from one subnet to other using the SQL Studio successfully.
NEED:
We have a java application which will be connected to AG Listener name. In case of failover, automatic re-connection to DB/AG Listener name should happen.
For this we use "sqljdbc4.jar" and added
'multiSubnetFailover=true' in our connection string. The connection String is given below.
cURL="jdbc:sqlserver://testsqlag:1433;databaseName=SalesDB;multiSubnetFailover=true;loginTimeout=200;applicationName=MyApp";
THE PROBLEM:
In case of AG failover, driver is not trying to re-connect to the AG Listener name. Not sure how to make it work.
Is this supported in SQL Server 2012 ?
Thanks,
Krishna.

Hi Sean,
Thanks for your answer.
I looked at the link earlier, but it was not very clear that, whether the mssql jdbc driver will automatically re-connect to AG Listener name in case of failure of Primary replica which will result in Multisubnet failover. Pasted the confusing statements
from the link
http://msdn.microsoft.com/en-us/library/gg558121(v=sql.110).aspx.
Also, because a connection can fail because of an availability group failover, you should implement connection retry logic, retrying a failed connection until it reconnects.
Connecting With MultiSubnetFailover :
During a multi-subnet failover, the client will attempt connections in parallel. During a subnet failover, the Microsoft JDBC Driver for SQL Server will aggressively retry the TCP connection.
Thanks,
Krishna.

SCCM 2012 R2 - will it support SQL 2012 AAG?

Dear all,
can't find any information about supported SQL Servers for SCCM 2012 R2.
We are completing the testing phase of SCCM 2012 SP1, but we are not happy about keeping its databases on SQL 2008R2.
Moving DBs to SQL 2012 AAG will significantly simplify our DR plan for SCCM.
Will really apreaciate any useful information on this topic

Hi,
As far as I know, no support for Always On Availability Groups has been anounneced. The new features in R2 can be found here:
http://technet.microsoft.com/en-us/library/dn236351.aspx
Regards,
Jörgen
-- My System Center blog ccmexec.com -- Twitter
@ccmexec

DPM 2012 SP1 and SharePoint 2013 on a SQL 2012 AlwaysOn AG

I am trying to protect a new SharePoint Foundation 2013 farm with it's databases stored on an SQL 2012 AlwaysOn Availability Group. I've run configureSharePoint.exe -EnableSharePointProtection on my WFE and SharePoint shows up in DPM when I try to
add it to a protection group. But I get the 32008 referenced here: http://support.microsoft.com/kb/970641 when trying to select the farm to back up.
If I run ConfigureSharePoint.exe -resolveallSQLAliases on the WFE it doesn't return anything.
I'm directly backing up databases on the SQL 2012 server, but not any of the SharePoint DBs.
K

Hi,
I'm having some trouble understanding what I'm seeing in the writer output from the WFE server. Specifically the machine names that the writer is reporting.
If you look in the wfewtiters.txt, What is the machine that ends in 02 ? Is that a physical machine or an alias ?
The machine ending in 06 is the Secondary SQL Server and that is what the Sharepoint writer is pointing to.
The WFE VSS Sharepoint writer shows this for two content DB’s
* WRITER "SharePoint Services Writer"
  - Writer ID   = {da452614-4858-5e53-a512-38aab25c61ad}
  - Writer instance ID = {c0c46d7b-1c01-44bd-8353-e3433f5b8f07}
  - Supports restore events = TRUE
  - Writer restore conditions = VSS_WRE_ALWAYS
  - Restore method = VSS_RME_RESTORE_AT_REBOOT_IF_CANNOT_REPLACE
  - Requires reboot after restore = FALSE
  - Excluded files:
+ Component "SharePoint Services Writer:\XXXX02\WSS_Content_at.contoso.local"
- Name: WSS_Content_at.Contoso.local
- Logical path: XXXX02
- Full path: \XXXX02\WSS_Content_at.Contoso.local
- Caption: Content Database WSS_Content_at.Contoso.local
- Type: VSS_CT_DATABASE [1]
- Is selectable: TRUE
- Is top level: TRUE
- Notify on backup complete: FALSE
- Paths affected by this component:
- Volumes affected by this component:
- Component Dependencies:
- Dependency to "{a65faa63-5ea8-4ebc-9dbd-a0c4db26912a}:\\YYYY06\YYYY06\WSS_Content_at.contoso.local"
                                + Component "SharePoint Services Writer:\XXXX02\WSS_Content_fw.Contoso.local"
- Name: WSS_Content_fw.contoso.local
- Logical path: XXXX02
- Full path: \XXXX02\WSS_Content_fw.Contoso.local
- Caption: Content Database WSS_Content_fw.Contoso.local
- Type: VSS_CT_DATABASE [1]
- Is selectable: TRUE
- Is top level: TRUE
- Notify on backup complete: FALSE
- Paths affected by this component:
- Volumes affected by this component:
- Component Dependencies:
- Dependency to "{a65faa63-5ea8-4ebc-9dbd-a0c4db26912a}:\\YYYY06\YYYY06\WSS_Content_fw.contoso.local"
Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread. Regards, Mike J. [MSFT]
This posting is provided "AS IS" with no warranties, and confers no rights.

Maintenance plan for SQL Server 2012 Database in AlwaysOn Availability Group

Hi all,
I need assistance creating a maintenance plan that will backup a databases logs in order to prevent them from filling up the drive they are located on. I have looked at some blogs but they do not specifically show how this is done.
My database is in an AlwaysOn Availability Group.
Thank you very much for your help!
Jake

Hi all,
I need assistance creating a maintenance plan that will backup a databases logs in order to prevent them from filling up the drive they are located on. I have looked at some blogs but they do not specifically show how this is done.
My database is in an AlwaysOn Availability Group.
Regular maintenance plan would work. Only thing to remember is that when you create log backup plan, there is a checkbox which says whether it should honor backup preference or not.
Balmukund Lakhani
Please mark solved if I've answered your question, vote for it as helpful to help other users find a solution quicker
This posting is provided "AS IS" with no warranties, and confers no rights.
My Blog |
Team Blog | @Twitter
| Facebook
Author: SQL Server 2012 AlwaysOn -
Paperback, Kindle

I'm trying to connect my iPad to my Samsung galaxy s by bluetooth but the ipad will pair with it but not connect and says "its not supported" does anyone know what this means and how I get it to work?

I'm trying to connect my iPad to my Samsung galaxy s by bluetooth but the ipad will pair with it but not connect and says "its not supported" does anyone know what this means and how I get it to work?

iOS devices do not have the BT profiles that support file sharing and othr general functions. See:
iOS: Supported Bluetooth profiles
Basically it support headphones, keyboards, speakers, peer-to-peer gaming

Moving the Reporting Services and Report Server DB into AlwaysON Availability Group

I have configured the new set of SQL 2012 AlwaysOn Availability Group and need to move the SSRS and it's Report Server DB into that Availability Group.
Can anyone give tell me the steps to do this move?
Can I just backup the ReportServer DB into the AG server then import that DB into the SSRS running on the new AlwasyOn AG SQL?

Hello,
Based on your description, it seems that you want to move the Report Server database to a different server. If so, both the reportserver and reportservertempdb databases must be moved or copied together. You can move the databases by using Detaching
and Attaching or Backup and Restore.
What's more, you should also backup the encryption keys for the report server database you want to move and then restore to the new server.
You can configure report server databases in Always On Availability Group to be part of a replica; however Reporting Services will not automatically use a different replica for the report server databases when a failover occurs
Reference:
Moving the Report Server Databases to Another Computer
Reporting Services with AlwaysOn Availability Groups (SQL Server)
Regards,
Fanny Liu
Fanny Liu
TechNet Community Support

AlwaysOn Availability groups and unable to backup LOG files

Hi,
I have an issue where we are using AlwaysOn availability groups, however my transaction log backup jobs are not working for any databases that are part of the groups. Databases which are standalone backup fine. I've tried using the builtin maintenance
plans as well as the 'maintenance script' from Ola Hallengren which is my preference.
All the jobs are reporting success even though nothing is bring written to disk, the jobs complete within a few seconds.
If I backup the log files individually myself they work fine. After
going a bit of Googling this appears to have been a known issue that was fixed in CU7, unfortunately I'm running CU9 and still have the issue.
I've tried changing the backup preference to any, as well as primary or secondary only to no avail.
I'm using SQL Server SP1 CU9, 2 nodes in the group. Anyone have any suggestions?
Marcus

Hi,
I understand that you have tried every options in Backup Preferences. I still suggest you enable the “For availability database. Ignore Replica Priority for Backup and Backup on Primary Settings” when you define the maintenance plan and check how it works.
This settings is off by default. And the maintenance plan will detect the availability group's AUTOMATED_BACKUP_PREFERENCE setting when deciding to backup a database or log if that database is defined in the group.
'Given that an availability group's default AUTOMATED_BACKUP_PREFERENCE setting is 'SECONDARY, a maintenance plan, defined and running on a SQL Server instance hosting the primary replica, will NOT backup databases defined in the availability group.
Reference:
http://blogs.msdn.com/b/alwaysonpro/archive/2014/01/02/maintenance-plan-does-not-backup-database-or-log-of-database-that-belongs-to-availability-group.aspx
Hope it helps.
Tracy Cai
TechNet Community Support

File Share Witness Resouces Errors in a SQL 2012 Alwayson Availability Group Environment

Hi I am getting the following error in WFC Manager and in my system event log:
Event ID1564:
File share witness resource 'File Share Witness' failed to arbitrate for the file share '\\SQL2012ClusterWitnessPath'. Please ensure that file share '\\SQL2012ClusterWitnessPath' exists and is accessible by the cluster.
Event ID 1069:
Cluster resource 'File Share Witness' of type 'File Share Witness' in clustered role 'Cluster Group' failed.
Based on the failure policies for the resource and role, the cluster service may try to bring the resource online on this node or move the group to another node of the cluster and then restart it. Check the resource and group state using Failover Cluster
Manager or the Get-ClusterResource Windows PowerShell cmdlet.
Event ID 1205:
The Cluster service failed to bring clustered service or application 'Cluster Group' completely online or offline. One or more resources may be in a failed state. This may impact the availability of the clustered service or application.
These errors showed up every hour on the hour and then suddenly stopped. I tried looking at the cluster.log file but there wasn't anything recorded there. The file share witness shows to be online and my AG did not fail over to another node.
The cluster has read and write permissions to the share. I did not find any error messages about the witness share on the remote server.
I am wondering what caused these series of events to occur?
Thanks.

Hi Kevin Ni,
Thanks for your reply. I have ran the validation test and I have 2 warnings. My environment has 2 nodes and 2 AG's with each node a failover for each AG. So that each node hosts and primary and a secondary of an AG. Both nodes are
on the same subnet. Here are the errors.
- Validate Multiple Subnet Properties
The RegisterAllProvidersIP property causes the network name to register all dependent IP addresses whether they are online or offline. Some DNS servers and clients in multi-subnet (multi-site) environments can identify the IP address that is in their subnet
and attempt connections only to that address. In such environments, it is usually best to set RegistrerAllProvidersIP to 1. This reduces DNS replication delays.
The RegisterAllProvidersIP property for network name 'Name: Listener1' is set to 1. For the current cluster configuration this value should be set to 0.
The RegisterAllProvidersIP property causes the network name to register all dependent IP addresses whether they are online or offline. Some DNS servers and clients in multi-subnet (multi-site) environments can identify the IP address that is in their subnet
and attempt connections only to that address. In such environments, it is usually best to set RegistrerAllProvidersIP to 1. This reduces DNS replication delays.
The RegisterAllProvidersIP property for network name 'Name: Listener2' is set to 1. For the current cluster configuration this value should be set to 0.
- Validate Network Communication
Node ONE.domain.com is reachable from Node TWO.domain.com by multiple communication paths, but each path includes network interface TWO.domain.com - TWO_NIC_Team. This network interface may be a single point of failure for communication within the
cluster. Please verify that this network interface
is highly available or consider adding additional networks or network interfaces to the cluster.
Node TWO.domain.com is reachable from Node ONE.domain.com by multiple communication paths, but each path includes network interface TWO.domain.com - TWO_NIC_Team. This network interface may be a single point of failure for communication within the
cluster. Please verify that this network interface
is highly available or consider adding additional networks or network interfaces to the cluster.
I have node TWO setup with NIC Teaming. Node ONE is also setup with NIC teaming but it also has a second IP address but the second IP address cannot communicate with node TWO.

Is it possible to install SharePoint 2013 and SQL 2012 on single Azure Virtual Machine

I had a Azure subscription, I need had created only one Virtual Machine, is it possible to install SharePoint 2013 and SQL Server 2012 on that single virtual machine in azure.
I had SharePoint 2013 and SQL Server 2012 licence from MSDN subscription,
Finally on Azure virtual machine is it possible to Install SharePoint 2013 and SQL server by downloading these software from MSDN.

Hi,
It is supported to install sharepoint 2013 and SQL server on the same server. However, please check the size of your Azure VM and make sure it is compatible for that.
The minimum recommended size for a virtual machine is A3 when using SQL Server Enterprise Edition. Select A3 or higher when using SQL Server Enterprise Edition. Select A4 when using SQL Server 2012 or 2014 Enterprise Optimized for Transactional Workloads
images. Select A7 when using SQL Server 2012 or 2014 Enterprise Optimized for Data Warehousing Workloads images. In addition, the default size for SharePoint 2013 image is A3.
In addition, as a best practice, you can install them in different servers and then deploy SharePoint 2013 with SQL Server AlwaysOn Availability Groups in Azure:
Deploying SharePoint 2013 with SQL Server AlwaysOn Availability Groups in Azure
http://msdn.microsoft.com/en-us/library/azure/dn275959.aspx
Best regards,
Susie
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]

DPM 2012 R2 CU4 protecting SQL 2014 AlwaysOn AG with Failover Cluster vs. DR location

Hello!
We have a problem protecting any Database of SQL 2014 AlwaysOn Availability Group with SQL Failover Cluster Instance when moved to DR location. Everything is protected using DPM 2012 R2 CU4 from Primary location.
FACTS
- all servers are Windows Server 2012 R2
- all servers are Virtual (except Hyper-V hosts obviously:)
- that means virtualization is based on Windows Server 2012 R2 Hyper-V
- all clusters (SQL, Exchange,...) are Guest Clusters on Hyper-V
- SQL 2014
- DPM 2012 R2 CU4
- Primary and DR location
SETUP
SQL
- Primary location: SQL 2014 Guest Cluster with SQL Failover Cluster Instance using Shared VHDX disks
- DR location: SQL 2014 Standalone using VHDX disks
- AlwaysOn Availability Group expands between the primary and DR location.
DPM
- Primary location: DPM 2012 R2 CU4
- DPM 2012 R2 CU4 Agents installed on every possible SQL 2014 Server.
SCENARIO
- DPM is backing up all the SQL Databases normally as long as they exist on any SQL Cluster Node on Primary location.
- As soon as any Database is moved to DR location, that Database is not backed up anymore with the following error.
DPM ERROR
Starting synchronization on SqlServerName\DatabaseName failed:
Error 104: An unexpected error occurred while the job was running.
Error details: The system cannot find the path specified (0x80070003)
Recommended action: Retry the operation.
TROUBLESHOOTING
- Tried to modify SQL Protection Group in DPM Server while Database was active on DR location
> error enumerating volumes or drives D:\, E:\, F:\ (I don't have exact error atm)
> this looks like DPM is not aware that DPM is active on DR location to me
- Checked Technet, blogs and forums; no useful information
QUESTION
Is this expected or by-design behavior? Is this a bug? I am aware there were quite some issues backing up AG's from DPM 2012 SP1 ans SQL 2012 on.
Does anybody have a lab of that kind to try it out?
Thank you!
Best Regards,
Damjan Grimšič
Lpd

OK. The issue has been resolved. Issue was related to possible Disks Owners in Failover Cluster Manager Console for SQL Cluster.
In Primary's site SQL Cluster Failover Manager Console / Storage / Disks.
SQL Server(s) from Secondary location need(s) to be unchecked as Possible owner(s) in Advanced Policies for all relevant Volumes.
Lpd

Backup and Restore of DQS (Data Quality Service SQL 2012) Databases

We are currently using DPM 2010 running on Server 2008 R2 as our backup solution. We will soon be leveraging the Data Quality Services in SQL 2012 along with the Master Data Service.
In the SQL 2012 documentation from Microsoft it states, “The backup and restore operations of the DQS databases must be synchronized.”
Otherwise the restored Data Quality Server will not be functional. Currently I believe that DPM will run serialized backups of databases from one SQL server.
I was hoping someone could point me towards some documentation for backing up DQS with DPM.
Is anybody currently doing this? If so have you been successful restoring?

LogicalName cant be same for mdf and ldf. verify again with FILELISTONLY. Also you have put wrong logical name
MOVE N'OriginalDB' TO N'D:\sql data\TargetDB.mdf'
Please paste the output of
RESTORE FILELISTONLY FROM DISK = 'D:\backup.bak'

Upgrading SQL 2012 sp1 to sp2 error - Overlapped I/O operation is in progress.

Hi Guys,
Having an issue patching two of my SQL servers which are currently in an AlwaysOn, we use SCOM 2012 R2 to monitor it and it's installed on Server 2012, this is the current SQL version:
Microsoft SQL Server 2012 (SP1) - 11.0.3128.0 (X64)
Dec 28 2012 20:23:12
Copyright (c) Microsoft Corporation
Enterprise Edition: Core-based Licensing (64-bit) on Windows NT 6.2 <X64> (Build 9200: ) (Hypervisor)
I get the error when trying to install any SQL updates, I have tried the following:
KB2977326
KB2958429
The installer gets to the end with error code: 997 when looking at the logs we get this:
Action required:
Use the following information to resolve the error, and then try the setup process again.
Feature failure reason:
An error occurred for a dependency of the feature causing the setup process for the feature to fail.
Error details:
§ Error installing SQL Server Setup Support Files
Overlapped I/O operation is in progress.
Error code: 997
Log file: C:\Program Files\Microsoft SQL Server\110\Setup Bootstrap\Log\20140826_104653\MSSQLSERVER\SqlSupport_Cpu64_1.log
Visit http://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=11.0.5058.0&EvtType=SqlSupport.msi%40ProcessComponents%40997 to get help on troubleshooting.

C:\Program Files\Microsoft SQL Server\110\Setup Bootstrap\Log\20140826_104653\MSSQLSERVER\SqlSupport_Cpu64_1.log
The end of that log:
Property(S): MsiLogFileLocation = C:\Program Files\Microsoft SQL Server\110\Setup Bootstrap\Log\20140826_104653\MSSQLSERVER\SqlSupport_Cpu64_1.log
Property(S): PackageCode = {5756C162-DB51-41EE-AE83-C4DAEE74CC31}
Property(S): ProductState = -1
Property(S): PackagecodeChanging = 1
Property(S): ADDLOCAL = SupportFiles
Property(S): UPGRADE = SupportFiles
Property(S): VSINSTALLDIR = C:\Program Files (x86)\Microsoft Visual Studio 10.0
Property(S): REBOOT = ReallySuppress
Property(S): EXTERNALMSICONTROL = 1
Property(S): CURRENTDIRECTORY = y:\78f5c042a94a1c9d28
Property(S): CLIENTUILEVEL = 3
Property(S): MSICLIENTUSESEXTERNALUI = 1
Property(S): CLIENTPROCESSID = 1876
Property(S): VersionDatabase = 405
Property(S): VersionMsi = 5.00
Property(S): VersionNT64 = 602
Property(S): WindowsBuild = 9200
Property(S): ServicePackLevel = 0
Property(S): ServicePackLevelMinor = 0
Property(S): MsiNTProductType = 3
Property(S): WindowsVolume = C:\
Property(S): System64Folder = C:\Windows\system32\
Property(S): SystemFolder = C:\Windows\SysWOW64\
Property(S): RemoteAdminTS = 1
Property(S): TempFolder = C:\Users\TEMP\AppData\Local\Temp\
Property(S): CommonFilesFolder = C:\Program Files (x86)\Common Files\
Property(S): CommonFiles64Folder = C:\Program Files\Common Files\
Property(S): AppDataFolder = C:\Users\TEMP\AppData\Roaming\
Property(S): FavoritesFolder = C:\Users\TEMP\Favorites\
Property(S): NetHoodFolder = C:\Users\TEMP\AppData\Roaming\Microsoft\Windows\Network Shortcuts\
Property(S): PersonalFolder = \\server\docs\user\My Documents\
Property(S): PrintHoodFolder = C:\Users\TEMP\AppData\Roaming\Microsoft\Windows\Printer Shortcuts\
Property(S): RecentFolder = C:\Users\TEMP\AppData\Roaming\Microsoft\Windows\Recent\
Property(S): SendToFolder = C:\Users\TEMP\AppData\Roaming\Microsoft\Windows\SendTo\
Property(S): TemplateFolder = C:\ProgramData\Microsoft\Windows\Templates\
Property(S): CommonAppDataFolder = C:\ProgramData\
Property(S): LocalAppDataFolder = C:\Users\TEMP\AppData\Local\
Property(S): MyPicturesFolder = \\server\docs\user\My Documents\My Pictures\
Property(S): AdminToolsFolder = C:\ProgramData\Microsoft\Windows\Start Menu\Programs\Administrative Tools\
Property(S): StartupFolder = C:\ProgramData\Microsoft\Windows\Start Menu\Programs\Startup\
Property(S): ProgramMenuFolder = C:\ProgramData\Microsoft\Windows\Start Menu\Programs\
Property(S): StartMenuFolder = C:\ProgramData\Microsoft\Windows\Start Menu\
Property(S): DesktopFolder = C:\Users\Public\Desktop\
Property(S): FontsFolder = C:\Windows\Fonts\
Property(S): GPTSupport = 1
Property(S): OLEAdvtSupport = 1
Property(S): ShellAdvtSupport = 1
Property(S): MsiAMD64 = 6
Property(S): Msix64 = 6
Property(S): Intel = 6
Property(S): PhysicalMemory = 7680
Property(S): VirtualMemory = 22117
Property(S): AdminUser = 1
Property(S): MsiTrueAdminUser = 1
Property(S): LogonUser = user
Property(S): UserSID = S-1-5-21-529874490-2830903538-1517016768-1630
Property(S): UserLanguageID = 2057
Property(S): ComputerName = sql02
Property(S): SystemLanguageID = 1033
Property(S): ScreenX = 1024
Property(S): ScreenY = 768
Property(S): CaptionHeight = 23
Property(S): BorderTop = 1
Property(S): BorderSide = 1
Property(S): TextHeight = 16
Property(S): TextInternalLeading = 3
Property(S): ColorBits = 32
Property(S): TTCSupport = 1
Property(S): Time = 10:52:12
Property(S): Date = 8/26/2014
Property(S): MsiNetAssemblySupport = 4.0.30319.17929
Property(S): MsiWin32AssemblySupport = 6.2.9200.16384
Property(S): RedirectedDllSupport = 2
Property(S): MsiRunningElevated = 1
Property(S): USERNAME =
Property(S): COMPANYNAME =
Property(S): DATABASE = C:\Windows\Installer\3613360.msi
Property(S): OriginalDatabase = C:\Program Files\Microsoft SQL Server\110\Setup Bootstrap\Update Cache\KB2958429\ServicePack\1033_ENU_LP\x64\setup\sqlsupport_msi\SqlSupport.msi
Property(S): UILevel = 2
Property(S): Preselected = 1
Property(S): ACTION = INSTALL
Property(S): MIGRATE = {8CB0713F-CFE0-445D-BCB2-538465860E1A}
Property(S): ROOTDRIVE = Z:\
Property(S): CostingComplete = 1
Property(S): OutOfDiskSpace = 0
Property(S): OutOfNoRbDiskSpace = 0
Property(S): PrimaryVolumeSpaceAvailable = 0
Property(S): PrimaryVolumeSpaceRequired = 0
Property(S): PrimaryVolumeSpaceRemaining = 0
Property(S): DOTNETCOREPATH = 1
Property(S): IsDotNet40Installed = 1
Property(S): SOURCEDIR = C:\Program Files\Microsoft SQL Server\110\Setup Bootstrap\Update Cache\KB2958429\ServicePack\1033_ENU_LP\x64\setup\sqlsupport_msi\
Property(S): SourcedirProduct = {977887EC-1C9B-47FA-8489-88E5E7F43D5E}
MSI (s) (94:B0) [10:52:12:328]: Windows Installer installed the product. Product Name: Microsoft SQL Server 2012 Setup (English). Product Version: 11.2.5058.0. Product Language: 1033. Manufacturer: Microsoft Corporation. Installation success or error status:
1603.
MSI (s) (94:B0) [10:52:12:328]: Deferring clean up of packages/files, if any exist
MSI (s) (94:B0) [10:52:12:328]: MainEngineThread is returning 1603
MSI (s) (94:B0) [10:52:12:328]: MainEngineThread is returning 1603
MSI (s) (94:FC) [10:52:12:328]: RESTART MANAGER: Session closed.
MSI (s) (94:FC) [10:52:12:328]: No System Restore sequence number for this installation.
=== Logging stopped: 26/08/2014 10:52:12 ===
MSI (s) (94:FC) [10:52:12:344]: User policy value 'DisableRollback' is 0
MSI (s) (94:FC) [10:52:12:344]: Machine policy value 'DisableRollback' is 0
MSI (s) (94:FC) [10:52:12:344]: Incrementing counter to disable shutdown. Counter after increment: 0
MSI (s) (94:FC) [10:52:12:344]: Note: 1: 1402 2: HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Installer\Rollback\Scripts 3: 2
MSI (s) (94:FC) [10:52:12:344]: Note: 1: 1402 2: HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Installer\Rollback\Scripts 3: 2
MSI (s) (94:FC) [10:52:12:344]: Decrementing counter to disable shutdown. If counter >= 0, shutdown will be denied. Counter after decrement: -1
MSI (s) (94:FC) [10:52:12:344]: Destroying RemoteAPI object.
MSI (s) (94:60) [10:52:12:344]: Custom Action Manager thread ending.
MSI (c) (54:A4) [10:52:12:344]: Decrementing counter to disable shutdown. If counter >= 0, shutdown will be denied. Counter after decrement: -1
MSI (c) (54:A4) [10:52:12:344]: MainEngineThread is returning 1603
=== Verbose logging stopped: 26/08/2014 10:52:12 ===

SQL 2012 AlwaysON High Availability for SharePoint 2013

Our Company have 2 Webfront Servers for Sharepoint 2013 and one Database SQL 2012 Server.
We got one more Server & we don't have Storage so need to configure Always On.
There are Some Confusions:
1- Database Server is in production, so how much down time required to Achieve the AlwaysOn?
2- What are the Changes need to be done on Production Server?
3- What are the Steps to be followed While Configuring new Database Server?
Regards,

Hi Genius1985,
According to your description, you want to configure a SQL Server 2012 AlwaysOn Availability Group for your database, right?
Question 1: Database Server is in production, so how much down time required to achieve the AlwaysOn?
There is no a certain downtime for AlwaysOn, it depends on the configuration of our AlwaysOn Availability Group, normally it can be several seconds or minutes. In order to understand why there is downtime for SQL Server with Microsoft Clustering, please refer
to the following article:
http://www.mssqltips.com/sqlservertip/1882/understanding-why-there-is-still-downtime-for-sql-server-with-microsoft-clustering/
Question 2 and 3: What are the Changes need to be done on Production Server? What are the Steps to be followed While Configuring new Database Server?
Since AlwaysOn Availability Groups require a Windows Server Failover Cluster, we first need to add the Windows Failover Cluster Feature to all the machines running the SQL Server instances that we will configure as replicas.
Once the Windows Server Failover Cluster has been created, we need to proceed with enabling the AlwaysOn Availability Groups feature in SQL Server 2012. This needs to be done on all of the SQL Server instances that we will configure as replicas in our
Availability Group.
For more details about Step-By-Step: Creating a SQL Server 2012 AlwaysOn Availability Group, please refer to the following article:
http://blogs.technet.com/b/canitpro/archive/2013/08/20/step-by-step-creating-a-sql-server-2012-alwayson-availability-group.aspx
If you have any question, please feel free to let me know.
Regards,
Jerry Li

Time-out issue Always on SQL 2012 Cluster

Currently I'm working on a large deployment of a SharePoint 2013 environment (stretched farm over 2 DC's). We are using a SQL 2012 alwayson multisubnet cluster (each DC has 1 SQL node). During the installation of SharePoint we encountered several connection
time-out errors from the SQL environment. (Exception calling "Open" with "0" argument(s): "Connection Timeout Expired. The timeout period elapsed during the post-login
phase. The connection could have timed out while waiting for server to complete the login process and respond;)
Steps we follow for SharePoint installation are:
Steps to configure SharePoint 2013 on an AlwaysOn Availability group:
1>Create SharePoint databases (with the PowerShell script)
Configure a SQL alias for a consistent SQL instance name.
Create farm on SQL instance/replica 1 (one of the SQL nodes), creating all databases needed (service-apps & web-apps). -->
we are connected directly to 1 SQL node and not connecting to the cluster. Installation server is in same DC as the SQL node.
Stop SharePoint so databases remain static during migration to an AlwaysOn cluster.
2>Move database to AlwaysOn high-availability group.
Restore all the DBs onto SQL replica 2 (with NORECOVERY).
Create AlwaysOn availability group, or use existing
Join the replica 2 databases to availability group.
Create listener.
3>Migrate SharePoint onto AlwaysOn on cluster
Make all SharePoint DB MultiSubnetFailover aware with PowerShell Cmdlet
Reconfigure SQL alias for new listener
àat this point the SharePoint farm is connecting to the SQL cluster (listener of AlwaysOn availability group of the SQL Instance), but we never reached this point so far.
Restart SharePoint services with updated alias.
Event errors and SQL log errors that I found:
Date,Source,Severity,Message,Category,Event,User,Computer
09/18/2014 07:34:59,Microsoft-Windows-FailoverClustering,Error,Cluster network name resource 'SPAG_CU8000001105' failed registration of one or more associated DNS name(s) for the following reason:<nl/>DNS bad key.<nl/>.<nl/><nl/>Ensure
that the network adapters associated with dependent IP address resources are configured with at least one accessible DNS server.,(19),1196,NT AUTHORITY\SYSTEM,CU8000000015
09/18/2014 07:34:59,MSSQL$SPAG,Information,The Service Broker endpoint is in disabled or stopped state.,(2),9666,,CU8000000015
09/18/2014 07:34:52,Microsoft-Windows-FailoverClustering,Error,Cluster network name resource 'SPWMAG_CU8000002105' failed registration of one or more associated DNS name(s) for the following reason:<nl/>DNS bad key.<nl/>.<nl/><nl/>Ensure
that the network adapters associated with dependent IP address resources are configured with at least one accessible DNS server.,(19),1196,NT AUTHORITY\SYSTEM,CU8000000015
09/18/2014 07:34:52,MSSQL$SPWMAG,Information,The Service Broker endpoint is in disabled or stopped state.,(2),9666,,CU8000000015
09/18/2014 07:34:47,Service Control Manager,Information,The WMI Performance Adapter service entered the running state.,(0),7036,,CU8000000015
09/18/2014 07:32:41,Microsoft-Windows-FailoverClustering,Error,Cluster network name resource 'SPSDAG_CU8000003105' failed registration of one or more associated DNS name(s) for the following reason:<nl/>DNS bad key.<nl/>.<nl/><nl/>Ensure
that the network adapters associated with dependent IP address resources are configured with at least one accessible DNS server.,(19),1196,NT AUTHORITY\SYSTEM,CU8000000015
09/18/2014 07:32:41,MSSQL$SPSDAG,Information,The Service Broker endpoint is in disabled or stopped state.,(2),9666,,CU8000000015
09/18/2014 07:31:09,PowerShell,Information,Engine state is changed from Available to Stopped. <nl/><nl/>Details: <nl/> NewEngineState=Stopped<nl/> PreviousEngineState=Available<nl/><nl/> SequenceNumber=61464<nl/><nl/> HostName=OpsMgr
PowerShell Host<nl/> HostVersion=7.0.5000.0<nl/> HostId=32012185-8d9a-41c2-be56-91929c02f1e8<nl/> EngineVersion=4.0<nl/> RunspaceId=af176e01-185d-4574-ab9b-0fd745178d29<nl/> PipelineId=<nl/> CommandName=<nl/> CommandType=<nl/> ScriptName=<nl/> CommandPath=<nl/> CommandLine=,(4),403,,CU8000000015
We are not allow to update/write in the DNS for the multisubnet cluster IP registration, so I think that explains the "failed registration
" error. But can this explains our time-out errors during the SharePoint installation? For the installation we are connection directly to 1 SQL node and not to the SQL
cluster.
Any help is appreciated!
Ronald Bruinsma - Independent SharePoint Consultant - iDocs.info - The Netherlands -- Please don't forget to propose this post as an answer or mark it as helpful if it did help you. Thanks.

Don't just change the connection timeout on your SharePoint farm. This will just hide the real issue. From your error message, it seems that the DNS record for the Availability Group listener name is not being written. Talk to your AD administrators to validate
if dynamic DNS registration is configured for the DNS servers. If it is, AD will create the DNS entry of the virtual computer object for the Availability Group listener name. The WSFC should also have Create Computer Objects permission in the AD Organizational
Unit where your Availability Group listener name will be created.
On a side note, make sure that you configure a separate SharePoint 2013 farm for your DR environment that will use the content databases joined in the Availability Group. For a stretched farm deployments, latency should be less than 1ms one way as
per this article. And while you can add your admin content and config databases on the Availability Group, asynchronous commit is
not supported.
Edwin Sarmiento SQL Server MVP | Microsoft Certified Master
Blog |
Twitter | LinkedIn
SQL Server High Availability and Disaster Recover Deep Dive Course

Will SCCM 2012 R2 , SCOM 2012 R2 and SCDPM R2 2012 support SQL 2012 AlwaysOn Availability Group ?

Similar Messages

Maybe you are looking for