Set Up Local Quotas

  • 2 minute(s) read
Prev Next

Local quotas are assigned per cloud drive folder on the portal and enforced on all the edge filers accessing the folder. When a file is added to the folder on the edge filer, if the folder quota has been exceeded, an error is displayed and the file is not added to the folder.

Note

Setting a local quota on a cloud folder removes any quota set for the folder owner.

You can a file to a folder directly to a portal when the quota has not yet been reached even if the added file caused the quota to be exceeded. After the file has been added, no more files can be added to the portal until files are removed from the folder to until the quota is not exceeded.

You cannot a file to a folder on the edge filer if the added file causes the quota to be exceeded.

A prerequisite to set up local quotas is that the CTERA Messaging Service is enabled on the CTERA Portal.

Note

CLI commands on the portal can be run by the global administrator in the user interface or by logging on to the portal as root via SSH and then accessing telnet to run the command:

  1. Using SSH, log in as root to the CTERA Portal primary server.
  2. Access the telnet interface by entering #telnet 0
  3. At the telnet prompt, input the login command Login <portal-name> admin <GlobalAdminName>
    Where portal-name is any string, such as myportal or a and GlobalAdminName is the actual global administrator username.
  4. At the prompt, enter the password for the global administrator.

For details about running CLI in the portal user interface, see Execute CLI Commands from the Global Administrator User Interface.

CLI commands on the edge filer are run by the administrator in the user interface. For details about running CLI in the edge filer user interface, see Execute CLI Commands from the Administrator User Interface.

Setting up local quotas requires definitions on the CTERA Portal and on each CTERA Edge Filer.

To set up local quotas:

  1. On the CTERA Portal, start the CTERA Messaging Service by running the following CLI: manage-quota-messaging-service start
  2. Restart the primary portal server by runing the command command portal-manage.sh restart
  3. Check the local quota status by running the following CLI: manage-quota-messaging-service status and if the state is RUNNING check that the service is running without any problems by running the following CLI: manage-quota-messaging-service is-healthy
    Note

    The logs of the services are located under /usr/local/lib/ctera/work/logs/services and there is a directory for each of the services.

  4. For each edge filer, connect it to the portal and enable syncing.
  5. Once the edge filer is fully synced, run the following CLI on each edge filer: set /config/cloudsync/enableLocalQuota true
  6. Suspend and unsuspend syncing and run the following CLI command to trigger a full scan:
    exec /config/cloudsync markFolderForScan folderID 0 ignoreOvl true

After the setting up local quota, the folder updates can take over ten minutes.