Azure NetApp Files for NFS storage with Moodle

Published Apr 29 2021 08:47 PM 2,414 Views
Microsoft

I received this great content from our partner team at NetApp. I felt it will be good to post this as Moodle is a very popular platform, and widely used all over the globe.

Thanks for your great contribution :

 

Moodle is one of the most popular and widely adopted free, open-source learning management systems written in PHP. Acquiring more than 30% market share globally, there are more than 180,000 Moodle customers worldwide. Moodle customers vary across industry verticals spanning Education Institutions, Enterprises, IT companies, FSI Institutions, etc.

Azure NetApp Files is an Azure service for migration and running the most demanding enterprise file-workloads in the cloud: native SMBv3.0 and NFS(v3.0 and v4.1) file shares, databases, SAP, and high-performance computing applications, with no code, changes.

Moodle architecture relies on NFS storage for content storage.

askha_1_0-1619586964929.png

With Azure NetApp Files, we can set up native NFS v3 or NFS v4.1 volume. Steps for the same are listed here:

Pre-requisites

 

  • You need to have access to Azure portal and active subscription to provision resources
  • You must have already set up a capacity pool.
  • A subnet must be delegated to Azure NetApp Files.
  • The NFS client should be in the same VNet or peered VNet as the Azure NetApp Files volume. Connecting from outside the VNet is supported; however, it will introduce additional latency and decrease overall performance.
  • Ensure that the NFS client is up-to-date and running the latest updates for the operating system.

Create an Azure NFS volume

  1. Click the Volumes blade from the Capacity Pools blade. Click + Add volume to create a volume.
    askha_1_1-1619588261701.png
    1. In the Create a Volume window, click Create, and provide information for the following fields under the Basics tab:
      • Volume name
        Specify the name for the volume that you are creating.
  2. A volume name must be unique within each capacity pool. It must be at least three characters long. You can use any alphanumeric characters.

    You cannot use default or bin as the volume name.

    • Capacity pool
      Specify the capacity pool where you want the volume to be created.
    • Quota
      Specify the amount of logical storage that is allocated to the volume.

    The Available quota field shows the amount of unused space in the chosen capacity pool that you can use towards creating a new volume. The size of the new volume must not exceed the available quota.

    • Throughput (MiB/S)
      If the volume is created in a manual QoS capacity pool, specify the throughput you want for the volume.

    If the volume is created in an auto QoS capacity pool, the value displayed in this field is (quota x service level throughput).

    • Virtual network
      Specify the Azure virtual network (VNet) from which you want to access the volume.

    The VNet you specify must have a subnet delegated to Azure NetApp Files. The Azure NetApp Files service can be accessed only from the same VNet or from a VNet that is in the same region as the volume through VNet peering. You can also access the volume from your on-premises network through Express Route.

    • Subnet
      Specify the subnet that you want to use for the volume.
      The subnet you specify must be delegated to Azure NetApp Files.
      askha_1_2-1619588493274.png

      If you have not delegated a subnet, you can click Create new on the Create a Volume page. Then in the Create Subnet page, specify the subnet information, and select Microsoft.NetApp/volumes to delegate the subnet for Azure NetApp Files. In each VNet, only one subnet can be delegated to Azure NetApp Files

      askha_1_5-1619588600013.png
  3.  Click Protocol, and then complete the following actions:
    • Select NFS as the protocol type for the volume.
    • Specify the file path that will be used to create the export path for the new volume. The export path is used to mount and access the volume.
      The file path name can contain letters, numbers, and hyphens ("-") only. It must be between 16 and 40 characters in length. The file path must be unique within each subscription and each region
    askha_1_6-1619588651708.png
    1. Click Review + Create to review the volume details. Then click Create to create the volume.
  4. The volume you created appears in the Volumes page.

    Azure NetApp Files NFS v3 volumes support NFS multipathing with nconnect in many Linux Client OS. For Best performance, it is recommended to size the VM SKUs correctly to support Azure accelerated networking and nconnect while deploying VMs in the Scale-Set, in addition to checking guest OS support for nconnect.  

    Instructions for mounting ANF NFS volumes on Moodle application server(s) are as below:

    You can mount or unmount a volume for Windows or Linux virtual machines as necessary. The mount instructions for Linux virtual machines are available on Azure NetApp Files:

    Requirements

    • You must have at least one export policy to be able to access an NFS volume.
    • To mount an NFS volume successfully, ensure that the following NFS ports are open between the client and the NFS volumes:
    • 111 TCP/UDP = RPCBIND/Portmapper
    • 635 TCP/UDP = mountd
    • 2049 TCP/UDP = nfs
    • 4045 TCP/UDP = nlockmgr (NFSv3 only)
    • 4046 TCP/UDP = status (NFSv3 only)

    Steps

    1. Click the Volumes blade, and then select the volume for which you want to mount.
    2. Click Mount instructions from the selected volume, and then follow the instructions to mount the volume.
      askha_1_8-1619588866790.png

       

      • If you are mounting an NFS volume, ensure that you use the vers option in the mount command to specify the NFS protocol version that corresponds to the volume you want to mount.
      • If you are using NFSv4.1, use the following command to mount your file system: sudo mount -t nfs -o rw,hard,rsize=65536,wsize=65536,vers=4.1,tcp,sec=sys $MOUNTTARGETIPADDRESS:/$VOLUMENAME $MOUNTPOINT

       

      Note

      If you use NFSv4.1, ensure that all VMs mounting the export use unique hostnames.

    3. If you want to have an NFS volume automatically mounted when an Azure VM is started or rebooted, add an entry to the /etc/fstab file on the host.

      For example: $ANFIP:/$FILEPATH /$MOUNTPOINT nfs bg,rw,hard,noatime,nolock,rsize=65536,wsize=65536,vers=3,tcp,_netdev 0 0

      • $ANFIP is the IP address of the Azure NetApp Files volume found in the volume properties blade.
      • $FILEPATH is the export path of the Azure NetApp Files volume.
      • $MOUNTPOINT is the directory created on the Linux host used to mount the NFS export.
      NFS storage with Moodle application typically hosts a large number of files and folders. Azure NetApp Files snapshot capabilities can be very useful with quick recovery of these files or folders or entire volumes or revert the entire volume from snapshot state. 
1 Comment
Microsoft

Thanks for sharing this guidance with tech community @askha_1, looking forward to our collaboration for other use cases. 

%3CLINGO-SUB%20id%3D%22lingo-sub-2309259%22%20slang%3D%22en-US%22%3ERe%3A%20Azure%20NetApp%20Files%20for%20NFS%20storage%20with%20Moodle%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2309259%22%20slang%3D%22en-US%22%3E%3CP%3EThanks%20for%20sharing%20this%20guidance%20with%20tech%20community%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F599480%22%20target%3D%22_blank%22%3E%40askha_1%3C%2FA%3E%2C%20looking%20forward%20to%20our%20collaboration%20for%20other%20use%20cases.%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2300630%22%20slang%3D%22en-US%22%3EAzure%20NetApp%20Files%20for%20NFS%20storage%20with%20Moodle%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2300630%22%20slang%3D%22en-US%22%3E%3CP%3EI%20received%20this%20great%20content%20from%20our%20partner%20team%20at%20NetApp.%20I%20felt%20it%20will%20be%20good%20to%20post%20this%20as%20Moodle%20is%20a%20very%20popular%20platform%2C%20and%20widely%20used%20all%20over%20the%20globe.%3C%2FP%3E%0A%3CP%3EThanks%20for%20your%20great%20contribution%20%3A%3C%2FP%3E%0A%3CUL%3E%0A%3CLI%3E%3CA%20href%3D%22https%3A%2F%2Fwww.linkedin.com%2Fin%2Ftarun-arora%2F%22%20target%3D%22_self%22%20rel%3D%22nofollow%20noopener%20noreferrer%22%3ETarun%20Arora%3C%2FA%3E%3CBR%20%2F%3E%3CA%20href%3D%22https%3A%2F%2Fwww.linkedin.com%2Fin%2Ftarun-arora%2F%22%20target%3D%22_self%22%20rel%3D%22nofollow%20noopener%20noreferrer%22%3EPrincipal%20Cloud%20Solutions%20Architect%20at%20NetApp%3C%2FA%3E%3C%2FLI%3E%0A%3CLI%3E%3CA%20href%3D%22https%3A%2F%2Fwww.linkedin.com%2Fin%2Frizul-khanna-a3b08139%2F%22%20target%3D%22_self%22%20rel%3D%22nofollow%20noopener%20noreferrer%22%3ERizul%20Khanna%3C%2FA%3E%3CBR%20%2F%3E%3CA%20href%3D%22https%3A%2F%2Fwww.linkedin.com%2Fin%2Frizul-khanna-a3b08139%2F%22%20target%3D%22_self%22%20rel%3D%22nofollow%20noopener%20noreferrer%22%3EEMEA%20Azure%20Cloud%20Architect%20-%20NetApp%3C%2FA%3E%3C%2FLI%3E%0A%3C%2FUL%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EMoodle%20is%20one%20of%20the%20most%20popular%20and%20widely%20adopted%20free%2C%20open-source%20learning%20management%20systems%20written%20in%20PHP.%20Acquiring%20more%20than%2030%25%20market%20share%20globally%2C%20there%20are%20more%20than%20180%2C000%20Moodle%20customers%20worldwide.%20Moodle%20customers%20vary%20across%20industry%20verticals%20spanning%20Education%20Institutions%2C%20Enterprises%2C%20IT%20companies%2C%20FSI%20Institutions%2C%20etc.%3C%2FP%3E%0A%3CP%3E%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fazure%2Fazure-netapp-files%2Fazure-netapp-files-introduction%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3EAzure%20NetApp%20Files%3C%2FA%3E%26nbsp%3Bis%20an%20Azure%20service%20for%20migration%20and%20running%20the%20most%20demanding%20enterprise%20file-workloads%20in%20the%20cloud%3A%20native%20SMBv3.0%20and%20NFS(v3.0%20and%20v4.1)%20file%20shares%2C%20databases%2C%20SAP%2C%20and%20high-performance%20computing%20applications%2C%20with%20no%20code%2C%20changes.%3C%2FP%3E%0A%3CP%3EMoodle%20architecture%20relies%20on%20NFS%20storage%20for%20content%20storage.%3C%2FP%3E%0A%3CP%20class%3D%22lia-indent-padding-left-150px%22%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20image-alt%3D%22askha_1_0-1619586964929.png%22%20style%3D%22width%3A%20400px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F276167i63F83009CBB23AFF%2Fimage-size%2Fmedium%3Fv%3Dv2%26amp%3Bpx%3D400%22%20role%3D%22button%22%20title%3D%22askha_1_0-1619586964929.png%22%20alt%3D%22askha_1_0-1619586964929.png%22%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%0A%3CP%3EWith%20Azure%20NetApp%20Files%2C%20we%20can%20set%20up%20native%20NFS%20v3%20or%20NFS%20v4.1%20volume.%20Steps%20for%20the%20same%20are%20listed%20here%3A%3C%2FP%3E%0A%3CP%3E%3CSTRONG%3EPre-requisites%3C%2FSTRONG%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CUL%3E%0A%3CLI%3EYou%20need%20to%20have%20access%20to%20Azure%20portal%20and%20active%20subscription%20to%20provision%20resources%3C%2FLI%3E%0A%3CLI%3EYou%20must%20have%20already%20set%20up%20a%20capacity%20pool.%3C%2FLI%3E%0A%3CLI%3EA%20subnet%20must%20be%20delegated%20to%20Azure%20NetApp%20Files.%3C%2FLI%3E%0A%3CLI%3EThe%20NFS%20client%20should%20be%20in%20the%20same%20VNet%20or%20peered%20VNet%20as%20the%20Azure%20NetApp%20Files%20volume.%20Connecting%20from%20outside%20the%20VNet%20is%20supported%3B%20however%2C%20it%20will%20introduce%20additional%20latency%20and%20decrease%20overall%20performance.%3C%2FLI%3E%0A%3CLI%3EEnsure%20that%20the%20NFS%20client%20is%20up-to-date%20and%20running%20the%20latest%20updates%20for%20the%20operating%20system.%3C%2FLI%3E%0A%3C%2FUL%3E%0A%3CP%20class%3D%22lia-indent-padding-left-30px%22%3E%3CSTRONG%3ECreate%20an%20Azure%20NFS%20volume%3C%2FSTRONG%3E%3C%2FP%3E%0A%3COL%3E%0A%3CLI%3EClick%20the%26nbsp%3B%3CSTRONG%3EVolumes%3C%2FSTRONG%3E%26nbsp%3Bblade%20from%20the%20Capacity%20Pools%20blade.%20Click%26nbsp%3B%3CSTRONG%3E%2B%20Add%20volume%3C%2FSTRONG%3E%26nbsp%3Bto%20create%20a%20volume.%3CBR%20%2F%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20image-alt%3D%22askha_1_1-1619588261701.png%22%20style%3D%22width%3A%20400px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F276168iC4F6B69CC1F19CBC%2Fimage-size%2Fmedium%3Fv%3Dv2%26amp%3Bpx%3D400%22%20role%3D%22button%22%20title%3D%22askha_1_1-1619588261701.png%22%20alt%3D%22askha_1_1-1619588261701.png%22%20%2F%3E%3C%2FSPAN%3E%3CBR%20%2F%3E%3COL%3E%0A%3CLI%3EIn%20the%20Create%20a%20Volume%20window%2C%20click%26nbsp%3B%3CSTRONG%3ECreate%3C%2FSTRONG%3E%2C%20and%20provide%20information%20for%20the%20following%20fields%20under%20the%20Basics%20tab%3A%3CUL%3E%0A%3CLI%3E%3CSTRONG%3EVolume%20name%3C%2FSTRONG%3E%3CBR%20%2F%3ESpecify%20the%20name%20for%20the%20volume%20that%20you%20are%20creating.%3C%2FLI%3E%0A%3C%2FUL%3E%0A%3C%2FLI%3E%0A%3C%2FOL%3E%0A%3C%2FLI%3E%0A%3CLI%3E%3CP%3EA%20volume%20name%20must%20be%20unique%20within%20each%20capacity%20pool.%20It%20must%20be%20at%20least%20three%20characters%20long.%20You%20can%20use%20any%20alphanumeric%20characters.%3C%2FP%3E%0A%3CP%3EYou%20cannot%20use%26nbsp%3Bdefault%26nbsp%3Bor%26nbsp%3Bbin%26nbsp%3Bas%20the%20volume%20name.%3C%2FP%3E%0A%3CUL%3E%0A%3CLI%3E%3CSTRONG%3ECapacity%20pool%3C%2FSTRONG%3E%3CBR%20%2F%3ESpecify%20the%20capacity%20pool%20where%20you%20want%20the%20volume%20to%20be%20created.%3C%2FLI%3E%0A%3CLI%3E%3CSTRONG%3EQuota%3C%2FSTRONG%3E%3CBR%20%2F%3ESpecify%20the%20amount%20of%20logical%20storage%20that%20is%20allocated%20to%20the%20volume.%3C%2FLI%3E%0A%3C%2FUL%3E%0A%3CP%3EThe%26nbsp%3B%3CSTRONG%3EAvailable%20quota%3C%2FSTRONG%3E%26nbsp%3Bfield%20shows%20the%20amount%20of%20unused%20space%20in%20the%20chosen%20capacity%20pool%20that%20you%20can%20use%20towards%20creating%20a%20new%20volume.%20The%20size%20of%20the%20new%20volume%20must%20not%20exceed%20the%20available%20quota.%3C%2FP%3E%0A%3CUL%3E%0A%3CLI%3E%3CSTRONG%3EThroughput%20(MiB%2FS)%3C%2FSTRONG%3E%3CBR%20%2F%3EIf%20the%20volume%20is%20created%20in%20a%20manual%20QoS%20capacity%20pool%2C%20specify%20the%20throughput%20you%20want%20for%20the%20volume.%3C%2FLI%3E%0A%3C%2FUL%3E%0A%3CP%3EIf%20the%20volume%20is%20created%20in%20an%20auto%20QoS%20capacity%20pool%2C%20the%20value%20displayed%20in%20this%20field%20is%20(quota%20x%20service%20level%20throughput).%3C%2FP%3E%0A%3CUL%3E%0A%3CLI%3E%3CSTRONG%3EVirtual%20network%3C%2FSTRONG%3E%3CBR%20%2F%3ESpecify%20the%20Azure%20virtual%20network%20(VNet)%20from%20which%20you%20want%20to%20access%20the%20volume.%3C%2FLI%3E%0A%3C%2FUL%3E%0A%3CP%3EThe%20VNet%20you%20specify%20must%20have%20a%20subnet%20delegated%20to%20Azure%20NetApp%20Files.%20The%20Azure%20NetApp%20Files%20service%20can%20be%20accessed%20only%20from%20the%20same%20VNet%20or%20from%20a%20VNet%20that%20is%20in%20the%20same%20region%20as%20the%20volume%20through%20VNet%20peering.%20You%20can%20also%20access%20the%20volume%20from%20your%20on-premises%20network%20through%20Express%20Route.%3C%2FP%3E%0A%3CUL%3E%0A%3CLI%3E%3CSTRONG%3ESubnet%3C%2FSTRONG%3E%3CBR%20%2F%3ESpecify%20the%20subnet%20that%20you%20want%20to%20use%20for%20the%20volume.%3CBR%20%2F%3EThe%20subnet%20you%20specify%20must%20be%20delegated%20to%20Azure%20NetApp%20Files.%3CBR%20%2F%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20image-alt%3D%22askha_1_2-1619588493274.png%22%20style%3D%22width%3A%20400px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F276171i6049BEF78137D01A%2Fimage-size%2Fmedium%3Fv%3Dv2%26amp%3Bpx%3D400%22%20role%3D%22button%22%20title%3D%22askha_1_2-1619588493274.png%22%20alt%3D%22askha_1_2-1619588493274.png%22%20%2F%3E%3C%2FSPAN%3E%3CP%3EIf%20you%20have%20not%20delegated%20a%20subnet%2C%20you%20can%20click%26nbsp%3B%3CSTRONG%3ECreate%20new%3C%2FSTRONG%3E%26nbsp%3Bon%20the%20Create%20a%20Volume%20page.%20Then%20in%20the%20Create%20Subnet%20page%2C%20specify%20the%20subnet%20information%2C%20and%20select%26nbsp%3B%3CSTRONG%3EMicrosoft.NetApp%2Fvolumes%3C%2FSTRONG%3E%26nbsp%3Bto%20delegate%20the%20subnet%20for%20Azure%20NetApp%20Files.%20In%20each%20VNet%2C%20only%20one%20subnet%20can%20be%20delegated%20to%20Azure%20NetApp%20Files%3C%2FP%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20image-alt%3D%22askha_1_5-1619588600013.png%22%20style%3D%22width%3A%20400px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F276174i7D5279AAEC81A1E5%2Fimage-size%2Fmedium%3Fv%3Dv2%26amp%3Bpx%3D400%22%20role%3D%22button%22%20title%3D%22askha_1_5-1619588600013.png%22%20alt%3D%22askha_1_5-1619588600013.png%22%20%2F%3E%3C%2FSPAN%3E%3C%2FLI%3E%0A%3C%2FUL%3E%0A%3C%2FLI%3E%0A%3CLI%3E%26nbsp%3BClick%26nbsp%3B%3CSTRONG%3EProtocol%3C%2FSTRONG%3E%2C%20and%20then%20complete%20the%20following%20actions%3A%3CBR%20%2F%3E%3CUL%3E%0A%3CLI%3ESelect%26nbsp%3B%3CSTRONG%3ENFS%3C%2FSTRONG%3E%26nbsp%3Bas%20the%20protocol%20type%20for%20the%20volume.%3C%2FLI%3E%0A%3CLI%3ESpecify%20the%26nbsp%3B%3CSTRONG%3Efile%20path%3C%2FSTRONG%3E%26nbsp%3Bthat%20will%20be%20used%20to%20create%20the%20export%20path%20for%20the%20new%20volume.%20The%20export%20path%20is%20used%20to%20mount%20and%20access%20the%20volume.%3CBR%20%2F%3EThe%20file%20path%20name%20can%20contain%20letters%2C%20numbers%2C%20and%20hyphens%20(%22-%22)%20only.%20It%20must%20be%20between%2016%20and%2040%20characters%20in%20length.%20The%20file%20path%20must%20be%20unique%20within%20each%20subscription%20and%20each%20region%3C%2FLI%3E%0A%3C%2FUL%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20image-alt%3D%22askha_1_6-1619588651708.png%22%20style%3D%22width%3A%20400px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F276175i8C0F38B34309935D%2Fimage-size%2Fmedium%3Fv%3Dv2%26amp%3Bpx%3D400%22%20role%3D%22button%22%20title%3D%22askha_1_6-1619588651708.png%22%20alt%3D%22askha_1_6-1619588651708.png%22%20%2F%3E%3C%2FSPAN%3E%3CBR%20%2F%3E%3COL%3E%0A%3CLI%3EClick%26nbsp%3B%3CSTRONG%3EReview%20%2B%20Create%3C%2FSTRONG%3E%26nbsp%3Bto%20review%20the%20volume%20details.%20Then%20click%26nbsp%3B%3CSTRONG%3ECreate%3C%2FSTRONG%3E%26nbsp%3Bto%20create%20the%20volume.%3C%2FLI%3E%0A%3C%2FOL%3E%0A%3C%2FLI%3E%0A%3CLI%3E%3CP%3EThe%20volume%20you%20created%20appears%20in%20the%20Volumes%20page.%3C%2FP%3E%0A%3CP%3EAzure%20NetApp%20Files%20NFS%20v3%20volumes%20support%20NFS%20multipathing%20with%20nconnect%20in%20many%20Linux%20Client%20OS.%20For%20Best%20performance%2C%20it%20is%20recommended%20to%20size%20the%20VM%20SKUs%20correctly%20to%20support%20Azure%20accelerated%20networking%20and%20nconnect%20while%20deploying%20VMs%20in%20the%20Scale-Set%2C%20in%20addition%20to%20checking%20guest%20OS%20support%20for%20nconnect.%20%26nbsp%3B%3C%2FP%3E%0A%3CP%3EInstructions%20for%20mounting%20ANF%20NFS%20volumes%20on%20Moodle%20application%20server(s)%20are%20as%20below%3A%3C%2FP%3E%0A%3CP%3EYou%20can%20mount%20or%20unmount%20a%20volume%20for%20Windows%20or%20Linux%20virtual%20machines%20as%20necessary.%20The%20mount%20instructions%20for%20Linux%20virtual%20machines%20are%20available%20on%20Azure%20NetApp%20Files%3A%3C%2FP%3E%0A%3CP%3E%3CSTRONG%3ERequirements%3C%2FSTRONG%3E%3C%2FP%3E%0A%3CUL%3E%0A%3CLI%3EYou%20must%20have%20at%20least%20one%20export%20policy%20to%20be%20able%20to%20access%20an%20NFS%20volume.%3C%2FLI%3E%0A%3CLI%3ETo%20mount%20an%20NFS%20volume%20successfully%2C%20ensure%20that%20the%20following%20NFS%20ports%20are%20open%20between%20the%20client%20and%20the%20NFS%20volumes%3A%3C%2FLI%3E%0A%3C%2FUL%3E%0A%3CUL%3E%0A%3CLI%3E111%20TCP%2FUDP%20%3D%26nbsp%3BRPCBIND%2FPortmapper%3C%2FLI%3E%0A%3CLI%3E635%20TCP%2FUDP%20%3D%26nbsp%3Bmountd%3C%2FLI%3E%0A%3CLI%3E2049%20TCP%2FUDP%20%3D%26nbsp%3Bnfs%3C%2FLI%3E%0A%3CLI%3E4045%20TCP%2FUDP%20%3D%26nbsp%3Bnlockmgr%26nbsp%3B(NFSv3%20only)%3C%2FLI%3E%0A%3CLI%3E4046%20TCP%2FUDP%20%3D%26nbsp%3Bstatus%26nbsp%3B(NFSv3%20only)%3C%2FLI%3E%0A%3C%2FUL%3E%0A%3CP%3E%3CSTRONG%3ESteps%3C%2FSTRONG%3E%3C%2FP%3E%0A%3COL%3E%0A%3CLI%3EClick%20the%26nbsp%3B%3CSTRONG%3EVolumes%3C%2FSTRONG%3E%26nbsp%3Bblade%2C%20and%20then%20select%20the%20volume%20for%20which%20you%20want%20to%20mount.%3C%2FLI%3E%0A%3CLI%3EClick%26nbsp%3B%3CSTRONG%3EMount%20instructions%3C%2FSTRONG%3E%26nbsp%3Bfrom%20the%20selected%20volume%2C%20and%20then%20follow%20the%20instructions%20to%20mount%20the%20volume.%3CBR%20%2F%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20image-alt%3D%22askha_1_8-1619588866790.png%22%20style%3D%22width%3A%20400px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F276177i9513FF3975E67D63%2Fimage-size%2Fmedium%3Fv%3Dv2%26amp%3Bpx%3D400%22%20role%3D%22button%22%20title%3D%22askha_1_8-1619588866790.png%22%20alt%3D%22askha_1_8-1619588866790.png%22%20%2F%3E%3C%2FSPAN%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CUL%3E%0A%3CLI%3EIf%20you%20are%20mounting%20an%20NFS%20volume%2C%20ensure%20that%20you%20use%20the%26nbsp%3Bvers%26nbsp%3Boption%20in%20the%26nbsp%3Bmount%26nbsp%3Bcommand%20to%20specify%20the%20NFS%20protocol%20version%20that%20corresponds%20to%20the%20volume%20you%20want%20to%20mount.%3C%2FLI%3E%0A%3CLI%3EIf%20you%20are%20using%20NFSv4.1%2C%20use%20the%20following%20command%20to%20mount%20your%20file%20system%3A%26nbsp%3Bsudo%20mount%20-t%20nfs%20-o%20rw%2Chard%2Crsize%3D65536%2Cwsize%3D65536%2Cvers%3D4.1%2Ctcp%2Csec%3Dsys%20%24MOUNTTARGETIPADDRESS%3A%2F%24VOLUMENAME%20%24MOUNTPOINT%3C%2FLI%3E%0A%3C%2FUL%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%3CSTRONG%3ENote%3C%2FSTRONG%3E%3C%2FP%3E%0A%3CP%3EIf%20you%20use%20NFSv4.1%2C%20ensure%20that%20all%20VMs%20mounting%20the%20export%20use%20unique%20hostnames.%3C%2FP%3E%0A%3C%2FLI%3E%0A%3CLI%3EIf%20you%20want%20to%20have%20an%20NFS%20volume%20automatically%20mounted%20when%20an%20Azure%20VM%20is%20started%20or%20rebooted%2C%20add%20an%20entry%20to%20the%26nbsp%3B%2Fetc%2Ffstab%26nbsp%3Bfile%20on%20the%20host.%3CBR%20%2F%3E%3CP%3EFor%20example%3A%26nbsp%3B%24ANFIP%3A%2F%24FILEPATH%20%2F%24MOUNTPOINT%20nfs%20bg%2Crw%2Chard%2Cnoatime%2Cnolock%2Crsize%3D65536%2Cwsize%3D65536%2Cvers%3D3%2Ctcp%2C_netdev%200%200%3C%2FP%3E%0A%3CUL%3E%0A%3CLI%3E%24ANFIP%26nbsp%3Bis%20the%20IP%20address%20of%20the%20Azure%20NetApp%20Files%20volume%20found%20in%20the%20volume%20properties%20blade.%3C%2FLI%3E%0A%3CLI%3E%24FILEPATH%26nbsp%3Bis%20the%20export%20path%20of%20the%20Azure%20NetApp%20Files%20volume.%3C%2FLI%3E%0A%3CLI%3E%24MOUNTPOINT%26nbsp%3Bis%20the%20directory%20created%20on%20the%20Linux%20host%20used%20to%20mount%20the%20NFS%20export.%3C%2FLI%3E%0A%3C%2FUL%3ENFS%20storage%20with%20Moodle%20application%20typically%20hosts%20a%20large%20number%20of%20files%20and%20folders.%20Azure%20NetApp%20Files%20snapshot%20capabilities%20can%20be%20very%20useful%20with%20quick%20recovery%20of%20these%20files%20or%20folders%20or%20entire%20volumes%20or%20revert%20the%20entire%20volume%20from%20snapshot%20state.%26nbsp%3B%3C%2FLI%3E%0A%3C%2FOL%3E%0A%3C%2FLI%3E%0A%3C%2FOL%3E%3C%2FLINGO-BODY%3E%3CLINGO-TEASER%20id%3D%22lingo-teaser-2300630%22%20slang%3D%22en-US%22%3E%3CDIV%3EWhen%20it%20comes%20to%20storage%20options%20in%20Azure%2C%20customers%20are%20not%20short%20of%20choices.%20In%20case%20NFS%20v3.0%20or%20NFS%204.0%20support%20in%20your%20storage%20subsystem%20is%20crucial%20for%20your%20application%20to%20transition%20to%20cloud%2C%20Azure%20NetApp%20Files%20(ANF)%20is%20definitely%20worth%20considering.%20In%20this%20blog%20post%20we%20will%20explore%20how%20we%20can%20leverage%20ANF%20for%20deploying%20Moodle%20in%20Azure.%3C%2FDIV%3E%3C%2FLINGO-TEASER%3E%3CLINGO-LABS%20id%3D%22lingo-labs-2300630%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EAzure-NetApp-Files-for-NFS-storage-with-Moodle%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E
Co-Authors
Version history
Last update:
‎Apr 28 2021 05:45 PM
Updated by: