I have an Azure VM with a managed disk (which is not located in any storage account).
The VM is located in West US while it's resource group is located in West Europe.
I want to move the VM to West Europe as well.
Is there a way to move this VM to another location without generalizing it?
I saw that there's something called AzCopy, But I don't think that I can use it because my VM's disk is managed and it's not located in a storage account.
I can't use the recovery vaults because the resource group of the VM is located in the region where I want to move my VM to.
It shows the following error when I try to create a recovery vault in the same region:
You cannot protect VMs from the same region as of the vault or vault’s resource group. In the event of a datacenter disruption, the vault or resource group also might not be available. Create (or use) a vault in a different region to protect these VMs.
And even If I could create the Vault, I still wouldn't find my VMs (to replicate) because they are in a different region than it's resource group.
Here is an official tutorial explaining every step you need to take https://learn.microsoft.com/en-us/azure/resource-mover/move-region-within-resource-group.
Alternatively, I would create a new resource group with my desire location and create a new custom virtual network. Then move my VM to the new created resource group. click on the VM and go to networking, click on NIC public IP; disassociate it and associate the new custom VN.
#ps:
you might want to disassociate it first before moving to the new resource group.
You can use Azure Site Recovery
https://learn.microsoft.com/en-us/azure/site-recovery/azure-to-azure-tutorial-migrate
In addition to using the Azure Site Recovery service to manage and
orchestrate disaster recovery of on-premises machines and Azure VMs
for the purposes of business continuity and disaster recovery (BCDR),
you can also use Site Recovery to manage migration of Azure VMs to a
secondary region. To migrate Azure VMs, you enable replication for
them, and fail them over from the primary region to the secondary
region of your choice.
Related
I have a storage account in a subscription which has a VNet that the storage account is setup to use. This works well in the kubernetes cluster in that subscription that attached to that Vnet. NFS works fine to the the storage account in question.
But we have a secondary subscription for failover in a paired region (East US and West US) that I'd like to have that k8s cluster also be able to mount the NFS share.
I've tried creating a peering and adding the secondary subscription's VNet (which doesn't overlap) to the Storage account, but the k8s cluster in the secondary subscription times out connecting the share.
I didn't do any routing options when creating the peering, but I would have assumed that this would just work.
Does anyone have any instructions on how to get this working so that the secondary cluster can access the NFS share?
The storage sync service and/or storage account can be moved to a different resource group, subscription, or Azure AD tenant. After the storage sync service or storage account is moved, you need to give the Microsoft.StorageSync application access to the storage account.
Click Access control (IAM) on the left-hand table of contents.
Click the Role assignments tab to the list the users and applications (service principals) that have access to your storage account.
Verify Microsoft.StorageSync or Hybrid File Sync Service (old application name) appears in the list with the Reader and Data Access role.
This GitHub document on Azure file share can give you better insights.
Basically, what I need is when a machine is replicated using Azure ASR and a VM is created after Test Failover or Final Failover, the newly created Azure VM should have premium disk types irrespective of on-premise disk type. Can this be achieved by making any changes on the Azure portal ?
While enabling replication for the first time you can mention what type of disks are needed after fail-over.Once you have enabled it you may change thru Powershell from standard to premium, however reverse direction is not supported
It seems the easiest option for this is to- First let the VM be created with Standard disks, then shutdown the VM, then go to 'Disks' properties and change the disk/s from Standard to Premium and then restart the VM. Seems, there is no option to let the VM itself be created with Premium disks.
There are two back up configuration options for Azure Recovery Service Vault - LRS vs GRS
This is a question regarding Azure Recovery Service Vault.
How does geo-redundant enabled recovery service vault being handled when its residing region failed ?
If the cross region restore is not being enabled for a recovery service, which by default it isn't, what will happen to my recovery service vault ?
I am trying to find out the difference between enabling cross region restore and not to.
There is not much info that i can find through the internet and official documents.
Configure cross region restore for recovery service vault
There is one more helpful link GRS vs LRS. However, as of time writing, seems like cross region restore has not been enabled, and right now, it is on enabled in west central us. However, we can enable GRS for all(most) regions.
The Recovery Services vault is an entity that stores the backups and recovery points created over time. Azure Backup automatically handles storage for the vault. The LRS and GRS mean to the Storage Replication type. Read the storage replication strategy.
Locally redundant storage (LRS) replicates your data three times
within a single data center.
GRS replicates your data to another data
center in a secondary region, but that data is available to be read
only if Microsoft initiates a failover from the primary to secondary
region.
Storage Replication type by default is set to Geo-redundant. The CRR feature is based on A vault created with GRS redundancy. So you can enable GRS for all(most) regions but CRR is currently available in the WCUS region. Read here.
As the GRS storage replication, If the primary region that geo-redundant enabled recovery service vault residing on failed, Microsoft initiates a failover from the primary to a secondary region. The secondary region serves as a redundant source for your data.
With CRR enabled service, The restore operation on the secondary region can be performed by Backup Admins and App admins. Which gives you full control to restore data to a secondary region. The secondary region is an Azure paired region.
Without CRR enabled service, you probably could not restore all the Azure VMs for the selected recovery point if the backup is done in the secondary region. You can create a new VM from a restore point, restores a VM disk, replace a disk on the existing VM. See the restore options.
Hope this could help you.
THis is another answer from Cross Region Restore - check comments for reference purpose.
The storage redundancy configuration for the Recovery Services Vault (RSV), is specific to Azure Backup data, not Azure Site Recovery (ASR).
This means, in the event of an Azure region failure, if the RSV is configured with Geo-Redundant Storage (GRS), then (with the help of the Azure support team), the RSV can be made available in the paired Azure region, and the data would be accessible.
The cross-region restore (CRR) option, is something that’s specific to Azure Backup, not ASR. You can have an RSV configured with GRS storage, but not have CRR enabled. The CRR feature allows you to take a backup of a VM in Region1, and perform a VM restore in Region2. The storage redundancy is for geo-failover of the RSV itself in the event of a full Azure region failure.
I have an Azure VM with un-managed disk. I want to move it to another region.
Is there any other way than generalizing my current VM?
Is there any other way than generalizing my current VM?
Azure does not support changing a VM's location. You need copy the VM's VHD to another location and use that VHD to create a new VM.
If you don't use current VM's VHD to create multiple VMs in other location, you don't need generalize your VM. Please refer to following steps.
Stop your VM.
Create a new storage account and blob container in another location.
Copy VHD to the new storage account, you could use Azcopy. For more information about Azcopy please refer to this article.
AzCopy /Source:https://shuidisks446.blob.core.windows.net/vhds /Dest:https://shuidiag102.blob.core.windows.net/vhds /SourceKey:sGqtdFHQWQWYyf2tRWGF5jkeAEubTp13AVaeTM25QogxXE+K0Ezq1ulcs18qGVPhCEp6ULdLLbKVa7fMbUvYZg== /DestKey:iCjeS+eegjkSJXHjH2UqCkqXnUPiCGvxaOG0Ad2LoPgUnvBoWl9wQJtC1jc//lOj4CF7khpLQe791P4QeyTY6Q== /Pattern:shui20161222141315.vhd
Use the VHD to create a new VM. It is easy for you to recreate with existing VHD by using this template.
Important: Because you don't generalize your currently VM, please don't start two VM at the same time. The second would have the same network issue.
Yes, even though the VM is generalized if you restore from backup the working state will get restored
Plan your VM backup infrastructure in Azure
https://learn.microsoft.com/en-us/azure/backup/backup-azure-vms-introduction
Back up Azure virtual machines to a Recovery Services vault
https://learn.microsoft.com/en-us/azure/backup/backup-azure-arm-vms
Use Azure portal to restore virtual machines
https://learn.microsoft.com/en-us/azure/backup/backup-azure-arm-restore-vms
Azure Site Recovery now offers migration capability between some regions. See this link for details.
https://learn.microsoft.com/en-us/azure/site-recovery/azure-to-azure-tutorial-migrate
Notably, you can only move between supported regions as shown here - basically the same continent.
https://learn.microsoft.com/en-us/azure/site-recovery/azure-to-azure-support-matrix#region-support
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.