Sharing Files between VMs in Same Resource Group

%3CLINGO-SUB%20id%3D%22lingo-sub-1512187%22%20slang%3D%22en-US%22%3ESharing%20Files%20between%20VMs%20in%20Same%20Resource%20Group%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1512187%22%20slang%3D%22en-US%22%3E%3CP%3EWe%20have%20two%20Azure%20Windows%2010%20VMs%20setup%20on%20the%20same%20resource%20group%20and%20they%20both%20need%20access%20to%20the%20same%20small%26nbsp%3B%20Access%20databases.%20MS%20Access%20on%20each%20VM%20will%20be%20used%20for%20the%20front%20end%20connect%20to%20these%20files.%20I%20setup%20a%20File%20Share%20in%20Blob%20Storage%20in%20this%20same%20RG%20and%20mapped%20it%20to%20a%20drive%20in%20each%20VM.%20While%20this%20works%2C%20it%20is%20slow.%20Since%20there%20are%20multiple%20databases%2C%20and%20they%20are%20added%20and%20edited%20frequently%2C%20it%20is%20not%20practical%20to%20put%20them%20in%20SQL.%20What%20is%20a%20better%20way%20to%20share%20these%20databases%3F%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-1512187%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EAzure%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1555855%22%20slang%3D%22en-US%22%3ERe%3A%20Sharing%20Files%20between%20VMs%20in%20Same%20Resource%20Group%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1555855%22%20slang%3D%22en-US%22%3E%3CP%3EHi%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F430862%22%20target%3D%22_blank%22%3E%40WalterWood44%3C%2FA%3E%26nbsp%3B%2C%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThere%20are%20several%20options%20available%20in%20the%20Azure%20Marketplace%20for%20providing%20an%20File%20Service%20to%20VMs%2C%20two%20are%20Microsoft-provided%20(Azure%20Files%20and%20Azure%20NetApp%20Files)%20and%20the%20rest%20is%20from%20Third%20Parties.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EConsidering%20your%20scenario%2C%20Azure%20NetApp%20Files%20would%20a%20complete%20overkill%20for%20you%20(due%20to%20the%20minimum%20volume%20size%20and%20pricing).%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EAzure%20Files%20are%20still%20the%20best%20alternative%2C%20in%20my%20opinion.%20You%20could%20%3CSTRONG%3Econsider%20trying%20two%20options%20to%20improve%20performance%3C%2FSTRONG%3E%20(can%20be%20applied%20together%20as%20well)%3A%3C%2FP%3E%3CP%3E-%20use%20the%20Premium%20SKU%20-%20AzureFiles%20storage%20account%20(backed%20by%20SSD%20disks)%3C%2FP%3E%3CP%3E-%20enable%20Private%20Endpoint%20from%20that%20storage%20account%20to%20your%20VNet%20with%20the%20VMs%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EJust%20for%20sake%20of%20completion%2C%20there%20is%20%3CSTRONG%3Eanother%20possibility%3C%2FSTRONG%3E%3A%20Deploy%20a%20Windows%20VM%20with%20File%20Server%20role%2C%20connect%20it%20to%20the%20same%20network%2C%20and%20host%20your%20Access%20files%20there.%20You%20could%20chose%20Premium%20managed%20disks%20for%20the%20File%20Server.%20There%20can%20be%20several%20factors%20affecting%20performance%3A%3C%2FP%3E%3CUL%3E%3CLI%3EVM%20SKUs%20of%20those%20Win10%20machines%20(it%20has%20also%20impact%20on%20network%20throughput)%3C%2FLI%3E%3CLI%3Eunderlying%20storage%20performance%20(hence%20my%20advice%20to%20try%20with%20Premium%20storage%20account%20and%2For%20Disks)%3C%2FLI%3E%3CLI%3Ephysical%20location%20of%20the%20VMs%3A%20in%20regions%20supporting%20Availability%20Zones%2C%20it%20would%20be%20better%20to%20deploy%20the%20VMs%20in%20the%20same%20zone.%20In%20this%20way%20you%20can%20get%20your%20VMs%20%22closer%22%20but%20you%20need%20to%20consider%20high-availability%20of%20this%20design.%20As%20an%20extra%20option%2C%20you%20could%20consider%20using%20'Proximity%20Placement%20Groups'%20to%20ensure%20these%20VMs%20are%20hosted%20very%20close%20to%20each%20other.%3C%2FLI%3E%3C%2FUL%3E%3CP%3EHope%20this%20helps.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1556025%22%20slang%3D%22en-US%22%3ERe%3A%20Sharing%20Files%20between%20VMs%20in%20Same%20Resource%20Group%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1556025%22%20slang%3D%22en-US%22%3E%3CP%3EIMO%2C%20your%20best%20shot%20(and%20the%20simplest%20option)%20is%20an%20SMB%203.0%20file%20share%20where%20Azure%20Storage%20Account%20serves%20as%20a%20common%20denominator.%20More%20details%20-ERR%3AREF-NOT-FOUND-here.%3C%2FP%3E%3C%2FLINGO-BODY%3E
Highlighted
Occasional Contributor

We have two Azure Windows 10 VMs setup on the same resource group and they both need access to the same small  Access databases. MS Access on each VM will be used for the front end connect to these files. I setup a File Share in Blob Storage in this same RG and mapped it to a drive in each VM. While this works, it is slow. Since there are multiple databases, and they are added and edited frequently, it is not practical to put them in SQL. What is a better way to share these databases? 

2 Replies
Highlighted

Hi @WalterWood44 ,

 

There are several options available in the Azure Marketplace for providing an File Service to VMs, two are Microsoft-provided (Azure Files and Azure NetApp Files) and the rest is from Third Parties.

 

Considering your scenario, Azure NetApp Files would a complete overkill for you (due to the minimum volume size and pricing).

 

Azure Files are still the best alternative, in my opinion. You could consider trying two options to improve performance (can be applied together as well):

- use the Premium SKU - AzureFiles storage account (backed by SSD disks)

- enable Private Endpoint from that storage account to your VNet with the VMs

 

Just for sake of completion, there is another possibility: Deploy a Windows VM with File Server role, connect it to the same network, and host your Access files there. You could chose Premium managed disks for the File Server. There can be several factors affecting performance:

  • VM SKUs of those Win10 machines (it has also impact on network throughput)
  • underlying storage performance (hence my advice to try with Premium storage account and/or Disks)
  • physical location of the VMs: in regions supporting Availability Zones, it would be better to deploy the VMs in the same zone. In this way you can get your VMs "closer" but you need to consider high-availability of this design. As an extra option, you could consider using 'Proximity Placement Groups' to ensure these VMs are hosted very close to each other.

Hope this helps.

Highlighted

IMO, your best shot (and the simplest option) is an SMB 3.0 file share where Azure Storage Account serves as a common denominator. More details here.