Veritas Access Appliance Administrator's Guide
- Section I. Introducing Access Appliance
- Section II. Configuring Access Appliance
- Managing users
- 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
- About managing local users and groups
- Using Access Appliance as an Object Store server
- Configuring the NFS server
- Section V. Managing Access Appliance security
- Section VI. Monitoring and troubleshooting
- Configuring event notifications and audit logs
- About alert management
- Appliance log files
- Configuring event notifications and audit logs
- 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
- Episodic replication job failover and failback
- Configuring continuous replication
- How Access Appliance continuous replication works
- Continuous replication failover and failback
- Using snapshots
- Using instant rollbacks
- Configuring episodic replication
- Section X. Reference
Setting retention in files
The retention feature provides a way to ensure that the files are not deleted or modified until the retention period is applied on the files. You can set and show the retention period on files from the Access command-line interface.
The file system should be created with worm=yes option to use the retention feature. See the Storage> fs create man page for more information.
To set retention:
Storage> fs retention set [path] [retention_period]
Where path is the specified file or directory on which retention is set. If the specified path is a directory, then retention is set on all the files that are currently present in the directory.
retention_period is the duration for which retention is set. It can be in [1-9](s|S|h|H|d|D|m|M|y|Y) or mm-dd-yyyy or mm-dd-yyyy:hh:mm:ss format.
The retention period cannot be reduced once it is set.
The retention period range is between 1 hour and 60 years. The retention period can be in hour(s), day(s), month(s), or year(s) if you use CLISH. The retention period can be in second(s), hour(s), day(s), month(s), or year(s) if you use the GUI. The retention period of a file should be within the minimum and maximum retention period of the WORM-enabled file system, share or bucket within which the file is present.
Note:
The retention period in Access Appliance is based on the file system compliance clock and not based on the system clock.
To show retention:
Storage> fs retention show [path]
Where path is the specified file on which retention is set.
In Enterprise lockdown mode, if retention period is given as 0, retention is removed on the specified file. You can also extend the retention period on a file by specifying a value which is greater than the currently set retention period on a file.
See the Storage> fs man page for detailed examples.
You can set retention on a file system using the Access Appliance GUI.