This is the best introduction/overview to Storage mover I've ever seen. Thank you! Even as a part of the Mover product team, I wouldn't be able to explain it as well as you did. Really appreciate you for making these videos to make our products more accessible!
Awesome explanation, Dean. Unfortunately, Azure file sync is not supported in the Clustered Volume storage(CVS), it can pick only the standalone cluster node. So we can’t use Azure file sync. Can we storage mover for this situation? Will it support?
Storage mover will move the files from a source share to a target share in Azure…I don’t see any docs on CSV either way…AND since Storage Mover is only interested in the files in the share I can’t see why it should not work
"If the agent runs into something like a file lock situation, no problem because the job can be run as many times as you want." So it sounds like Azure Storage Mover 1) has open file awareness, and 2) is configured to skip open files. If that's correct, can it be configured to copy open files (similar to how robocopy has no open file awareness). Also sounds like there is no real-time sync component, so for active file shares, you'd need an outage window long enough to complete the final scan before cut over.
it depends how long you give the agents to do their thing before your cut over date. If you start far enough in advance it should get it done without an outage…just cut over. The project reports in the portal will tell you if there are any files left to be copied, and if you need to you can schedule a outage cut over.
You can’t directly deploy the storage mover agent in Azure…HOWEVER, you can build a VM and make it a hyper-v server, then download the agent on to there… You will need to set up NAT translation for it to work…watch this for how to: ruclips.net/video/RRYhlZCLATQ/видео.htmlsi=0duDjazLO-aQ7c14
Dean, sorry for the quick second comment, but could you PRETTY PLEASE do a quick to the point Azure NetApp Files video? I want to migrate an on-prem LOB application with a flat file database to Azure, and the shop has a steady 1mbps up/down fiber pipe and would like to see how the performance would be, on hot blob storage with low latency. We are talking about $600 spend a month including AAD DS.
How about security groups with access to specific folders, and subfolders where individual access has been assigned (read: not inherited)? Will that also transferred?
So... I was just about to provision a OneDrive for Business P2 "all you can eat" license to put on an ole Win Server 2012 r2 box to get everything up eventually replacing the box with an on-prem machine that would actually be Azure File Shares over SMB, while allowing some Windows365 outside sales employees into the same OD account, or tunnel on-prem to grab the same data... Dean, is your solution in this video still a better way to go? OneDrive does have a "Delta Sync / Robocopy" feel to it as well. Would you happen to work for Microsoft? Are you an MVP? Thanks so much for your content sir!!
I do work directly for Microsoft, I’m in the Azure engineering group along with the other product groups. The question of storage mover vs. Azure Files Sync vs. push to share point online / OneDrive for business all comes down to the presentation of the files back to the users. If this is personal users data, then OneDrive. Central file server data where you want a local hot file cache for faster on prem access for the users then Azure Files Sync And if you want it all moved to the cloud and accessed from the cloud, Storage Mover is what you want.
I haven't looked at Azure Files in quite some time but from what I've read online, Azure Files and AAD joined devices (no on-prem), is still not super user friendly. I think MS needs to figure out if they want Onedrive, Sharepoint Documents or Azure files (with a GUI front end like DropBox etc) to be the defacto cloud file server. Right now I see third party apps that leverage Azure Files and allow for mapped drives etc.
The reason there is no Defacto service is because each one has a specific use case and the user interface layer also has a lot to do with it. SharePoint docs are files for SharePoint sites. OneDrive for business is a layer on top of SharePoint for File server replacement, corporate licensing OneDrive for personal is your own cloud file storage, personal licensing Azure Files is file share storage, but not tied to users licensing at all, but centrally controlled and permissioned. Then there is Blob Storage which is a whole other animal. and since each of these has their own strengths, licensing, cost and admin interface...all aimed at different audiences...we have multiple solutions. but I do agree that the world would be simpler with a single solution 😊💯
Great question: it comes down to your purpose. If you want your files migrated to the cloud Storage Mover is the tool for you. But if you want the files in the cloud and then accessed from on prem File Sync is what you need. So it all comes down to where the files should be accessed from
Hello Dean, Thanks for the great video. I would like to ask, what would happen to my on-prem servers (DC, SQL or APP) if I use Azure Migration. Would the server be unavailable to use while Azure Migration doing it's process? Would they turn off automatically? Would they be unusable? I am curious to know in case if there is a project in near future :) . Hope to hear from you soon. Ciao
Azure Migrate will copy a full replica of your VM starting NOW and all the changes that you make on that VM until you start the VMs migration to the cloud. Once done you stop further syncing the data, the on prem VM is powered off and you are running in the cloud Watch this for more ruclips.net/video/8F0J-1w7fYA/видео.htmlsi=9QS4noD6RPz3J0Kv
@@AzureAcademy Thanks Dean for your response. Would you be able to assist me and confirm if the following information is correct? - Azure Migrate can migrate my on-premises SQL Server and databases to Azure VM - Azure Migration Service attempts to migrate users and roles from old to new server - The migrated server and databases will retain their original names by default - I can keep on-premises server operational after migration for a period of time for fallback or additional data transfer if needed Appreciate the video link you have shared, I'll watch it soon. Thanks again and I look forward to hearing from you soon :)
Yes Azure Migrate will replicate the exact server 100% as is, including the name, into the cloud. Once done the on prem source server will be powered off…but won’t be deleted unless you delete it, so you can revert back if you need to
Hello Dean, great video! I have 3 file servers to migrate to Azure file and I would like your opinion on the best method to use. The goal of the migration is to completely remove on-premises file servers. Do you think Azure storage mover is the best solution for me ? Compared to Robocopy / Azcopy or azure file sync ?
Yes, storage mover is the best option. It is a managed agent that makes migrations a breeze. Robocopy / AZcopy need a system to run the terminal on and monitor. AFS can be used to bring data into Azure but is not technically a migration tool
@@AzureAcademy Thank you for your answer. Once I have completed a job, can I do a delta? in order to only copy changes before migration day? I would also like to know what the costs will be linked to the migration, I understand that there will be costs for the logging part but will there be others? Thanks !
cost of storage mover is ZERO. Azure Files has its own cost structure to store your files in shares...which depends on the TIER of the storage account and the access type you selected.
One of our customer currently have File shares on Azure VMs. They have 60 TB of data. I am planning to migrate the file shares to Azure files (PaaS) hot tier which i believe would save a lot of money. Can i spin up Azure storage mover agent VM in Azure to migrate the data from file share VM to Azure files?
Yes you can…but the agents are only Linux based and not supported as Azure VMs today…So you would have to stand up a VM with nested virtualization then setup hyper-V and deploy the agents on hyper-V. Then you can set the source VMs that you have in Azure and the targets as the Azure Files shares
@@AzureAcademy Thanks very much for the suggestion. Just wondering why Microsoft couldn’t give a vhd image that would work as Azure VM. Not sure what vm SKU supports nested virtualisation. Can I not convert the downloaded vhdx to vhd to get this working in Azure?
The agent is still a Linux OS and the “normal” way to use storage mover is to deploy it on prem where your file servers are, so you can migrate that data to the cloud. So the PG did not build the agents with all the Azure VM requirements, because it isn’t built to run in Azure. So the way you can make it work is to build your own on prem in the cloud That’s why you would build a VM with nested virtualization enabled So you can run hyper-V on a VM in Azure and run the agents there… Make sense?
Oh dear, is Microsoft going backwards Why is the agent unix based and If for some technical reason they had to use unix, why didnt microsoft use a GUI wizard to perform the required settings. Don't really like the command based system unless I have to use it!!
I would not say that the command line or this simple interface is “going backwards” it is a simple interface that does its purpose. Why design an expensive GUI when you need to add 4 bits of data once in its life…then never look at it again, because everything else is done in the portal. Now I agree that an improvement could be adding those details to the agent through a file or script that you download then drop into the agent could be cool…I’ll suggest that as an improvement Thanks!
So you think moving that much data is crazy…but spending 10s of $1,000 for an on prem storage system that YOU have to manage, pay to maintain while you pay for power and cooling isn’t crazy…?
@@AzureAcademy well, for some organisation that actually works out better. I have worked with massive construction, architecture, and media companies which are very data (egress) heavy and cannot make a sane business case for the cost of having much in the cloud except for PaaS resources and a few critical infrastructure for failover/landing zone requirements.
@@AzureAcademy No assessment/pentesting don't yet. It would be flat NO to plugging strange appliances into production network without usual security and management agents. Even if I get an exception it would take months to get necessary risk reviews and assessments performed to allow a new type of device into production. Windows installer MSI would be no problem. Microsoft MCAS log collector was another pain. It assumed you had infra to host docker containers when it was just a Java app that could run anywhere. Need easy options in them locked down corp environments.
So I’m confused on one part… an appliance isn’t ok, even though you are given all the info on what’s running on it…and you can log in and verify all of it…but it’s ok to give you an MSI file and tell you what’s in it…and you can’t check what it’s doing until it did it… Help me understand why one is ok and the other isn’t
This is the best introduction/overview to Storage mover I've ever seen. Thank you! Even as a part of the Mover product team, I wouldn't be able to explain it as well as you did. Really appreciate you for making these videos to make our products more accessible!
WOW thank you! DM me with the other things the team is working on so we can partner on those as well ☺️
Awesome explanation, Dean.
Unfortunately, Azure file sync is not supported in the Clustered Volume storage(CVS), it can pick only the standalone cluster node.
So we can’t use Azure file sync. Can we storage mover for this situation? Will it support?
Storage mover will move the files from a source share to a target share in Azure…I don’t see any docs on CSV either way…AND since Storage Mover is only interested in the files in the share I can’t see why it should not work
"If the agent runs into something like a file lock situation, no problem because the job can be run as many times as you want."
So it sounds like Azure Storage Mover 1) has open file awareness, and 2) is configured to skip open files. If that's correct, can it be configured to copy open files (similar to how robocopy has no open file awareness).
Also sounds like there is no real-time sync component, so for active file shares, you'd need an outage window long enough to complete the final scan before cut over.
it depends how long you give the agents to do their thing before your cut over date.
If you start far enough in advance it should get it done without an outage…just cut over.
The project reports in the portal will tell you if there are any files left to be copied, and if you need to you can schedule a outage cut over.
What about migrating file shares on a file server IN AZURE? Do I have to figure out a way deploy the appliance in Azure?
You can’t directly deploy the storage mover agent in Azure…HOWEVER, you can build a VM and make it a hyper-v server, then download the agent on to there…
You will need to set up NAT translation for it to work…watch this for how to: ruclips.net/video/RRYhlZCLATQ/видео.htmlsi=0duDjazLO-aQ7c14
@@AzureAcademy whoa whoa... Wait a second... Is it an actual installable agent or a virtual appliance?
It is a VM that is a Linux Appliance…
Dean, sorry for the quick second comment, but could you PRETTY PLEASE do a quick to the point Azure NetApp Files video? I want to migrate an on-prem LOB application with a flat file database to Azure, and the shop has a steady 1mbps up/down fiber pipe and would like to see how the performance would be, on hot blob storage with low latency. We are talking about $600 spend a month including AAD DS.
Already one the channel check it out
👉 ruclips.net/video/bswIbTB62mY/видео.htmlsi=QR8_8FkcjogevFg_
Thanks!!!!!
anytime!
How about security groups with access to specific folders, and subfolders where individual access has been assigned (read: not inherited)? Will that also transferred?
just like RoboCopy, the NTFS Permissions will all be preserved.
So... I was just about to provision a OneDrive for Business P2 "all you can eat" license to put on an ole Win Server 2012 r2 box to get everything up eventually replacing the box with an on-prem machine that would actually be Azure File Shares over SMB, while allowing some Windows365 outside sales employees into the same OD account, or tunnel on-prem to grab the same data...
Dean, is your solution in this video still a better way to go?
OneDrive does have a "Delta Sync / Robocopy" feel to it as well.
Would you happen to work for Microsoft? Are you an MVP? Thanks so much for your content sir!!
I do work directly for Microsoft, I’m in the Azure engineering group along with the other product groups. The question of storage mover vs. Azure Files Sync vs. push to share point online / OneDrive for business all comes down to the presentation of the files back to the users.
If this is personal users data, then OneDrive.
Central file server data where you want a local hot file cache for faster on prem access for the users then Azure Files Sync
And if you want it all moved to the cloud and accessed from the cloud, Storage Mover is what you want.
I haven't looked at Azure Files in quite some time but from what I've read online, Azure Files and AAD joined devices (no on-prem), is still not super user friendly. I think MS needs to figure out if they want Onedrive, Sharepoint Documents or Azure files (with a GUI front end like DropBox etc) to be the defacto cloud file server. Right now I see third party apps that leverage Azure Files and allow for mapped drives etc.
The reason there is no Defacto service is because each one has a specific use case and the user interface layer also has a lot to do with it.
SharePoint docs are files for SharePoint sites.
OneDrive for business is a layer on top of SharePoint for File server replacement, corporate licensing
OneDrive for personal is your own cloud file storage, personal licensing
Azure Files is file share storage, but not tied to users licensing at all, but centrally controlled and permissioned.
Then there is Blob Storage which is a whole other animal.
and since each of these has their own strengths, licensing, cost and admin interface...all aimed at different audiences...we have multiple solutions.
but I do agree that the world would be simpler with a single solution 😊💯
Excellent answer@@AzureAcademy
👍👍
Why would you use Azure storage mover, insted of setting up Azure file sync?
Great question: it comes down to your purpose.
If you want your files migrated to the cloud Storage Mover is the tool for you.
But if you want the files in the cloud and then accessed from on prem File Sync is what you need.
So it all comes down to where the files should be accessed from
Hello Dean,
Thanks for the great video.
I would like to ask, what would happen to my on-prem servers (DC, SQL or APP) if I use Azure Migration.
Would the server be unavailable to use while Azure Migration doing it's process?
Would they turn off automatically?
Would they be unusable?
I am curious to know in case if there is a project in near future :) .
Hope to hear from you soon.
Ciao
Azure Migrate will copy a full replica of your VM starting NOW and all the changes that you make on that VM until you start the VMs migration to the cloud. Once done you stop further syncing the data, the on prem VM is powered off and you are running in the cloud
Watch this for more ruclips.net/video/8F0J-1w7fYA/видео.htmlsi=9QS4noD6RPz3J0Kv
@@AzureAcademy
Thanks Dean for your response.
Would you be able to assist me and confirm if the following information is correct?
- Azure Migrate can migrate my on-premises SQL Server and databases to Azure VM
- Azure Migration Service attempts to migrate users and roles from old to new server
- The migrated server and databases will retain their original names by default
- I can keep on-premises server operational after migration for a period of time for fallback or additional data transfer if needed
Appreciate the video link you have shared, I'll watch it soon.
Thanks again and I look forward to hearing from you soon :)
Yes Azure Migrate will replicate the exact server 100% as is, including the name, into the cloud.
Once done the on prem source server will be powered off…but won’t be deleted unless you delete it, so you can revert back if you need to
@@AzureAcademy
Sweet. Thank you so much
👍☺️👍
Hello Dean, great video!
I have 3 file servers to migrate to Azure file and I would like your opinion on the best method to use.
The goal of the migration is to completely remove on-premises file servers.
Do you think Azure storage mover is the best solution for me ?
Compared to Robocopy / Azcopy or azure file sync ?
Yes, storage mover is the best option. It is a managed agent that makes migrations a breeze. Robocopy / AZcopy need a system to run the terminal on and monitor. AFS can be used to bring data into Azure but is not technically a migration tool
@@AzureAcademy Thank you for your answer.
Once I have completed a job, can I do a delta? in order to only copy changes before migration day?
I would also like to know what the costs will be linked to the migration, I understand that there will be costs for the logging part but will there be others?
Thanks !
yes you can do deltas. and the portal will report on your % complete each time you run the job
@@AzureAcademy Perfect ! And regarding the costs, what will be the costs associated with the use of this service to make a migration ?
cost of storage mover is ZERO. Azure Files has its own cost structure to store your files in shares...which depends on the TIER of the storage account and the access type you selected.
Can you elaborate what you mean by “the end of server support is coming”? You mean like windows server will be no more?
Server 2012 End of support is in October
The most domain controllers and file servers are on 2012
One of our customer currently have File shares on Azure VMs. They have 60 TB of data. I am planning to migrate the file shares to Azure files (PaaS) hot tier which i believe would save a lot of money. Can i spin up Azure storage mover agent VM in Azure to migrate the data from file share VM to Azure files?
Yes you can…but the agents are only Linux based and not supported as Azure VMs today…So you would have to stand up a VM with nested virtualization then setup hyper-V and deploy the agents on hyper-V.
Then you can set the source VMs that you have in Azure and the targets as the Azure Files shares
@@AzureAcademy Thanks very much for the suggestion. Just wondering why Microsoft couldn’t give a vhd image that would work as Azure VM. Not sure what vm SKU supports nested virtualisation. Can I not convert the downloaded vhdx to vhd to get this working in Azure?
The agent is still a Linux OS and the “normal” way to use storage mover is to deploy it on prem where your file servers are, so you can migrate that data to the cloud.
So the PG did not build the agents with all the Azure VM requirements, because it isn’t built to run in Azure.
So the way you can make it work is to build your own on prem in the cloud
That’s why you would build a VM with nested virtualization enabled
So you can run hyper-V on a VM in Azure and run the agents there…
Make sense?
@@AzureAcademy Thank you so much for your help. I have now built in Azure on a hyper v vm. It’s working fine
👍☺️👍
Oh dear, is Microsoft going backwards Why is the agent unix based and If for some technical reason they had to use unix, why didnt microsoft use a GUI wizard to perform the required settings. Don't really like the command based system unless I have to use it!!
I would not say that the command line or this simple interface is “going backwards” it is a simple interface that does its purpose. Why design an expensive GUI when you need to add 4 bits of data once in its life…then never look at it again, because everything else is done in the portal.
Now I agree that an improvement could be adding those details to the agent through a file or script that you download then drop into the agent could be cool…I’ll suggest that as an improvement
Thanks!
@@AzureAcademy Please, no more Wizards :(
I make no promises 🫢🤯
Anyone putting that much data in the cloud is either crazy or has too much money and doesn't know what to do with it
So you think moving that much data is crazy…but spending 10s of $1,000 for an on prem storage system that YOU have to manage, pay to maintain while you pay for power and cooling isn’t crazy…?
@@AzureAcademy well, for some organisation that actually works out better. I have worked with massive construction, architecture, and media companies which are very data (egress) heavy and cannot make a sane business case for the cost of having much in the cloud except for PaaS resources and a few critical infrastructure for failover/landing zone requirements.
Fair enough ☺️
An appliance?! What was Microsoft thinking? So difficult to get unmanaged systems into corp environment. Just give us the software installer!
I’ll pass along your feedback, can you tell me if your security people have looked at this agent and what their issues are so we can address them?
@@AzureAcademy No assessment/pentesting don't yet. It would be flat NO to plugging strange appliances into production network without usual security and management agents. Even if I get an exception it would take months to get necessary risk reviews and assessments performed to allow a new type of device into production. Windows installer MSI would be no problem. Microsoft MCAS log collector was another pain. It assumed you had infra to host docker containers when it was just a Java app that could run anywhere. Need easy options in them locked down corp environments.
So I’m confused on one part… an appliance isn’t ok, even though you are given all the info on what’s running on it…and you can log in and verify all of it…but it’s ok to give you an MSI file and tell you what’s in it…and you can’t check what it’s doing until it did it…
Help me understand why one is ok and the other isn’t