Veritas NetBackup™ Flex Scale Release Notes
- Getting help
- Features, enhancements, and changes
- What's new in this release
- What's new in this release
- Limitations
- Known issues
- Cluster configuration issues
- Disaster recovery issues
- Miscellaneous issues
- NetBackup issues
- Networking issues
- Node and disk management issues
- Security and authentication issues
- Upgrade issues
- UI issues
- Cluster configuration issues
- Fixed issues
Fixed issues in version 3.1
The following issues are fixed in this release:
Table:
ID | Description |
---|---|
4051797 | Unable to view the login banner after an upgrade. |
4064943 | Upgrade from version 2.1 to 3.0 fails if the cluster is configured with an external certificate. |
APPSOL-154850 | After an upgrade, the proxy server configured for Call Home is disabled but is displayed as enabled in the UI. |
APPSOL-154989 | After an upgrade Call Home does not work. |
IA-27647 | An NVMe disk is wrongly selected as a target disk while replacing a SAS SSD. |
IA-30046 | When disaster recovery gets configured on the secondary site, the catalog storage usage may be displayed as zero. |
IA-30204 | Replacing an NVMe disk fails with a data movement from source disk to destination disk error. |
IA-30251 | Catalog backup policy may fail or use the remote media server for backup. |
4012004 | Takeover to a secondary cluster fails even after the primary cluster is completely powered off. |
IA-32032 | Empty log directories are created in the downloaded log file. |
IA-32201 and IA-32246 | For the private network, if you use the default IPv4 IP address but specify an IPv6 IP other than the default, the specifiedIPv6 IP address is ignored. |
IA-32203 | Catalog replication may fail to resume automatically after recovering from node fault that exceeds fault tolerance limit. |
IA-32612 | Add node fails because of memory fragmentation. |
IA-36540 | If both primary and secondary clusters are down and are brought online again, it may happen that the replication is in error state. |
IA-36090 | Unable to perform a takeover operation from the new site acting as the secondary |
IA-36990 | Rollback fails after a failed upgrade. |
IA-37443 | Add node operation hangs on the secondary site after an upgrade. |
IA-37656 | After replacing a node, the AutoSupport settings are not synchronized to the replacement node. |
IA-37405 and IA-37304 | Log rotation does not work for files and directories in |
IA-37062 | Node is displayed as unhealthy if the node on which the management console is running is stopped. |
IA-39351 | Enabling compliance mode for the first time on the secondary cluster may fail if disaster recovery is configured. |
IA-39899 | If disaster recovery is configured and an upgrade from NetBackup Flex Scale 2.1 to 3.0, the upgrade operation hangs. |
IA-40346 | On a NetBackup Flex Scale cluster with disaster recovery configuration, the replication state shows Primary-Primary on the faulted primary cluster after takeover. |
IA-39890 | AD/LDAP domain unreachable alerts do not get cleared after the AD/LDAP server is deleted |
IA-39642 | AD server test connection fails due to incorrect username on the IPV6 media only cluster |
IA-40140 | The Add nodes to the cluster button remains disabled even after providing all the inputs |
IA-40062 | After cluster reboot all/shutdown all operation, AD/LDAP domains become unreachable from one or more nodes on a NetBackup Flex Scale cluster on which only media servers are deployed |
IA-40058 | Assigning role to correct AD/LDAP user/group with wrong domain causes the user listing to fail |
IA-40218 | Alerts about inconsistent login banner and password policy appear after an upgrade. |
IA-40368 | Unable to add more than seven nodes simultaneously to the cluster. |
IA-40370 | Alerts about node being down are generated during an upgrade. |
IA-40381 | GUI takes a long time to update the status of the upgrade task. |
IA-40377 | Upgrade may fail if operations such as such as OS reboot, cluster restart, and node stop and shutdown are used during the upgrade. |
4019408 | NetBackup fails to discover VMware workloads in an IPv6 environment |
IA-24663 IA-31849 | DNS of container does not get updated when the DNS on the network is changed |
IA-26730 | Bond modify operation fails when you modify some bond mode options such as xmit_hash_policy |
4020899 | AD/LDAP configuration may fail for IPv6 addresses |
IA-30306 IA-40255 | Upgrade fails during pre-flight in VCS service group checks even if the failover service group is ONLINE on a node, but FAULTED on another node |
IA-40311 | In a disaster recovery environment, upgrade gets stuck during node evacuation stage as VVRInfra_Grp cannot be brought down |
IA-40597 | Upgrade may fail after node evacuation if a VCS parallel service group is OFFLINE on a partial set of nodes at the beginning of the upgrade |
IA-25874 | In-progress user creation tasks disappear from the infrastructure UI if the management console node restarts abruptly |
IA-40121 | CRL mode does not get updated on the secondary site after ECA is renewed on a cluster on which disaster recovery is configured |
IA-27537 | After an upgrade, if checkpoint is restored, backup and restore jobs may stop working |
IA-36129 | Disaster recovery configuration fails if the lockdown mode on the secondary cluster is enterprise or compliance |
4042920 | After an upgrade, the metadata format in cloud storage of MSDP cloud volume is changed |
IA-30521 | During EEB installation, a hang is observed during the installation of the fourth EEB and the proxy log reports "Internal Server Error" |
IA-40332 | GUI login fails with LDAP user if the domain is configured with SSL |