Veritas™ Resiliency Platform 2.2 Update 3 Release Notes
- Overview
- System requirements
- Fixed issues
- Known issues
- Disaster recovery (DR) configuration for resiliency group fails if Microsoft Hyper-V Replica is configured after you add a virtual machine in Resiliency Platform
- In the VM Inventory report, instead of allocated memory, Resiliency Platform shows the total memory of the virtual machines
- Certain validations do not work while creating a resiliency group of applications (3721289)
- Rehearsal does not work after being aborted
- The configure DR operation fails if virtual machines in the resiliency group belong to different servers
- For resiliency groups containing VMware virtual machines with NFS datastore mounted from a NetApp volume with substring vol, Migrate or takeover operations may fail
- The license expiry status is inconsistent on Resiliency Managers configured on different time zones
- In the Hyper-V guest environment, the writable disk is shown in the Read-Only state (3785911)
- Long SRDF device group names are not discovered (3786826)
- Multiple repository paths on the same host are not allowed for the repository server (3734149)
- Unknown state displayed for the Resiliency groups of dark sites that are part of VBS (3794650)
- An Oracle custom application is not discovered if the instance names do not match (3796579)
- VBS DR operations fail when an application resiliency group with unconfigured DR is added in VBS (3794105)
- Expired resiliency plan cannot be executed even after editing the schedule (3861955)
- Resiliency groups for Hitachi enclosures are not displayed on dashboard under Top RG by replication lag chart (3861173)
- Snapshot disk is read only after rehearse operation is performed in Hyper-V with SRDF replication (3862088)
- Static IP customization may not work under certain conditions (3862916, 3862237)
- Need to manually refresh all assets after a site recovery (3861929)
- Disk utilization risk not resolved after DR operations
- Migrate operation becomes unresponsive if the operation is initiated from an unavailable site (3862253)
- Remote cluster group dependencies not validated before migrate (3863082)
- VBS migrate operation cannot be performed after failure (3862124)
- Resiliency group state does not get updated when production site is down (3863081)
- Replication information error (5170)
- DNS customization does not work if FQDN is not defined (5037)
- Previously configured network mapping may not work after re-adding a VMware vCenter server
- Some versions of VMware Tools are not supported (4969)
- Login to the Resiliency Manager console fails at times
- Resiliency group and VBS names in charts are displayed incorrectly in Japanese and Chinese (8465)
- Warning message may be displayed for network mapping (8644)
- Cannot edit application discovery frequency for the uploaded application bundles from console (8433)
- Metering report does not work for third-party replication technologies (8617)
- Replication information not discovered for Hyper-V virtual machines configured in Microsoft Failover Clustering environment using Non-English characters in the CSV path (8697)
- An operation may fail if invoked at a time when virtual machine is being migrated using Vmotion (6476)
- vLan mapping compulsory for DRS enabled Vmware virtual machines (10322)
- Known issues: Resiliency Platform Data Mover
- Virtual Machine protection using Data Mover has a few policy related limitations (5181)
- Iofilter bundle not removed from ESX hosts even after unconfiguring virtual machines (5178)
- Storage policy needs to be manually removed after all the virtual machines are unconfigured (5180)
- VMDK and VMX files need to be in the same folder(5167)
- Edit resiliency group operation may fail after rehearsal or cleanup rehearsal (5092)
- Replication gets paused if you perform add disk operation (5182)
- Cannot perform any operation after deleting disk from virtual machine (5182)
- Data Mover virtual machine in no op mode risk cannot be resolved (5183)
- Risks not generated after taking snapshot of virtual machine replicated using Data Mover(6886)
- Known issues: Recovery to Amazon Web services (AWS)
- Some DHCP enabled NICs are not present on Cloud after migrate (7407)
- One or more NICs of a migrated Windows virtual machine may not be visible (7718)
- Cloud IPs get added to on-premise NICs after migrate back to the on-premise site and reboot (7713)
- Migrate or takeover operations fail at the Add Network for AWS task and Create Network Interface sub-task (7719)
- Sometimes network comes up on only one NIC although there are multiple NICs (8232)
- Known issues: NetBackup integration
- MAC address starting with 00:0c:29 not supported for VMware virtual machines (7103)
- A virtual machine backed up by multiple NBU master servers gets mapped with only one master server in the console (7608)
- A transient virtual machine remains in the ESX server in one scenerio (7413)
- Operations for virtual machine do not work if the remote master server gets reconfigured (8600)
- Known issues: Recovery to vCloud
- Limitations
- Rehearsal is not supported if volume is configured using asynchronous replication in IBM XIV enclosure
- Limitations for on-premises Windows hosts for Resiliency Platform Data Mover replication
- Hyper-V hosts having snapshots not supported for recovery to AWS
- Computer name of virtual machine on vCloud differs if the name exceeds permitted character limit
- Localization of adding application type is not supported
- Datastore name with special characters
- Appendix A. Virtual appliance security features
Fixed issues
This chapter lists the issues that have been fixed after releasing Veritas Resiliency Platform version 2.0 HF5 (2.0.0.500).
Table: Issues fixed in Veritas Resiliency Platform 2.2 Update 3 (2.2.0.300)
Incident number | Abstract |
|---|---|
10162 | DR operation fails if the password of the target vCenter server contains special character such as '$' |
9350 | Configuration files and Veritas Replication Set information on the ESX server does not get cleaned up after deletion of resiliency group containing VMware VAIO virtual machines |
9917 | Resiliency Platform Applications add-on gets pushed to Veritas InfoScale Operations Manager as part of upgrade |
9999 | Lookup entries for IMS in the Resiliency Manager memory local cache do not get refreshed after deletion of IMS |
9377 | No support for InfoScale application DR running on a virtual machine which is discovered by Veritas Resiliency Platform through vCenter server configuration |
9933 | Add host operation fails if you uninstall the ITRP add-on from the host and then try to add the host again |
9267 | Assets Lookup service has multiple mappings if a virtual machine gets discovered from vCenter server as well as by Veritas InfoScale Operations Manager |
9918 | Secure SMTP configuration not validated before passing the user information for email alert configuration |
9608 | Stale entries for NIC objects in the database do not get deleted |
9607 | Stale entries for LUNs in the database do not get deleted |
10047 | Hosts that have underscore in names not blocked during bootstrap |
9675 | If Veritas Resiliency Platform Data Mover bundle is uninstalled from the host, and then IMS is not accessible from the host where the bundle was uninstalled, subsequent installation of Data Mover bundle on that host may fail. |
9998 | Custom Script Execution fails if a virtual machine gets discovered from vCenter server as well as by Veritas InfoScale Operations Manager, or if some of the hosts belonging to an ESX server are added as host while others get discovered by the vCenter server |
10046 | Resiliency Manager upgrade from console is not supported and needs to be blocked |
9251 | IP customization fails after the timeout of one minute |
10063 | User needs to be notified that running loggather command with full option stops the IMS services |
8762 | No option to automatically cleanup loggather files |
9854 | Risks raised before upgrade do not get cleared after upgrade |
Table: Issues fixed in Veritas Resiliency Platform 2.2 Update 2 (2.2.0.200)
Incident number | Abstract |
|---|---|
9500 | Access profile service fails to restart in first attempt |
9471 | keytab file does not get passed correctly to IMS |
9348 | Entries in |
9385 | DNS operation shows success even when kinit fails and actual operation fails |
9384 | HyperV ITRP_NR discovery triggers unnecessary full HyperV discovery if HyperV virtual machine name is long |
9126 | IP customization fails with the error: unable to create VRP directory |
9388 | Filter IO throttling option needs to be provided |
9258 | After Upgrade to Resiliency Platform 2.2, Hyper-V virtual machines are not discovered |
9053 | Resiliency Platform Subnet network pair gets deleted from list after DR Rehearsal network is changed |
9269 | Veritas InfoScale Operations Manager (VIOM) side APIs getting directed to IMS instead of VIOM since VIOM server was treated as addressable object |
9351 | Recovery Operations on resiliency group using VAIO replication fails if resiliency group is edited on recovery data center |
9278 | IOTAP virtual machine configured for recovery to AWS gets crashed |
9345 | Retry count for Datastore unmount operation should be configurable |
9556 | In case of VMware VAIO, if there are multiple clusters and datastores, the target cluster selection page becomes unresponsive |
9268 | Upgrade should work even if there are some stale resiliency group entries exist |
6764 | Resiliency plan becomes unresponsive if you edit the plan while it is getting executed |
8899 | InfoScale operations should not become unresponsive even if entire cluster is down |
8636 | Create resiliency group operation fails for HyperV virtual machines if the LUN size is greater than 1 TB |
9018 | Show appropriate error if user generating keytab file does not have enough privileges to update DNS |
8752 | After restarting the gateway appliance, the gateway state remains faulted and the gateway pair in disconnected state |
Table: Issues fixed prior to Veritas Resiliency Platform 2.2 Update 2 (2.2.0.200)
Incident number | Abstract |
|---|---|
7709 | Refresh operation for EMC SRDF enclosure does not work |
7704 | Remove DNS operation fails if DNS customization done by editing resiliency group |
7717 | VLAN pairing for distributed port group gets deleted after upgrade |
8735 | Custom script execution as part of resiliency plan fails intermittently |
8730 | Create resiliency group operation fails with the error: No gateway pair found for the assets |
8661 | Migration fails due to HP 3PAR discovery issue |
8599 | Virtual machines do not get powered on due to missing VLAN configuration after failback |
8240 | Resiliency group creation using VAIO fails due to failure in fetching virtual machine profile from vCenter |
8095 | Network mapping for VLAN gets deleted after upgrade |
8094 | Web UI performance slow after upgrade |
8093 | After upgrade to 2.1, VMware migration fails with the error: Invalid technology workflow |
8074 | Create resilience group operation with Resiliency Platform data mover fails with not enough space available error, even tough enough space is available on the data store |
7982 | Orchestration workflow fails due to error in fetching information for VMware |
7861 | Resiliency group using VAIO replication gets created without name if ESX runs out of memory |
7756 | VCS applications in a resiliency group cannot be brought online or taken offline |
6309 | VRP and VIOM disconnected state displayed in the risk section |
6297 | Migration of resiliency group fails with the error: Invalid technology |
6133 | Distributed vSwitch not available after re-adding vCenter |
6092 | Virtual machines on the replicated storage are not included in the disaster recovery configuration |