I am running the Azure Site Recovery planner tool to provide us with some information for our local VMware environment, so we can later setup Azure Site Recovery.
I'm having problems with the Bandwidth checker command which is failing to give me the bandwidth we would require to Azure
Here is the command I run:
ASRDeploymentPlanner.exe -Operation GetThroughput -Directory "C:\AzureSiteRecovery\PlannerTool\ProfileData" -Virtualization VMware -VMListFile "C:\AzureSiteRecovery\PlannerTool\ProfileVMList.txt" -StorageAccountName MyStorage -StorageAccountKey XXXXXXXXXXXX
Here's the error I get:
VMWARE TO AZURE ASR DEPLOYMENT PLANNER
Finding achievable throughput from server 'MyServer' to Azure storage account 'MyStorage'. It might take from few minutes to hours based upon bandwidth availability and number of VMs in the given filename. Please wait...
Creating VHDs
Uploading VHD files to storage account: MyStorage...
Error in uploading files. Failed to calculate achievable throughput.
Possible reasons:
STORAGE_COMMUNICATION_ERROR. Unable to communicate to Azure Storage blob. Check network connectivity to Azure and if bandwidth from on-premises to Azure is very low.
Deleting 'asrvhdfile*' files from storage account...
Successfully deleted files.
Deleting 'asrvhdfile*' files from local machine...
Successfully deleted the files.
Get throughput operation failed.
I can see its placing the VHD files in the Blob storage so there is a connection there.
It seems the same issue as this post:
https://learn.microsoft.com/en-us/answers/questions/529111/storage-communication-error-unable-to-communicate.html
However I have no idea where to enter the code they mentioned in the Azure site recovery planner tool.
I have excluded this vm from any proxies and checked the firewall url and ports required are allowed.
A speed test shows 80MB up and down
Running an AZ speed test PowerShell test shows I'm getting about 24 MS response times from my Azure region
I can upload files to the blob storage manually using Azure Storage Explorer, and see an upload of 80mbps
I have also tested this tool in a hyper v environment (home lab) and have the same error
Has anyone had any experience with this issue or have any suggestions I can try, thanks in advance.
Related
I'm using Azure ML workspace. I'm having an issue with running ML experiment for segmentation. When I submit a run it will always end with this error:
UserError: AzureMLCompute job failed. BFSMountError: Unable to mount blob fuse file system Info: Could not mount Azure Blob Container azureml-blobstore-{UID} at workspaceblobstore: Unauthorized. Cannot access the storage account with the given account key. Please verify that the account key is valid. Info: Failed to prepare an environment for the job execution: Job environment preparation failed on 10.0.0.5 with err exit status 1.
I believe that documentation says that this blob is created automatically for storage of model files.
Storage account in which this blob resides is integrated into VNET. Datastore has Use workspace managed identity for data preview and profiling in Azure Machine Learning studio set to yes, access key has been copied from storage account portal page, number of times. I have no idea why is this happening.
Thanks for reaching out to us.
Please check out https://learn.microsoft.com/en-us/azure/machine-learning/how-to-secure-workspace-vnet for Azure Machine Learning resources vNet settings.
For this specific error, can you please help to confirm the following settings in your workspace:
whether storage account(workspaceblobstore) is within the same vNet with the compute?
whether allow access to microsoft service is checked in the storage account(workspaceblobstore)
I am trying to create a VM on Azure, from VHD of an On Premise Server. As per the steps, I have created the VHD file of the C Drive of my server (including the system reserved partition), and have uploaded the same VHD to Blob Storage (as Page Blob). I have uploaded it through Portal.
Now as per next step, I am trying to create an Image from it, so that it can be used to create VM.
But I am getting the following error:
Failed to create image 'NewImage'. Error: At least one resource
deployment operation failed. Please list deployment operations for
details. Please see https://aka.ms/arm-debug for usage details.
Not able to identify the actual error or problem in this.
From description i believe the issue is with the way you converted the VHD. People always miss the section where is says the VHD must be Fixed Size VHD.
Not sure if disk2vhd has the option but you can use the Convert-VHD command in Hyper-V module or Microsoft VM Converter.
Convert-VHD –Path c:\test\MY-VM.vhdx –DestinationPath c:\test\MY-NEW-VM.vhd -VHDType Fixed
Also, VHD images on Azure must have a virtual size aligned to 1 MB. Typically, VHDs created using Hyper-V are aligned correctly.
To create the Azure VM from a VHD file which created on-premise. You need to do a lot of steps to prepare the VHD file. Not just convert the disk to the VHD file, you need to make sure it can run well on-premise.
The error you get does not show the reason that causes the accident. What I can provide are the steps that you can follow to create an available VHD file. And all the steps and recommends in Prepare a Windows VHD or VHDX to upload to Azure.
I'm a lone dev that inherited a giant undocumented mess of an azure vm without any sysadmin-like training nor a lab to test things out. This vm runs our website just fine, but I couldn't log in to VestaCp because disk space usage is at 100%.
I did setup azure to make daily backups. Now I'm wondering if azure somehow stores them on the same machine e.g. they're the cause of the full disk space.
if so, how do I remove a set of old backups?
Now I'm wondering if azure somehow stores them on the same machine e.g. they're the cause of the full disk space.
As mentioned in the official document about creating a recovery services vault for a VM:
The location of Recovery Services vault determines the geographic region where your backup data is sent.
If you have virtual machines in multiple regions, create a Recovery Services vault in each region.
There is no need to specify the storage accounts used to store the backup data--the Recovery Services vault and the Azure Backup service automatically handle the storage.
Per my understanding, your VM backup data could be stored on the storage accounts that are managed automatically by the Recovery Services vault (ARM) and the Azure Backup service (ASM).
Moreover, if this issue could not be solved by removing a set of old backups, I assumed that you could follow this tutorial to resize Azure VM OS or Data Disk created using Azure Service Manager (ASM) or this tutorial for resizing ARM VM OS & Data disk.
Could someone please help me understand this? I created Virtual Machine in Azure running Windows Server 2012. I noticed Azure created a storage account automatically. When I go inside that storage account, click Containers tab, and under vhds name it shows a name-name2-2014-12-05.vhd which is 127 GB and it always has recent Last modified date. What is that for? Is that my live backup image of my entire server deployment? If so where can I see how often it backs up?
When I go inside that storage account, click Containers tab, and under
vhds name it shows a name-name2-2014-12-05.vhd which is 127 GB and it
always has recent Last modified date. What is that for?
Virtual Machines in Azure are Stateful in nature. What that means is that any changes you make to the Virtual Machines like installing software, creating files etc. are persisted. The way Azure achieves this is by storing the Virtual Machine VHD as a page blob in Azure Storage. What you see as name-name2-2014-12-05.vhd is the VHD using which Azure launches your VM.
Is that my live backup image of my entire server deployment?
It is your VM and not the backup image. If by mistake you delete it (though Azure makes it real hard for you to delete it but its possible), your VM is gone. If you want, you can take a backup of this and store it in some other place. Search for Create Azure Virtual Machine Images and you will find ample resources.
If so where can I see how often it backs up?
By default Azure keeps 2 extra copies (a total of 3 including the main) of it in the data center and if you have enabled geo-redundancy, then Azure keeps additional 3 copies in a separate datacenter. However please keep in mind that it is not a backup. Any changes you make to your VM are replicated to all the copies. You would need to come up with your backup approach.
My recommendation would be to read more about Azure Virtual Machines. I'm sure if you search for it, you will get plentiful of resources.
A couple of months ago our MSDN Visual Studio subscription was appeared cancelled. When contacted Microsoft, they restored our account. But all our servers running in the subscription was stopped. But I was able to start all servers except one (Ubuntu server). It was showing "internal server error". We managed to recover most of the data from our backups. But I would like to recover some other data that was not in the backup. Now, when I tried starting the server, it shows the error "A disk with nae xxxxxx-2012080707000 does not exist in the subscription". When checked, this particular disk is not listed in the "Disks" tab in Virtual Machines.
I am unable to attach or detach disks to the VM or upgrade it.
How can i troubleshoot it and start the VM
Thank you in advance
Since the VHDs are stored as page blobs in blob storage, you can start by looking for a page blob named the same as your disk. Usually you would find these blobs in vhds blob container. If you have this blob, you can create a disk using this and attach it to your VM. However if the blob is not there, then I don't think you can do anything.