Configuring Space Reclaiming With Wasabi Cloud NAS
    • 26 Aug 2024
    • 5 Minutes to read
    • PDF

    Configuring Space Reclaiming With Wasabi Cloud NAS

    • PDF

    Article summary

    Aside from turning on Space Reclaiming, to instruct Wasabi Cloud NAS on conditions under which it should replace replicated files on the source(s) with nearline files, you must configure the following parameters:

    Space Reclaiming policy — Wasabi Cloud NAS decides which replicated files to replace with nearline files on the source volume based on two parameters—minimal file size and time interval for which the file has not been accessed. For example, if you set the file size threshold to 10MB and the time interval to 2 weeks, Wasabi Cloud NAS will replace with nearline files all replicated files with size 10MB or above that have not been accessed for at least 2 weeks, leaving on the source volume replicated files whose size is smaller than 10MB and also replicated files with bigger size that have been accessed by a client computer in less than 2 weeks. By default, Wasabi Cloud NAS is set to replace any file, which has not been accessed for more than 4 weeks, regardless of its size.

    Used space thresholds for Space Reclaiming — The default used space threshold is 0% and Space Reclaiming is triggered as soon as any file meets the criteria for replacement with a nearline file. You can increase the used space threshold and let Wasabi Cloud NAS reclaim space only when a given amount of your source is full. You can also specify maximum used space threshold on your sourceit specifies when all files subject to replication are queued for replacement with nearline files regardless of their size and last access time. By default, maximum used space value is set to 90% for all source volumes.

    Wasabi Cloud NAS processes the queue of files scheduled for replacement with nearline files starting from the ones, which are least recently accessed.

    Processes triggering file retrieval — By default, each process, attempting to open a nearline file on the source volume, triggers its retrieval from the bucket. To prevent useless retrieval of nearline files by your antivirus software, for example, you can specify which processes exactly can trigger the file retrieval operation. You can do this by creating either a list of processes allowed to trigger retrieval or by creating a list of processes, which cannot trigger retrieval of nearline files. There is no need to create both lists. In case you create a list of processes allowed to trigger nearline file retrieval from the bucket, any process not included in the list will not trigger the operation when this process attempts to open the file. In case you decide to specify the processes, which are not allowed to trigger file retrieval from the bucket, any process not mentioned in the list will trigger the nearline file retrieval when this process attempts to open that file.

    With a NAS source, nearline files are located in the shadow copy folder and not on the network share. Still, when retrieving them, actual data is retrieved directly on the NAS source. To learn more about Space Reclaiming on NAS sources, refer to NAS Source Prerequisites and Setup.

    You can configure a global Space Reclaiming policy, valid for each pair of source and bucket, which does not have its own Space Reclaiming policy assigned. You can overwrite the global Space Reclaiming policy for a given pair of source and bucket or disable Space Reclaiming for that pair only. When any local policy is DELETED the source is inheriting the global policy. When the reclaim space policy is DISABLED it instructs Wasabi Cloud NAS to NEVER reclaim. This allows you to set up a global policy for all your sources but make sure that one particular source does not reclaim at all.

    Configure the Global Space Reclaiming Policy

    1. Select Wasabi Cloud NAS in the left pane.
    2. Click the Add policy button.
    3. In the Policy Type dialog, select Reclaim space and click OK.
    4. In the right pane, specify the parameters for file access time and size as well as for used space thresholds.


    5. Click Apply.

    The global Space Reclaiming policy is valid for all sources that do not have their own policy assigned. To edit the global policy, simply select it in the left pane, edit the desired parameter and click Apply. To delete the global policy, select it in the left pane and click the Delete policy button.

    By default, all automatic Wasabi Cloud NAS operations are initially paused. To resume them, follow the steps in Pausing/Resuming Automatic Wasabi Cloud NAS Operations.

    Overwriting the Global Space Reclaiming Policy for a Specific Source

    1. Select the source in the left pane.
    2. Click the Add policy button.
    3. In the Policy Type dialog, select Reclaim space and click OK.
      If the selected source already has its own Space Reclaiming policy assigned, you cannot add a new Space Reclaiming policy. You can edit the existing policy, following the steps below.
    4. In the right pane, make sure the Enabled check box is selected and specify the parameters for file access time and size as well as for used space thresholds.
    5. Click Apply.

    TIP: To make the source use the global Space Reclaiming policy set for all sources, delete the Space Reclaiming policy by selecting it in the left pane and clicking the Delete Policy button. If you do not want the source space reclaiming at all, disable the policy by clearing the Enabled check box in the right pane.

    By default, all automatic Wasabi Cloud NAS operations are initially paused. To resume them, follow the steps in Pausing/Resuming Automatic Wasabi Cloud NAS Operations.

    Configuring the Processes

    To configure the processes, which can or cannot trigger retrieval of files from the bucket:

    1. In the left pane, click Global Settings.
    2. Click the Process filtering button toward the bottom of the right pane.
    3. In the Process Filtering dialog, do one of the following:
      • Enter the name of a process in either the list of processes allowed to trigger the retrieving of nearline files or in the list of processes forbidden to trigger the retrieving of nearline files. Then, click OK.
        TIP: Click the + button on top of each list to place the cursor at the end of each respective list.
      • Delete a process from either list. Then, click OK.
        TIP: Click the – button on top of each list to remove the last process of the respective list.

    4. Click Apply.



    ESC

    Eddy AI, facilitating knowledge discovery through conversational intelligence