Important Update: Cohesity Products Documentation
All Cohesity product documentation are now managed via the Cohesity Docs Portal: https://docs.cohesity.com/HomePage/Content/home.htm. Some documentation available here may not reflect the latest information or may no longer be accessible.
NetBackup™ Access Appliance 8.5 Release Notes
- Overview of Access Appliance
- 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
- 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
- The displayed proxy server state is inconsistent if the specified proxy server settings are incorrect
- GUI issues
- Infrastructure issues
- Installation and configuration issues
- MSDP-C issues
- Networking issues
- NFS issues
- ObjectAccess issues
- Replication issues
- STIG issues
- Storage issues
- 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
- 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
- Upgrade issues
- The system config import command does not work as expected
- After multi-step upgrade from 7.4.2 to 8.5 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
- Upgrade preflight check fails with password expiry error
- Upgrade from Access Appliance version 8.2/8.2.x, 8.3/8.3.x to version 8.5 fails during free space pre-check for "/" partition
- AD is disabled after an upgrade from Access Appliance version 8.3.100 to 8.5
- After you upgrade from Access Appliance version 8.2/8.2.002 to version 8.5, the CTDB server and ADClientService goes into PARTIAL state or is not ONLINE on all the nodes
- Veritas Data Deduplication issues
- Access Appliance operational notes
- Access Appliance known issues
- Getting help
Access services do not restart properly after storage shelf restart
If the Veritas Access 3340 Appliance loses connectivity to an attached Primary or Expansion storage shelf, the underlying storage connectivity is lost and the VxVM disk group goes into a deported state. This issue occurs whenever a storage shelf intentionally or unintentionally restarts. To correct this issue, you need to restart the Access services.
To restart the Access services after the appliance storage shelves restart
- Log onto the Access shell menu over the console IP address.
- Run the following command to import the VxVM disk group and other Access configurations:
ltrcluster> storage scanbus
- Restart the services that were configured before the storage shelf restart.
For example, if the S3 server is configured, use the following commands
ltrcluster> objectaccess server status ObjectAccess Status on ltrcluster_01 : OFFLINE|FAULTED ObjectAccess Status on ltrcluster_02 : OFFLINE|FAULTED ltrcluster> objectaccess server stop ACCESS ObjectAccess ERROR V-493-10-4 ObjectAccess server already stopped. ltrcluster> objectaccess server start ACCESS ObjectAccess SUCCESS V-493-10-4 ObjectAccess started successfully. ltrcluster> objectaccess server status ObjectAccess Status on ltrcluster_01 : ONLINE ObjectAccess Status on ltrcluster_02 : ONLINE ltrcluster>