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

Last Published:
Product(s): Appliances (8.5)
Platform: Veritas 3340,Veritas 3350,Veritas 3360
  1. Overview of Access Appliance
    1.  
      About this release
    2. Changes in this release
      1.  
        Advance notification for deprecated functionality in future releases
    3.  
      Supported NetBackup client versions
    4.  
      Supported versions of Veritas Data Deduplication
    5.  
      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.  
          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.  
          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.  
          Partially uploaded software upgrade package is displayed in the GUI
      4. Infrastructure issues
        1.  
          The Access Appliance management console is not available after a node is deleted and the remaining node is restarted
        2.  
          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
        2.  
          If the console node reboots, the install operation fails for inconsistent EEBs
      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 network ip addr show command does not display all the FQDN entries for an IP address
        2.  
          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.  
          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
      12. Storage issues
        1.  
          Rollback service group goes in faulted state when respective cache object is full and there is no way to clear the state
        2.  
          Event messages are not generated when cache objects get full
        3.  
          Storage fs addcolumn operation fails but error notification is not sent
        4.  
          Unable to create space-optimized rollback when tiering is present
        5.  
          The CVM service group goes in to faulted state after you restart the management console node
        6.  
          After a cluster reboot, the UI shows that the storage is not configured
      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.5 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.  
          Upgrade preflight check fails with password expiry error
        5.  
          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
        6.  
          AD is disabled after an upgrade from Access Appliance version 8.3.100 to 8.5
        7.  
          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
      14. Veritas Data Deduplication issues
        1.  
          Provisioning for Veritas Data Deduplication is displayed as failed in GUI
        2.  
          After upgrade, Veritas Data Deduplication configuration fails as the virtual IP association with deduplication is being used by CIFS
      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

After multi-step upgrade from 7.4.2 to 8.5 eth1 device is not listed in the network ip add show output

After a mult-step upgrade to 8.5, unable to add the eth1 device to the cluster. (IA-53773)

Workaround:

To add eth1 dev of each node, in Access cluster do the following on both the nodes:

  1. Elevate to root shell.
  2. Delete following directives from the /etc/sysconfig/network-scripts/ifcfg-eth1 file on all the nodes of the cluster:

    • IPADDR

    • NETMASK

    • NETWORK

    • GATEWAY

  3. Reset the device using the following command:

    ifdown eth1 && ifup eth1

  4. Verify if the default route for eth1 has been deleted by using the following command:

    ip route show

  5. If the default route for eth1 still persists, run the following command to remove the default route:

    route del default gw gateway ip dev eth1

  6. After deleting the default route, delete the entry from the /opt/VRTSnas/conf/net_globalroutes.conf file.
  7. From the elevated prompt of the node where the management console is running, execute the Access CLISH command as follows:

    LOGNAME=primary /opt/VRTSnas/clish/bin/clish -u primary

  8. Bring eth1 under Access management:

    Network> device add eth1

  9. Monitor the state of the Phantomgroup_pubethx service group using following command. Ensure that the service group is brought online:

    hagrp -state | grep Phantomgroup_pubeth

  10. Add a free IP address from cluster for eth1 using the following command:

    amigrtionclus> network ip addr add IP NETMASK physical eth1 nodename

  11. Verify that the IP address is added correctly by checking the output of the following command:

    amigrtionclus> network ip addr show

  12. Log out from the Access CLI.
  13. Update the /opt/VRTSnas/conf/net_preexist_dev.conf file on both the nodes with the entry for eth1
  14. Add default global route:

    amigrationclus> network ip route add all 0.0.0.0 0.0.0.0 via new_gw dev eth1 scope=global

    Note:

    The scope parameter is available from 7.4.3 and later versions. If you on version 7.4.2.x, the scope parameter is not available and you must use the Linux command instead to add the route.

  15. Change the console IP:

    amigrationclus> network ip addr modify old_ip new_ip new_pub_nm device

    Note:

    The current logged in Access CLISH session is terminated.