Veritas Access Appliance 8.3 Release Notes

Last Published:
Product(s): Appliances (8.3)
Platform: Veritas 3360,Veritas 3350,Veritas 3340
  1. Overview of Access Appliance
    1.  
      About this release
    2. Changes in this release
      1.  
        End of life for Wolf Pass server chassis
      2.  
        Support for single node configuration
      3.  
        Upgrading the appliance using the UI
      4.  
        Installing EEBs using the appliance UI
      5.  
        Improved diagnostic support
      6.  
        Viewing performance and aggregate usage details on the appliance dashboard
      7.  
        Unsupported features in this release
      8.  
        Planned deprecations in future releases
    3.  
      Supported NetBackup client versions
    4.  
      Access Appliance simple storage service (S3) APIs
  2. Software limitations
    1.  
      Limitations related to CIFS
    2. Limitations related to installation and upgrade
      1.  
        Underscore character is not supported for host names
    3.  
      Limitation related to cloud tiering
    4.  
      Limitations related to networking
    5.  
      Limitations related to Veritas Data Deduplication
    6.  
      Kernel-based NFS v4 limitations
    7.  
      File system limitation
    8.  
      Access Appliance S3 server limitation
    9.  
      Long-term data retention (LTR) limitations
    10. Limitation related to replication
      1.  
        Limitation related to continuous replication
    11.  
      Limitations related to user management
  3. Known issues
    1. Access Appliance known issues
      1. CIFS issues
        1.  
          CIFS share created on Access Appliance 8.x version may not be accessible if all the virtual IPs are on a VLAN device
        2.  
          Error message is displayed when the CIFS server is restarted if shares are already configured and the clustering mode is changed to ctdb
        3.  
          CIFS share add command fails to add share on the target cluster for a filesystem which is used in the configuration of episodic replication
      2. General issues
        1.  
          Reimaging the appliance from the SSD device fails if a CD with the ISO image is inserted in the CD-ROM
        2.  
          User is not logged out from the command-line interface after running the Cluster> stop all command
        3.  
          User account gets locked on a management or non-management console node
        4.  
          Addition of a user named 'admin' fails from GUI and CLISH
        5.  
          Cluster reboot all command shows missing host message
        6.  
          The displayed proxy server state is inconsistent if the specified proxy server settings are incorrect
      3. GUI issues
        1.  
          When provisioning storage, the Access web interface or the command-line interface displays storage capacity in MB, GB, TB, or PB
        2.  
          GUI stops working after ECA deployment
        3.  
          GUI stops working if the ECA certificates are not renewed or get revoked
        4.  
          When an account gets locked because incorrect login attempts were exceeded, log in from GUI fails even though unlock time is exceeded
        5.  
          Partially uploaded software upgrade package is displayed in the GUI
      4. Infrastructure issues
        1.  
          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.
        2.  
          The Access Appliance management console is not available after a node is deleted and the remaining node is restarted
        3.  
          Add node fails if upgrade is performed from 7.4.2.200 or lower version
      5. Installation and configuration issues
        1.  
          When you configure Access Appliance as an iSCSI target, the initiator authentication does not work
      6. MSDP-C issues
        1.  
          MSDP-C duplication job fails with OpenStorage WORM lock error after the file system is grown to100%
      7. Networking issues
        1.  
          The IPs hosted on an interface that is not the current IPv6 default gateway interface are not reachable outside the current IPv6 subnet
        2.  
          The network ip addr show command does not display all the FQDN entries for an IP address
        3.  
          Unable to log in to IPMI intermittently
      8. NFS issues
        1.  
          Kernel-NFS v4 lock failover does not happen correctly in case of a node crash
        2.  
          Kernel-NFS v4 export mount for Netgroup does not work correctly
        3.  
          System software share open command displays IPV6 IP on NFS share if the management NIC (eth1) is configured with VLAN
      9. ObjectAccess issues
        1.  
          If the cluster name does not follow the DNS hostname restrictions, you cannot work with the ObjectAccess service in Access Appliance
        2.  
          The Object Access server crashes whenever any operation on the Object Access server requires authentication with the AD server using an AD user
      10. Replication issues
        1.  
          Continuous replication is unable to go to the replicating state if the Storage Replicated Log becomes full
        2.  
          Unplanned failover and failback in continuous replication may fail if the communication of the IPTABLE rules between the cluster nodes does not happen correctly
      11. STIG issues
        1.  
          The changed password is not synchronized across the cluster
        2.  
          STIG status is not preserved if the system configuration is imported after reimaging the nodes
      12. Storage issues
        1.  
          Rollback refresh fails when running it after running Storage> fs growby or growto commands
        2.  
          Rollback service group goes in faulted state when respective cache object is full and there is no way to clear the state
        3.  
          Event messages are not generated when cache objects get full
        4.  
          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
        5.  
          Storage> fs addcolumn operation fails but error notification is not sent
        6.  
          Unable to create space-optimized rollback when tiering is present
        7.  
          The CVM service group goes in to faulted state after you restart the management console node
        8.  
          After a cluster reboot, the UI shows that the storage is not configured
        9.  
          Factory reset fails on a deleted node with a storage-related error even if you opt not to reset the storage configuration
      13. Upgrade issues
        1.  
          The system config import command does not work as expected
        2.  
          After multi-step upgrade from 7.4.2 to 8.3 eth1 device is not listed in the network ip add show output
        3.  
          Checkpoints might remain in the file systems used by Veritas Data Deduplication (VDD) after the system rolls back after an upgrade failure
        4.  
          Multifactor authentication may not work on a container which is upgraded while upgrading the appliance
      14. Veritas Data Deduplication issues
        1.  
          Provisioning for Veritas Data Deduplication is displayed as failed in GUI
        2.  
          During reconfiguration of Veritas Data Deduplication, the specified username is not considered
        3.  
          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
        4.  
          After upgrade, Veritas Data Deduplication configuration fails as the virtual IP association with deduplication is being used by CIFS
        5.  
          Starting deduplication services using the Veritas Data Deduplication 19.0.1 restricted shell fails
        6.  
          Earlier set outbound connection rules get removed if the cluster is restarted after dedupe stop command
        7.  
          Reconfiguration of Veritas Data Deduplication 19.0.1 version with securecomm enabled option displays an error
      15. Access Appliance operational notes
        1.  
          Access services do not restart properly after storage shelf restart
  4. Getting help
    1.  
      Displaying the Online Help
    2.  
      Displaying the man pages
    3.  
      Using the Access Appliance product documentation

During reconfiguration of Veritas Data Deduplication, the specified username is not considered

During the initial configuration of Veritas Data Deduplication, the username and password are used to configure the storage server. During reconfiguration, the username is taken as input from the user, but since the storage server was already configured, the credentials are not utilized anywhere, and the services are started.

Hence, the username provided during reconfiguration is not validated against that provided during the initial configuration and is not stored anywhere.

Workaround:

This behavior is by design and there is no workaround for this issue.