Looking for some insight/input for setting up a "hot site"/fail-over environment
-
@scottalanmiller said in Looking for some insight/input for setting up a "hot site"/fail-over environment:
@dave247 said in Looking for some insight/input for setting up a "hot site"/fail-over environment:
@wrx7m said in Looking for some insight/input for setting up a "hot site"/fail-over environment:
What type of Windows licensing do you have? Replication can be affected by that.
We have Microsoft Volume Licensing and I haven't looked into weather or not we'd have to purchase "double" or not.. I'm not sure but I thought a backup environment doesn't quite count as production.
You need the second site licensed if it is hot, meaning turned on. You do not need anything if it is cold, meaning powered off. Powered off, it's just a backup that's extremely "ready to go".
ok that's good to know. I don't doubt you, but do you know where this info is explicitly stated by MS? I'd like to have it on hand. I may just have to dig through the licensing ToS or something.
-
@dave247 said in Looking for some insight/input for setting up a "hot site"/fail-over environment:
@wrx7m said in Looking for some insight/input for setting up a "hot site"/fail-over environment:
@dave247 said in Looking for some insight/input for setting up a "hot site"/fail-over environment:
@wrx7m said in Looking for some insight/input for setting up a "hot site"/fail-over environment:
What type of Windows licensing do you have? Replication can be affected by that.
We have Microsoft Volume Licensing and I haven't looked into weather or not we'd have to purchase "double" or not.. I'm not sure but I thought a backup environment doesn't quite count as production.
I would say "Hot"=Active.
hot/warm/standby environment is more what I'm talking about. I do plan to look into the licensing requirements involved. We have Datacenter for the vmware environment.
I think only cold gets away with no licensing.
-
How are you planning on handling the IP change - I'm assuming each building is in a different IP range, so routing will become an issue - just another piece of the puzzle.
-
@Dashrender said in Looking for some insight/input for setting up a "hot site"/fail-over environment:
How are you planning on handling the IP change - I'm assuming each building is in a different IP range, so routing will become an issue - just another piece of the puzzle.
Stop building environments with static IPs period. That is an old way of thinking
-
@dave247 said in Looking for some insight/input for setting up a "hot site"/fail-over environment:
@IRJ said in Looking for some insight/input for setting up a "hot site"/fail-over environment:
@dave247 said in Looking for some insight/input for setting up a "hot site"/fail-over environment:
We have a few locations that are all relatively close by
That is probably the craziest thing about going through all this hassle and being in the same geographic region. I would seriously consider a colo outside of the area. I mean you do all that work and put in all these expenses and you have an area wide disaster and its potentially gone.
Colocation costs are not much more than hosting at your own facility.yeah that would be preferred but we likely won't be able to get our company owners to spend that much money. Setting up a minimal warm site in our other building would be much cheaper/easier.
I went through what you're going through about 10 years ago. Almost identical.
What we found is that everything we put in place and all the procedures we had to follow to meet our BCDR was so much work that we decided it was extremely stupid to spend hundreds of thousands of dollars in licensing, manpower, and procedure to get our stuff operational to meet our BCDR and then fail because of a location.
My boss asked for a remote site instead of using another local facility and it was a no brainer to everyone involved include C level non IT people. They understood costs and effort level to get there.
-
@IRJ said in Looking for some insight/input for setting up a "hot site"/fail-over environment:
@Dashrender said in Looking for some insight/input for setting up a "hot site"/fail-over environment:
How are you planning on handling the IP change - I'm assuming each building is in a different IP range, so routing will become an issue - just another piece of the puzzle.
Stop building environments with static IPs period. That is an old way of thinking
yeah, OK - with IPv6, that's not really a thing anyway, right?
(not that IPv6 has anything to do with anything regarding this project - it's just the future way of IPing and brings along lack of static IPs)
-
@Dashrender said in Looking for some insight/input for setting up a "hot site"/fail-over environment:
@IRJ said in Looking for some insight/input for setting up a "hot site"/fail-over environment:
@Dashrender said in Looking for some insight/input for setting up a "hot site"/fail-over environment:
How are you planning on handling the IP change - I'm assuming each building is in a different IP range, so routing will become an issue - just another piece of the puzzle.
Stop building environments with static IPs period. That is an old way of thinking
yeah, OK - with IPv6, that's not really a thing anyway, right?
(not that IPv6 has anything to do with anything regarding this project - it's just the future way of IPing and brings along lack of static IPs)
I'm not even thinking about IPv6 but yeah having a DNS service that can do health checks is ideal and route to another host when when you spin it up.
This can all be automated using terraform in the cloud and even to alot of extent on prem. For example you could spin up hosts on prem and pull all the ip addresses from your terraform state file for easy import into your DNS server.
On AWS, as soon as terraform creates the instance you build your DNS entry. The old one fails health check and it points to new server. Boom you are done
-
@IRJ said in Looking for some insight/input for setting up a "hot site"/fail-over environment:
@Dashrender said in Looking for some insight/input for setting up a "hot site"/fail-over environment:
How are you planning on handling the IP change - I'm assuming each building is in a different IP range, so routing will become an issue - just another piece of the puzzle.
Stop building environments with static IPs period. That is an old way of thinking
Nobody said anything about static IPs at all. I assume he just meant in terms of having a secondary environment (especially a hot one) there would be an additional network involved to support the DR site - but the servers and appliances being replicated/sitting on stand-by would be on the same subnet/have the same IP addresses as the primary environment - which could lead to conflicts/be an obstacle.
-
@scottalanmiller said in Looking for some insight/input for setting up a "hot site"/fail-over environment:
@dave247 said in Looking for some insight/input for setting up a "hot site"/fail-over environment:
@wrx7m said in Looking for some insight/input for setting up a "hot site"/fail-over environment:
What type of Windows licensing do you have? Replication can be affected by that.
We have Microsoft Volume Licensing and I haven't looked into weather or not we'd have to purchase "double" or not.. I'm not sure but I thought a backup environment doesn't quite count as production.
You need the second site licensed if it is hot, meaning turned on. You do not need anything if it is cold, meaning powered off. Powered off, it's just a backup that's extremely "ready to go".
I found the info I needed in the Windows Server 2016 Licensing Guide and if I understand it correctly, we would need Software Assurance coverage with our licensing, which we do not have. We purchased licenses only (with necessary CALs).
-
@Dashrender said in Looking for some insight/input for setting up a "hot site"/fail-over environment:
@dave247 said in Looking for some insight/input for setting up a "hot site"/fail-over environment:
@wrx7m said in Looking for some insight/input for setting up a "hot site"/fail-over environment:
@dave247 said in Looking for some insight/input for setting up a "hot site"/fail-over environment:
@wrx7m said in Looking for some insight/input for setting up a "hot site"/fail-over environment:
What type of Windows licensing do you have? Replication can be affected by that.
We have Microsoft Volume Licensing and I haven't looked into weather or not we'd have to purchase "double" or not.. I'm not sure but I thought a backup environment doesn't quite count as production.
I would say "Hot"=Active.
hot/warm/standby environment is more what I'm talking about. I do plan to look into the licensing requirements involved. We have Datacenter for the vmware environment.
I think only cold gets away with no licensing.
That's correct.
-
@IRJ said in Looking for some insight/input for setting up a "hot site"/fail-over environment:
@Dashrender said in Looking for some insight/input for setting up a "hot site"/fail-over environment:
@IRJ said in Looking for some insight/input for setting up a "hot site"/fail-over environment:
@Dashrender said in Looking for some insight/input for setting up a "hot site"/fail-over environment:
How are you planning on handling the IP change - I'm assuming each building is in a different IP range, so routing will become an issue - just another piece of the puzzle.
Stop building environments with static IPs period. That is an old way of thinking
yeah, OK - with IPv6, that's not really a thing anyway, right?
(not that IPv6 has anything to do with anything regarding this project - it's just the future way of IPing and brings along lack of static IPs)
I'm not even thinking about IPv6 but yeah having a DNS service that can do health checks is ideal and route to another host when when you spin it up.
This can all be automated using terraform in the cloud and even to alot of extent on prem. For example you could spin up hosts on prem and pull all the ip addresses from your terraform state file for easy import into your DNS server.
On AWS, as soon as terraform creates the instance you build your DNS entry. The old one fails health check and it points to new server. Boom you are done
Right. Using things like Consul for service discovery makes it easy.
Also even just doing automated configs for your load balancers works as well.
-
@dave247 said in Looking for some insight/input for setting up a "hot site"/fail-over environment:
I found the info I needed in the Windows Server 2016 Licensing Guide and if I understand it correctly, we would need Software Assurance coverage with our licensing, which we do not have. We purchased licenses only (with necessary CALs).
SA is the standard way to do it. You can do it without SA by double purchasing all the licenses (but not the CALs, no need to double up there. The humans aren't being duplicated.) Obviously, SA is cheaper than that, and that's why everyone goes with SA.
-
Of course, somewhere, someone actually doubles up the humans. Those crazy people need more CALs
-
@scottalanmiller said in Looking for some insight/input for setting up a "hot site"/fail-over environment:
@dave247 said in Looking for some insight/input for setting up a "hot site"/fail-over environment:
I found the info I needed in the Windows Server 2016 Licensing Guide and if I understand it correctly, we would need Software Assurance coverage with our licensing, which we do not have. We purchased licenses only (with necessary CALs).
SA is the standard way to do it. You can do it without SA by double purchasing all the licenses (but not the CALs, no need to double up there. The humans aren't being duplicated.) Obviously, SA is cheaper than that, and that's why everyone goes with SA.
So, in the case with replicating virtual machines through Veeam Backup & Replication and storing those powered off servers on a spare VMware ESXi server would require me to purchase additional MS licensing?
-
@dave247 said in Looking for some insight/input for setting up a "hot site"/fail-over environment:
@scottalanmiller said in Looking for some insight/input for setting up a "hot site"/fail-over environment:
@dave247 said in Looking for some insight/input for setting up a "hot site"/fail-over environment:
I found the info I needed in the Windows Server 2016 Licensing Guide and if I understand it correctly, we would need Software Assurance coverage with our licensing, which we do not have. We purchased licenses only (with necessary CALs).
SA is the standard way to do it. You can do it without SA by double purchasing all the licenses (but not the CALs, no need to double up there. The humans aren't being duplicated.) Obviously, SA is cheaper than that, and that's why everyone goes with SA.
So, in the case with replicating virtual machines through Veeam Backup & Replication and storing those powered off servers on a spare VMware ESXi server would require me to purchase additional MS licensing?
Yes and you will have both running simultaneously to do fail over testing
-
@IRJ said in Looking for some insight/input for setting up a "hot site"/fail-over environment:
@dave247 said in Looking for some insight/input for setting up a "hot site"/fail-over environment:
@scottalanmiller said in Looking for some insight/input for setting up a "hot site"/fail-over environment:
@dave247 said in Looking for some insight/input for setting up a "hot site"/fail-over environment:
I found the info I needed in the Windows Server 2016 Licensing Guide and if I understand it correctly, we would need Software Assurance coverage with our licensing, which we do not have. We purchased licenses only (with necessary CALs).
SA is the standard way to do it. You can do it without SA by double purchasing all the licenses (but not the CALs, no need to double up there. The humans aren't being duplicated.) Obviously, SA is cheaper than that, and that's why everyone goes with SA.
So, in the case with replicating virtual machines through Veeam Backup & Replication and storing those powered off servers on a spare VMware ESXi server would require me to purchase additional MS licensing?
Yes and you will have both running simultaneously to do fail over testing
Anyone know off-hand if I can purchase Software Assurance after already having purchased my licenses? If not, guess we'll bite the bullet and purchase licensing for the warm site + get SA on all future purchases.
-
How many VMs are you restoring?
It may be worth looking into restoring into Azure VM replication?
-
@dave247 said in Looking for some insight/input for setting up a "hot site"/fail-over environment:
@IRJ said in Looking for some insight/input for setting up a "hot site"/fail-over environment:
@dave247 said in Looking for some insight/input for setting up a "hot site"/fail-over environment:
@scottalanmiller said in Looking for some insight/input for setting up a "hot site"/fail-over environment:
@dave247 said in Looking for some insight/input for setting up a "hot site"/fail-over environment:
I found the info I needed in the Windows Server 2016 Licensing Guide and if I understand it correctly, we would need Software Assurance coverage with our licensing, which we do not have. We purchased licenses only (with necessary CALs).
SA is the standard way to do it. You can do it without SA by double purchasing all the licenses (but not the CALs, no need to double up there. The humans aren't being duplicated.) Obviously, SA is cheaper than that, and that's why everyone goes with SA.
So, in the case with replicating virtual machines through Veeam Backup & Replication and storing those powered off servers on a spare VMware ESXi server would require me to purchase additional MS licensing?
Yes and you will have both running simultaneously to do fail over testing
Anyone know off-hand if I can purchase Software Assurance after already having purchased my licenses? If not, guess we'll bite the bullet and purchase licensing for the warm site + get SA on all future purchases.
I don't believe so.
-
@dave247 said in Looking for some insight/input for setting up a "hot site"/fail-over environment:
@IRJ said in Looking for some insight/input for setting up a "hot site"/fail-over environment:
@dave247 said in Looking for some insight/input for setting up a "hot site"/fail-over environment:
@scottalanmiller said in Looking for some insight/input for setting up a "hot site"/fail-over environment:
@dave247 said in Looking for some insight/input for setting up a "hot site"/fail-over environment:
I found the info I needed in the Windows Server 2016 Licensing Guide and if I understand it correctly, we would need Software Assurance coverage with our licensing, which we do not have. We purchased licenses only (with necessary CALs).
SA is the standard way to do it. You can do it without SA by double purchasing all the licenses (but not the CALs, no need to double up there. The humans aren't being duplicated.) Obviously, SA is cheaper than that, and that's why everyone goes with SA.
So, in the case with replicating virtual machines through Veeam Backup & Replication and storing those powered off servers on a spare VMware ESXi server would require me to purchase additional MS licensing?
Yes and you will have both running simultaneously to do fail over testing
Anyone know off-hand if I can purchase Software Assurance after already having purchased my licenses? If not, guess we'll bite the bullet and purchase licensing for the warm site + get SA on all future purchases.
Yes, you often can, but it is more costly.
-
@coliver said in Looking for some insight/input for setting up a "hot site"/fail-over environment:
@dave247 said in Looking for some insight/input for setting up a "hot site"/fail-over environment:
@IRJ said in Looking for some insight/input for setting up a "hot site"/fail-over environment:
@dave247 said in Looking for some insight/input for setting up a "hot site"/fail-over environment:
@scottalanmiller said in Looking for some insight/input for setting up a "hot site"/fail-over environment:
@dave247 said in Looking for some insight/input for setting up a "hot site"/fail-over environment:
I found the info I needed in the Windows Server 2016 Licensing Guide and if I understand it correctly, we would need Software Assurance coverage with our licensing, which we do not have. We purchased licenses only (with necessary CALs).
SA is the standard way to do it. You can do it without SA by double purchasing all the licenses (but not the CALs, no need to double up there. The humans aren't being duplicated.) Obviously, SA is cheaper than that, and that's why everyone goes with SA.
So, in the case with replicating virtual machines through Veeam Backup & Replication and storing those powered off servers on a spare VMware ESXi server would require me to purchase additional MS licensing?
Yes and you will have both running simultaneously to do fail over testing
Anyone know off-hand if I can purchase Software Assurance after already having purchased my licenses? If not, guess we'll bite the bullet and purchase licensing for the warm site + get SA on all future purchases.
I don't believe so.
You actually can - but only for 90 days after purchase.
