Virtualization Redemption?
-
@scottalanmiller said:
Did not realize that the restore machine would not need it, but makes sense. Jared cleared that up for me.
I would reconfirm that with Veeam if @hubtechagain goes that route. I ended up not using the 3 host scenario. But it does make sense and the sale rep was upfront on that device not needing the license.
-
we have any veeam representation here?
-
@hubtechagain said:
we have any veeam representation here?
We do but they have not been very active lately
-
Wait... what if we are over thinking this... What about Replication? HOST1 Replicates to HOST_DR every xx minutes?
That way only the changes replicate?
-
@dafyre said:
Wait... what if we are over thinking this... What about Replication? HOST1 Replicates to HOST_DR every xx minutes?
That way only the changes replicate?
OMG, dose of reality time!! You are so right. Talking ESXi blinded us to the most obvious answer!
-
-
Pretty sure that HyperV does what is needed, for free, completely included and we just overlooked it. Doh!
-
Note: HOST2 could also replicate to HOST_DR... 8-)
-
Alternatively if you have any extra hardware to run you can look into any of these.
Open Source Storage: 49 Tools for Backup and Recovery
Using for a much smaller amount, we use Create Synchronicity for our mobile users.
It works well enough.
For this Amanda might be what you need.
-
Here are the heavier details on HyperV Replication from Technet. Pretty sure you can choose Azure as the DR too, if you wanted.
-
Also... more thinking out loud... Doesn't XenServer have replication options like that as well?
-
@dafyre said:
Also... more thinking out loud... Doesn't XenServer have replication options like that as well?
That's what DRBD Proxy is. They've had it long before HyperV did, but it is less than trivial to set up.
-
@scottalanmiller said:
@dafyre said:
Also... more thinking out loud... Doesn't XenServer have replication options like that as well?
That's what DRBD Proxy is. They've had it long before HyperV did, but it is less than trivial to set up.
I was thinking more along the lines of like Hyper-V's replication... not the DRBD / HA setup.
-
Okay, so it's possible we have reached a free (other than my time) means of accomplishing this goal. yes?
I can do all of this on site so tell me if i'm off base or not.
-
setup new DR server with 2 new drives and reconfigure to raid 6
-
Setup Hyperv12 on DR server
-
P2V current VMs to DR host temporarily
-
HV 2012 on two "main site" servers
-
Migrate servers to their respective hosts
-
Setup Replication locally before shipping server to datacenter
-
Ship DR server to datacenter
-
Allow replication to do its thing?
-
-
@hubtechagain That sounds about right. You should note that the replication is not real time and happens on a set schedule (not sure what the lower limit is), so there could be a potential for data loss of XX minutes between the time HOST1 dies and its last replication to HOST_DR.
I would also dare suggest that Replication is not a replacement for backups. 8-)
-
from TechNet
Replication frequency—In Windows Server 2012 replication occurs every 5 minutes. In Windows Server 2012 R2, you can configure the replication frequency every 30 seconds, 5 minutes, or 15 minutes.That being said, this server will only ever be used if we have a complete physical failure at our main location. this is EXACTLY what i was looking for @dafyre you get atleast 100 nuggets.
-
@hubtechagain said:
-
setup new DR server with 2 new drives and reconfigure to raid 6 (if that means 5+ drives per machine, then yes that makes sense.)
-
Setup Hyperv12 on DR server (Yes!)
-
P2V current VMs to DR host temporarily (Yes!)
-
HV 2012 on two "main site" servers (Yes!)
-
Migrate servers to their respective hosts (Yes!)
-
Setup Replication locally before shipping server to datacenter (probably makes sense.)
-
Ship DR server to datacenter (Yes!)
-
Allow replication to do its thing? (Yes!)
-
-
Sounds like a good plan. Now the question becomes, how do you handle the two local servers? Are they going to be stand alones? or are they going to do full clustering like StarWind?
-
@dafyre said:
@hubtechagain That sounds about right. You should note that the replication is not real time and happens on a set schedule (not sure what the lower limit is), so there could be a potential for data loss of XX minutes between the time HOST1 dies and its last replication to HOST_DR.
I would also dare suggest that Replication is not a replacement for backups. 8-)
DR sites, currently, are always "non real time" or asynchronous. No reasonable technology lets you do anything differently today. HyperV Replication, Veeam, DRBD Proxy... all the same.
-
@scottalanmiller They will more than likely just be two individual hosts. why would I change that up now?
