What is/are: Runtime Architecture: Quotas and File Block

Introduction

This article provides a highlevel view of the runtime architecture of quota and file block policies. Due to differences between devices, specifically the availability and type of APIs delivered by the device or operating system manufacturer, it is necessary for different operational flows to be followed. The sections below show the operations used for different platforms.

NetApp Clustered Data ONTAP, EMC VNX, HDS/HNAS

CDOTVNX Runtime

1. User triggers a file operation on target device.

2. The operating system on the target device queries the policies defined within NSS (internal lock list), determining if the action should be allowed. Operations that are allowed are used to update quota usage levels. Paths are added/removed from the internal lock-list where necessary. Notifications are sent where necessary. A short history of activity is maintained to allow advanced notification options.

3. Operations that are allowed are committed to disk.

 

NetApp 7-Mode

7mode

1. User triggers a file operation on target device.

2. The operating system on the target device queries the policies defined within NSS, (internal lock list) determining if the action should be allowed. Notifications are sent where necessary (denied operations). A short history of activity is maintained to allow advanced notification options.

3. Allowed operations are performed.

4. The CIFS Server on the target device informs NSS that changes have occurred under a specified folder.

5. NSS scans the affected folders to update quota usage levels. Paths are added/ removed from the internal lock-list where necessary. Notifications are triggered where necessary.

 

EMC Isilon, EMC VNXe

IsilonVNXe

1. User triggers a file operation on target device.

2. The operation is performed.

3. The CIFS Server on the target device informs NSS that changes have occurred under a specified folder.

4. NSS scans the affected folders, updates quota usage levels and triggers notifications where necessary.

 

Direct Attached Storage, Storage Area Network

DASSAN

1. User triggers a file operation on target device.

2. The operation passes through the NSS filter driver. If the intended operation would lead to an increase in a locked quota or is in violation of a file block policy, the operation is denied.

3. The CIFS Server on the target device informs NSS that changes have occurred under a specified folder.

4. NSS scans the affected folders, updates quota usage levels and triggers notifications where necessary.

5. An internal lock list, managed by the NSS filter driver, is updated where necessary.

Note that NSS must be installed locally on the target Windows file server. If no local installation is present then NSS will revert to the operational flow described for EMC Isilon, EMC VNXe.

ADDITIONAL RESOURCES

  • KB1752 About: The Concept of NSS Quotas
  • KB3042 What is/are: Communication Channels: Quotas and File Block
  • KB Article: 3040

    Updated: 5/7/2015

    • Category
      • Reference
    • Affected versions
      • NSS 9.5
      • NSS 9.6

    North America HQ

    NORTHERN Parklife, Inc.
    301Edgewater Place, Suite 100
    Wakefield, MA 01880
    USA

    Voice: 781.968.5424
    Fax: 781.968.5301

    salesUS@northern.net

     

    Additional Contact Information

    EMEA & APAC HQ

    NORTHERN Parklife AB
    St. Göransgatan 66
    112 33 Stockholm
    Sweden

    Voice: +46 8 457 50 00

    salesHQ@northern.net

    Northern Parklife



    ©2018 northern parklife

    privacy statement 
    terms of use