Worm file system

The file systems created in a batch have the same capacity. NOTE: If this option is not selected, the suffix number starts at by default. NOTE: For example, if you want to create 30 file systems, the start number is from 0 to Select a security style based on service requirements.

The security style defines the access control mechanism of the file system accessible through multiple protocols. The default Windows user must be an existing local authentication user or AD domain user. This parameter applies to VRC60 and later versions. For files beyond the Retention, common users and system administrators cannot modify or rename, but can delete them.

For file systems containing files within the Retention, system administrators cannot delete the file systems. For file systems containing files that are all beyond the Retention, system administrators can delete the file systems. Enterprise compliance: For files within the Retention, common users and system administrators cannot modify, delete, or rename them. For file systems with the enterprise compliance property, system administrators can delete the file systems whatever files in the file systems are within or beyond the Retention.

NOTE: The maximum retention period cannot be 0. NOTE: Write operation include file data change or metadata change. NOTE: Before enabling this function, ensure that files do not need protection and can be automatically deleted by the system after they expire. Follow-up Procedure If the automatic lock function of the WORM file system is not enabled, you must enable files in the file system to enter the protection state. If the automatic lock function is enabled for the WORM file system, you can also enable the files to enter the protection state manually within a specific period of time Lockout Wait Time since a change based on service requirements.

If the automatic deletion function is not enabled for the WORM file system and you want to delete a file, you must manually delete it. For details about operations, see 4. When thin provisioning is enabled, the capacity is the maximum capacity allocated to the thin file system.

That is, the total capacity dynamically allocated to the file system cannot exceed the maximum capacity. When thin provisioning is disabled, the capacity will be allocated to a thick file system once and for all. The system supports the creation of block-level file systems. To create such a file system, select capacity unit Blocks. One block is equal to bytes.

Thin file system: The maximum capacity can exceed the available capacity of the storage pool where the thin file system resides but must fall into the range of 1 GB to TB. Application scenarios of file systems, which include: VM : After this scenario is selected, the system will set the file system block size to 8 KB, and automatically adjust system resources to adapt to this scenario.

Database : In this scenario, y ou are advised to select a storage pool containing only SSDs for the file system and enable the data compression function. When the storage pool to which a file system belongs contains only SSDs , the system will set the file system block size to 16 KB and enable the data compression function by default. In this scenario, you are advised to enable the data compression function.

If the time value is increased, the WORM clock of each file system can be corrected forward for at most s one hour, which shortens the file protection period. All rights reserved. Huawei Enterprise Support Community.

User Guide New to the community? Find out how to get started! Stay connected! Choose the types of newsletters you want to receive! Community Forums Storage. WORM file system global s The following problems are raised: Is that normal or abnormal? Q: Is this normal or abnormal? Q: Does the function be affected? How can I fix the problem or do not need to be rectified? Q: What is the impact if the global security regulation clock is damaged?

To set the retention period to permanent retention, set the access time to its largest possible value: In this example, the retention period is extended to Aug 18, at AM, which is 26 minutes from the time the WORM trigger was initially applied. Use the sls command to view WORM file attributes. Use this option on a file to display when the retention period began, when it will end, the current retention state, and the duration as specified on the command line.

In this example, the retention state is active, as shown by the retention: active designation, meaning that the file has the WORM bit set. The retention period started on August 18, , at and will end on August 18, , at The retention period was specified to be 0 years, 0 days, 0 hours, and 6 minutes.

Use the sfind utility to search for files that have certain retention periods. The following options are available:. The time is specified as MyNdOhPm , where M, N, O, , and P are arbitrary non-negative integers and y, d, h ,and m represent the number of years, days, hours, and minutes, respectively. For example, the following command finds files for which more than 1 year, 10 days, 5 hours, and 10 minutes remain before expiration. The time is specified as MyNdOhPm , where M, N, O , and P are arbitrary non-negative integers and y, d, h , and m represent the number of years, days, hours, and minutes, respectively.

For example, the following command finds files that have retention periods longer than 10 days. Search Scope:. Document Information Preface 1.

File System Overview 2. About the Master Configuration File 3. Configuring the File System 5. Configuring a Shared File System 6. Administering File System Quotas 7. Advanced File System Topics 8. The system administrator is allowed to delete files before retention expiration and reduce the file retention period. File data and path integrity remain immutable. The WORM bit is set by changing a directory or file from writeable to read-only.

All rights reserved. Ratio of the file system snapshot space to the file system space. Snapshot space cannot be used to store service data of the source file system.

To avoid a waste of storage space, it is advised to contact Huawei technical support to set this parameter to a proper value. For details about the file system snapshot feature, see the HyperSnap feature guide for file specific to your product model and version. An integer ranging from 0 to Application Scenario.

Application scenarios of file systems, which include:. VM , Database , or User-defined. File System Block Size. This parameter is displayed only when Application Scenario is set to User-defined. Data in a file system consists of blocks. The size of the blocks also known as file system block size affects disk space usage and performance.

You are advised to configure the block size following the principles below:. Number of file systems to be created in batches. Set this parameter based on your needs. Manually specify the suffix. When creating multiple file systems, the system automatically adds a suffix number to the name of each file system for file system distinction.

You can manually set the start suffix number after selecting this option. If this option is not selected, the suffix number starts at by default. Start Number. This parameter is valid after Manually specify the suffix is selected. From the start number you configured, the system adds an increasing suffix number to the name of each file system to distinguish the file system. For example, if you want to create 30 file systems, the start number is from 0 to Security Style. The latest configured permissions prevail.

This parameter applies to VRC50 and later versions. Click Advanced. The Advanced dialog box is displayed. Table describes the related parameters. This parameter cannot be modified.