Release Notes
- Release Overview
- System requirements
- Known issues
- General known issues
- A network group becomes faulted if any of its network member is unavailable (VRP-25636)
- HTML format is not supported for large sized reports (VRP-25649)
- RG creation for Virtual machines that replicated by NetApp SnapMirror, fails with error (23189)
- Rehearsal virtual machine Identifier is not same as workload virtual machine Identifier on an upgraded setup (22369)
- Replication becomes inactive after performing the Replace Gateway operation when the gateway has workload's snapshot disks attached (25722)
- Certain links in the help point to an older help version
- Known issues: Recovery from physical environment to virtual machines
- Known issues: Recovery to Amazon Web services (AWS)
- Known issues: Recovery to Azure
- 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 from physical environment to virtual machines
- Known issues: Recovery using third-party replication
- Known issues: NetBackup integration
- A virtual machine backed up by multiple NBU master servers gets mapped with only one master server in the console (7608)
- Resiliency group task name shows TAKEOVER during evacuation (16466)
- Issue with support for restoring of UEFI-enabled virtual machines from Netbackup
- Restoring of virtual machines through Veritas Resiliency Platform may fail under certain conditions
- Known issues: Upgrade
- Replace gateway configuration may not get updated in virtual machine's configuration after Veritas Resiliency Platform is upgraded from 3.3.2 to 3.4 (VRP-25508)
- "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)
- General known issues
- Limitations
- General limitations
- 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
- Limitations: Support for OpenStack configuration
System resource requirements for Resiliency Platform
The amount of virtual CPUs, memory, and disk space that Veritas Resiliency Platform requires are listed in this section.
The minimum configuration that is recommended for a virtual appliance for Resiliency Manager, Infrastructure Management Server (IMS), Replication Gateway, and YUM repository server:
Table: Minimum configurations
Component | Minimum configuration |
|---|---|
Resiliency Manager | Disk space 150 GB RAM 32 GB Virtual CPU 8 |
Infrastructure Management Server (IMS) | Disk space 60 GB RAM 16 GB Virtual CPU 8 |
Replication Gateway | Disk space 40 GB RAM 16 GB Virtual CPU 8 Additional external thick provisioned disk of 50 GB This staging storage is the minimum needed by Replication Gateway Appliance and up to 4 virtual machines can be configured with this default configuration. Additional virtual machines can be configured by extending this staging storage with the size of 12 GB per virtual machine. |
YUM repository server | Disk space 60 GB RAM 4 GB Virtual CPU 2 |
Hosts to be added to Veritas Resiliency Platform:
| Disk space 15 GB RAM 4 GB Dual processor CPU If you are using a single host for multiple purposes, add the disk space and RAM required for each purpose. For example, if you are using a single host as storage discovery host and as application host, then you need to have at least 30 GB disk space and 8 GB RAM. |
Note:
You need to reserve the resources for Resiliency Manager, IMS, and Replication Gateway. It ensures that these resources do not get swapped in case of hypervisors getting overloaded.
If the virtual appliance does not meet the minimum configuration, you get a warning during the bootstrap of the virtual appliance and you are required to confirm if you want to continue with the current configuration.
If you plan not to use the YUM virtual appliance, you need a Linux server with a minimum of 50-GB disk space, to be configured as the repository server. Provisioning for the repository server is optional, it is required to install the Veritas Resiliency Platform patches or updates in the future.
If you want to enable dynamic memory on Hyper-V, make sure that the following prerequisites are met:
Startup memory and minimal memory should be equal to or greater than the amount of memory that the distribution vendor recommends.
If you are using dynamic memory on a Windows Server 2012 operating system, specify Startup memory, Minimum memory, and Maximum memory parameters in multiples of 128 megabytes (MB). Failure to do so can lead to dynamic memory failures, and you may not see any memory increase in a guest operating system.
Even if you are using dynamic memory, the above mentioned minimum configuration should be met.