Veritas Access 7.3 Release Notes

Last Published:
Product(s): Access (7.3)
Platform: Linux
  1. Overview of Veritas Access
    1.  
      About this release
    2.  
      Important release information
    3. Changes in this release
      1.  
        Changes to the GUI
      2.  
        Additional cloud providers
      3.  
        Scale-out file system enhancements
      4.  
        Installer enhancements
      5.  
        Multi-protocol support for NFS with S3
      6.  
        Support for kernel-based NFS version 4
      7.  
        Managing application I/O workloads using maximum IOPS settings
      8.  
        Veritas Access sync replication
      9.  
        WORM storage for Enterprise Vault archiving
      10.  
        Creation of Partition Secure Notification (PSN) file for Enterprise Vault archiving
      11.  
        Changing firewall settings
      12.  
        Setting retention in files
      13.  
        Not supported in this release
    4. Technical preview features
      1.  
        Veritas Access as an iSCSI Target
      2.  
        IP load balancing
      3.  
        Erasure coding for Object Store buckets
      4.  
        Veritas Access Streamer as a storage type for Enterprise Vault
  2. Fixed issues
    1.  
      Fixed issues since the last release
  3. Software limitations
    1.  
      Limitations on using shared LUNs
    2. Flexible Storage Sharing limitations
      1.  
        If your cluster has DAS disks, you must limit the cluster name to ten characters at installation time
    3. Limitations related to installation and upgrade
      1.  
        If required VIPs are not configured, then services like NFS, CIFS, and S3 do not function properly
      2.  
        Rolling upgrade is not supported from CLISH
    4.  
      Limitations in the Backup mode
    5.  
      Veritas Access IPv6 limitations
    6.  
      FTP create_homedirs limitation
    7.  
      Samba ACL performance-related issues
    8. Veritas Access language support
      1.  
        Veritas Access does not support non-English characters when using the CLISH (3595280)
    9.  
      Limitations on using InfiniBand NICs in the Veritas Access cluster
    10.  
      Limitation on using Veritas Access in a virtual machine environment
    11.  
      NFS-Ganesha limitations
    12.  
      Kernel-based NFS v4 limitations
    13. File system limitation
      1.  
        Any direct NLM operations from CLISH can lead to system instability (IA-1640)
    14.  
      Veritas Access S3 server limitation
    15.  
      LTR limitations
  4. Known issues
    1. Veritas Access known issues
      1. AWS issues
        1.  
          The CLISH storage commands appear to hang when EBS disks are forcibly detached from the AWS console (IA-5042)
        2.  
          CIFS server start command fails on one of the nodes if the clustering mode is set to CTDB
      2. Backup issues
        1.  
          Backup or restore status may show invalid status after the BackupGrp is switched or failed over to the other node when the SAN client is enabled (3606322)
      3. CIFS issues
        1.  
          Cannot enable the quota on a file system that is appended or added to the list of homedir (3853674)
        2.  
          Deleting a CIFS share resets the default owner and group permissions for other CIFS shares on the same file system (3824576, 3836861)
        3.  
          Default CIFS share has owner other than root (IA-4771)
        4.  
          Listing of CIFS shares created on a Veritas Access cluster fails on Windows server or client
      4. Deduplication issues
        1.  
          Removing lost+found files for a mount point that has deduplication enabled may cause issues with deduplication (3472414)
      5. Enterprise Vault Attach known issues
        1.  
          Error while setting full access permission to Enterprise Vault user for archival directory (IA-7685)
      6. FTP issues
        1.  
          If a file system is used as homedir or anonymous_login_dir for FTP, this file system cannot be destroyed (IA-1876)
      7. GUI issues
        1.  
          When both volume-level and file system replication links are set up in Veritas Access 7.3, provisioning of storage using High Availability and Data Protection policies does not work (IA-7646)
        2.  
          When a new node is added or when a new cluster is installed and configured, the GUI may not start on the console node after a failover
        3.  
          When an earlier version of the Veritas Access cluster is upgraded, the GUI shows stale and incomplete data (IA-7127)
      8. Installation and configuration issues
        1.  
          After you restart a node that uses RDMA LLT, LLT does not work, or the gabconifg - a command shows the jeopardy state (IA-1796)
        2.  
          Running individual Veritas Access scripts may return inconsistent return codes (3796864)
        3.  
          Configuring Veritas Access with the installer fails when the SSH connection is lost (3794964)
        4.  
          Excluding PCIs from the configuration fails when you configure Veritas Access using a response file (3686704)
        5.  
          Installer does not list the initialized disks immediately after initializing the disks during I/O fencing configuration (3659716)
        6.  
          If the same driver node is used for two installations at the same time, then the second installation shows the status of progress of the first installation (IA-3446)
        7.  
          If the same driver node is used for two or more installations at the same time, then the first installation session is terminated (IA-3436)
        8.  
          If you run the Cluster> show command when a slave node is in the restart, shutdown, or crash state, the slave node throws an exception (IA-900)
        9.  
          If duplicate PCI IDs are added for the PCI exclusion, the Cluster> add node name command fails (IA-1850)
        10.  
          If installing using a response file is started from the cluster node, then the installation session gets terminated after the configuring NICs section (IA-3570)
        11.  
          After finishing system verification checks, the installer displays a warning message about missing third-party RPMs (IA-3611)
        12.  
          Installer appears to hang when you use the installaccess command to install and configure the product from a node of the cluster (IA-5300)
        13.  
          Phantomgroup for the VLAN device does not come online if you create another VLAN device from CLISH after cluster configuration is done (IA-6671)
        14.  
          Rolling upgrade fails to bring the cfsmount resources online when you perform an upgrade from 7.2.1 version (IA-7388)
        15.  
          Rolling upgrade is not allowed if the scale-out file system is online and being used by the NFS or S3 server
        16.  
          Veritas Access fails to install if LDAP or the autofs home directories are preconfigured on the system
      9. Networking issues
        1.  
          CVM service group goes into faulted state unexpectedly (3793413)
        2.  
          In a mixed IPv4 and IPv6 VIP network setup, the IP balancing does not consider IP type (3616561)
        3.  
          The netgroup search does not continue to search in NIS if the entry is not found in LDAP (3559219)
        4.  
          VIP and PIP hosted on an interface that is not the current IPv6 default gateway interface are not reachable outside the current IPv6 subnet (3596284)
      10. NFS issues
        1.  
          Slow performance with Solaris 10 clients with NFS-Ganesha version 4 (IA-1302)
        2.  
          Random-write performance drop of NFS-Ganesha with Linux clients (IA-1304)
        3.  
          Latest directory content of server is not visible to the client if time is not synchronized across the nodes (IA-1002)
        4.  
          NFS> share show may list the shares as faulted for some time if you restart the cluster node (IA-1838)
        5.  
          NFS-Ganesha shares faults after the NFS configuration is imported(IA-849)
        6.  
          NFS-Ganesha shares may not come online when the number of shares are more than 500 (IA-1844)
        7.  
          Exporting a single path to multiple clients through multiple exports does not work with NFS-Ganesha (3816074, 3819836)
        8.  
          For the NFS-Ganesha server, bringing a large number of shares online or offline takes a long time (3847271)
        9.  
          NFS client application may fail with the stale file handle error on node reboot (3828442)
        10.  
          NFS> share show command does not distinguish offline versus online shares (IA-2758)
        11.  
          Difference in output between NFS> share show and Linux showmount commands (IA-1938)
        12.  
          NFS mount on client is stalled after you switch the NFS server (IA-6629)
        13.  
          Kernel NFS v4 lock failover does not happen correctly in case of a node crash (IA-5083)
        14.  
          Kernel NFS v4 export mount for Netgroup does not work correctly (IA-6672)
      11. ObjectAccess issues
        1.  
          ObjectAccess server goes in to faulted state while doing multi-part upload of a 10-GB file with a chunk size of 5 MB (IA-1943)
        2.  
          When trying to connect to the S3 server over SSLS3, the client application may give a warning like "SSL3_GET_SERVER_CERTIFICATE:certificate verify failed" (IA-5378)
        3.  
          If you have upgraded to Veritas Access 7.3 from an earlier release, access to S3 server fails if the cluster name has upper case letters (IA-5628)
        4.  
          If the cluster name does not follow the DNS hostname restrictions, you cannot work with ObjectAccess service in Veritas Access (IA-5631)
        5.  
          ObjectAccess operations do not work correctly in virtual hosted-style addressing when SSL is enabled (IA-5737)
        6.  
          ObjectAccess server enable operation fails on a single node (IA-5704)
        7.  
          ObjectAccess (S3) service goes OFFLINE when the node is restarted (IA-6282)
        8.  
          Bucket creation may fail with "Timed out Error" (IA-7432)
        9.  
          Temporary objects may be present in the bucket in case of multi-part upload (IA-7434)
        10.  
          Bucket CreationDate is incorrect if the bucket is created by mapping the filesystem path (IA-7227)
        11.  
          Group configuration does not work in ObjectAccess if the group name contains a space (IA-7407)
        12.  
          An erasure coded file system may show mirrored layout in the Storage> fs list command (IA-7266)
        13.  
          Accessing a bucket or object in the S3 server fails with S3 internal errors
      12. OpenDedup issues
        1.  
          If OpenDedup is installed on Veritas Access 7.3, then failover is not supported.
        2.  
          OpenDedup is not highly available
      13. OpenStack issues
        1.  
          Cinder and Manila shares cannot be distinguished from the CLISH (3763836)
      14. Replication issues
        1.  
          Running replication and dedup over the same source, the replication file system fails in certain scenarios (3804751)
        2.  
          The System> config import command does not import replication keys and jobs (3822515)
        3.  
          The job uses the schedule on the target after replication failover (3668957)
        4.  
          Replication fails with error "connection reset by peer" if the target node fails over (IA-3290)
        5.  
          Synchronous replication shows file system layout as mirrored in case of simple and striped file system (IA-7308)
        6.  
          Synchronous replication is unable to come in replicating state if the Storage Replicated Log becomes full
        7.  
          If you restart any node in the primary or secondary cluster, replication may go into PAUSED state (IA-7567)
        8.  
          Sync replication failback does not work (IA-7524)
        9.  
          Replication jobs created in Veritas Access 7.2.1.1 or earlier versions are not recognized after upgrade to 7.3 version (IA-7597)
        10.  
          Setting the bandwidth through the GUI is not enabled for replication (IA- 7295)
        11.  
          Sync replication fails when the 'had' daemon is restarted on the target manually (IA-7357)
      15. SmartIO issues
        1.  
          SmartIO writeback cachemode for a file system changes to read mode after taking the file system offline and then online (IA-3423)
      16. Storage issues
        1.  
          Snapshot mount can fail if the snapshot quota is set (IA-1542)
        2.  
          Sometimes the Storage> pool rmdisk command does not print a message (IA-1733)
        3.  
          The Storage> Pool rmdisk command sometimes can give an error where the file system name is not printed (IA-1639)
        4.  
          Not able to enable quota for file system that is newly added in the list of CIFS home directories (IA-1851)
        5.  
          Destroying the file system may not remove the /etc/mtab entry for the mount point (3801216)
        6.  
          The Storage> fs online command returns an error, but the file system is online after several minutes (3650635)
        7.  
          Removing disks from the pool fails if a DCO exists (3452098)
        8.  
          Scale-out file system returns an ENOSPC error even if the df command shows there is space available in the file system (IA-3545)
        9.  
          Rollback refresh fails when running it after running Storage> fs growby or growto commands (3588248)
        10.  
          If an exported DAS disk is in error state, it shows ERR on the local node and NOT_CONN on the remote nodes in Storage> list (IA-3269)
        11.  
          Inconsistent cluster state with management service down when disabling I/O fencing (IA-3427)
        12.  
          Storage> tier move command failover of node is not working (IA-3091)
        13.  
          Rollback service group goes in faulted state when respective cache object is full and there is no way to clear the state (IA-3251)
        14.  
          Event messages are not generated when cache objects get full (IA-3239)
        15.  
          Storage device fails with SIGBUS signal causing the abnormal termination of the scale-out file system daemon (IA-2915)
        16.  
          Storage> tier move list command fails if one of the cluster nodes is rebooted (IA-3241)
        17.  
          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 (IA-3398)
        18.  
          Storage> fs addcolumn operation fails but error notification is not sent (IA-5434)
        19.  
          Unable to create space-optimized rollback when tiering is present (IA-5690)
        20.  
          Enabling fencing on a setup with volume manager objects present fails to import the disk group (IA-7219)
        21.  
          For the rollback cache growto and growby operations, the cache size values cannot be specified in terms of g/G, m/M or k/K (IA-7473)
        22.  
          File system creation fails when the pool contains only one disk (IA-7515)
        23.  
          After starting the backup service, BackupGrp goes into FAULTED state on some nodes (IA-7174)
        24.  
          A scale-out file system created with a simple layout using thin LUNs may show layered layout in the Storage> fs list command (IA-7604)
        25.  
          A file system created with a largefs-striped or largefs-mirrored-stripe layout may show incorrect number of columns in the Storage> fs list command (IA-7628)
  5. Getting help
    1.  
      Displaying the online Help
    2.  
      Displaying the man pages
    3.  
      Using the Veritas Access product documentation

Replication fails with error "connection reset by peer" if the target node fails over (IA-3290)

Replication creates a connection between the source and the target to replicate data. Replication uses one of the nodes from the target to access the file system to replicate data. In case the connection to this node breaks due to some error like a reboot, replication fails with an error message. If there is a scheduled replication job, the next iteration continues this failed replication session, possibly with a new node from the target.

Workaround:

If there is no scheduled replication job, you need to issue the Replication> job sync command to start the replication job once the target node is up.