locked
Requirements File-Server for WAP RRS feed

  • Question

  • Hello!

    I'm looking for some help regarding fileserver requirements for WAP. The documentation is unclear regarding this document:

    technet.microsoft.com/en-us/LIBRary/dn469315.aspx   (please copy/paste)

    It says: "a production environment usually requires a more robust solution such as a Windows File Server Cluster or third-party Network Attached Storage device (NAS). Windows Azure Pack: Web Sites uses does not depend on per-web site file share permissions, which enables it to work with heterogeneous file storage implementations such as NAS devices."

    And then: "Windows Azure Pack: Web Sites relies on File Server Resource Manager (FSRM), which does not support scale-out file servers."

    So why is a NAS supported and not a scale-out fileserver? I doubt that fsrm is supported on any nas server...

    As I understand is that FSRM used on both sides, on the Web-Roles AND the Fileserver (Cluster). This means that at the end of the day, only a Windows File Server Cluster is supported as HA solution?

    thanks for help!

    chr.

    Monday, January 19, 2015 7:05 PM

Answers

  • The Windows File Server Cluster is the only Windows HA solution for storing websites content for Azure Pack Websites. The FSRM quotas are stored in the volume and in the cluster scenario, this volume is shared across the servers of the cluster.

    The following file server technologies are not supported for Azure Pack Websites:

    1. Scale-out file server
      Scale-out file server has no support for FSRM which we use for quotas.
    2. DFS-namespace and DFS-Replication
      DFS-R does not synchronize FSRM quotas across file servers.

    However you can host the websites content in a NAS device if:

    1. Your NAS device has a way to set quotas programmatically and the quotas can be defined for each folder and not just at the share level.
    2. You will need to modify the following powershell scripts for Azure Pack to set quotas with your NAS device:
    • set-directoryquota.ps1
    • get-directoryquota.ps1

    In other words, Azure Pack has no out of the box support for NAS devices but it is extensible to enable this scenario.

    Regarding scale-out file servers, in Virtual Machine Manager it is common to use scale-out file servers as infrastructure storage to store VHDs and it is possible to deploy a guest cluster (virtual cluster) in which you can deploy the file server cluster for Azure Pack Websites.

    Monday, January 19, 2015 10:44 PM

All replies

  • The Windows File Server Cluster is the only Windows HA solution for storing websites content for Azure Pack Websites. The FSRM quotas are stored in the volume and in the cluster scenario, this volume is shared across the servers of the cluster.

    The following file server technologies are not supported for Azure Pack Websites:

    1. Scale-out file server
      Scale-out file server has no support for FSRM which we use for quotas.
    2. DFS-namespace and DFS-Replication
      DFS-R does not synchronize FSRM quotas across file servers.

    However you can host the websites content in a NAS device if:

    1. Your NAS device has a way to set quotas programmatically and the quotas can be defined for each folder and not just at the share level.
    2. You will need to modify the following powershell scripts for Azure Pack to set quotas with your NAS device:
    • set-directoryquota.ps1
    • get-directoryquota.ps1

    In other words, Azure Pack has no out of the box support for NAS devices but it is extensible to enable this scenario.

    Regarding scale-out file servers, in Virtual Machine Manager it is common to use scale-out file servers as infrastructure storage to store VHDs and it is possible to deploy a guest cluster (virtual cluster) in which you can deploy the file server cluster for Azure Pack Websites.

    Monday, January 19, 2015 10:44 PM
  • Great Answer, thanks!
    Tuesday, January 20, 2015 8:03 AM
  • Hi Kristian,

    We would love to have the ability to use a Scale-out file server in combination with WAP Websites.

    I noticed that this message was posted on the 19th of January, has there perhaps been a change on this yet after the latest update rollups for Websites v2?

    Kind Regards,

    Danny den Braver


    Friday, October 2, 2015 7:53 AM
  • We definitely want to support SOFS and new upcoming file server technologies from Windows Server 10. Additionally, we want to simplify working with NAS devices.

    The main blocker for this new file server technologies is FSRM, so we are working on making changes to enforce the storage quotas inside the Websites sandbox. It may go out in the next update but it is hard to tell at this point.

    Friday, October 2, 2015 8:32 AM
  • Thank you for your quick reply.

    Would it in the meantime be possible to still use a Scale-Out Fileserver, and take it for granted that the Quoting does not work? (for example, create our own work-around for this problem) Or would the Websites Controller simply not accept the fileserver?

    Friday, October 2, 2015 8:40 AM
  • You can try to deploy with the pre-configured file server option using a share backed by SOFS and then change the file server type to external:

    PS C:\> Import-Module Websites
    PS C:\> Set-WebSitesConfig -Type Global -FileServerType External

    This way we will skip calling FSRM to set quotas.

    Note that with this configuration you will be running exposed and one single tenant could potentially fill the shared content share.

    Additionally, you will not see the storage usage information in the portal

    Friday, October 2, 2015 8:56 AM
  • I will change the FileServerType to External in my settings hash during Initialize in our lab and see how it goes, thank you!

    Friday, October 2, 2015 9:17 AM