Azure Migration
-
@DustinB3403 said in Azure Migration:
@BRRABill said in Azure Migration:
@scottalanmiller said in Azure Migration:
If that is correct, then you need a tool like StorageCraft or Veeam Endpoint Protection that will do an agent-based full system backup of the VM from inside of the VM itself. Then use that to restore to the new VM.
It funny how I used to not "like" this method when I was new to VMs.
Now, it's awesome!
It works, but isn't awesome IMO.
Like trying to zip your fly with your tongue after taking a piss. . . (not that I've tried this or anything, it's just always painful IMO)
I hate when I have to do that.
-
@scottalanmiller said in Azure Migration:
If that is correct, then you need a tool like StorageCraft or Veeam Endpoint Protection that will do an agent-based full system backup of the VM from inside of the VM itself. Then use that to restore to the new VM.
This was my plan. We have a Storagecraft subscription so this is what we'll plan on doing. Now if we can figure out how to do a headstart restore to Azure we could do it with almost no downtime.
We are anticipating this being difficult due to lack of cooperation from the old provider.
-
@NETS said in Azure Migration:
We are anticipating this being difficult due to lack of cooperation from the old provider.
So the old Azure provider is trying to hold you ransom?
-
@NETS said in Azure Migration:
@scottalanmiller said in Azure Migration:
If that is correct, then you need a tool like StorageCraft or Veeam Endpoint Protection that will do an agent-based full system backup of the VM from inside of the VM itself. Then use that to restore to the new VM.
This was my plan. We have a Storagecraft subscription so this is what we'll plan on doing. Now if we can figure out how to do a headstart restore to Azure we could do it with almost no downtime.
We are anticipating this being difficult due to lack of cooperation from the old provider.
Yes, sounds like it will be a pain. What kind of migration window do you have?
-
A weekend
-
Hopefully you are using Azure direct for the new VM? If using Azure, that works the best. Azure has account-related outages, you don't want to be tied to anyone else's account on Azure.
-
-
-
And a follow up to the VM size, is what is your internet bandwidth like?
-
@DustinB3403 said in Azure Migration:
And a follow up to the VM size, is what is your internet bandwidth like?
Azure to Azure the bandwidth has to be 10Gig easy.
-
@scottalanmiller said in Azure Migration:
@DustinB3403 said in Azure Migration:
And a follow up to the VM size, is what is your internet bandwidth like?
Azure to Azure the bandwidth has to be 10Gig easy.
Do you think they'll be able to go directly between the two? I was thinking he'd have to download the file, and then upload it into the new host.
Direct connection would be way better though.
-
I know the data store is 500GB in size but I don't think they are using that much.
-
@NETS said in Azure Migration:
I know the data store is 500GB in size but I don't think they are using that much.
Assuming that was all you had to transfer (500GB) and you had to download it at 30MBps you'd be waiting about a ~2 days to download.
-
My thought is to do it from another Azure VM
-
@DustinB3403 said in Azure Migration:
@scottalanmiller said in Azure Migration:
@DustinB3403 said in Azure Migration:
And a follow up to the VM size, is what is your internet bandwidth like?
Azure to Azure the bandwidth has to be 10Gig easy.
Do you think they'll be able to go directly between the two? I was thinking he'd have to download the file, and then upload it into the new host.
Direct connection would be way better though.
Directly, yes. Or to an Azure storage point. Don't leave Azure in this whole process.
-
Yes, I see no reason to leave Azure.
If we can find out what DC it's in we will fire up the new VM in that DC as well.
-
@NETS said in Azure Migration:
Yes, I see no reason to leave Azure.
Money, stability. Those seem like big reasons. What business doesn't want to save money, especially if they get a better product by doing so? Minor reason: ease of use.
What's the reason to stay?
-
@NETS said in Azure Migration:
If we can find out what DC it's in we will fire up the new VM in that DC as well.
Even between DCs the speed is high.
-
@NETS said in Azure Migration:
Yes, I see no reason to leave Azure.
NEver been through any of the Azure outages? Azure customers don't tend to be a happy group when they talk to each other. Only cloud provider that we ever felt the need to drop due to reliability concerns. That their cost is insane doesn't help, but was a minor factor. The constant outages and account problems make them non-viable to us as a production system. And their cost makes them non-viable for anything else.
-
For migration purposes I see no reason to leave Azure in order to keep the speeds up and the migration window short. After this is done we can work on moving them to a cheaper more stable option.
