Arctera InfoScale™ Operations Manager 9.0 Release Notes

Last Published:
Product(s): InfoScale & Storage Foundation (9.0)
Platform: AIX,HP-UX,Linux,Solaris,VMware ESX,Windows
  1. Overview of this release
    1.  
      About InfoScale Operations Manager
    2. New features and changes in InfoScale Operations Manager 9.0
      1.  
        Online migration to encrypted volumes
      2.  
        Support for dynamic LUN expansion in FSS environments
      3.  
        Support for Windows-based Management server in disaster recovery environment
      4.  
        Support for configuring SecureFS for PostgreSQL
      5.  
        Support for SecureFS Single Click Recovery for Oracle and PostgreSQL
    3.  
      Deprecated functionality in version 9.0
    4.  
      Issues fixed in the InfoScale Operations Manager 9.0 release
  2. System requirements
    1.  
      Operating system requirements
    2. System resource requirements
      1.  
        About space estimation for data logs
      2.  
        About the frequency of managed host, enclosure and switch information discovery
    3.  
      Supported hardware
    4.  
      Web browser requirements
    5. Network and firewall requirements
      1.  
        Internet Protocol version requirements
    6.  
      About the consumption of the managed host components
  3. Software limitations
    1.  
      InfoScale Operations Manager 9.0 managed host not supported on AIX in Network Installation Manager
    2.  
      InfoScale Operations Manager 9.0 does not support HA Plugin functionality
    3.  
      Control host add-on is not compatible with the Windows platform (4119171)
    4.  
      Volume layout not discovered for LDM-managed volumes mounted without a drive letter
    5.  
      Backup and restore limitations in InfoScale Operations Manager 9.0
    6.  
      InfoScale Operations Manager does not support the discovery of LDoms and Zones together on the same host
    7.  
      Deployment-related limitations
    8.  
      Windows Management Server high availability configuration limitations
    9.  
      Solaris Zones virtualization support limitations
    10.  
      Discovery limitations for virtualization support
    11.  
      VCS configuration check reports violations only if at least one node in the cluster is running Cluster Server
    12.  
      Limitations related to the correlation between the disks and the disk groups
    13.  
      CIFS shares from NetApp and Celerra arrays that are mapped to a Windows host are not discovered
    14.  
      Limitations on SF operations on Windows CVM cluster
    15.  
      ESX servers not able to access an RDM disk associated with a shared datastore might cause failed discovery of RDM disk by InfoScale Operations Manager
    16.  
      InfoScale Operations Manager does not validate if the cluster node is managed by the Management Server during the VBS start operation
  4. Known issues
    1.  
      xprtld.service fails to start during yum upgrade (4188076)
    2.  
      Incorrect VCS configuration message is displayed during SecureFS checkpoint recovery (4189119)
    3.  
      SSO login failure after Windows CMS upgrade (4188548)
    4.  
      VBS logs missing on InfoScale Operations Manager server (4188788)
    5.  
      LDAP configuration fails on a fresh Windows CMS installation (4188000)
    6.  
      InfoScale Operations Manager CMS services fail to start after a system reboot (4188737)
    7.  
      Disks not visible in InfoScale Operations Manager UI (4188991)
  5. Appendix A. Getting help
    1.  
      InfoScale Operations Manager on the Web
    2.  
      Getting help
    3.  
      Using the product documentation

InfoScale Operations Manager does not validate if the cluster node is managed by the Management Server during the VBS start operation

When you perform the Virtual Business Service (VBS) start operation, InfoScale Operations Manager does not check whether Management Server manages the cluster node. InfoScale Operations Manager brings the service group online using the -any option on the available systems for that service group.

Workaround:

Although there is no functional loss, it is recommended that you add all the cluster nodes to the Management Server domain.