Forum Discussion
MicrosoftLimitation of CSV import
Hi - I work in FSI and have a customer that cannot run the appliance against their production workload. When they attempt to upload the CSV file they hit the limit on the number of disks per VM which means they have to split the disks into 4 VM's. This means they will get an invalid recommendation for a VM size. Do we have any plans to improve the upload to allow for more disks/volumes?
3 Replies
Hi kodaksmile! With the current import functionality, we do have a limitation that you can add up to eight disks per VM. We do have the improvement planned to support more disks in our backlog. Though, we would love to know if there is something we can do to help you and the customer use the appliance and perform discovery. Are there any specific issues with running the appliance?
- kodaksmile
rashijoshi Their system is mission critical (they lose a lot of money when it's down) and has had outages due to spikes in the workload. They will not run anything new directly against the machines involved. They are already collecting performance metrics from their storage (Pure Storage), VMWare and monitoring tools.
kodaksmile I understand. Though Azure Migrate appliance discovers metadata and performance data of machines from vCenter in an agentless way. You can then perform an assessment even with 1 day worth of performance data. Linking the architecture here: Azure Migrate appliance architecture - Azure Migrate | Microsoft Docs
We will keep the thread posted when we release support for more than 8 disks per VM through the import method.
