<div>
So Internet connections are 10MbitPS /10MbitPS and 50MbitPS/1MbitPS?<br />
<br />
So with 10 bits per byte over a comms link that is approx 1MBPS/1MBPS and 5MBPS/100KBPS<br />
<br />
The 100KBytes/sec is going to be a bit of bottleneck!<br />
<br />
How do you plan to sync the two sites, 100GB+ over a 1MB/s link is going to take a very long time. Once it is synched, 1GB per day shouldnt stretch the link too much, but is there going to be other traffic on this link as well?<br />
<br />
So failover shouldnt be too much of a truma, but what about fail-back? have you worked out how long that is going to take?
</div>


<div>
Hi Gerald<br />
<br />
Thanks for coming. Yes, those figures are correct. The 100KBPS is going to be a serious pain, but as I say my opinion isnt really being asked for. I am being engaged to deploy a specific setup as per somebody elses design. IMO, if the site does fail over for any extended period of time we might even just go in and restore a backup of the DR server onto the main server once its repaired.<br />
<br />
Oh yeh, and did i mention they only have 15 users?<br />
<br />
Anyways, whats the best method to do DR replication over a wan link? I am under the impression that all built in MS technologies pretty much wont work without unnecessary and costly SAN/iSCSI ETC
</div>


<div>
There are a couple of ways I would do this based on my real world experience as an IT consultant. &nbsp;We used to use a SAN setup that also incorporated a server (vm or physical is fine) that ran a software called AppAssure Replay. &nbsp;Dell recently (in the last year to year and a half) purchased AppAssure and is making them more robust as we speak. &nbsp;They do, however, provide a really good backup solution already, with a feature built in ( you have to turn it on and configure it which isn't hard) called Live Recovery which basically exports a live working VM of your server(s) to a designated storage spot (preferably a local or offsite SAN) every 5 minutes. &nbsp;Now, keep in mind that the software is already backing up, deduplicating, and can replicate all backups to another Core (that's what AppAssure calls the actual backup servers with the console installed on them) all on top of this Live Recovery option. &nbsp;You don't need a SAN as long as you have enough room to wherever you are replicating the Live Recovery and the backups. &nbsp;They also have a feature called Seeding that allows you to take the initial backup offsite with an external hard drive and that way all 100GBs don't have to go across the Internet, just the changes do.<br />
<br />
Let me know if you're interested and I'll set you up with a more detailed plan of what we used to do.<br />
<br />
<a href="http://www.appassure.com/" rel="ugc">http://www.appassure.com/</a>
</div>


<div>
<blockquote>
Firstly, forgive the ridiculousness of this question.
</blockquote>
No problem, those questions are way more fun ;-)<br />
<br />
I agree this is a slightly odd request, but what the hell. if this is what they want there's no harm in considering it.<br />
<br />
OK, so both Hyper- &amp;&nbsp;VMware have replication facilities built in and can replicate VMs very well if setup accordingly. it's well worth considering but there are a few issues with this option:<br />
Can be expensive to setup<br />
Can slow VMs down if the storage isn't fast enough (uses delta files for VMs which can reduce performance a little)<br />
Is rubbish if you cannot exclude the VM disk that contains the pagefile<br />
<br />
Alternatively, you could use a backup facility that can be restored directly to a VM (eg backup exec &amp;&nbsp;many others) which is easier to setup, but this tends to be a little harsh on the bandwidth (which may be an issue for you)<br />
<br />
You could consider replicating the applications instead of the VMs (eg exchange DAG, SQL log shipping, DFS file replication etc etc) but this can be costly for purchasing licenses etc, and may not be possible with some applications.<br />
<br />
Let me know if any of these are worth discussing in more details and I'm happy to expand on it a bit if you'd like.
</div>


<div>
Sorry for the absence guys.<br />
<br />
Appreciate the input. Do any of these proposals incorporate an automatic failover?<br />
<br />
Just to clarify, we will have two completely seperate sites with 1 server on each site. The servers only have internal direct attached storage. There is no budget for properly redundant SAN, and we want to avoid the ipod &quot;Inverted Pyramid of Doom&quot;.<br />
<br />
All we need is for a backup of a live server to be replicated over a WAN link, and upon failure of the onsite server the DR server has a recent operating copy of the failed system.<br />
<br />
It doesnt necessarily have to be &quot;live&quot; DR. But clost as possible with a solution that is bandwidth friendly
</div>


<div>
Thanks guys.<br />
<br />
Yes, as suspected, there is no good or easy way to do this. &nbsp;The best answer is no when the closest answer to yes is maybe. The cost of maintaining two WAN links with the appropriate amount of bandwidth to accomodate the requested system is simply unjustifiable. A few hours downtime while a Backup is restored is the best option.<br />
<br />
Instead, we are looking into an online backup solution that enables your backup to be immediately loaded as a virtual machine so you have access to the resource even whilst the restoration takes place.<br />
<br />
Cheers, Paul
</div>


<div>
Paul,<br />
<br />
StorageCraft Cloud Premium will do what you ask. It snapshots your VMs, creates continuing differentials and allows you to upload all of your backup images to StorageCraft's cloud service. Then, if disaster strikes, you can boot your uploaded images (it consolidates your differentials with your last full snapshot, then boots off of the consolidated image) in the cloud, on their servers.<br />
<br />
Now all your servers are running as VMs in their cloud, based off of your backups. Does that make sense?<br />
<br />
There are several ways of doing instant failover, but a very cheap one that immediately springs to mind is dynDNS. I.e., have one of your servers update a dynDNS service every minute, so that your hostname(s) point to that IP.<br />
<br />
Then have an external service (or rent a virtual host somewhere) ping your DNS hostnames every minute. If it stops responding, send an email to yourself (not to your corporate email account, of course). Or send an email to an email-to-SMS service, so you get a text message on your phone.<br />
<br />
After 5 minutes of no response from ping, and no intervention by you, have it kick StorageCraft's DR service into action, so it boots your backup images. All of this can be relatively easily scripted on either Windows or Linux.<br />
<br />
Finally, have the script disable dynDNS updates from your original IP once the DR site is online and has registered its IP. You don't want your DNS flip-flopping back and forth every 30 seconds.<br />
<br />
How's that for a (relatively) cheap DR solution with failover?<br />
<br />
Regards, G<br />
(No connection to StorageCraft, but I do work for a company which has clients who use it, and are happy with it)
</div>


<div>
<div class="content wysiwyg-content">
Firstly, forgive the ridiculousness of this question.<br />
<br />
Scenario is this<br />
<br />
A server at 1 location. Operating a virtual Host OS (VMware / Hyper-V) with 2 or 3 guests <br />
<br />
1. Windows Server (2012?) with Standard Roles such as DC, File server, Exchange Email, SQL Server roles)<br />
2. Windows Terminal Server (2012?)<br />
3. Possible Legacy virtual system operating Server 2003 with legacy database application<br />
<br />
He wants the above to replicate over the internet to an identical setup at another site for DR purposes. Internet connection at primary site is 10/10 and secondary site is 50/1 The amount of file store data involved in total excluding OS files is around 100GB. Daily changes will be below 1GB.<br />
<br />
Im looking for advice on whats the best way to achieve this. Preferably using internal storage. I am fairly certain the answer is 3rd party software which enhances the capabilities of cluster failover, or negates it altogether. Automatic and instantaneous failover would be preferable, but small downtime (5-30m) should be OK but again, without intervention. Even better if that software also handles backups, and if not, an idea of how such a setup would interact with inbuilt Windows Server Backup.<br />
<br />
For the record, no hardware or software has been purchased yet, so theres a blank slate from that perspective. You have carte blanche in terms of suggesting the appropriate setup balancing reliability and functionality against cost.<br />
<br />
Thanks for your input people, <br />
<br />
Kind Regards.
</div>
</div>


Firstly, forgive the ridiculousness of this question.

Scenario is this

A server at 1 location. Operating a virtual Host OS (VMware / Hyper-V) with 2 or 3 guests 

1. Windows Server (2012?) with Standard Roles such as DC, File server, Exchange Email, SQL Server roles)
2. Windows Terminal Server (2012?)
3. Possible Legacy virtual system operating Server 2003 with legacy database application

He wants the above to replicate over the internet to an identical setup at another site for DR purposes. Internet connection at primary site is 10/10 and secondary site is 50/1 The amount of file store data involved in total excluding OS files is around 100GB. Daily changes will be below 1GB.

Im looking for advice on whats the best way to achieve this. Preferably using internal storage. I am fairly certain the answer is 3rd party software which enhances the capabilities of cluster failover, or negates it altogether. Automatic and instantaneous failover would be preferable, but small downtime (5-30m) should be OK but again, without intervention. Even better if that software also handles backups, and if not, an idea of how such a setup would interact with inbuilt Windows Server Backup.

For the record, no hardware or software has been purchased yet, so theres a blank slate from that perspective. You have carte blanche in terms of suggesting the appropriate setup balancing reliability and functionality against cost.

Thanks for your input people, 

Kind Regards.

Windows Server DR using replication / Failover accross WAN

Disaster Recovery is the planning for and creation of policies and procedures related to the resumption or continuation of an organization's functions following a catastrophic event. The term is most frequently used in relation to failure of networks, but DR preparations also include other business systems and personnel considerations.

Disaster Recovery

Windows Server 2012 is the server version of Windows 8 and the successor to Windows Server 2008 R2. Windows Server 2012 is the first version of Windows Server to have no support for Itanium-based computers since Windows NT 4.0. Windows Server 2012, now in its second release (Windows Server 2012 Release 2) includes Foundation, Essentials, Standard and Datacenter, and does not support IA-32 or IA-64 processors.

Windows Server 2012

VMware, a software company founded in 1998,  was one of the first commercially successful companies to offer x86 virtualization. The storage company EMC purchased VMware in 1994. Dell Technologies acquired EMC in 2016. VMware’s parent company is now Dell Technologies.

VMware has many software products that run on desktops, Microsoft Windows, Linux, and macOS, which allows the virtualizing of the x86 architecture.  Its enterprise software hypervisor for servers, VMware vSphere Hypervisor (ESXi), is a bare-metal hypervisor that runs directly on the server hardware and does not require an additional underlying operating system.