SSAS High Availability in Azure (not SQL DBE)

Hello,
I was wondering what would be my options for having an SSAS environment with High Availability in Azure?
Please refrain from mentioning HA solutions for the SQL Database Engine itself - that is
not the issue at hand.
The issue is that as far as I know (and please correct me if I am wrong), the only way to provide SSAS HA is through clustering that involves share storage -- which is not available in Azure.
So I was wondering if anyone has come across such requirement before and if there are any sort of novel/original solutions
(thinking outside the box).
Regards,
P.

Hi Pmdci,
According to your description, you need implement SSAS environment with High Availability in Microsoft Azure, the problem is that you need to use share storage in this environment which is not available in Azure, right?
Based on my research, a clustered implementation of SSAS can be configured in Microsoft Azure.
A clustered implementation of SSAS can also span from on premises to Azure (or any qualified cloud) if networking is properly configured so that the nodes on premise and in the cloud can see each other, talk to Active Directory, and access storage.
http://azure.microsoft.com/en-in/documentation/articles/storage-dotnet-how-to-use-files/
Regards,
Charlie Liao
If you have any feedback on our support, please click
here.
Charlie Liao
TechNet Community Support

Similar Messages

Choosing VM as high availability for BizTalk's SQL Server databases

Hi,
I'm lloking to choose the architecture of our BizTalk 2013 solution.
The application server will be build on virtual machines, but I still have interrogation about the SQL Server.
Is a SQL Server on a VM supported for BizTalk 2013 ?
Because in case of physical failure, the VM moved to another server can we considered the VM as a solution of High-Availability ?
thanks for your reply.

When the SQL VM fails over what attributes of the server will change? If everything including the server name, the mapped SAN locations (for Databases) and/or the versions of SQL will remain the same then it will behave like a temporary network outage between
the Front-end and the SQL.
If however, the failed over VM has a different set of mapped location for DB then you would need to establish a BizTalk Log Shipping between SQL VM 1 and SQL VM 2. In this scenario, the recovery will require time and cannot be automatic.
A word of caution though. If you have SLA's pertaining to transactions/messages per second with the customer then you might want to evaluate having dedicated boxes of SQL. The SQL Licensing is PER CORE and in a VIRTUAL ENVIRONMENT all the
CORES have to be licensed since the Virtualization does not permit you to BIND the VM to a specific set of CORES. The same would apply for your BizTalk Servers. This just might work out costlier as opposed to the dedicated server environment.
Regards.

NCS High Availability, Database does not sync

Hi All, i have a setup with NCS 1.1 in a HA Environment. The initial Syncing tooks Place. Since then i added Templates, Maps and so on. Now i tested Failover. The Server comes up, logging in possible. Controllers and AP are available, but no Configuration Template or Campus or Map. As the NCS Config Guide promised, syncing should be done automatically. Is there a way to check the synchronisation or have i something forgotten to deploy? Any Hint or Experience?
TiA, Michael

Mike:
I don't think that templates are being copied! as per the guide:
The following files are copied over from the primary to the secondary NCS:•DB password file•all auto provisioning startup config files•all domain maps•all history reports which are generated by scheduled report tasks
Reference: http://www.cisco.com/en/US/docs/wireless/ncs/1.0/configuration/guide/admin.html#wp1178663

SQL Server Analysis Services (SSAS) 2012 High Availability Solution in Azure VM

I have been testing an AlwaysOn high availability failover solution in SQL Server Enterprise on an Azure VM, and this works pretty well as a failover for SQL Server Databases, but I also need a high availability solution for SQL Server
Analysis Server, and so far I haven't found a way to do this. I can load balance it between two machines, but this isn't working as a failover and because of the restriction of not being able to use shared storage in a Failover Cluster in Azure
VM's, I can't set it up as a cluster which is required for AlwaysOn in Analysis Services.
Anyone else found a solution to use an AlwaysOn High Availability for SQL Analysis Services in Azure VM? As my databases are read-only, I would be satisfied with even just a solution that would sync the OLAP databases and switch
the data connection to the same server as the SQL databases.
Thanks!
Bill

Bill,
So, what you need is a model like SQL Server failover cluster instances. (before sql server 2012)
In SQL Server 2012, AlwaysOn replaces SQL Server failover cluster, and it has been seperated to
AlwaysOn Failover Cluster Instances (SQL Server) and
AlwaysOn Availability Groups (SQL Server).
Since your requirement is not in database level, I think the best option is to use AlwaysOn Failover Cluster Instances (SQL Server).
As part of the SQL Server AlwaysOn offering, AlwaysOn Failover Cluster Instances leverages Windows Server Failover Clustering (WSFC) functionality to provide local high availability through redundancy at the server-instance level—a
failover cluster instance (FCI). An FCI is a single instance of SQL Server that is installed across Windows Server Failover Clustering (WSFC) nodes and, possibly, across multiple subnets. On the network, an FCI appears to be an instance of SQL
Server running on a single computer, but the FCI provides failover from one WSFC node to another if the current node becomes unavailable.
It is similar to SQL Server failover cluster in SQL 2008 R2 and before.
Please refer to these references:
Failover Clustering in Analysis Services
Installing a SQL Server 2008 R2 Failover Cluster
Iric Wen
TechNet Community Support

BizTalk 2013 Azure VM (IaaS) High availability

Hi,
We have a 2 BT , 1 SQL configuration for the BizTalk Environment. BizTalk 2013 VMs and SQL 2012 VM provisioned from the gallery. Since there is a limitation on having a highly available SQL tier (for BizTalk) on Azure, we are evaluating a possible
replacement of the Azure setup with a on-premise setup which will guarantee highly available environment(as the SQL tier will be highly available too and with the SSO service). Wanted to know your thoughts on the below topics.
1) Is the BizTalk 2013 Azure (IaaS) used widely in production scenarios today (given the limitation for HA). If yes, what could be the mitigating solution
2) Is the roadmap for Microsoft (BizTalk Server related) going to address this scenario.
Appreciate your inputs in this regard which would help us to make an informed decision to switch back to on-premise.
Thanks,
Ujjwal
-Ujjwal

Theoretically since SQL Always-ON or database mirroring is not supported with BizTalk, SQL Server Azure virtual machines do not support Failover Cluster Instances.
But ensure by selecting “Availability Set” your virtual machine will be deployed to different fault domains and update domain thus ensuring that your application is available during network failures, hardware failures, and any planned downtime. This increases
the case of server/service high availability. And with these features unavailability of the server in Azure is very less.
But if you’re one of those customers you still want to ensure they don’t let any chance of failure (or don’t afford for any failure) and still look to implement failover Cluster Instances, then simple answer is SQL Server Azure virtual machines do not support
Failover Cluster Instances. If you ask about mitigation plan, then ensure you have selected “Availability Set” while provisioning the servers.
To answer to you couple of specific questions:
1) Is the BizTalk 2013 Azure (IaaS) used widely in production scenarios today (given the limitation for HA). If yes,
what could be the mitigating solution - Ican't
answer BizTalk as Iaas is widely used, this question has to be asked to Microsoft directly. And regarding the mitigation plan, as mentioned provisional your server across fault
domains and update domain minimize the down time or increases the high availability.
2) Is the roadmap for Microsoft (BizTalk Server related) going to address this scenario. - As of now SQL Always-ON or database mirroring are not supported for BizTalk and roadmap remains same.
If this answers your question please mark it accordingly. If this post is helpful, please vote as helpful by clicking the upward arrow mark next to my reply.

Cluster install, high availability

Hi All,
Does anyone have a guide or can detail the steps (differences from a single server install) to install BPC 7.0 Microsoft version in a Cluster Environment(High Availability).
Cheers

Hello Jitendra,
SQL should have its own cluster group. So should DTC and the shared storage.
The name of the cluster that Sorin is refering to is the virtual name associated with the clustered resource, so in this case the DNS name of the SQL cluster group. The idea is that BPC does not care that it is running on a cluster, all it wants is a SQL server. The clustering aspect is transparent to BPC and is left to MS Clustering. Same thing if you have a specific group for SSAS, you give that group's DNS name when installing BPC.
The WEB/App servers components should not be installed on the cluster, but rather on NLB nodes.
Reporting services can be installed either on the cluster or on the web/app server, but keep in mind that most companies don't like having a web server on database servers, so we usually install SSRS on the web/app servers. The SSRS database repository would be located on the SQL cluster in either case.
In the case of NLB being used for the web/app servers, the file share should be located on a shared resource, it cannot be local on the web/app servers. It can be located on the cluster, or any dependable network share that uses the same AD security as the servers.
Note that for NLB we usually recommend using a hardware solution as it is faster than using the software solution that is part of Windows, and does not take resources away from the web/app server.
I hope this helps
Best regards,
Bruno Ranchy

Oracle High Availability Training

I am seeking training on High-Availability Oracle solutions - Not just Parallel server, but Standby, and HA configuration in Sun Clustered environments. The training should focus on the RDBMS (8i/9i).
Any recommendations for Oracle or Third-Party training classes would be appreciated.
I understand that Oracle alone will provide high reliability but to get to .9995 reliability (not 5 9s) we'll need some sort of high-availability solution.
Thank You for your time.
null

Hi
Check with Oracle University for High Availability classes. I
had an opportunity to look at their new features papers and they
were very good
sarath

Possible to use Azure SQL as database for RD Connection broker high availability?

I am looking in to setting up a highly available Remote Desktop services service on Azure and note that the high availability for the Connection Broker service needs a full SQL database (rather than the LocalDB used for one instance). Is it possible
to use an Azure SQL database for these purposes (i.e. opposed to VMs running SQL Server)?
Has anyone had any experience with this? This would be nice as I am not looking at thousands of users and the Azure SQL would provide the high availability for the database without creating multiple (expensive) VMs running SQL server.

So far there's no such a feature in azure sql, you can vote for it
http://feedback.azure.com/forums/217321-sql-database/suggestions/423275-enable-sql-service-broker-in-sql-azure

Transaction Log Truncate not working on Sql Server 2012 High Availability Groups

Hi Everyone
Firstly I have tried to search the forum for similar issues but can't seem to find any that match our situation.
We have a SQL Server 2012 High Availability Group with 2 Nodes
Node 1 = Primary
Node 2 = Secondary
Backup Schedule as follows
Full Database Backup @ 00:00
Transaction Log Backup every 30 minutes from 00:30:00 till 23:59:59.
These backups are run by Maintenance Jobs, but we have also tried doing direct backups in SSMS using Backup Database and Backup Log commands.
Before we configured the High Availability group the transaction log backups worked fine.
After we configured the High Availability group we performed a Full Backup and the T-Log schedule did the T-Log backup. The 1st T-log backup truncated the log (Used space Decreased) as expected.
However subsequent T-Log backups do not truncate the T-Log.
This happens both in our acceptance and Live environments. This also happens when running the backups as a Backup operator and sysadmin, this does not seem to be a permissions issue at all.
We have tried running the Backup on the Primary and Secondary Replica.
What about High Availability groups could stop Transaction Log Backups from not truncating the log?
Thanks
James

Hi Sean
Thank you for your reply, please see the output of the sys.databases query below, and some others which you may find usefull.
Query: select database_id,recovery_model_desc, log_reuse_wait, log_reuse_wait_desc from sys.databases
where database_id = 5
Result: database_id   recovery_model_desc   log_reuse_wait   log_reuse_wait_desc
                 5
FULL   0
NOTHING
I also ran the following
select database_id, truncation_lsn, last_received_lsn, last_commit_lsn, last_hardened_lsn, last_redone_lsn,*
from sys.dm_hadr_database_replica_states
go
database_id
truncation_lsn
last_received_lsn
last_commit_lsn
last_hardened_lsn
last_redone_lsn
database_id
group_id
replica_id
group_database_id
is_local
synchronization_state
synchronization_state_desc
is_commit_participant
synchronization_health
synchronization_health_desc
database_state
database_state_desc
is_suspended
suspend_reason
suspend_reason_desc
recovery_lsn
truncation_lsn
last_sent_lsn
last_sent_time
last_received_lsn
last_received_time
last_hardened_lsn
last_hardened_time
last_redone_lsn
last_redone_time
log_send_queue_size
log_send_rate
redo_queue_size
redo_rate
filestream_send_rate
end_of_log_lsn
last_commit_lsn
last_commit_time
low_water_mark_for_ghosts
5
1231833000417170000000
1231833000418880000000
1231833000418880000000
1231833000418890000000
1231833000418880000000
5
1391A499-3F9A-47D5-BCE0-70BC204E2A5B
7E8BFC2E-363F-4C48-86F0-C276D3E0C8D9
0581E17A-6B7B-4B8F-9288-BF765BFBCE77
0
2
SYNCHRONIZED
1
2
HEALTHY
NULL
NULL
0
NULL
NULL
4294967295429490000000000
1231833000417170000000
1
41863
1231833000418880000000
41863
1231833000418890000000
41863
1231833000418880000000
41863
0
25541
0
84404
75304
1231833000418880000000
1231833000418880000000
41863
441019861
5
1231833000417170000000
NULL
1231833000418880000000
1231833000418890000000
NULL
5
1391A499-3F9A-47D5-BCE0-70BC204E2A5B
83B9F00E-D63F-4AC0-98FC-35E48FFA2C6F
0581E17A-6B7B-4B8F-9288-BF765BFBCE77
1
2
SYNCHRONIZED
1
2
HEALTHY
0
ONLINE
0
NULL
NULL
4294967295429490000000000
1231833000417170000000
NULL
NULL
NULL
NULL
1231833000418890000000
NULL
NULL
NULL
NULL
NULL
NULL
NULL
NULL
1231833000418880000000
1231833000418880000000
41863
441019861
And
dbcc loginfo
go
RecoveryUnitId
FileId
FileSize
StartOffset
FSeqNo
Status
Parity
CreateLSN
0
2
458752
8192
1231828
0
128
0
0
2
458752
466944
1231829
0
128
0
0
2
458752
925696
1231830
0
128
0
0
2
712704
1384448
1231831
0
128
0
0
2
19398656
2097152
1231832
0
128
1229654000000040000000
0
2
10199171072
21495808
1231833
2
128
1229656000000010000000
0
2
10199171072
10220666880
0
0
64
1229656000000010000000
0
2
10199171072
20419837952
1231827
0
64
1229656000000010000000
0
2
10199171072
30619009024
0
0
128
1229656000000010000000
0
2
10199171072
40818180096
0
0
128
1229656000000010000000
0
2
10199171072
51017351168
0
0
128
1229656000000010000000
0
2
10199171072
61216522240
0
0
128
1229656000000010000000
0
2
10199171072
71415693312
0
0
128
1229656000000010000000
0
2
10199171072
81614864384
0
0
128
1229656000000010000000
0
2
536870912
91814035456
0
0
64
1229989001661260000000
0
2
536870912
92350906368
0
0
64
1229989001661260000000
0
2
536870912
92887777280
0
0
64
1229989001661260000000
0
2
536870912
93424648192
0
0
64
1229989001661260000000
0
2
536870912
93961519104
0
0
64
1229989001661260000000
0
2
536870912
94498390016
0
0
64
1229989001661260000000
0
2
536870912
95035260928
0
0
64
1229989001661260000000
0
2
536870912
95572131840
0
0
64
1229989001661260000000
0
2
536870912
96109002752
0
0
64
1229989001661260000000
0
2
536870912
96645873664
0
0
64
1229989001661260000000
0
2
536870912
97182744576
0
0
64
1229989001661260000000
0
2
536870912
97719615488
0
0
64
1229989001661260000000
0
2
536870912
98256486400
0
0
64
1229989001661260000000
0
2
536870912
98793357312
0
0
64
1229989001661260000000
0
2
536870912
99330228224
0
0
64
1229989001661260000000
0
2
536870912
99867099136
0
0
64
1229989001661260000000
0
2
536870912
100403970048
0
0
64
1229995000058520000000
0
2
536870912
100940840960
0
0
64
1229995000058520000000
0
2
536870912
101477711872
0
0
64
1229995000058520000000
0
2
536870912
102014582784
0
0
64
1229995000058520000000
0
2
536870912
102551453696
0
0
64
1229995000058520000000
0
2
536870912
103088324608
0
0
64
1229995000058520000000
0
2
536870912
103625195520
0
0
64
1229995000058520000000
0
2
536870912
104162066432
0
0
64
1229995000058520000000
0
2
536870912
104698937344
0
0
64
1229995000058520000000
0
2
536870912
105235808256
0
0
64
1229995000058520000000
0
2
536870912
105772679168
0
0
64
1229995000058520000000
0
2
536870912
106309550080
0
0
64
1229995000058520000000
0
2
536870912
106846420992
0
0
64
1229995000058520000000
0
2
536870912
107383291904
0
0
64
1229995000058520000000
0
2
536870912
107920162816
0
0
64
1229995000058520000000
0
2
536870912
108457033728
0
0
64
1229995000058520000000
0
2
536870912
108993904640
0
0
64
1230004000028400000000
0
2
536870912
109530775552
0
0
64
1230004000028400000000
0
2
536870912
110067646464
0
0
64
1230004000028400000000
0
2
536870912
110604517376
0
0
64
1230004000028400000000
0
2
536870912
111141388288
0
0
64
1230004000028400000000
0
2
536870912
111678259200
0
0
64
1230004000028400000000
0
2
536870912
112215130112
0
0
64
1230004000028400000000
0
2
536870912
112752001024
0
0
64
1230004000028400000000
0
2
536870912
113288871936
0
0
64
1230004000028400000000
0
2
536870912
113825742848
0
0
64
1230004000028400000000
0
2
536870912
114362613760
0
0
64
1230004000028400000000
0
2
536870912
114899484672
0
0
64
1230004000028400000000
0
2
536870912
115436355584
0
0
64
1230004000028400000000
0
2
536870912
115973226496
0
0
64
1230004000028400000000
0
2
536870912
116510097408
0
0
64
1230004000028400000000
0
2
536870912
117046968320
0
0
64
1230004000028400000000
0
2
536870912
117583839232
0
0
64
1230012000103140000000
0
2
536870912
118120710144
0
0
64
1230012000103140000000
0
2
536870912
118657581056
0
0
64
1230012000103140000000
0
2
536870912
119194451968
0
0
64
1230012000103140000000
0
2
536870912
119731322880
0
0
64
1230012000103140000000
0
2
536870912
120268193792
0
0
64
1230012000103140000000
0
2
536870912
120805064704
0
0
64
1230012000103140000000
0
2
536870912
121341935616
0
0
64
1230012000103140000000
0
2
536870912
121878806528
0
0
64
1230012000103140000000
0
2
536870912
122415677440
0
0
64
1230012000103140000000
0
2
536870912
122952548352
0
0
64
1230012000103140000000
0
2
536870912
123489419264
0
0
64
1230012000103140000000
0
2
536870912
124026290176
0
0
64
1230012000103140000000
0
2
536870912
124563161088
0
0
64
1230012000103140000000
0
2
536870912
125100032000
0
0
64
1230012000103140000000
0
2
536870912
125636902912
0
0
64
1230012000103140000000
0
2
536870912
126173773824
0
0
128
1230338000973820000000
0
2
536870912
126710644736
0
0
128
1230338000973820000000
0
2
536870912
127247515648
0
0
128
1230338000973820000000
0
2
536870912
127784386560
0
0
128
1230338000973820000000
0
2
536870912
128321257472
0
0
128
1230338000973820000000
0
2
536870912
128858128384
0
0
128
1230338000973820000000
0
2
536870912
129394999296
0
0
128
1230338000973820000000
0
2
536870912
129931870208
0
0
128
1230338000973820000000
0
2
536870912
130468741120
0
0
128
1230338000973820000000
0
2
536870912
131005612032
0
0
128
1230338000973820000000
0
2
536870912
131542482944
0
0
128
1230338000973820000000
0
2
536870912
132079353856
0
0
128
1230338000973820000000
0
2
536870912
132616224768
0
0
128
1230338000973820000000
0
2
536870912
133153095680
0
0
128
1230338000973820000000
0
2
536870912
133689966592
0
0
128
1230338000973820000000
0
2
536870912
134226837504
0
0
128
1230338000973820000000
0
2
536870912
134763708416
0
0
128
1230338001901440000000
0
2
536870912
135300579328
0
0
128
1230338001901440000000
0
2
536870912
135837450240
0
0
128
1230338001901440000000
0
2
536870912
136374321152
0
0
128
1230338001901440000000
0
2
536870912
136911192064
0
0
128
1230338001901440000000
0
2
536870912
137448062976
0
0
128
1230338001901440000000
0
2
536870912
137984933888
0
0
128
1230338001901440000000
0
2
536870912
138521804800
0
0
128
1230338001901440000000
0
2
536870912
139058675712
0
0
128
1230338001901440000000
0
2
536870912
139595546624
0
0
128
1230338001901440000000
0
2
536870912
140132417536
0
0
128
1230338001901440000000
0
2
536870912
140669288448
0
0
128
1230338001901440000000
0
2
536870912
141206159360
0
0
128
1230338001901440000000
0
2
536870912
141743030272
0
0
128
1230338001901440000000
0
2
536870912
142279901184
0
0
128
1230338001901440000000
0
2
536870912
142816772096
0
0
128
1230338001901440000000
0
2
536870912
143353643008
0
0
128
1230346000103040000000
0
2
536870912
143890513920
0
0
128
1230346000103040000000
0
2
536870912
144427384832
0
0
128
1230346000103040000000
0
2
536870912
144964255744
0
0
128
1230346000103040000000
0
2
536870912
145501126656
0
0
128
1230346000103040000000
0
2
536870912
146037997568
0
0
128
1230346000103040000000
0
2
536870912
146574868480
0
0
128
1230346000103040000000
0
2
536870912
147111739392
0
0
128
1230346000103040000000
0
2
536870912
147648610304
0
0
128
1230346000103040000000
0
2
536870912
148185481216
0
0
128
1230346000103040000000
0
2
536870912
148722352128
0
0
128
1230346000103040000000
0
2
536870912
149259223040
0
0
128
1230346000103040000000
0
2
536870912
149796093952
0
0
128
1230346000103040000000
0
2
536870912
150332964864
0
0
128
1230346000103040000000
0
2
536870912
150869835776
0
0
128
1230346000103040000000
0
2
536870912
151406706688
0
0
128
1230346000103040000000
0
2
536870912
151943577600
0
0
128
1230355000086930000000
0
2
536870912
152480448512
0
0
128
1230355000086930000000
0
2
536870912
153017319424
0
0
128
1230355000086930000000
0
2
536870912
153554190336
0
0
128
1230355000086930000000
0
2
536870912
154091061248
0
0
128
1230355000086930000000
0
2
536870912
154627932160
0
0
128
1230355000086930000000
0
2
536870912
155164803072
0
0
128
1230355000086930000000
0
2
536870912
155701673984
0
0
128
1230355000086930000000
0
2
536870912
156238544896
0
0
128
1230355000086930000000
0
2
536870912
156775415808
0
0
128
1230355000086930000000
0
2
536870912
157312286720
0
0
128
1230355000086930000000
0
2
536870912
157849157632
0
0
128
1230355000086930000000
0
2
536870912
158386028544
0
0
128
1230355000086930000000
0
2
536870912
158922899456
0
0
128
1230355000086930000000
0
2
536870912
159459770368
0
0
128
1230355000086930000000
0
2
536870912
159996641280
0
0
128
1230355000086930000000
0
2
536870912
160533512192
0
0
128
1230364000070870000000
0
2
536870912
161070383104
0
0
128
1230364000070870000000
0
2
536870912
161607254016
0
0
128
1230364000070870000000
0
2
536870912
162144124928
0
0
128
1230364000070870000000
0
2
536870912
162680995840
0
0
128
1230364000070870000000
0
2
536870912
163217866752
0
0
128
1230364000070870000000
0
2
536870912
163754737664
0
0
128
1230364000070870000000
0
2
536870912
164291608576
0
0
128
1230364000070870000000
0
2
536870912
164828479488
0
0
128
1230364000070870000000
0
2
536870912
165365350400
0
0
128
1230364000070870000000
0
2
536870912
165902221312
0
0
128
1230364000070870000000
0
2
536870912
166439092224
0
0
128
1230364000070870000000
0
2
536870912
166975963136
0
0
128
1230364000070870000000
0
2
536870912
167512834048
0
0
128
1230364000070870000000
0
2
536870912
168049704960
0
0
128
1230364000070870000000
0
2
536870912
168586575872
0
0
128
1230364000070870000000
0
2
536870912
169123446784
0
0
128
1230373000054750000000
0
2
536870912
169660317696
0
0
128
1230373000054750000000
0
2
536870912
170197188608
0
0
128
1230373000054750000000
0
2
536870912
170734059520
0
0
128
1230373000054750000000
0
2
536870912
171270930432
0
0
128
1230373000054750000000
0
2
536870912
171807801344
0
0
128
1230373000054750000000
0
2
536870912
172344672256
0
0
128
1230373000054750000000
0
2
536870912
172881543168
0
0
128
1230373000054750000000
0
2
536870912
173418414080
0
0
128
1230373000054750000000
0
2
536870912
173955284992
0
0
128
1230373000054750000000
0
2
536870912
174492155904
0
0
128
1230373000054750000000
0
2
536870912
175029026816
0
0
128
1230373000054750000000
0
2
536870912
175565897728
0
0
128
1230373000054750000000
0
2
536870912
176102768640
0
0
128
1230373000054750000000
0
2
536870912
176639639552
0
0
128
1230373000054750000000
0
2
536870912
177176510464
0
0
128
1230373000054750000000
0
2
536870912
177713381376
0
0
128
1230382000038660000000
0
2
536870912
178250252288
0
0
128
1230382000038660000000
0
2
536870912
178787123200
0
0
128
1230382000038660000000
0
2
536870912
179323994112
0
0
128
1230382000038660000000
0
2
536870912
179860865024
0
0
128
1230382000038660000000
0
2
536870912
180397735936
0
0
128
1230382000038660000000
0
2
536870912
180934606848
0
0
128
1230382000038660000000
0
2
536870912
181471477760
0
0
128
1230382000038660000000
0
2
536870912
182008348672
0
0
128
1230382000038660000000
0
2
536870912
182545219584
0
0
128
1230382000038660000000
0
2
536870912
183082090496
0
0
128
1230382000038660000000
0
2
536870912
183618961408
0
0
128
1230382000038660000000
0
2
536870912
184155832320
0
0
128
1230382000038660000000
0
2
536870912
184692703232
0
0
128
1230382000038660000000
0
2
536870912
185229574144
0
0
128
1230382000038660000000
0
2
536870912
185766445056
0
0
128
1230382000038660000000
The create LSN column seems to have been truncated so here is is again, sorry for the bulky reply.
CreateLSN
0
0
0
0
1229654000000041600001
1229656000000012000001
1229656000000012000001
1229656000000012000001
1229656000000012000001
1229656000000012000001
1229656000000012000001
1229656000000012000001
1229656000000012000001
1229656000000012000001
1229989001661260800316
1229989001661260800316
1229989001661260800316
1229989001661260800316
1229989001661260800316
1229989001661260800316
1229989001661260800316
1229989001661260800316
1229989001661260800316
1229989001661260800316
1229989001661260800316
1229989001661260800316
1229989001661260800316
1229989001661260800316
1229989001661260800316
1229989001661260800316
1229995000058525600316
1229995000058525600316
1229995000058525600316
1229995000058525600316
1229995000058525600316
1229995000058525600316
1229995000058525600316
1229995000058525600316
1229995000058525600316
1229995000058525600316
1229995000058525600316
1229995000058525600316
1229995000058525600316
1229995000058525600316
1229995000058525600316
1229995000058525600316
1230004000028405600295
1230004000028405600295
1230004000028405600295
1230004000028405600295
1230004000028405600295
1230004000028405600295
1230004000028405600295
1230004000028405600295
1230004000028405600295
1230004000028405600295
1230004000028405600295
1230004000028405600295
1230004000028405600295
1230004000028405600295
1230004000028405600295
1230004000028405600295
1230012000103148800147
1230012000103148800147
1230012000103148800147
1230012000103148800147
1230012000103148800147
1230012000103148800147
1230012000103148800147
1230012000103148800147
1230012000103148800147
1230012000103148800147
1230012000103148800147
1230012000103148800147
1230012000103148800147
1230012000103148800147
1230012000103148800147
1230012000103148800147
1230338000973824800555
1230338000973824800555
1230338000973824800555
1230338000973824800555
1230338000973824800555
1230338000973824800555
1230338000973824800555
1230338000973824800555
1230338000973824800555
1230338000973824800555
1230338000973824800555
1230338000973824800555
1230338000973824800555
1230338000973824800555
1230338000973824800555
1230338000973824800555
1230338001901449600555
1230338001901449600555
1230338001901449600555
1230338001901449600555
1230338001901449600555
1230338001901449600555
1230338001901449600555
1230338001901449600555
1230338001901449600555
1230338001901449600555
1230338001901449600555
1230338001901449600555
1230338001901449600555
1230338001901449600555
1230338001901449600555
1230338001901449600555
1230346000103044000554
1230346000103044000554
1230346000103044000554
1230346000103044000554
1230346000103044000554
1230346000103044000554
1230346000103044000554
1230346000103044000554
1230346000103044000554
1230346000103044000554
1230346000103044000554
1230346000103044000554
1230346000103044000554
1230346000103044000554
1230346000103044000554
1230346000103044000554
1230355000086934400510
1230355000086934400510
1230355000086934400510
1230355000086934400510
1230355000086934400510
1230355000086934400510
1230355000086934400510
1230355000086934400510
1230355000086934400510
1230355000086934400510
1230355000086934400510
1230355000086934400510
1230355000086934400510
1230355000086934400510
1230355000086934400510
1230355000086934400510
1230364000070872800554
1230364000070872800554
1230364000070872800554
1230364000070872800554
1230364000070872800554
1230364000070872800554
1230364000070872800554
1230364000070872800554
1230364000070872800554
1230364000070872800554
1230364000070872800554
1230364000070872800554
1230364000070872800554
1230364000070872800554
1230364000070872800554
1230364000070872800554
1230373000054757600431
1230373000054757600431
1230373000054757600431
1230373000054757600431
1230373000054757600431
1230373000054757600431
1230373000054757600431
1230373000054757600431
1230373000054757600431
1230373000054757600431
1230373000054757600431
1230373000054757600431
1230373000054757600431
1230373000054757600431
1230373000054757600431
1230373000054757600431
1230382000038664800234
1230382000038664800234
1230382000038664800234
1230382000038664800234
1230382000038664800234
1230382000038664800234
1230382000038664800234
1230382000038664800234
1230382000038664800234
1230382000038664800234
1230382000038664800234
1230382000038664800234
1230382000038664800234
1230382000038664800234
1230382000038664800234
1230382000038664800234
Thanks
James

Multi Site SQL High Availability group

Hi,
We have our primary Data Centre where we have 2 MS SQL 2012 Enterprise Servers and 2 SharePoint 2013 Enterprise servers.
We have SQL High Availability group implemented on our primary Site (Site A)
Site A has subnet of 192.168.0.0.
We recently added a new DR Site (Site B). Site B we have MS SQL 2012 Enterprise Servers. Site B have a subnet of
172.1.1.0
Both sites are connected via a VPN Tunnel. MS SQL 2012 Enterprise Server on Site B has been added in have SQL High Availability
group of Site A.
SQL High Availability group have 2 IPs 192.168.0.32 and 172.1.1.32. SQL Listener have 2 IPs 192.168.0.33 and 172.1.1.33
We want to make sure that if Site A completely down then Site B work as an active Site. But when Site A down we are unable
to ping High Availability group and Site B is unable to work as active site. SQL and SharePoint services are completely down.
Site A has AD(Primary Domain Controller) and Site B has ADC(Additional Domain Controller).
Site A has witness server.
We are using Server 2012 Data Centre
Please suggest.
Farooq

SharePoint is not the same as any other applications. The DR site has to be a completely different farm from your production. This means that the SharePoint_AdminContent and config databases on both farms are different and should not be included in the Availability
Group (they do not support asynchronous Availability Group.) Only content databases and other SharePoint databases supported in an Availability Group should be included as per this
TechNet article. Have a look at this
blog post for your networking configuration.
The reason your Windows cluster service goes down in the DR data center when the when your primary data center goes down is because the cluster has no majority votes. You have 4 available votes in your cluster - 3 in the primary data center in the form of
the 2 Availability Group replicas and the witness server and 1 in the DR data center. If the Windows cluster does not have majority of votes, it automatically shuts down the cluster. This is by design. That is why when this situation happens, you need to force
the cluster to start without a quorum as described in
this article (Windows Server 2012 R2 introduced the concept of dynamic witness and dynamic quorum to address this concern.) By default, the IP address of the Availability Group listener name will be registered on all of the DNS servers if the cluster is
running Windows Server 2012 and higher (this is the RegisterAllProvidersIP property that Samir mentioned.) However, you need to flush the DNS cache on the SharePoint web and application servers and point them to the correct IP address on the DR server after
failover. This is because the default TTL value of the Availability Group listener name is 20 minutes.
It is important to define your DR strategies and objectives when designing the architecture to make sure that the solution will meet your goals. This will also help you automate some of the processes in the DR data center when failover or a disaster occurs.
Edwin Sarmiento SQL Server MVP | Microsoft Certified Master
Blog |
Twitter | LinkedIn
SQL Server High Availability and Disaster Recover Deep Dive Course

Access Services 2013 high available on SQL 2012?

Hi,
Does anyone know how we get the randomly created databases from access services 2013 services high available on our SQL 2012 cluster?
For the SharePoint content databases, we use the ‘always on’ functionality of SQL 2012. This functionality is not supported for Access services 2013.
Thanks in advance,
Johan

Hi Edwin,
Thanks again for your answer.
Failover clustering is a perfect solution for high availability.
A last additional question:
Now we using ‘Always On groups’. The 2 instances are located one a different physical location.With that configuration, we have a High available solution and disaster recovery solution.
If we going for a Failover Cluster we have a High Available solution, but we don’t have a disaster recovery solution anymore because everything is located on the same physical location.
We can configure SQL mirroring, but then we have the same behavior like the ‘always On Groups’.-> Not possible to delete db’s from SharePoint and not automatically mirrored when created a new access services 2013 db.
Is there any solution/configuration to accomplish this?
Thanks,
Johan

Is the Azure Files data highly available/replicated under the covers?

I am assuming that with Azure Files, under the covers data is replicated multiple times for High Availability. Is that correct? For some applications, typically failover application, where the application doesn't assume highly available storage;
the applications themselves build logic to either replicate/sync data. An example is Elastic Search. In these cases, the system lands up making too many copies. Is the Azure File Semantic the same as blob store, in this regard.

Hi,
Would request you to refer to the article below to understand Azure File Service (in preview now):
Introducing MS Azure File Service
http://blogs.msdn.com/b/windowsazurestorage/archive/2014/05/12/introducing-microsoft-azure-file-service.aspx
Below article helps us understand the same better with a "how-to" perspective:
The Azure File Service
http://clemmblog.azurewebsites.net/azure-file-service/
Lastly, would like to keep you informed on the Features Not Supported By The Azure File Service
http://msdn.microsoft.com/en-us/library/azure/dn744326.aspx
Thank you,
Arvind

SQL Server 2005 High Availability and Disaster Recovery options

Hi, We are are working on a High Availability & Disaster Recovery Planning solution for an application database which is on SQL Server 2005. What different options have we got to implement this for SQL Server 2005 and after we have everything setup how
do we test the failover is working?
Thanks in advance.........
Ione

DR : Disaster recovery is the best option for the business to minimize their data loss and downtime. The SQL server has a number of native options. But, everything is depends upon your recovery time objective RTO and recovery point objective RPO.
1. Data center disaster
Geo Clustering
2. Server(Host)/Drive (Except shared drive) disaster
Clustering
3. Database/Drive disaster
Database mirroring
Log shipping
Replication
Log shipping
Log shipping is the process of automating the full database backup and transaction log on a production server and then automatically restores them on to the secondary (standby) server.
Log shipping will work either Full or Bulk logged recovery model.
You can also configure log shipping in the single SQL instance.
The Stand by database can be either restoring or read only (standby).
The manual fail over is required to bring the database online.
Some data can be lost (15 minutes).
Peer-to-Peer Transactional Replication
Peer-to-peer transactional replication is designed for applications that might read or might modify the data in any database that participates in replication. Additionally, if any servers that host the databases are unavailable, you can modify the application
to route traffic to the remaining servers. The remaining servers contain same copies of the data.
Clustering
Clustering is a combination of one or more servers it will automatically allow one physical server to take over the tasks of another physical server that has failed. Its not a real disaster recovery solution because if the shared drive unavailable we cannot
bring the database to online.
Clustering is best option it provides a minimum downtime (like 5 minutes) and data loss in case any data center (Geo) or server failure.
Clustering needs extra hardware/server and it’s more expensive.
Database mirroring
Database mirroring introduced in 2005 onwards. Database Mirroring maintain an exact copy of a database on a different server. It has automatic fail over option and mainly helps to increase the database availability too.
Database mirroring only works FULL recovery model.
This needs two instances.
Mirror database always in restoring state.
http://msdn.microsoft.com/en-us/library/ms151196%28v=sql.90%29.aspx
http://blogs.technet.com/b/wbaer/archive/2008/04/19/high-availability-and-disaster-recovery-with-microsoft-sql-server-2005-database-mirroring-and-microsoft-sql-server-2005-log-shipping-for-microsoft-sharepoint-products-and-technologies.aspx
http://www.slideshare.net/rajib_kundu/disaster-recovery-in-sql-server
HADR Considerations
Need to Understand the business motivations and regulatory requirements that are driving the customer's HA/DR requirements. Understand how your customer categorizes the workload from an HA/DR perspective. There is likely to be an alignment between the needs
and categorization.
Check for both the recovery time objective (RTO) and the recovery point objective (RPO) for different workload categories, for both a failure within a data center (local high availability) and a total data center failure (disaster recovery). While RPO and
RTO vary for different workloads because of business, cost, or technological considerations, customers may prefer a single technical solution for ease in operations. However, a single technical solution may require trade-offs that need to be discussed with
customers so that their expectations are set appropriately.
Check and understand if there is an organizational preference for a particular HA/DR technology. Customers may have a preference because of previous experiences, established operational procedures, or simply the desire for uniformity across databases from
different vendors. Understand the motives behind a preference: A customers' preference for HA/DR may not be because of the functions and features of the HA/DR technology. For example, a customer may decide to adopt a third-party solution for DR to maintain
a single operational procedure. For this reason, using HA/DR technology provided by a SAN vendor (such as EMC SRDF) is a popular approach.
To design and adopt an HA/DR solution it is also important to understand the implications of applying maintenance to both hardware and software (including Windows security patching). Database mirroring is often adopted to minimize the service disruption
to achieve this objective.
HADR Options :
Failover clustering for HA and database mirroring for DR.
Synchronous database mirroring for HA/DR and log shipping for additional DR.
Geo-cluster for HA/DR and log shipping for additional DR.
Failover clustering for HA and storage area network (SAN)-based replication for DR.
Peer-to-peer replication for HA and DR (and reporting).
Backup & Restore ( DR)
keep your server DB backups in network location ( DR)
Always keep your sql server 2005 upto date, in case if you are not getting any official support from MS then you have to take care of any critical issues and more..
Raju Rasagounder Sr MSSQL DBA

High Availability Installation issue (ASCS instance did not stop)?

Hi,
We are facing an issues in High availability system installation. (ERP ECC6.0 EHP5) We have completed Node A installation.
We are installing based on Virtual IP.
Node A Installation:
Steps 1: ASCS instance
Step 2 : DB Instance
Step 3: Enqueue replciation Server istance
Step 4: Central instance
I have complete these steps successfully. But We have started Node B installation. We have faced error in Node B. Error is on ASCS instance.
Error Details: "SID/ASCS00(partially) did not stop. " In ASCS instance 5th phase, we are getting this error.
Due to this error, We are not able to continue the process.
Could you please help to solve this.
Thanks!!!

Hi Sir/Madam
I have one to install SAP cluster with two node with window server 2003 x64 R2, SQL server 2005.
below it is my step.
1. assume my window cluster and sql server are working fine.
2. I have start install ASCS on virtual disk from node 1.
3. i have install First MSCS on virtual from node 1.
4. I have install Database instance on virtual disk from node 1.
5. I have install Second MSCS on virtual from node2.
6 I have install ERS on physic disk on node 1.
7. i have instgall ERS on physic disk on node2.
8 i have install CI on physic disk on node 1
9 i have install DI on physic disk on node 2.
this is procedure that my consultant have set up on my real sap system . but when I try to install on lab . i got error when i finish on step 5 above .
could you please tell me the above step is correct or not ?
thanks .

Sql Server High availability failover trigger

Hello,
We are implementing sql server 2012 availability groups (AG). Our secondary databases are not accessible in order to save licenses.
We have a lot of issues concerning monitoring, backup and SSIS. They all come down to the fact that they want basic information from the secondary, that is not accessible. We are implementing SSIS, which is supported on AG, but the SSISDB is encrypted.
Backup problem
The secondary instance does not know anything about the backups made in the primary instance. After a failover differential backups fail.
SSIS problem:
There is a blog (http://blogs.msdn.com/b/mattm/archive/2012/09/19/ssis-with-alwayson.aspx) that suggest to make a job that checks whether the status has changed from secondary to primary. If so, you can decrypt and encrypt again.
This job has to be executed every minute. Which is way too much effort for an event that happens once in a while. There are a few other problems with this solution. The phrase "use ssisdb" has to be included in the a job step. And the
jobstep fails. The secondary is not accessible.
Monitoring problems:
We use Microsoft tooling for monitoring: SCOM. Scom does not recognize a non readable secondary and tries to login continuously.
There are a few solutions that I can think of:
- sql server build in failover trigger
- Special status of secondary database.
Failover trigger:
We would like a build-in failover trigger, in stead of a time based job, that starts a few standard maintenance actions if only at the time (or directly after) a failover has occurred. Because now our HA cluster is not really high available until :
- SSISDB works and is accessible after failover
- Backup information is synchronised
- SCOM monitoring skips the secondary database (scom produces loads of login failures)
Does anyone have any suggestion how to fix this?

No built in trigger can achieve your requirement.

SSAS High Availability in Azure (not SQL DBE)

Similar Messages

Maybe you are looking for