I am trying to migrate my applications from GoDaddy virtual machine to Azure Virtual machine.
I want to have 1 VM as a database server and another VM as webserver, but it works extremely slow in that case, I installed DB on the same server as web application and it's fast.
So the question: How can I increase performance between two virtual machines? Both are located in "East US", is it some way to may be locate both in the same box...?
What can you suggest?
Found the issue. It's not Azure, it's problem with MySQL database.
I have to set parameter
skip-name-resolve
in my.ini file, and not it's as fast as when both located on the same server.
Make sure you have the VM's in the same affinity group so the machines are geolocated together by the Fabric Controller i.e. in East US
Machines in the sames Cloud Service and affinity group should have lightening direct network traffic, can you run some ping tests between them on the same affinity group and share with us plz.
e.g. RDP in and run ping from the command line.
As stated above the beefer the machines the better the bandwidth/network traffic, scaling up the SQL machine is advisable.
*More on Affinity Groups here: http://convective.wordpress.com/2012/06/10/affinity-groups-in-windows-azure/
Cheers
Affinity Group is the way to go. Configure both VM in the same affinity group will co-locate those two VMs.
Related
i have several Linux Vms in MS Azure within the same security group and i can access all of them over SSH expect one. Here i need to restart the VM 5 to 10 times before i also can access it via SSH.
anyone has an idea whats wrong with this VM?
If the problem seems specific to this VM alone, you might want to check the VM's Resource Health first. Ensure that the VM reports as being healthy. If you have boot diagnostics enabled, verify the VM is not reporting boot errors in the logs.
If that looks clean, you might consider redeploying the VM. This redeploys a VM to another node within Azure, which may correct any underlying networking issues.
Do note that post this operation completes, ephemeral disk data is lost and dynamic IP addresses that are associated with the virtual machine are updated.
Additional troubleshooting guidance can be found here.
We are setting up ASR for in an environent. We are having multiple VMs in VMWare environment. VMware environment is managed by Third Party who does not want to give any service account for VMWare as their environment is shared with different customers. So we have access only to the VMs.
Can we treat these VMs as Physical servers and use ASR to replicate these machines to Azure? Is this something which is supported by Microsoft?
I am checking this step by step guide but it does not talk about my scenario: Replicate VMware virtual machines and physical machines to Azure with Azure Site Recovery using the Azure portal
Any pointers for this will be appreciated.
No, you cannot proceed like this. A list of permissions that you need are given here:
https://azure.microsoft.com/en-us/documentation/articles/site-recovery-vmware-to-azure/#vmware-account-permissions.
You will need to have access to the vCenter server or the ESX/ESXi host with all of those above roles and permissions.
Further, if you're adding the vCenter server or vSphere host with an account that doesn't have administrator privileges on the vCenter or host server, then make sure that the account has these privileges enabled: Datacenter, Datastore, Folder, Host, Network, Resource, Virtual machine, vSphere Distributed Switch. In addition the vCenter server needs the Storage views privilege.
We were able to migrate VMs without any VMWare level access. We used the option of "Not virtualized/other" in the "Prepare Infrastructure" wizard of ASR. We treated the VMs as physical servers and did not face any issues during the migration. I am still not sure if this is supported configuration. But I am sure that this works. We have migrated many servers successfully and without any issues using this approach.
You can find more about this at this blog: ASR Setup for VMs running in VMWare without VMware level User Access
I'm setting up my environment in azure and I´d to know how I can put my VM on the same network as my application server (web sites)?
Currently, there is a big latency between my database (on VM) and my application (on web sites).
You can add them to the same Virtual Network, to add a VM to a virtual network in the old portal remember to choose to "Create from gallery" as that is the only place where you can choose virtual network.
In the new portal you can add a website to the Virtual Network when opening the website.
One point worth remembering is that it is a VIRTUAL network, but as it used to be with affinity groups a VNET should make sure that your servers are located "close by"
You can connect Azure Web Applications to VNETs - the best practice is to make sure they are in the same data center.
You're still going to have some latency (more than what you would on your local dev machine) - but as long as they are in the same datacenter region (EAST US, etc), that should minimize latency.
Your database should also not be open to the public (best practices here), and a VNET would solve this problem.
With the lack of native SSAS support on Azure I am inclined to install it on a VM Role. I want to know if this sounds like a feasible option. Questions that come to mind:
It sounds like the VM drive is persisted on Azure Storage. Is this efficient for holding a SQL Server installation? Or are the drives not durable at all?
Can this VM be able to communicate with SQL Azure, Worker Roles, and Web Roles?
Can SSAS be accessed by Worker Roles and Web Roles?
If the answer to 2 or 3 is yes. Would the traffic be considered internal traffic or would it be subject to data transfer rates?
Thanks,
Yes - with the latest Virtual Machine announcements the drives are durable. So you can install SSAS on a VM along with SQL Server. Check out the details of the preview program here: https://www.windowsazure.com/en-us/home/features/virtual-machines/
A VM can communicate to SQL Azure like an other application as long as you open up the firewall to allow internal connections. I am not sure what you mean by accessing Worker Roles from a VM; what do you have in mind? Generally speaking you can access other endpoints through URLs; beware however that IP Addresses can change, so it's a good idea to have formal URLs for machines/end points you are trying to connect to.
The reverse is true as well; worker roles can communicate with other endpoints; just don't use IP addresses because they could change on you.
If you are deploying all your services within the same data center in Azure, it would all be internal traffic, so you would not be charged for that traffic.
The answers are as below:
Yes. You sure can use SQL Server 2008/2012 on any Azure VM. Be sure to have larger VM for better performance.
Yes, you can connect directly to Azure VM in between role as long as you have opened proper ports. As long as all machines are in Same DC this will not have any problem or need any special configuration.
Yes. #2 applies.
As long your egress/ingress is between all those machines are within same DC, it is all considered internal traffic.
Here is my scenario:
I have three Windows VMs on Windows Azure (which is at its preview stage right now) and all the VMs are connected to each other, in other words they are under the same cloud service. What I need to do now is that I will use one VM only for Redis and the other two VMs need to talk to it. I don't wanna open up the redis to the whole World for several reasons and one of them is that I don't want to talk to it through the load balancer. I want my VMs to talk to it directly (as explained here: Bypass the load balancer when communicating servers between each other).
I consider using MSOpenTech implementation of Redis. Any I idea how I can configure a structure like this?
Running Redis on A Windows Azure Virtual Machine (Windows or Linux) is exactly same as any other machine so I don't think you will met any problem there.
If you have one instance of Virtual Machine it is not configured through Load Balancer and you can see that when you will add endpoint to your VM. Only if you have more then 1 instances of a virtual machine, and then you add endpoint, then you will have a chance to configure the load blanacer for that specific endpoint. In your case as you want to run Redis on one single VM, you are really not behind load balancer.
IF you want to have your all 3 machines talking to each other you can create a virtual network and provision all 3 machines withing this VNET so they can talk to each other the way you want.
I figured this out by trying it out. Here is the solution:
SignalR with Redis Running on a Windows Azure Virtual Machine