Veritas Access Appliance 8.2 Administrator's Guide
- Section I. Introducing Access Appliance
- Section II. Configuring Access Appliance
- Managing users
- Managing licenses
- Configuring the network
- Configuring authentication services
- Configuring user authentication using digital certificates or smart cards
- Section III. Managing Access Appliance storage
- Configuring storage
- Managing disks
- Access Appliance as an iSCSI target
- Configuring storage
- Section IV. Managing Access Appliance file access services
- Configuring the NFS server
- Setting up Kerberos authentication for NFS clients
- Using Access Appliance as a CIFS server
- About configuring CIFS for Active Directory (AD) domain mode
- About setting trusted domains
- About managing home directories
- About CIFS clustering modes
- About migrating CIFS shares and home directories
- Using Access Appliance as an Object Store server
- Configuring the S3 server using GUI
- Configuring the NFS server
- Section V. Managing Access Appliance security
- Managing security
- Setting up FIPS mode
- Configuring STIG
- Setting the banner
- Setting the password policy
- Immutability in Access Appliance
- Deploying certificates on Access Appliance
- Single Sign-On (SSO)
- Configuring multifactor authentication
- Section VI. Monitoring and troubleshooting
- Monitoring the appliance
- Configuring event notifications and audit logs
- About alert management
- Appliance log files
- Section VII. Provisioning and managing Access Appliance file systems
- Creating and maintaining file systems
- Considerations for creating a file system
- About managing application I/O workloads using maximum IOPS settings
- Modifying a file system
- Managing a file system
- Creating and maintaining file systems
- Section VIII. Provisioning and managing Access Appliance shares
- Creating shares for applications
- Creating and maintaining NFS shares
- About the NFS shares
- Creating and maintaining CIFS shares
- About the CIFS shares
- About managing CIFS shares for Enterprise Vault
- Integrating Access Appliance with Data Insight
- Section IX. Managing Access Appliance storage services
- Configuring episodic replication
- Configuring an episodic replication job using the GUI
- Episodic replication job failover and failback
- Configuring continuous replication
- How Access Appliance continuous replication works
- Configuring a continuous replication job using the GUI
- Continuous replication failover and failback
- Using snapshots
- Using instant rollbacks
- Configuring episodic replication
- Section X. Reference
Enabling WORM on a file system
You can enable WORM on a file system using the storage fs worm commands.
storage> fs worm set <fs_name> [minret] [maxret]
Where
fs_name | Specifies the name of the file system |
minret | Specifies the minimum time period of retention. It can contain: [1-9](s|S|h|H|d|D|m|M|y|Y) |
maxret | Specifies the maximum time period of retention. It can contain: [1-9](s|S|h|H|d|D|m|M|y|Y) |
The minimum and maximum retention period of a file system can be increased in the Enterprise and Compliance lockdown mode but it can be decreased only in the Enterprise lockdown mode. The range of the minimum and maximum retention period should be between 1 hour and 60 years.
If the minimum retention and maximum retention values are provided with suffix as M or m, the retention period is converted to seconds using the following the calculations:
Days in a year: 365 Days in a month: 31 Seconds in a day: 24*60*60
You can also check if a particular file system is WORM-enabled.
storage> fs worm get
You cannot rename a folder on a WORM-enabled file system.
Note:
If episodic replication is configured on a file system, the storage fs worm set <fs_name> and storage fs worm set <fs_name> <min_retention> <max_retention> commands are successful on the source cluster only if the destination cluster is reachable and vice-versa. After these commands are successfully executed, WORM is enabled and/or retention is set on the remote cluster as well.
Note:
The storage fs worm set <fs_name> and storage fs worm set <fs_name> <min_retention> <max_retention> commands fail to set WORM on the file system if continuous replication is configured on a file system. If you want to set WORM on the file system, you have to disable continuous replication.
You can enable WORM on a file system using the Access Appliance GUI.