HyperV Nested Virtualization Announced for Container Support
-
Here is the pricing for site recovery. https://azure.microsoft.com/en-us/pricing/details/site-recovery/.
Is an instance an individual virtual machine? If that is the case the pricing isn't really that bad. Looks like you will also incur charges for storage transactions and usage.
-
You pay for all usage, but only for usage not potential.
-
@dafyre said:
@DustinB3403 I would think more portable as in live migration... You don't have any generators at your main site and the power company needs to take you down for 24 hours. You could then Migrate your Nested Hyper-V infrastructure to Azure for a day and not have to scramble to find generators and such, and you don't even have to scramble to bring things back up because they never go down.
That would be the way I see it. As I said, I may be completely out of my mind, but that is what I envision with containers.
We'll ignore the completely badly configured Hyper-V setup that you have now.
How small are your VMs that you could push them to Azure in less than 24 hours?
-
@Dashrender This goes back to what he ws saying about keeping things in Sync.
-
@scottalanmiller said:
@DustinB3403 said:
So one has to ask, if you have a site wide unplanned outage but do have access to Azure, how do you get your Hyper-V data to them so you can at least get to a functional state?
Generally you would keep it synced there all of the time.
and how much does that cost? Yes I know this is a generic question that has no direct answer without knowing the amount of change, what your storage usage is, etc - but is it considered online and in usage when you don't have the VM's powered up?
-
@dafyre said:
@Dashrender This goes back to what he ws saying about keeping things in Sync.
Yeah I was writing questions while reading the thread.
-
@Dashrender said:
@scottalanmiller said:
@DustinB3403 said:
So one has to ask, if you have a site wide unplanned outage but do have access to Azure, how do you get your Hyper-V data to them so you can at least get to a functional state?
Generally you would keep it synced there all of the time.
and how much does that cost? Yes I know this is a generic question that has no direct answer without knowing the amount of change, what your storage usage is, etc - but is it considered online and in usage when you don't have the VM's powered up?
From looking at the backup and site recovery pricing the answer is no. You just pay for the data transfer and the storage. When you spin it up you start paying for the compute cycles.
-
@Dashrender said:
@scottalanmiller said:
@DustinB3403 said:
So one has to ask, if you have a site wide unplanned outage but do have access to Azure, how do you get your Hyper-V data to them so you can at least get to a functional state?
Generally you would keep it synced there all of the time.
and how much does that cost? Yes I know this is a generic question that has no direct answer without knowing the amount of change, what your storage usage is, etc - but is it considered online and in usage when you don't have the VM's powered up?
Depends how you do it. Do you just have it stored cold dr? Do you have it built as VMs but off warm dr? Do you have the VMs up and running hot dr? All makes a difference.
-
@scottalanmiller said:
@Dashrender said:
@scottalanmiller said:
@DustinB3403 said:
So one has to ask, if you have a site wide unplanned outage but do have access to Azure, how do you get your Hyper-V data to them so you can at least get to a functional state?
Generally you would keep it synced there all of the time.
and how much does that cost? Yes I know this is a generic question that has no direct answer without knowing the amount of change, what your storage usage is, etc - but is it considered online and in usage when you don't have the VM's powered up?
Depends how you do it. Do you just have it stored cold dr? Do you have it built as VMs but off warm dr? Do you have the VMs up and running hot dr? All makes a difference.
I would guess for most SMBs it would be the first or the second, probably the built VMs but off.
I looked at the VM storage cost - for my 2 TB that would be around $100/mth. Plus any transfer fee. Then it would be a matter of making the networking work. -
@Dashrender said:
I would guess for most SMBs it would be the first or the second, probably the built VMs but off.
Not for @ntg but, you know, we are a bit hard core.
-
@Dashrender said:
I looked at the VM storage cost - for my 2 TB that would be around $100/mth. Plus any transfer fee. Then it would be a matter of making the networking work.
Always a challenge. This is where Pertino really rocks.
-
@scottalanmiller said:
@Dashrender said:
I would guess for most SMBs it would be the first or the second, probably the built VMs but off.
Not for @ntg but, you know, we are a bit hard core.
You have hot running VMs for DR? lol you value your uptime. How do you handle the networking side of things?
-
@Dashrender said:
@scottalanmiller said:
@Dashrender said:
I would guess for most SMBs it would be the first or the second, probably the built VMs but off.
Not for @ntg but, you know, we are a bit hard core.
You have hot running VMs for DR? lol you value your uptime. How do you handle the networking side of things?
Yes. Our DR site is Azure Virginia (aka Azure East 2). Our secondary DC is there and always on.
-
-
From reading some other threads, it sounds like ZeroTier would be a perfect fit there as well, now, right?
-
I've already told Scott I would love to see one of the first major projects on the new NTG lab be to setup a ZT network.
But @Reid-Cooper post makes me think it would be cool to mirror NTG's network in the Lab and see how it works without the DNS craziness that Pertino has.
-
@Dashrender said:
I've already told Scott I would love to see one of the first major projects on the new NTG lab be to setup a ZT network.
I like this idea. We could use the ZT Network for the NTG lab as a management network or something.
