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
Enabling WORM on storage snapshots
You can enable WORM on storage snapshots which are created on WORM enabled filesystem to make the snapshot data unmodifiable. WORM storage snapshot allows you to retain the snapshot data in read-only form for a specified period for security or governance purposes. The retention period for a WORM storage snapshot specifies the time period for which the snapshot must be retained. The snapshot can be deleted after the retention period has expired. To protect the snapshot data from ransomware attack, you must keep the snapshots in read-only state. You cannot perform write operations to the storage snapshot.
Considerations for enabling WORM on snapshots:
This feature is supported only in Compliance and Enterprise lockdown mode.
The retention period is based on the compliance clock. The minimum retention period is 1 day and the maximum period is 2038-01-19.
You can extend the retention period in Compliance and Enterprise mode, but retention period can be reduced only in Enterprise mode.
You cannot set the retention period on a snapshot if snapshot is not WORM-enabled.
Snapshots which are WORM-enabled cannot be online/mounted in read-write mode.
Snapshots with active retention period cannot be destroyed. You can set WORM and retention period to existing snapshots. Snapshots which are created on WORM enabled file system cannot be restored.
You can create and modify snapshot schedules if WORM is enabled and retention period is set.
The schedule destroyall command does not destroy snapshots which have active retention period.
To enable WORM on a snapshot
- To enable WORM on an existing non-WORM snapshot, enter the following:
Storage> snapshot worm set snapshot_name fs_name
snapshot_name
Specifies the name for the snapshot.
fs_name
Specifies the name for the file system.
To set the retention period on a snapshot
- To set retention period on WORM-enabled snapshot, enter the following:
Storage> snapshot retention set snapshot_name fs_name retention_period
snapshot_name
Specifies the name for the snapshot.
fs_name
Specifies the name for the file system.
retention_period
Specifies the retention period. The format can be [1-9](d|D|m|M|y|Y) or yyyy-mm-dd.
You can also extend the retention period or set a retention date in the past using this command.