Please enter search query.
Search <book_title>...
Release Notes
Last Published:
2019-02-05
Product(s):
Resiliency Platform & CloudMobility (3.3.2)
- 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
Configuring resiliency group for remote recovery fails during Add disk task (16245)
While configuring a resiliency group for remote recovery the operation sometimes fails during the Add disk task. This happens because VMware updates the instanceUUID of the virtual machine hosting the Replication Gateway. The instanceUUID discovered by Resiliency Platform does not match the current instanceUUID and hence the task fails.
Workaround:
To fix this, complete the following steps in the order mentioned:
Delete the resiliency group which was unsuccessfully created.
Create a new Replication Gateway pair.
Create a new resiliency group using the above gateway pair.
This issue is applicable when the replication technology used is Resiliency Platform Data Mover and Resiliency Platform Data Mover with VMware VAIO (vSphere APIs for IO Filter) interfaces.