I'm aware I can now do this through the portal in the storage blade however the account I need to migrate is a production account. It's just blobs, tables and queues, no VMs.
I can stomach some downtime (say an hour or 2) but am unsure how long it would take to migrate approx 750GB, does anyone have experience with the migration and an idea on the time it takes based on a similar volume size?
I also assume once migrated all my storage keys will change so I will need to update all the references in my app settings.
For anyone else wondering about this what #4c74356b41 said appears to be true.
Thanks to this post and the PowerShell command, couldn't get the ARM template to dpeloy at least not from VS, I was able to create a classic storage account. Didn't think this was still possible!
I then kicked off a 50k files container copy from another storage account in the Azure Storage Explorer container into this new classic resource and then while that was running ran the full migration including commit and the file copy carried on regardless.
Final step was to move the new resource (file copy is still ongoing at this point) from the migrated resource group back into the same resource group as the original classic storage account.
Once the move was complete the file copy was still going smoothly and all the Keys remained unchanged so this does seem to be truly seamless.
Related
I have Azure Pay-As-You-Go subscription account having Azure Storage general purpose V1 Service where I store files. I wondered yesterday, when I found another storage account with different location which I haven't created. For details screen shot is given:
If you have any knowledge about it or faced same behavior on Azure Storage, please guide and share your experience as I want to know what it is for and why it has been created on different location as my other services are in different resource group on Notrh Europe Location.
please guide and share your experience as I want to know what it is
for and why it has been created on different location as my other
services are in different resource group on Notrh Europe Location.
When you use Azure cloud shell, on the initial start, Cloud Shell prompts you to associate a new or existing file share to persist files across sessions.
When you use basic settings and select only a subscription, Cloud
Shell creates three resources on your behalf in the supported region
that's nearest to you. The auto-generated storage account always names cs<uniqueGuid>, read here.
Also, Azure creates a disk image of your $Home directory to persist all contents within the directory. The disk image is saved in your specified file share as acc_<User>.img
at fileshare.storage.windows.net/fileshare/.cloudconsole/acc_<User>.img, and it automatically syncs changes.
About the region, it depended on the region when you select the associated Azure storage account when initially start with Cloud shell. Associated Azure storage accounts must reside in the same region as the Cloud Shell machine that you're mounting them to. Its region is totally not related to your other Azure resource group. You also could run clouddrive unmount to re-select an associated storage account for the Azure file share.
To find your current region you may run env in Bash and locate the variable ACC_LOCATION.
I've set up Azure Site Recovery to replicate a VM using Azure-to-Azure replication. Everything is working great, but I've now added a new disk to my VM and I do not see the .vhd page blob in the replicated storage account.
How can I get the newly added disk to replicate? Do I need to remove replication and then redo it?
Currently, this feature is not available. Probably you need to redo it.
You may vote up an idea submitted by another Azure customer:
https://feedback.azure.com/forums/256299-site-recovery/suggestions/6438471-automatically-replicate-the-new-disk
All of the feedback you share in these forums will be monitored and reviewed by the Microsoft engineering teams responsible for building Azure.
I have on my account one windows server with IIS and one OS disk which is 127gb.
I also have another sql server with the os disk also 127gb and 3 additional disks, one for the tempdb, another one for datafiles and another one for the logs.
The application is very critical, and we need to change it to another account. However the maintenance window cant be more than 2 hours.
What is the fastest way to copy the VHDS from one location to the other account?
I tried cloudberry explorer adding the storage accounts and just copying the files, but its been more than 5 minutes and it has only copies 5% of one 127GB file.
Maybe this tool is using my computer as a temp location while it copies to the next storage account?
Is there a faster way?
The recommended way is to use AzCopy as below documentation link suggests.
https://azure.microsoft.com/en-us/documentation/articles/storage-use-azcopy/#blob-copy
If you have heard about PowerShell command Start-AzureStorageBlobCopy it will give you almost same duration: Link
Another way is to use hands of Azure operator.
Submit a support ticket and they can help you to move a Storage to another subscription. If you prepare Virtual machine image, it will be achieved less than 1 hour downtime (hopefully?).
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.
I mistakenly created a VM without linking it to an extant storage account. When I realized my mistake I deleted the VM and then sought to delete the storage account. I found the auto created storage account and attempted to remove the container. However even 24 hours later I get told that the container contains resources in use by the (now deleted) VM and so cannot be deleted.
Clearly there is some kind of dependency which is not apparent from the management portal which needs to be removed. I am looking for some advice on a powershell approach to investigating and resolving this issue.
You have to disassociate the disk with the VM image (VHD) before you can delete the blob or container.
You can do so from the Windows Azure management portal. Go to the VMs tab. Choose 'DISKS' from the top menu and remove it. If I remember well, it will also ask you whether you'd also like to delete the blob (VHD) from the storage account.