Please enter search query.
Search <book_title>...
Veritas Access Appliance 8.3 Release Notes
Last Published:
2024-12-15
Product(s):
Appliances (8.3)
Platform: Veritas 3360,Veritas 3350,Veritas 3340
- Overview of Access Appliance
- About this release
- Changes in this release
- End of life for Wolf Pass server chassis
- Support for single node configuration
- Upgrading the appliance using the UI
- Installing EEBs using the appliance UI
- Improved diagnostic support
- Viewing performance and aggregate usage details on the appliance dashboard
- Unsupported features in this release
- Planned deprecations in future releases
- Supported NetBackup client versions
- Access Appliance simple storage service (S3) APIs
- Software limitations
- Limitations related to CIFS
- Limitations related to installation and upgrade
- Limitation related to cloud tiering
- Limitations related to networking
- Limitations related to Veritas Data Deduplication
- Kernel-based NFS v4 limitations
- File system limitation
- Access Appliance S3 server limitation
- Long-term data retention (LTR) limitations
- Limitation related to replication
- Limitations related to user management
- Known issues
- Access Appliance known issues
- CIFS issues
- CIFS share created on Access Appliance 8.x version may not be accessible if all the virtual IPs are on a VLAN device
- Error message is displayed when the CIFS server is restarted if shares are already configured and the clustering mode is changed to ctdb
- CIFS share add command fails to add share on the target cluster for a filesystem which is used in the configuration of episodic replication
- General issues
- Reimaging the appliance from the SSD device fails if a CD with the ISO image is inserted in the CD-ROM
- User is not logged out from the command-line interface after running the Cluster> stop all command
- User account gets locked on a management or non-management console node
- Addition of a user named 'admin' fails from GUI and CLISH
- Cluster reboot all command shows missing host message
- The displayed proxy server state is inconsistent if the specified proxy server settings are incorrect
- GUI issues
- When provisioning storage, the Access web interface or the command-line interface displays storage capacity in MB, GB, TB, or PB
- GUI stops working after ECA deployment
- GUI stops working if the ECA certificates are not renewed or get revoked
- When an account gets locked because incorrect login attempts were exceeded, log in from GUI fails even though unlock time is exceeded
- Partially uploaded software upgrade package is displayed in the GUI
- Infrastructure issues
- The NetBackup client add-on package is not automatically installed on the node when the node is deleted from the cluster and then added to the cluster again.
- The Access Appliance management console is not available after a node is deleted and the remaining node is restarted
- Add node fails if upgrade is performed from 7.4.2.200 or lower version
- Installation and configuration issues
- MSDP-C issues
- Networking issues
- NFS issues
- ObjectAccess issues
- Replication issues
- STIG issues
- Storage issues
- Rollback refresh fails when running it after running Storage> fs growby or growto commands
- Rollback service group goes in faulted state when respective cache object is full and there is no way to clear the state
- Event messages are not generated when cache objects get full
- When a policy run completes after issuing Storage> fs policy resume, the total data and total files count might not match the moved data and files count as shown in Storage> fs policy status
- Storage> fs addcolumn operation fails but error notification is not sent
- Unable to create space-optimized rollback when tiering is present
- The CVM service group goes in to faulted state after you restart the management console node
- After a cluster reboot, the UI shows that the storage is not configured
- Factory reset fails on a deleted node with a storage-related error even if you opt not to reset the storage configuration
- Upgrade issues
- The system config import command does not work as expected
- After multi-step upgrade from 7.4.2 to 8.3 eth1 device is not listed in the network ip add show output
- Checkpoints might remain in the file systems used by Veritas Data Deduplication (VDD) after the system rolls back after an upgrade failure
- Multifactor authentication may not work on a container which is upgraded while upgrading the appliance
- Veritas Data Deduplication issues
- Provisioning for Veritas Data Deduplication is displayed as failed in GUI
- During reconfiguration of Veritas Data Deduplication, the specified username is not considered
- If you run the storage fs offline command on a file system on which Veritas Data Deduplication is configured while the dedupe shrink operation is in progress, it may lead to an incorrect configuration of the duplication server
- After upgrade, Veritas Data Deduplication configuration fails as the virtual IP association with deduplication is being used by CIFS
- Starting deduplication services using the Veritas Data Deduplication 19.0.1 restricted shell fails
- Earlier set outbound connection rules get removed if the cluster is restarted after dedupe stop command
- Reconfiguration of Veritas Data Deduplication 19.0.1 version with securecomm enabled option displays an error
- Access Appliance operational notes
- CIFS issues
- Access Appliance known issues
- Getting help
Unplanned failover and failback in continuous replication may fail if the communication of the IPTABLE rules between the cluster nodes does not happen correctly
In case of unplanned failover and failback, the IPTABLE rules may not get restored properly. The communication between the nodes does not happen correctly.
Workaround:
Flush the IPTABLES on all the nodes in the cluster on the primary as well as the secondary site.
# iptables -F