Azure Migration
-
@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.
-
@NETS said in Azure Migration:
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.
Only reason would be that the migration only needs to be done once. There is certainly value in simply getting off of the bad vendor's situation as quickly as possible.
Is there any window in which you can do a test migration?
-
I believe so.
-
@NETS said in Azure Migration:
I believe so.
If so, test both. What I would propose (if possible only) is take a backup now and see how a restore goes to Azure. See if you can get it working. Then blow that VM away. Record the steps and time it took. Make sure you have a documented process so that you are ready for the weekend.
If that was reasonably done, take the same backup and do a test restore to Vultr or Rackspace (I'd do Vultr). See if that works, record the time and steps, etc.
Then you have both a backup plan as well as a documented procedure for the weekend and you have the choice of whether to do a two step migration or a one step one.
-
How do you use storageCraft or Veeam to backup from Azure to Azure? Would you have to stand up another VM in Azure first, then use that to backup the old VM to the backup server, then boot the new VM from the SC or Veeam media and restore?
-
@Dashrender you'd download the recovery iso that they provide and point it to the backup you have.
This would pull in all of the files etc from the backup and restore it.
