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
Network and firewall requirements
The following are the network requirements for Veritas Resiliency Platform:
Before you use the hostname and the IP address in the Network settings, you need to register them with the DNS server.
The hostname or the IP address which is used for product configuration, should not have multiple entries in the DNS server. For example, the IP address should not be associated with multiple hostnames, or the hostname should not be associated with multiple IP addresses.
Ensure that ports 88 and 750 on DNS server are open for communication with IMS.
In case of recovery to cloud, ensure that port 53 on DNS server is open for bi-directional communication with the cloud data center.
The hostname that you use for a virtual appliance must not start with a digit and must not contain the underscore ( _ ) character.
Veritas Resiliency Platform supports only Internet protocol version (IPV) 4.
If you plan to use the DHCP server, the DHCP server should be in the same subnet where you plan to deploy the product.
The following ports are used for Veritas Resiliency Platform:
Table: Ports used for Resiliency Manager
Ports used | Purpose | For communication between | Direction | Protocol |
|---|---|---|---|---|
443 | Used for SSL communication | Resiliency Manager and web browser | Browser to Resiliency Manager | HTTPS, TLS v1.1+ |
14176 | Used for communication between the Resiliency Manager and Infrastructure Management Server (IMS) | Resiliency Manager and IMS | Bi-directional | HTTPS, TLS v1.1+ |
7001 | Used for database replication | Resiliency Manager and IMS | Bi-directional | TCP with SSL/TLS1.1+ |
389 | Used for communication with LDAP/AD server | Resiliency Manager and LDAP/AD server | Bi-directional | TCP, user provided |
636 | Used for communication with LDAP/AD server | Resiliency Manager and LDAP/AD server | Bi-directional | TCP with SSL/TLS, user provided |
22 | Used for communication between remote host to the appliance klish access | Appliance and the hosts | Bi-directional | TCP |
123 | Used for NTP synchronization | Appliance and the NTP server | Bi-directional | TCP |
14180 | Used for accessing API service | Resiliency Manager and the API service | Bi-directional | HTTS, TLSv1.1+ |
Table: Ports used for on-premises IMS and in-cloud IMS
Ports used | Description | For communication between | Direction | Protocol |
|---|---|---|---|---|
14176 | Used for communication between the Resiliency Manager and Infrastructure Management Server (IMS) | Resiliency Manager and IMS | Bi-directional | HTTPS, TLSv1.1+ |
5634 | Used for IMS configuration | IMS and the hosts | Bi-directional | HTTPS, TLSv1.1+ |
14161 | Used for running the IMS console | Resiliency Manager and IMS | Resiliency Manager to IMS | HTTPS, TLSv1.1+ |
22 | Used for communication between remote host to the appliance klish access Used for remote deployment of the packages on remote UNIX host from IMS | IMS and the hosts | Bi-directional | TCP |
135 | Used for remote deployment on client computer (inbound) | Host and remote Windows hosts | Bi-directional | TCP |
123 | Used for NTP synchronization | Appliance and the NTP server | Bi-directional | TCP |
Table: Ports used for on-premises Replication Gateway and in-cloud Replication Gateway
Ports used | Description | For communication between | Direction | Protocol |
|---|---|---|---|---|
33056 | Used for replication | On-premises virtual machine and Replication Gateway/Storage Proxy | Bi-directional | TCP |
5634 | Used for communication with IMS | IMS and Replication Gateway/Storage Proxy | Bi-directional | HTTPS, TLSv1.1+ |
8089 | Used for replication | in-cloud component and on-premises component | Bi-directional | TCP |
443 | Used for communication between paired Gateways | Paired Gateways | Bi-directional | HTTPS, TLS v1.1+ |
Table: Ports used for target Gateway in resync operation
Ports used | Description | For communication between | Direction | Protocol |
|---|---|---|---|---|
67 | BOOTP server | Target Gateway enabled with DHCP role and physical host | Uni-directional | UDP |
68 | BOOTP client | Target Gateway enabled with DHCP role and physical host | Uni-directional | UDP |
69 | TFTP protocol | Target Gateway enabled with PXE role and physical host | Uni-directional | TCP/UDP |
Table: Ports used for virtual machines
Ports used | Description | For communication between | Direction | Protocol |
|---|---|---|---|---|
22 | Used for communication between remote host to the appliance klish access Used for remote deployment of the packages on remote UNIX host from IMS | IMS and the hosts | Bi-directional | TCP |
5634 | Used for communication with IMS | IMS and the hosts | Bi-directional | HTTPS, TLSv1.1+ |
33056 | Used for replication | On-premises virtual machine and Replication Gateway | Bi-directional | TCP |