asked on

Azure file server disk limitation of 1023 Gb (1 TB)

Hi Experts,

We would like to migrate our on-premises file server to an Azure Windows VM. We have single file shares with over 1 TB of data. Azure VMs can only attach a 1 TB sized volume, What would be the recommended approach (best practice) to migrate the data to an Azure Windows VM and give users SMB file access to a larger than 1 TB file share? Ideally I'd like to have a 2 TB file share.

Potential options:

1. Break the data up and share out multiple SMB file shares (multiple mapped drive letters).
2. Use Windows Storage Spaces.
3. Use Disk spanning within disk management.

I performed a bit of research on Storage Spaces, and it does seem like a viable, and supported option within Azure. Therefore, I am leaning towards Storage Spaces. What do you think? Are there any other good options?

Thanks!

ASKER CERTIFIED SOLUTION

Philip Elder

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial

SOLUTION

Aaron Tomosky

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial

lighthousekeeper

ASKER

Thanks Aaron, that is a good point. Do you think Microsoft would charge more for consumption when using Fixed provisioning versus thin provisioning, even if no data is added? My guess would be no, but what do you think?

SOLUTION

Aaron Tomosky

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial

SOLUTION

Zachariah Browning

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial

Aaron Tomosky

All comments agree: Storage spaces is how you stripe volumes in azure for size and performance. Number of disks is tied to VM size and storage is billed as used.