I have an application in centos VM running in amazon EC2 and now I need to migrate it to windows azure.
Is there a way to copy a snapshot to azure??
I wish to answer it step by step, but I found a link that is more than good & have almost details required to migrate an existing instance from Amazon EC2 to Windows Azure with video. The link is Guided Hands-on Lab: Migrate VMs to Windows Azure from Amazon AWS [ 20 Key Cloud Scenarios with Windows Azure Infrastructure Services ]
I hope it will help.
Well this is only possible if you are running Windows Server on your EC2 instance by following this link:
https://convective.wordpress.com/2014/07/04/migrating-a-vm-from-ec2-to-azure-at-300-mbps/
If you're running linux, currently there's no simple tool that does it, but you can go to your Azure account and follow these steps:
1- Mimic your architecture of servers on your Azure account by keeping eyes on number of VMs, Network, Storages, and other services if found.
2- Make the correct setup on those servers (configure your web server, db server, etc..)
3- Zip all of your data files found on EC2 (/var/www/Web_Folder) and use mysqldump to backup your database as well.
4- Create a windows server VM on Azure that you can connect to Remotely (Profit from the cloud internet speed) and use filezilla to download your zipped files from EC2 and then upload them back to newly created VMs on Azure. Upload your db backup file there as well.
5- Create a new database on your Azure VMs with the same old name, give user access, exit mysql and then restore your db backup file that you uploaded using: mysql -u root -p DB_Name
Just an update, Now you can accomplish this task using Azure Site Recovery this is a super easy task. In site recovery once you do failover all the virtual machines will automatically gets created which means with minimal or no downtime the migration can be performed https://azure.microsoft.com/en-in/documentation/articles/site-recovery-migrate-aws-to-azure/
Related
I want to create a baseline copy of Azure VM, Install all SQL and some 3rd party software I needed to it and create a copy / backup of it locally.
This copy / backup can be re-deployed again to a new VM for a new client.
currently I'm spending 1 to 2 days setting up this VM, installing and configuring this server.
How do I do it ?
Use any configuration management tools Ansible, Puppet, Chef...
Docker is the simplest thing I can think of. Upload your own image to a registry and then spawn as many VMs using it as you want.
See this for some pointers: Deploy image from Azure Container Registry to an Azure Linux Virtual Machine
Ansible and other CM tools will give you more functionality for more effort.
I'm planning to migrate our on-prem Azure Devops Server to Amazon AWS and would like to use SQL Server via AWS RDS as it's underlying database. I know that SQL Server running in AWS RDS has some limitations compared to a "normal" SQL Server running on a Windows Server VM. So I would like to know whether that difference would affect my Azure Devops Server installation in AWS in any way.
So, does Azure DevOps Server support running on an AWS RDS MS SQL Server database?
I looked everywhere for an answer, but did not manage to find an exact one.
bacpac method
You can achieve this by using the native backup and restore method, we can either use .bak (native backups) or .bacpac (backup package).
We have Windows Server 2016 Azure Virtual Machines using managed disks.
I am trying to create an Azure Data Factory pipeline that will let me copy certain files from a folder on the hard drives of those VMs, to our Azure SQL Server. I was quite surprised to see no ADF connectors available for Azure VMs; then I checked Logic Apps - same issue, no available connectors for connecting to Azure VM's there either.
Then I did some Googling to find out how, in general, you can access an Azure VM file structure from outside (without using Remote Desktop) and was even more surprised to see that there isn't any info out there about this (not even that it can't be done).
Is it possible for me to access the file system of my Windows Server 2016 Azure VM without using Remote Desktop? The VM's are running Managed Disks if that makes any difference.
You can either ssh your_vm_ip and then use rsync command to download or upload files.
rsync -au --progress your_user_name#ip.ip.ip.ip:/remote_dir/remote_dir/ /local_dir/local_dir/
Otherwise you can install Dropbox in the VM and your local computer, transfering small files in the shared Dropbox folder is very fast..
Here are some instruction slides on the Azure storage system and their Storage Explorer App.
I am working in Microsoft Azure. I have created a table in a database in postgres in linux virtual machine(vm) using shell script. Now, I have to move this created table to blob storage.
I come to know that I have to install self hosted integration run time in linux, since my data is in the vm. So is there a way to install and set up integration run time there?
I have one more question.
Since my source is postgres I create a linked service with postgres.
What would be the server name, user name and password? Will it be the vm's user name and password or the user name and password of database in postgres?
Unless
The data store is located inside an on-premises network, inside Azure Virtual Network, or inside Amazon Virtual Private Cloud.
The data store is a managed cloud data service where the access is restricted to IPs whitelisted in the firewall rules.
Then Azure Data factory can connect to Postgre SQL without a need for integration runtime.
And no you can't install this on Linux.
Even if you would manage to do it somehow it wouldn't be recommended as it wasn't built with this in mind.
We have a requirement to Migrate EC2 instance of AWS to Azure as VM, have been trying to implement the same from this source,
unable to complete the process. Tried and stuck on Protection Group.
I'm looking in these other links
Migrating a VM from EC2 to Azure at 300 Mbps For this I'm able to create VM in Classis portal but unable connect to it only port 80 is active all other ports are not working
Migrate virtual machines in Amazon Web Services (AWS) to Azure with Azure Site Recovery
https://learn.microsoft.com/en-us/azure/site-recovery/site-recovery-vmware-to-azure
https://aws.amazon.com/ec2/vm-import/ on trying this I'm getting this unresolved EC2 API export to S3 ACL issue
Can anyone suggest me a workflow on how to implement this?
I achieved this by downloading AWS EC2 VHD to an Hyper-V enabled machine on-premises.
Following are the steps.
Create VM from VHD and Remove AWS related software.
Open Hyper-V manager and create VM from the downloaded VHD.
Log in to the VM and uninstalled AWS related services from control panel (AWS Drivers, EC2configService, AWS Tools for Windows, AWS SSM Agent)
All these changes were affected on the VHD.
Upload the converted VHD to Azure Storage (using the Azure PowerShell cmdlets)
Create av Azure VM-Image from that VHD in Classic Azure Portal
Create an Azure VM using the new Image.
Created a classic VM in Azure portal.
For creating a VM under Resource manager, created VHD of newly migrated VM and using that created a new VM in azure portal.
Mention any workflow other than this.
There are multiple ways to migrate machines.
Azure Migrate: Server Migration is one tool that lets you do that and is the recommended way to rehost x86 machines to Azure. You can treat the EC2 instance (AWS VM) as though it were a Physical machine and migrate it to Azure as long as the Operating System on the machine is supported by the Physical Server Migration flow (also check the kernel version to ensure it is supported) https://learn.microsoft.com/en-us/azure/migrate/tutorial-migrate-physical-virtual-machines
That being said, EC2 VMs may have some changes that you’ll need to make before migrating them, or it may cause issues once in Azure. For example if they are using cloudinit for VM provisioning, you may want to disable cloudinit on the VM before replicating it because the provisioning steps performed by cloudinit on the VM maybe AWS specific and wont be valid after the migration to Azure.
The other thing to note is if the VM is a PV VM (para-virtualized) and not a HVM VM you may not be able to run it as is because paravirtualized VMs use a custom boot sequence in AWS (you may be able to get over this challenge by installing GRUB 2 on the VM and building grub)
The recommendation, if you are using this approach, is to always perform a test migration first to test the process.