You can control how files in the cloud storage are recalled automatically to the source NSS volume. When a file is migrated to cloud storage and replaced with a CBV file on the source NSS volume, the CBV file should look and behave like the original file. The size on the disk for the CBV file will be in KBs. File recall is the process by which the user clicks the CBV file and quickly accesses the original file available in the cloud storage.
The CBV file contains the information required to find the original file. When a user attempts to read the CBV file, NSS sends a recall request to CIS, which then executes the recall and passes the file to the NSS.
Table 10-1 describes use cases for recalling files based on the user access.
Table 10-1 Recall Behaviors for Files in the Cloud
|
Source NSS Volume |
Cloud Storage |
|---|---|---|
|
When the file is modified |
The file gets recalled from the cloud storage and will be available for the duration based on the value configured in the MOVE_ON_MODIFY_DURATION parameter. After that duration, the file retains in the NSS volume. |
A copy of the file is available on the cloud for the duration based on the value configured in the MOVE_ON_MODIFY_DURATION parameter. After that duration, the file copy gets deleted, and it is no longer available. |
|
When the file is accessed but not modified |
The file gets recalled from the cloud storage and will be available for the duration based on the value configured in the MOVE_ON_MODIFY_DURATION parameter. After that duration, a new CBV file is created, and the recalled file gets deleted to free up space. |
A copy of the file is available on the cloud for the duration based on the value configured in the MOVE_ON_MODIFY_DURATION parameter. After that duration, the file copy retains in the cloud. |
The recalled files are available on both the source NSS volume and cloud storage for a specific time duration based on the value configured in the MOVE_ON_MODIFY_DURATION parameter. To modify this time duration, perform the following on the CIS server:
Open a terminal console, then log in as a root user.
Go to the /etc/opt/novell/cis/config file and configure the MOVE_ON_MODIFY_DURATION parameter with the required time duration. The default value is 3 days. The available range is 1 to 3 days.
For example:
MOVE_ON_MODIFY_DURATION=1
Restart the metadata service.
systemctl restart oes-cis-metadata.service