Manually editing NetworkConfig.xml for multi-site VPN

I'm designing a network comprised of on-premise, Azure East US VNet and Azure North Central US VNet. East will be my production VNet and North Central will be backup/dev. I want them routed together as well and accessible via on premise-VPN with RRAS and
using point-to-site. I have successfully made all these connections individually in test scenarios but never simultaneously as the portal only has one field for a site-to-site VPN and this scenario requires two.
I understand it's possible to create this design by editing the NetworkConfig.xml file. However, it's confusing to me why even when making small or no edits to the NetworkConfig.xml file the portal tells me my existing networks will be deleted and re-created.
Does that take out my gateway IPs, etc as well? If so, I'll have to re-enter all the new IPs in RRAS and basically start from scratch. I have a few test VMs in each VNet as well to test connectivity between sites. I'm guessing those would have to go too or
the VNets wouldn't be able to be deleted in the first place.
Also, an unrelated static network that I make no changes to in the xml file says it will be updated when I upload even an unchanged NetworkConfig.xml. This is concerning as it's hard to know what downtime and issues I'm going to cause if I save the new file.
Any tips would be appreciated. My sense is you have to have your whole design in your head first, get it into the NetworkConfig.xml and then move forward with creating the gateways and entering your IPs into RRAS or whatever your VPN tool my be. Being able
to edit existing VNets, specifically adding additional site-to-site VPNs after they are in use would really be helpful. Perhaps this is possible and I'm missing something.

Hi,
Firstly, you need to delete the gateway and all resources in the virtual network before you delete it.
In addition, based on my experience, you just need to add the local network sites parts into the network configuration file for a multi-site VPN connection. If you are afraid that the virtual
network configuration would be wrong after importing, I recommend you to keep the previous network configuration file as a backup. In addition, I am glad to help you with the network configuration file, you can also share me the whole network configuration
file and tell me some more detailed information about your requirement. (Please hide the Public IP addresses for your VPN gateways and VPN device.)
Meanwhile, you can also refer to the link below for reference:
https://msdn.microsoft.com/en-us/library/azure/dn690124.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]

Similar Messages

Manually edit config.xml

Hi,
I'm working with WL 8.1SP3, and I need to add the atribute 'StatementTimeout' to
'JDBCConnectionPool' entry in config.xml.
The weblogic console can not do the job, but manually edit config.xml work fine.
Subsequently when I use WL console to make other changes, the system overwrite any manual previous changes.
How can I make persistent manual changes in config.xml file?

On the new machine I am trying to create a new set of servers to be added to the cluster. However I am running into errors, of which various post suggest changing some of the security stuff in the config. But I have not found a way to persist my modifications. Each time I restart it gets overwritten again.
I am running in production mode, could this be the problem?
I have tried stopping everything, delete all .lok files on both machines, and restarting everything. On startup the .lok files reappear and my changes are reverted.

Deploy Exchange 2013 Edge Transport Server for multi-site environment

Hi,
I have a multi-site Exchange 2013 environment. The configurations are as below.
Active Directory Sites and Exchange Servers.
SiteA - EXMB1 & EXCAS1
SiteB - EXMB2 & EXCAS2
SiteC - EXMB3 & EXCAS3
All sites are connected via VPN. (Good speed. No latency issues)
All the three Mailbox Servers are in DAG. Only one mailbox database. All servers running Exchange 2013.
I am planning to deploy Edge Servers in the infrastructure (I am doing it for the first time). Normally, it will be in DMZ.
Now, I can deploy 2 Edge Servers for reliability.
Question.
1. Can I deploy 2 Edge Servers and create subscription to all the mailbox server in 3 different site? Or, is it like one edge server can make subscription to only mailbox servers in one Active Directory Site? I am not sure about this and could not find much
information from TechNet.
One Edge Server can make subscription to all 3 mailbox server in 3 sites. Similarly, I can make the subscriptions in the second edge server as well. Configure 2 external MX records with the same priority so that there will be some load balancing.
Also, in such a case if the mailbox database become active from a different site, I need not make any new changes to the Edge Servers right?
2. If the first way is not correct, I will have to deploy 1 Edge Server each for each of the Active Directory Site. (In DMZ only, not in domain)
Make Edge Subscription to the mailbox server in corresponding site.
Make 1 MX record and point it to the Edge Server which is subscribed to the Mailbox Server from which the Database is Active. The problem is, every time will have to change the DNS record when ever the database copy is activated from a different mailbox
server. And the issues with propagation.. delay..
I am not sure which of the above 2 ways will work. Appreciate suggestions from anyone who have previous experience with similar infrastructure.
Thanks in advance. :)

Hi
One or more Edge Transport servers can be subscribed to a single Active Directory site. However, an Edge Transport server can't be subscribed to more than one Active Directory site. If you have more than one Edge Transport server deployed, each server can be
subscribed to a different Active Directory site. Each Edge Transport server requires an individual Edge Subscription.
A subscribed Edge Transport server is associated with a particular Active Directory site. If more than one Mailbox server exists in the site, any of them can replicate data to the subscribed Edge Transport servers.
I don't think there is a solution to subscribe edge servers for more than 1 site. Edge Servers can be scoped only to one site.
Remember to mark as helpful if you find my contribution useful or as an answer if it does answer your question.That will encourage me - and others - to take time out to help you Check out my latest blog posts on http://exchangequery.com Thanks Sathish
(MVP)

Simplifying printers for multi-site users

Windows 2008 R2
Windows 7 Enterprise
Topology: Central network with about 50 users/computers and 5 servers. 25 remote sites, 2-4 users/computers per site (no servers at the sites). Each site also has one network printer.
Currently all sites have the same IP scheme (we use DirectAccess for file access so unique subnets are not required). All of the printers are the same model and have the same static IP. So no matter what site a roaming user goes to printing works with no
confusion.
Some new technology is being implemented that will require us to make unique subnets (which is actually desirable for obvious reasons). At the same time we will be implementing site-to-site VPNs, so there will be full connectivity to AD/central site.
So, here in lies the problem. Our super simple printing solution, now will not work. Some users roam to a dozen sites or more, will they have to have that many printers? Then they have to make sure to print to the one that is online/ready? Is there a GPO
setting to hide offline printers or something? I wouldn't care if there were 25 print queues as long as only available printers were displayed. I see that there is some location aware printing features of AD/W7, but I am concerned all the offline printers
will confuse users.
Any ideas?

Have you considered Group Policy Preferences - Printers ?
http://technet.microsoft.com/en-us/library/cc731562.aspx
http://www.grouppolicy.biz/tag/printer/
http://deployhappiness.com/best-practices-for-group-policy-printer-preferences/
http://blogs.technet.com/b/grouppolicy/archive/2009/06/24/gp-preferences-set-a-default-printer.aspx
https://the.geekorium.com.au/deploy-printers-with-group-policy-without-using-local-loopback/
Don
(Please take a moment to "Vote as Helpful" and/or "Mark as Answer", where applicable.
This helps the community, keeps the forums tidy, and recognises useful contributions. Thanks!)

DNS for multi-site same server scenario

I setting up the DNS for a multi-site server, I understand that the second (and subsequent) site needs to be an alias of the first.
I have tried setting up the DNS entires as aliases (CNAME) as well as A records to no avail.
I am sure that it is me, but what am I missing?
I am unable to access these sites locally so I am positive that no on can access the site outside of the firewall.
Thank you!

There's not much detail there to go on...
In general, yes, you should create one A record for the host, e.g.:
webserver.domain1.com. IN A 192.168.1.2
Then other domains should, ideally, point to this via a CNAME:
www.domain2.com. IN CNAME webserver.domain1.com.
Technically, it's OK to have additional A records pointing to the same IP, it just makes it a little harder to keep track of, and changing server addresses is a PITA (there's only one place to change it when using CNAMEs).
As to what your issue is, there's no way of knowing without seeing your domain records and the name server logs. bind is pretty good about logging errors and often provides a good clue when things are amiss. If I had to hazard a guess, though, I'd say you missed a trailing . on the CNAME records, but that's largely a shot in the dark without more information.

Use configuration management for multi site application

Hi,
My client develop an application multi site with designer 6i. We want to use the configuration management .
The application will be deploy in 10 sites, but not necessary with the same version of the application.
You want to control that with the configuration management of designer 6i.
Someone has some experience with that ??
Can i have some reference or detail experience ??
Thanks a lot
chris

I asked this sort of question for creating a live and a test release of an application. The answer I got was to create a configuration of based on my application and then to create an applications based on the the versions of the configuration.
Then, I could check the configuration against the main workarea to tell me what was out of date.
I could also use the configuration wizard to create a new version (of the configuration) selecting the versions of the modules I wanted (ie: newer ones). Then I created a new version of the release application using the new configuration.
Finally, in the command tool I can select the release work area which will extract correct module versions (I have the .fmbs) and I can compile a release.
I guess your solution here is to have a main workarea with all the source, then a configuration of that and then one release application for every site. Each release application could use a different version of the configuration - depending on how up to date they are.
HTH
Steve

Design view not editable or viewable for validated site

I can see the site fine at http://www.wwu.edu/atustest - it validates and is viewable in the browser and in "Live" or "code" view in Dreamweaver. However when I try to display it in "Design" view nothing shows except the header, and that is garbled. None of the content is viewable or editable. Help! I cannot deliver this to my non-coding users.

If my code challenged clients want to maintain their own site, I give them a CMS. DW is for experienced web developers. It's not for amateurs.
Perch ($59 license per site)
PHP & MySql required
http://grabaperch.com/
WebAssist Design Extender with CMS
http://www.webassist.com/dreamweaver-extensions/design-extender
Adobe Business Catalyst (subscription includes CMS & web hosting)
http://www.businesscatalyst.com/
Nancy O.

Failover option(s) for remote site VPN

Currently, I have several remote VPN locations, in which most of them of ISDN dial backup in case the primary connection goes down. Can I use DSL/T1 circuit as a failover/dial backup link? If so, please point me to the right direction in finding documentations. Thank you.

As per your config, I guess you are referring to the VPN connectivity with Peer IP 166.149.125.81.
If yes than you have missed the other subnets of main site in the ACL outside_cryptomap_1
which have been mapped in the VPN with this Peer.
object-group network DM_INLINE_NETWORK_2
under this statement match the network-object with the subnets at main site that needs communication with the subnet 192.168.90.x/24 at remote site (same as you have done for 192.168.0.0/24 subnet)and vice versa.
BR
Please rate if this solve your problem.

SLP Advice for Multi Site

Hi
I did post another SLP query related to this but received no responses. I have been reading up on SLP setup, we have had our existing SLP setup in place for a number of years, however we have had issues where if a site link is off the site cannot log in locally at all - it is obviously trying to locate resources in a container in does not have a replica of.
When our SLP was setup the resources were placed at the central site under the central site's container. I am wondering if a) it is OK to move the SLP scope container (and DA object?) to root and then place a root replica at each WAN site? (I have read you should not place a local DA at each site though had considered this also) and b) should I place a backup SLPDA somewhere incase there is a problem with the server housing the DA (which has also happened to me - and sites could not log in at all while it was restarting!) Can I point to 2 in my server and client configs?
We will be moving to OES2 next year but I need to make sure this keeps operational as efficiently as possible until that time.
Advice from a Novell expert would be much appreciated
Thanks

I would be interested in knowing more about this as well if anyone answers....I would not hold my breath. :-)
We have 10 partitions/containers which are scattered location-wise. We have 1 server in each container and are running slpdas on 2 servers in HQ pointing to a central scope. However, I have found that if a link isolates one of the containers from talking to the HQ container with the scope and slpda, then login is not possible from the local isolated container. I would like to set up slp to mitigate this if possible. We use SLES10/OES2 so this is not as easy as it was with NetWare 6.5....
--El
Originally Posted by shazzypoos
Hi
I did post another SLP query related to this but received no responses. I have been reading up on SLP setup, we have had our existing SLP setup in place for a number of years, however we have had issues where if a site link is off the site cannot log in locally at all - it is obviously trying to locate resources in a container in does not have a replica of.
When our SLP was setup the resources were placed at the central site under the central site's container. I am wondering if a) it is OK to move the SLP scope container (and DA object?) to root and then place a root replica at each WAN site? (I have read you should not place a local DA at each site though had considered this also) and b) should I place a backup SLPDA somewhere incase there is a problem with the server housing the DA (which has also happened to me - and sites could not log in at all while it was restarting!) Can I point to 2 in my server and client configs?
We will be moving to OES2 next year but I need to make sure this keeps operational as efficiently as possible until that time.
Advice from a Novell expert would be much appreciated
Thanks

Azure multiple site-to-site VPNs (dynamic gateway) with Cisco ASA devices

Hello
I've been experimenting with moving certain on-premise servers to Azure however they would need a site-to-site VPN link to our many branch sites e.g. monitoring of nodes.
The documentation says I need to configure a dynamic gateway to have multiple site-to-site VPNs. This is not a problem for our typical Cisco ISR's. However three of our key sites use Cisco ASA devices which are listed as 'Not Compatible' with dynamic routing.
So I am stuck...
What options are available to me? Is there any sort of tweak-configuration to make a Cisco ASA work with Azure and dynamic routing?
I was hoping Azure's VPN solution would be very flexible.
Thanks

Hello RTF_Admin,
1. Which is the Series of CISCO ASA device you are using?
Thank you for your interest in Windows Azure. The Dynamic routing is not supported for the Cisco ASA family of devices.
Unfortunately, a dynamic routing VPN gateway is required for Multi-Site VPN, VNet to VNet, and Point-to-Site.
However, you should be able to setup a site-to-site VPN with Cisco ASA 5505 series security appliance as demonstrated in this blog:
Step-By-Step: Create a Site-to-Site VPN between your network and Azure
http://blogs.technet.com/b/canitpro/archive/2013/10/09/step-by-step-create-a-site-to-site-vpn-between-your-network-and-azure.aspx
You can refer to this article for Cisco ASA templates for Static routing:
http://msdn.microsoft.com/en-us/library/azure/dn133793.aspx
If your requirement is only for Multi-Site VPN then there is no option but to upgrade the device as Multisite VPN requires dyanmic routing and unfortunately there is no tweak or workaround due to hardware compatibility issue.
I hope that this information is helpful
Thanks,
Syed Irfan Hussain

Azure Site to Site VPN with Cisco ASA 5505

I have got Cisco ASA 5505 device (version 9.0(2)). And i cannot connect S2S with azure (azure network alway in "connecting" state). In my cisco log:
IP = 104.40.182.93, Keep-alives configured on but peer does not support keep-alives (type = None)
Group = 104.40.182.93, IP = 104.40.182.93, QM FSM error (P2 struct &0xcaaa2a38, mess id 0x1)!
Group = 104.40.182.93, IP = 104.40.182.93, Removing peer from correlator table failed, no match!
Group = 104.40.182.93, IP = 104.40.182.93,Overriding Initiator's IPSec rekeying duration from 102400000 to 4608000 Kbs
Group = 104.40.182.93, IP = 104.40.182.93, PHASE 1 COMPLETED
I have done all cisco s2s congiguration over standard wizard cos seems your script for 8.x version of asa only?
(Does azure support 9.x version of asa?)
How can i fix it?

Hi,
As of now, we do not have any scripts for Cisco ASA 9x series.
Thank you for your interest in Windows Azure. The Dynamic routing is not supported for the Cisco ASA family of devices.
Unfortunately, a dynamic routing VPN gateway is required for Multi-Site VPN, VNet to VNet, and Point-to-Site.
However, you should be able to setup a site-to-site VPN with Cisco ASA 5505 series security appliance as
demonstrated in this blog:
Step-By-Step: Create a Site-to-Site VPN between your network and Azure
http://blogs.technet.com/b/canitpro/archive/2013/10/09/step-by-step-create-a-site-to-site-vpn-between-your-network-and-azure.aspx
You can refer to this article for Cisco ASA templates for Static routing:
http://msdn.microsoft.com/en-us/library/azure/dn133793.aspx
Did you download the VPN configuration file from the dashboard and copy the content of the configuration
file to the Command Line Interface of the Cisco ASDM application? It seems that there is no specified IP address in the access list part and maybe that is why the states message appeared.
According to the
Cisco ASA template, it should be similar to this:
access-list <RP_AccessList>
extended permit ip object-group
<RP_OnPremiseNetwork> object-group <RP_AzureNetwork>
nat (inside,outside) source static <RP_OnPremiseNetwork>
<RP_OnPremiseNetwork> destination static <RP_AzureNetwork>
<RP_AzureNetwork>
Based on my experience, to establish
IPSEC tunnel, you need to allow the ESP protocol and UDP Port 500. Please make sure that the
VPN device cannot be located behind a NAT. Besides, since Cisco ASA templates are not
compatible for dynamic routing, please make sure that you chose the static routing.
Since you configure the VPN device yourself, it's important that you would be familiar with the device and its configuration settings.
Hope this helps you.
Girish Prajwal

SQL Server 2012 Multi-Site clustering with 2 nodes for HA and DR

Usually we setup 2 Node Prod cluster for Local HA and 1 or 2 Nodes in other data centre for DR
Given that we have an option to setup multi-site / multi-subnet clustering from SQL 2008 R2/2012. I am planning to use just 2 nodes, 1 in prod data centre and 1 in DR data centre with 2 or 3 instances. This will act as both HA and DR solution.
I would like to know if this solution is good, and any disadvantages, any best practices, etc.? By implementing this I can save some cost on physical servers.
Following will be configured:
* Will be using different subnets, quorum on different server with "Node and File Share Majority"
* All virtual IPs will be registered for virtual name, and Subnetdelay, Subnet threshold will be modified accordingly
* All nodes on same domain
* Use SAN Disk with replication to DR site

SQL 2008 R2 doesn't support multi-subnet clustering. You would still need 3rd party component like VLAN and Disk Replication. SQL 2012 is the first version to support multi-subnet clustering without using VLAN. you would still need disk replication hardware/software.
Taken from my book
Since nodes are often located in two different data centers at geographically dispersed locations, there is no shared storage between the nodes in a multi-site cluster. Clustering across two different data centers provides a higher level of availability and
protection at the storage level as we have more than a single copy of the data.
For SAN replication technology implemented in such clusters, the main activity is to keep data replicated between the sites. Typically, if we have nodes on two different sites, we would have two different network infrastructures and the nodes would be in
different subnets. In such cases, if we are on a SQL Server version before 2012, we need to use third party VLAN (Virtual LAN) technology so that one IP address travels between two sites. This is called wide-IP. Companies hesitate with this solution because
of the need to buy a third party solution to deploy the VLAN. Using VLAN technology means the same IP address would failover to the remote site in case of a local site disaster. Network administration might consider this as an overhead to maintenance and an
extra piece of the networking component that needs to be secure.
With SQL Server 2012 we do not need to use stretch VLAN technology but SAN replication is still needed for multi-site clustering. The OS version for this can be from Windows Server 2008 R2 and above. In this deployment, we can have a SQL virtual network
name having an “OR” dependency on two different IP addresses. One address would be representing each subnet. With the “OR” dependency, if IP1 or IP2 is online we just use the network name. This is one of the Enterprise Editions only features.
Other option which you can think of, without using 3rd party solutions would be AlwaysOn Availability Group. I have written details about it in my book.
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
Author: SQL Server 2012 AlwaysOn -
Paperback, Kindle

Windows 2008 R2 Multi-Site (geo) Cluster File Server

We need to come up with a new HA file server (user drive data) solution complete with DR. It needs to be 2008 R2, cater for about 25TB of data, and be suitable for 500 users (nothing high end on I/O). I don't want to rely on DFS for any form of resilience
due to its limitations for open files. We have two active-active data centers (a third can be used for file share quorum).
We could entertain:
1)
Site1 - 2 x HP ProLiants with MSA storage, replicating with something like DoubleTake to a third HP Proliant at site 2 for DR.
2)
Site1 - 2 x HP ProLiants with local storage and VSA or HP StoreVirtual array (aka LeftHand), using SAN replication to site 2 where we could have a one or two node config of the same setup.
Ideally I would like all 3/4 nodes in these configurations to be part of the same multi-site cluster to ensure resources like file shares are in sync. With two pieces of storage across this single cluster (either a DoubleTake or SAN replication to local
disks in DR) will this work? How will the cluster/SAN fail over the storage?
We do have VMWare 5.0/1 (not 5.5 yet). We don't have Hyper-V yet either. Any thoughts on the above, and possible alternatives welcome. HA failover RTO we'd like in seconds. DR longer, perhaps 30 mins.
Thanks in advance for any thoughts and guidance.

For automated failover between sites, the storage replication needs to have a way to script the failover so you can have a custom resource that performs the failover at the SAN level before the disks come online.
DoubleTake has GeoCluster which should accomplish this. I'm not sure about how automated Lefthand's solution is for multi-site clusters.
VMware has Site Recovery Manager, though this is really an assisted failover and not really an automatic site failover solution. It's automated so that you can failover between sites at the push of a button, but this would need to be a planned failover.
RTO of seconds might be difficult to accomplish as you need to give the storage replication enough time to reverse direction while giving the MS cluster enough time to bring cluster applications online.
When planning your multi-site cluster, I'd recommend going with 2 nodes on each site and then use the file share witness quorum on your 3rd site. If you only had one node on the remote site, the primary site would never be able to failover to the remote
site without manually overriding the quorum as 1 node isn't enough to gain enough votes for quorum. With 2 nodes on each site and a FSW, each site has the opportunity to gain enough votes to maintain quorum should one of the sites go down.
Hope this helps.
Visit my blog about multi-site clustering

Cisco ASA 5510 site to site VPN only

Hi,
Need some expert help. I will be deploying the CISCO ASA 5510 in VPN site to site scenario only. One interface will be for the WAN and the other LAN interface is connected to another firewall appliance. The main purpose of the ASA is for branch site VPN connection only. My default gateway is pointing to the Internet router on my WAN inteface. Should NAT be enabled on my WAN inteface? The only expected traffic to go thru my ASA is VPN traffic to the other site. I have already defined static routes and have gone thru the wizard for site to site VPN and added my local and remote networks. Also how do I approach my access policies, the default deny any any is in place. Should I allow anything on it? The firewall connected to my LAN interface is expected to do the filtering, like I said the ASA's purpose is just to do VPN site to site. Thanks all

Thanks Jon. That is what I want to clarify as well, running the VPN site to site wizard, will automatically create the 'cryptomap' access rules, will the existing deny all rule apply to the VPN traffic? I think there was an option that VPN traffic will bypass access rules.
So having NAT enabled for anything that goes out on My WAN inteface would not matter at all, even if the VPN traffic will go out of that interface right? Hope I don't sound confusing.
As per your second question, I know it sounds weird and is not good network design, but customer just renewed maintenance contract for the other firewall box that is why he does not want to get rid of it yet. Although ISA can perform the function as well. Thanks.

Windows Multi Site/Geo Cluster

Hi,
I am looking for a Multi Site Cluster solution for File Server and SQL DB. Could you pls help with any case study of solution approach for building the Multi Site cluster using Windows 2012 ?
What is recommended for Replication
Which all Application/DB are compatible for Multi Site
Are there any implementation documents
pls suggest
Regards:Mahesh

Hi,
I am looking for a Multi Site Cluster solution for File Server and SQL DB. Could you pls help with any case study of solution approach for building the Multi Site cluster using Windows 2012 ?
What is recommended for Replication
Which all Application/DB are compatible for Multi Site
Are there any implementation documents
pls suggest
General suggestion: if possible use async replication rather then sync. Sync mirror puts high stress on WAN and lack of reliable channels can lead to cluster either non-operational (all WAN links down so cluster node w/o quorum kills itself) or brain split
issue (all WAN links down so separated cluster nodes continue working AS IS damaging data). For async replication you may look @ DFS-(R) as a file server, see:
Distributed File System
http://technet.microsoft.com/en-us/library/cc753479(v=ws.10).aspx
For SQL Server look at AlwaysOn in async way, see:
AlwaysOn for SQL Server
http://msdn.microsoft.com/en-us/library/ff877884.aspx
Availability Modes
The availability mode is a property of each availability replica. The availability mode determines whether the primary replica waits to commit transactions on a database until a given secondary replica has written the transaction log records to disk (hardened
the log). AlwaysOn Availability Groups supports two availability modes—asynchronous-commit mode and synchronous-commit mode.
Asynchronous-commit mode
An availability replica that uses this availability mode is known as an asynchronous-commit replica. Under asynchronous-commit mode, the primary replica commits transactions without waiting for acknowledgement that
an asynchronous-commit secondary replica has hardened the log. Asynchronous-commit mode minimizes transaction latency on the secondary databases but allows them to lag behind the primary databases, making some data loss possible.
Of course it's possible to configure SMB 3.0 failover file share on geo-separated sites and use Failover Cluster Instances for SQL Server in the same scenario. Just make sure you configure reliable witness (you'll have to do it for SQL Server AlwaysOn either
way...) on some third location. For file server I'd suggest to use some sort of a software replication in sync way instead of a geo-distributed physical shared storage. That one is for SQL Server and SteelEye Data Keeper but you can use any Windows-native
(preferred) software as well. See:
SQL Server Geo-Cluster with software shared storage
http://clusteringformeremortals.com/2009/10/07/step-by-step-configuring-a-2-node-multi-site-cluster-on-windows-server-2008-r2-–-part-3/
Good luck! :)
StarWind VSAN [Virtual SAN] clusters Hyper-V without SAS, Fibre Channel, SMB 3.0 or iSCSI, uses Ethernet to mirror internally mounted SATA disks between hosts.

Manually editing NetworkConfig.xml for multi-site VPN

Similar Messages

Maybe you are looking for