Release Notes
- Release Overview
- New features and changes in Veritas Resiliency Platform 3.3.2
- Removal of Windows Install Hosts
- Monitoring API support
- Replace faulty or healthy gateway
- Simplified licensing
- Extended In-Guest IOTAP
- Mark Resiliency Group in maintenance mode
- Collect logs from Veritas Resiliency Platform appliances from the user interface
- Service pack delivery mechanism
- Localization support is extended to Chinese language
- Improved user interface
- Separate Security Group for rehearsal and disaster recovery operations
- Introduced new risk signatures
- Using the product documentation
- More information
- New features and changes in Veritas Resiliency Platform 3.3.2
- System requirements
- Fixed issues
- Known issues
- General known issues
- Known issues: Recovery to Amazon Web services (AWS)
- Known issues: Recovery to vCloud
- Migrate or takeover operation may fail due to unavailability of independent disks on the vCloud Director (14639)
- After migrating back, the storage profile selection for the existing virtual machine may be incorrect (16901)
- After migrating back, the IP and MAC addresses assigned to a NIC are displayed incorrect on using Customize Network intent (16458)
- Known issues: Resiliency Platform Data Mover
- Known issues: Resiliency Platform Data Mover used for recovery to on-premises data center
- Known issues: Recovery using third-party replication
- 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)
- Resiliency group task name shows TAKEOVER during evacuation (16466)
- Known issues: Recovery of InfoScale applications
- Known issues: Upgrade
- Upgrade of Replication Gateway fails if a Veritas Replication Set is in stopping state (19976)
- "Asset disk configuration changed" risk with description "New disk is attached to virtual machine" may come for RBT disk after upgrade to 3.3.2.0 (23118)
- Kernel RPM package cannot be recovered if partially installed on VSA during upgrade (22625)
- For VC 6.5, VIB upgrade fails because of ESX maintenance mode (22493)
- New UI alignment is not updated after upgrade in same tab or session (22240)
- False risk of GW is not upgraded popup is shown while performing DR operation after upgrade (22768)
- Limitations
- General limitations
- Limitations: Recovery to AWS
- Limitations: Recovery to vCloud Director
- Limitations: Recovery of physical machines to VMware virtual machines
- Limitations: Recovery of VMware virtual machines to on-premises data center using Resiliency Platform Data Mover
- Limitations: Recovery of VMware virtual machines to on-premises data center using third party replication
- Limitations: Windows hosts for Resiliency Platform Data Mover replication
- Limitations: Localization
Fixed issues
This chapter lists the issues that have been fixed in the Veritas Resiliency Platform 3.3.2 release.
Table: Issues fixed in Veritas Resiliency Platform 3.3.2
Incident number | Abstract |
|---|---|
12946 | DNS customization changes are not updated while editing resiliency group |
19305 | Data availability missing for some resiliency groups after a DR operation |
19885 | Scheduled scan does not clear the risk when the vCenter server is removed and re-added into the IMS |
19859 | IMS disconnected risk does not get resolved immediately after adding new IMS |
19949 | Windows host may appear to be disconnected after migrate back to on-premises data center |
7407 | Some DHCP enabled NICs are not present on Cloud after migrate |
8232 | Sometimes network comes up on only one NIC on virtual machines having multiple NICs |
8326 | Resiliency group details in the console displays stale vCloud virtual machine entries after migrating back a resiliency group to the premises site |
13024 | Recovery data center details are not displayed after upgrade if the disk name is greater than 128 characters |
19818 | Sometimes replication gets stuck after upgrade or restart of Replication Gateway |
5181 | Virtual machine protection using Resiliency Platform Data Mover has a few policy related limitations |
5183 | Data Mover virtual machine in no op mode risk cannot be resolved |
10821 | Newly added Resiliency Manager cannot remove the existing offline Resiliency Manager |