You are on page 1of 32

RELEASE NOTES

EMC RecoverPoint® for Virtual Machines

Release 4.3

Release Notes
302-001-907
REV 10

December, 2016

These release notes contain information about release 4.3 and service pack and patch
releases of EMC RecoverPoint for Virtual Machines. Topics included in the document:
◆ Revision history........................................................................................................ 2
◆ Product description.................................................................................................. 3
◆ Product features....................................................................................................... 4
◆ Environment and system requirements................................................................... 16
◆ Known problems and limitations ............................................................................ 17
◆ Documentation ...................................................................................................... 30
◆ Software media, organization, and files.................................................................. 30
◆ Installation and Upgrade ........................................................................................ 30
◆ Troubleshooting and getting help ........................................................................... 31

EMC RecoverPoint for Virtual Machines 4.3 Release Notes 1


Revision history

Revision history
The following table presents the revision history of this document:

Revision Date Description

10 December, 2016 Release of RecoverPoint for Virtual Machines


4.3.1.4. Added bug fixes and known issues.

09 August, 2016 Release of RecoverPoint for Virtual Machines


4.3.1.3. Added new features.

08 July, 2016 Release of RecoverPoint for Virtual Machines


4.3.1.2. Added bug fixes.

07 April, 2016 Release of RecoverPoint for Virtual Machines


4.3.1.1. Added bug fixes.

06 February, 2016 Release of RecoverPoint for Virtual Machines


4.3.1. Added fixed bugs.

05 December, 2015 Added upgrade information.

04 December, 2015 Release of RecoverPoint for Virtual Machines


4.3.0.1. Added fixed bugs

03 August 18, 2015 Updated scale and performance table.

02 August 10, 2015 Added limitations.

01 July 14, 2015 Release of RecoverPoint for Virtual Machines


4.3.

2 EMC RecoverPoint for Virtual Machines 4.3 Release Notes


Product description

Product description
EMC RecoverPoint for Virtual Machines 4.3 is a hypervisor-based, software-only data
protection solution for protecting VMware® virtual machines.
RecoverPoint for VMs enables both local and remote replication, allowing recovery to any
point-in-time. RecoverPoint for VMs consists of a VMware vSphere Web Client plug-in, a
RecoverPoint write-splitter embedded in the ESX hypervisor enabling replication from any
storage type to any storage type, and a virtual appliance integrated in the VMware ESXi
server environment.
An EMC Simple Support Matrix (ESSM) on E-Lab™ Navigator
https://elabnavigator.EMC.com serves the RecoverPoint product family.
Table 1 on page 3 identifies the build and size of the RecoverPoint ISO image associated
with the 4.3 releases.

Table 1 RecoverPoint for VMs release, build, and ISO image size

Release Build ISO image size

4.3.1.4 rel4.3.SP1.P4_h.282 1.01 GB

4.3.1.3 rel4.3.SP1.P3_h.269 1.01 GB

4.3.1.2 rel4.3.SP1.P2_h.255 1.01 GB

4.3.1.1 rel4.3.SP1.P1_h.192 1.01 GB

4.3.1 rel4.3SP1_h.152 1.01 GB

4.3.0.1 rel4.3_c.122 0.91 GB

4.3 rel4.3_c.112 0.91 GB

Scale and performance information is provided in the EMC RecoverPoint for Virtual
Machines 4.3 Scale and Performance Guide, available on EMC Online Support.

EMC RecoverPoint for Virtual Machines 4.3 Release Notes 3


Product features

Product features
This section lists the product features and changes of RecoverPoint for VMs 4.3.

New features and changes for release 4.3.1.4


This section lists the new features and changes in RecoverPoint for VMs 4.3.1.4.
◆ Fixed problems
Table 2 on page 9 lists the problems fixed in this release.
RecoverPoint for VMs continues to support the VAIO splitter in 4.3.1.4.

New features and changes for release 4.3.1.3


This section lists the new features and changes in RecoverPoint for VMs 4.3.1.3.
◆ IO Filter splitter

• The IO Filter splitter for RecoverPoint for Virtual Machines uses the VMware
APIs for IO filtering (VAIO) for capturing protected virtual machines’ IO writes
and is officially signed by VMware for “VMwareAccepted” level certification.
• IO Filter splitter supports all functionalities of RecoverPoint for VMs,
excluding support for raw device mapping (RDM).
• To request additional information and enable IO Filter splitter, use the
following mailing list: io.filter.request.rp4vms@emc.com.

New features and changes for release 4.3.1.2


This section lists the new features and changes in RecoverPoint for VMs 4.3.1.2.
◆ Network Configuration (Re-IP) Documentation TCE
The network configuration procedures in the EMC RecoverPoint Administrator’s Guide
have been expanded, illustrated, and revised for better understanding.
◆ Fixed problems
Table 3 on page 10 lists the problems fixed in this release.

New features and changes for release 4.3.1.1


This section lists the new features and changes in RecoverPoint for VMs 4.3.1.1.
◆ Deployer improvements
• In the Create cluster wizard, when selecting a datastore for the repository volume,
VVol-managed datastores will not be displayed in the list of datastores.
• In the Connect clusters wizard, when configuring the gateway of the cluster to
connect to, all currently configured gateways are displayed.
◆ Network configuration improvements

4 EMC RecoverPoint for Virtual Machines 4.3 Release Notes


Product features

• The network configuration settings can now be entered directly through the plugin
GUI, for a specific VM in a consistency group copy.
• When importing a new network configuration to a group copy or a RecoverPoint
system, a message is now displayed to the user when the import action is
successfully applied.
◆ Shadow VM naming convention change
The shadow VM naming convention has changed to enable easier identification:
• Old format: .<VM_Name>.recoverpoint
• New format: rp.<VM_Name>.shadow
The naming convention of existing shadow VMs is not effected when upgrading to
4.3.1.1.
◆ Fixed problems
Table 4 on page 11 lists the problems fixed in this release.

New features and changes for release 4.3.1


This section lists the new features and changes in RecoverPoint for VMs 4.3.1.
◆ Improved deployment flow using the new RecoverPoint for VMs Deployer:
RecoverPoint for VMs 4.3.1 has a new deployment tool that provides an easier
installation experience, including:
• Easy navigation from the Deployer main page to all available actions including
installing and connecting vRPA clusters and modifying network configuration
• Clear vRPA cluster status overview through the landing page cluster topology view
• Pre-deployment validations check environment compatibility for RecoverPoint for
VMs deployment providing auto-fixes when possible, or guidelines for resolving
issues.
• No unmonitored manual steps. Splitter installation and iSCSI configuration are
moved to a new post-deployment ESXi cluster registration step in the RecoverPoint
for VMs plug-in.
For more information, limitations and environment and system requirements refer to
the EMC RecoverPoint for Virtual Machines 4.3.1 Installation and Deployment Guide.
Upgrading from 4.3.0.x to 4.3.1 is non-disruptive. The upgrade is performed using the
Deployment Manager, available as part of the Upgrade and Maintenance Kit.
◆ Deployment REST API
New methods and resource paths have been added to the WADL. The deployment
REST API is documented in the RecoverPoint for VMs 4.3.1 Deployment REST API
Programming Guide.
◆ Enhancements to the RecoverPoint for VMs plug-in
• Registering ESXi clusters

EMC RecoverPoint for Virtual Machines 4.3 Release Notes 5


Product features

Registering ESXi clusters is performed in the RecoverPoint for VMs plug-in using
the Administration > vRPA Clusters > Register ESXi Clusters tab. During registration,
the RecoverPoint for VMs splitter is automatically installed on all of the ESXi hosts
of the registered ESXi clusters.
RecoverPoint for VMs performs troubleshooting and detects connectivity issues
between the ESXi cluster and the vRPA cluster. Some of these issues can be fixed
automatically.
• vRPA log collection
In support scenarios, splitter and vRPA logs can now be collected using the
Administration > vRPA Clusters > Log Collection tab.
• VC credentials management
vCenters can now be registered at a vRPA cluster using the Administration > vRPA
Clusters > vCenter Servers tab and vCenter registration can now be managed using
the Administration > vCenter Servers > Registration tab.
• vRPA clusters conflict management
If the settings of the vRPA clusters in a system differ, a pop-up dialog box is
automatically displayed allowing the user to select the vRPA cluster with the
correct system settings.
◆ Enhanced Multi-Site protection
RecoverPoint for VMs now supports up to five vRPA clusters per system, enabling up to
five concurrent copies of the same consistency group, including the production copy.
◆ VxRAIL support
RecoverPoint for VMs 4.3.1 is supported by the VxRAIL Bretton Woods 3.0
hyper-converged infrastructure appliance.
◆ VSAN 6.0, 6.1 and 6.2 support
RecoverPoint for VMs supports protecting VMs, repository and journal volumes on
VSAN 6.0, 6.1, and 6.2.
◆ Virtual volumes (VVOLs) qualification with vVNX and VMAX3
RecoverPoint 4.3.1 is qualified to support replicating VMs residing on VMware VVols.
◆ Fixed problems
Table 5 on page 12 lists the problems fixed in this release.

New features and changes for release 4.3.0.1


This section lists the new features and changes in RecoverPoint for VMs 4.3.0.1.
◆ VxRAIL support
RecoverPoint for VMs 4.3.0.1 is supported by the VxRAIL 1.1.1 hyper-converged
infrastructure appliance.
◆ Fixed problems
Table 6 on page 14 lists the problems fixed in this release.

6 EMC RecoverPoint for Virtual Machines 4.3 Release Notes


Product features

New features and changes for release 4.3


This section lists the new features and changes in RecoverPoint for VMs 4.3.
◆ Multi-cluster support
RecoverPoint for VMs 4.3 now supports up to three copies (including the production
copy) per consistency group and up to three vRPA clusters per RecoverPoint for VMs
system, enabling concurrent local and remote replication.
◆ VC licensing
RecoverPoint for VMs licenses are now per vCenter Server (as opposed to per vRPA
cluster), enabling multiple vRPA clusters connected to a single vCenter Server to share
the same license.
◆ Deployment Automation with REST API
Enterprise users and service providers can use the new REST API to perform the
following system deployment actions automatically:
• Download RP4VMs OVA image files.
• Import OVA image files via vCenter wizard.
• Configure vRPA networking (including IP address and connectivity to ESXi).
• Open web interface and configure vRPA cluster in DM flow.
• Pair between two clusters using credentials.
• Receive operation status.
• Register vCenter plug-in.
• Install ESXi splitter without rebooting the ESXi.
◆ Orchestration
• Disk provisioning of copy VMs
When creating consistency groups users can now select the type of VMDK to use
for the copy VMs. Possible options are thin, thick, or same as source. Default is
same as source.
• Expansion of VMDKs
VMDKs can now be expanded without loosing the journal or causing a full sweep
for the entire consistency group in cases where users want to add additional space
to protect the VMDK.
• Exclusion of VMDKs
VMs containing VMDKs that are shared or non-persistent can now be replicated, as
such VMDKs can now be excluded from replication.
• Automatic replication of VMDKs
VMs can now also be configured to include newly added VMDKs from replication
automatically.
• Adding a VMDK without journal loss

EMC RecoverPoint for Virtual Machines 4.3 Release Notes 7


Product features

Replication sets can now be added to a consistency group without causing journal
loss or a full sweep.
• Replicating VM hardware changes
Each production VM’s hardware resources (such as CPU, memory, etc.) can now
automatically be replicated to its copy VM during image access.
◆ Start-up sequence
Users can now define the power-up order of VMs in a consistency group (and
consistency groups in a group set) as image access is enabled when testing a copy,
failing over, or recovering production. VMs can also be marked as critical to stop the
start-up sequence if that VM doesn't power up.
• User prompts
You can now define messages that must be acknowledged by RecoverPoint for VMs
administrators before and after each VM’s power-up.
• User scripts
You can now save and run scripts before and after powering on VMs by defining an
external host per vRPA cluster in a RecoverPoint for VMs system.
• Networking enhancements
All of the networking details of the VMs in a RecoverPoint for VMs system, or the
VMs at a copy in a RecoverPoint for VMs system, can now be imported and
automatically applied, or exported for future use.
◆ Application-consistent bookmark support via VSS
Application-consistent bookmarks can now be created on every VMware-based virtual
machine in its own consistency group that uses VSS and is running Windows 2008 or
2012 R2.
◆ Scale and performance improvements
RecoverPoint for VMs 4.3 supports increased scale and performance. Refer to the EMC
RecoverPoint for VMs 4.3 Scale and Performance Guide for more information.
◆ Getting started wizard
A wizard is now automatically displayed after the initial installation of a RecoverPoint
for VMs system to guide users through the process of licensing and registering their
RecoverPoint for VMs system and enabling support. This wizard is also displayed
when adding the first license using the main RecoverPoint for VMs Management >
Administration > Licenses screen.
◆ Recovery activity reports
For each recovery activity a detailed report can now be displayed including the final
status of each step, as well as the overall status, of the recovery activity.
◆ EMC Storage Analytics (ESA) supports RecoverPoint for VMs
◆ Internationalization and localization
• The RecoverPoint for VMs plug-in for the vSphere Web Client is now available in
English, Chinese, Japanese, Korean, German, and French.

8 EMC RecoverPoint for Virtual Machines 4.3 Release Notes


Product features

• The following documents are now available in English, Chinese, Japanese, Korean,
German, and French:
– EMC RecoverPoint for Virtual Machines 4.3 Release Notes “New features and
changes” section
– EMC RecoverPoint for Virtual Machines 4.3 Installation and Deployment Guide
– EMC RecoverPoint for Virtual Machines 4.3 Quick Start Installation Poster
◆ Fixed problems
Table 7 on page 14 lists the problems fixed in this release.

Fixed problems
Table 2 on page 9 list the problems fixed in RecoverPoint for VMs 4.3.1.4.
Table 3 on page 10 list the problems fixed in RecoverPoint for VMs 4.3.1.2.
Table 4 on page 11 list the problems fixed in RecoverPoint for VMs 4.3.1.1.
Table 5 on page 12 list the problems fixed in RecoverPoint for VMs 4.3.1.
Table 6 on page 14 lists the problems fixed in RecoverPoint for VMs 4.3.0.1.
Table 7 on page 14 lists the problems fixed in RecoverPoint for VMs 4.3.

Table 2 Problems fixed in RecoverPoint for VMs 4.3.1.4 (page 1 of 2)

Issue number Product feature Problem summary

128904 ESX splitter The kdriver crashes after unprotecting or deleting a volume.

130014 ESX splitter kdriver.log.running_vms.continues uses excessive amount of space, due to a large amount of
VMs running on the ESX, causing the scratch disk free to run out of space.

136557 ESXsplitter A shortage in memory may cause kdriver to crash and the ESX server to fail starting up.

137356 Image access During image access, the network configuration may fail or override the adapter
configuration/MAC address. As a result, the replica VM is loaded with incorrect network
configuration.

134618 Replication When created, the shadow VM is located outside the replica folder instead of inside the replica
folder.

131616 Replication The actions recover production, fail over or disable image access might fail, causing the
consistency group to be in an error state.

131515 Security Possible security vulnerability.

133782 Security Possible security vulnerability.

133792 Shadow VM An error during the shadow's creation causes the shadow VM to appear outside the replica's
folder.

127750 Snapshot Snapshot consolidation fails, and the user is unable to access desired images by specifying a
time or bookmark name to search (RecoverPoint > Protection > Manage Protection > Journal tab).

EMC RecoverPoint for Virtual Machines 4.3 Release Notes 9


Product features

Table 2 Problems fixed in RecoverPoint for VMs 4.3.1.4 (page 2 of 2)

Issue number Product feature Problem summary

129362 Snapshot The following error message can appear when:


◆ Choosing a snapshot from the image list on a Group Set - the error message appears
although the snapshot is still in the list.

◆ Requesting Image Access based on a given time (approximate query) - the error message
appears although the snapshot was not even selected from the list.

Error message: “ERROR: Specified image removed from journal.”


In both cases, the image that is selected might not be the best point-in-time image available.

135957, System The order of the production VM's network interfaces changes when the user has virtual
136268, distributed switches. The network interfaces are randomly allocated. This can happen during
137550 Consistency Group creation, image access, failover, and failback. In addition, the network may
not be not be configured for the replica if there is no network with the same name if there is a
matching ETH device on the remote ESX.

131445 vCenter The VM is protected and replicating, but the following error continues to stream in the vCenter:
"ERROR - RegisterVMAction Failed.
com.emc.recoverpoint.connectors.actions.infra.ActionFailedException: Invalid datastore path
'[CMP-DR-vRPA-Copy2] hcnsrvr.copy/hcnsrvr.copy.vmx'. ERROR - RegisterVMAction Failed."

Table 3 Problems fixed in RecoverPoint for VMs 4.3.1.2 (page 1 of 2)

Issue number Product feature Problem summary

129319 GUI When collecting logs from the RPA, the time displayed in the Collection Period is different from
the actual time. As a result, log collection from the RPA fails if you want to collect a log until the
current time, or the current time minus the timezone, for time zones from GMT -1 to -12.

130001 GUI If upgrading using the Deployment GUI, and previous tweaks (modifications) were done to the
configuration, the tweaks are reset and are not reused after the upgrade.

131543 GUI On the Administration tab when selecting a vRPA cluster, on the vRPA System tab, in the Network
Configuration area of the screen, you are unable to export the network configuration for all
protected VMs in the selected cluster.

131820 GUI Cannot upload the ISO for upgrade from the Deployment GUI.

131962 NDU Installing a non-disruptive upgrade (NDU) package fails if a user pauses the consistency group
link between the site being upgraded and a different site.

129142 RecoverPoint In RecoverPoint for VMs 4.3.1 and 4.3.1.1, the RecoverPoint for VMs plugin for vCenter does not
for VMs plugin display in vSphere web client release 5.1.

129565 RecoverPoint If any ESX contained within the vCenter does not have a "serviceInfo” object, that checks if there
for VMs plugin is a splitter installed, then the RecoverPoint plugin will stop functioning and replication will stop.

129595 Replication After replicating a VM, you may receive a warning in the vCenter indicating a MAC conflict
between VMs.

129875 Replication Replicating production VMDKs which are thick eager zero are, by default, lazy zero on the replica
side. To change the default, contact EMC Customer Support.

129794 Replication After excluding a volume (disk) from protection, replication may stop, and the consistency group
will not resume its data transfer.

130081 Replication A REST request to replicate a VM, without the array ID parameter, causes reboot regulation.

129674 Security Possible security vulnerability

129663 Shadow VM While trying to create a shadow VM, protecting (replicating) a VM might fail, or failover might not
occur.

10 EMC RecoverPoint for Virtual Machines 4.3 Release Notes


Product features

Table 3 Problems fixed in RecoverPoint for VMs 4.3.1.2 (page 2 of 2)

Issue number Product feature Problem summary

129937 System Consistency Groups are in a state of Error when the RPA message-ID reaches its maximum value.

130996 System You are unable to perform any consistency group operations if any of the journals are not
provisioned.

131995 Upgrading When upgrading the splitters, the Consistency Groups might enter a state of Error.

129229 vCenter Linked In RecoverPoint for VMs 4.3, 4.3.0.1, 4.3.1, and 4.3.1.1, when using vCenter Server in linked
Mode mode, an incomplete list of VMs may appear in the Protection > Virtual Machines screen of the
RecoverPoint for VMs plugin.

131837 VM Powering If you have a consistency group with several VMs and you power off a VM, data transfer might
off stop, and the consistency group might move from the Active state to a state of "Paused by the
system", or "Error".

130370 VMware Due to a VMware issue with reload configuration, the replica VM is loaded with the shadow
memory reservation instead of the memory reservation allocated to the source VM.

Table 4 Problems fixed in RecoverPoint for VMs 4.3.1.1

Issue number Product feature Problem summary

128526 CLI Users with admin privileges can now use the update_vcenter_server_registration CLI command
to change the registration details of a vCenter Server.

126421 Deployer When creating a vRPA cluster using the RecoverPoint for VMs Deployer, if you select VVol
datastores while using a vSCSI splitter, virtual repository creation fails and the message “Error:
Insufficient disk space on datastore.” is displayed.

127557 Deployer vRPA clusters cannot be deployed if the NTP server is defined as a host name.
(127556)

129045 ESX registration In RecoverPoint for VMs 4.3 and 4.3.1, when storage adapters do not exist on an ESX that has
been registered at a vRPA cluster in RecoverPoint, the RecoverPoint for VMs plugin and the
RecoverPoint for VMs Actions menu are not displayed in the vCenter Web client hosting the ESX.

128434 Image access RecoverPoint for VMs is unable to create a shadow VM for a copy VM if there is a device
(128921) configured on IDE0:0 of its corresponding production VM.

127174 NDU When upgrading a multi-site environment from RecoverPoint 4.3.0.1 to RecoverPoint 4.3.1,
upgrading only one vRPA cluster may result in a settings conflict. Upon completing the DM
wizard, you will receive the following error message: “Error: conflict in setting - please resolve”.

129182 Protecting VMs In RecoverPoint for VMs 4.3 and later, when protecting VMs with a large number of VMDKs,
replication may not start.

128434 Shadow VMs In version 4.3.1, RecoverPoint for VMs is unable to create a shadow VM for a copy VM if there is a
device configured on IDE0:0 of its corresponding production VM.

127333 vCenter If a user manually copies a VM to a different vCenter Server and tries to power it on, vCenter
displays a message asking the user whether he copied or moved the copied VM. If the user
selected the move option, the copied VM can be added to a group and replication will start when
the group is created but when the user tries to perform any operations on this group the
message “Error: The same volume has been added at more than one RPA cluster.” is displayed
and all operations on the group are blocked.

129215 VMware NSX If a user defines NSX security group rules on a VM and manually selects it as the target VM while
(129218) protecting a VM, fails over, or recovers production, the copy VM will be disassociated from the
security group.

128589 VSAN When creating a repository or journal larger than 254 GB in a given VSAN cluster, the operation
fails with the following error: “WARNING: At least one Journal volume that was supposed to be
provisioned - failed.”

EMC RecoverPoint for Virtual Machines 4.3 Release Notes 11


Product features

Table 5 Problems fixed in RecoverPoint for VMs 4.3.1(page 1 of 2)

Issue number Product feature Problem summary

120486 Adding a Automatically provisioning a journal for a disabled consistency group may enable the group,
journal causing a full sweep.

124651 Auto When exporting the auto registration table to a .csv file, the table may display incorrectly.
registration

120584 Automatic No error message is issued when a new network configuration is imported with one or more
network invalid VM IP addresses.
configuration

120708 Automatic When using the Administration > vRPA Clusters > Networking screen to export and then import a
network network configuration at the system level with an empty Adapter ID field, a zero is placed in the
configuration Adapter ID field in the CSV file, causing an error in the automatic network configuration process,
and the network settings in the CSV file are not applied upon import.

123369 boxmgmt Using boxmgmt on cluster control to change the iSCSI IP addresses of multiple vRPAs in the clus-
ter may fail.

118380 Configuring a A VM’s datastore size may appear as 0 bytes in the Configure copy settings step of the Protection
copy wizard.

122004 Dashboard System health data will not be displayed in the RecoverPoint for VMs plugin.

120583 Datastores You may not be able to copy the VIB file to the datastore and the ESXi splitter will not deploy. You
will receive the following error: “Exception. Failed deploying splitter on all ESXs. Failed to deploy
splitter on some of the ESXs.”

122144 Deployment You will not be able to run the Deployment Manager if the Deployment Manager .exe file path is
Manager too long.

121039 Deployment When using the RecoverPoint for Virtual Machines 4.3 Deployment REST API, the deployment
REST API server may return the message “Failed validation - found duplicate IP.” This occurs when an IP
address is used more than once, for instance when the router is acting as the gateway, DNS,
and/or NTP; vCenter is acting as NTP and DNS server; or DNS and NTP are configured on the same
server.

120726 ESXi After an ESXi disaster, the consistency group may enter an error state. This may result in a full
sweep.

126366 ESXi splitters In RecoverPoint for VMs 4.3.0.1, putting an ESXI into maintenance mode may result in a full
126566 sweep.

118161 GUI In the Modify link policy dialog, the values of Dynamic by Latency automatically round to the
nearest millisecond. The maximum value of Dynamic by Throughput is 76800 for both KB and
MD. If you enter a value greater than 76800, the value automatically resets to 76800.

120447 GUI The activity report for image access of a group set displays incorrectly.

121140 GUI You may receive the message “There are no recovery activities to display.” even though the
recovery activities are displayed. You will not be able to select the next action from the
drop-down list.

121117 Image access After enabling image access, disabling image access, and disabling the consistency group, the
consistency group will be in error state when you try to enable it.

117139 KVSS After running KVSS, the command vssadmin List Writers may show writers involved in the
125446 previous KVSS command in Error state.

120648 MPI MPI logs are not available in the current version of RecoverPoint for Virtual Machines.

119055 NDU During a non-disruptive upgrade, you may not be able to recover data.

12 EMC RecoverPoint for Virtual Machines 4.3 Release Notes


Product features

Table 5 Problems fixed in RecoverPoint for VMs 4.3.1(page 2 of 2)

Issue number Product feature Problem summary

120962 Protecting VMs When protecting a VM or creating a consistency group, you may get a settings conflict in the sys-
tem. You will receive the following error: “Error: Illegal settings - too many replication set names.”

40235 Removing You cannot remove a link between two clusters as long as a consistency group copy on that
cluster cluster is linked to a copy of the same consistency group on any other cluster.

120575 Replication After a long initialization, if more data is received than the vRPA can handle replication will be
paused by system. When replication resumes there will be a short initialization.

120667 Replication In rare cases, after an initialization of more than one consistency group, the replication process
may be paused by system.

118756 System After installing the ISO, the RPA may enter a reboot regulation and cannot be attached to the
cluster.

119766 System In rare cases, replication of the RPAs containing replica copies is unresponsive. After ~20 min-
utes, replication can be restarted or killed by the memory manager. This causes a short init. The
consistency groups on the affected RPA may be affected and unable to run control flows. The like-
lihood of this bug increases in image access mode or during TSP write.

119949 System After a fatal journal error, it is possible that the RPA will enter reboot regulation. In this case, the
only solution is to disable the consistency group and then to enable it again. This will cause a full
sweep, but after the full sweep, replication should continue normally, and the copy should be
fully synchronized with the source.

121383 System The GUI and CLI may be slow or unresponsive.

122034 System If the production copy becomes corrupted, you must recreate it before recovering production.

122232 System If transfer is paused during the initialization of a synchronous replication link, the system may re-
start the entire initialization 0%.

122576 System When attempting to remove a replication set from a consistency group, where the replication set
contains a volume that cannot be seen by RecoverPoint for VMs, the consistency group will enter
an error state and replication will be paused by system.

123776 System When adding volumes to a consistency group during the initialization, there may be journal loss
and a full sweep.

125022 System After protecting a new VM, the consistency group may be paused by system or in error state and
initialization does not start. You may receive one of the following warnings:

126243 System If you have not defined a primary or secondary DNS, you may not be able to modify settings.

125451 System After un-protecting or deleting a volume, the ESXi splitter may crash.
126540

120685 Upgrading to After upgrading a RecoverPoint for VMs splitter from 4.2 to 4.3, you may receive errors indicating
RecoverPoint that the vRPA does not see user volumes.
for VMs 4.2

121320 VMDK After including a previously excluded production VMDK that a copy VMDK has previously been
exclusion created for, and enabling image access to a point in time at which the specified VMDK was
excluded, the excluded VMDK may still be attached to the copy VM after failover or recover
production.

120336 vRPA restart After restarting the primary vRPA, you may receive the following error: “RPA1 in Cluster1 can't ac-
cess repository volume”.

121837 vSphere plug-in The RecoverPoint for VMs plugin may be missing from vSphere.

EMC RecoverPoint for Virtual Machines 4.3 Release Notes 13


Product features

Table 6 Problems fixed in RecoverPoint for VMs 4.3 P1

Issue number Product feature Problem summary

123807 ESXi If an ESXi is in maintenance mode when you add ESXis to the cluster, the splitter will not be
installed on the ESXi and consistency groups will not be able to replicate.

120881, Image access You may not be able to enable image access in the plug-in. Either you will receive the following
122783 error: “ERROR: Cannot enable image access: One of the virtual network devices is not visible by
the ESX”, or it will appear as though image access was enabled when really it did not enable.

121041 Large scale In a large scale environment, after rebooting the ESXi splitter, it may become paused by system
environment for a few minutes.

121785, System After protecting a VM, initialization does not start.


123384

121856 System During replication, vRPAs may become inaccessible causing replication to be paused by system.

122006 System In rare cases, after creating a new consistency group, if you are unable to create journal volumes
either because there is not enough space in the resource pool or because the amount of free
space listed is out-of-date, the RPA may detach from the cluster.

122634 System IO throttling may not work in RecoverPoint for VMs.

120960 vCenter If you update the vCenter credentials while performing other RecoverPoint for VMs actions, you
may see a delay in RecoverPoint activities.

121945 vCenter If you are running vCenter 6.0, the RecoverPoint for VMs plugin may not appear in the vSphere
Web Client.

122494 vCenter When using dvSwitches, the RecoverPoint for VMs plug-in may not display your clusters. You will
not be able to protect VMs in a cluster that is not displayed.

Table 7 Fixed problems in RecoverPoint for VMs 4.3 (page 1 of 2)

Issue Number Product Feature Problem Summary

44484 REST API When retrieving REST API events using https://IP/fapi/rest/4_1/events, they are returned
sorted by uniqueId rather than time. Since a maximum of 9000 events is listed, the most recent
and relevant events may not be displayed.

116903 Security A buffer overflow in of the functions of glibc that might have caused a vulnerability during an
internal code audit has been fixed. There is no evidence that this vulnerability can be exploited
on RecoverPoint. Nonetheless, the vulnerable GNU C Library has been replaced.

119001 VMDKs After automatically creating a new VMDK on the non-production copy or automatically recreating
a deleted VMDK the VMDK cannot be accessed by the vRPA. You will not be able to perform a
stun action on the VM.

119011 Creating new After automatically creating a new VMDK on the non-production copy or automatically recreating
VMDKs a deleted VMDK the VMDK cannot be accessed by the vRPA. A stun action will not be possible on
the VM.

43838 Powering on When image access is enabled, and a change is made in the journal (such as deleting a snap-
Shadow VM shot) image access is disabled, if you power on the Shadow VM before the system automatically
powers it on, it causes an invalid configuration. The consistency group will stop replicating and
the vRPA will repeatedly issue commands to the vCenter to fix the problem and fail. Note that the
shadow VM is for internal use only and unsupported use may lead to undesirable results.

43514 Protection errors When a VM is on an ESXi host that does not have a splitter installed, and you try to protect it, the
consistency group is created, but the link is in an error state. If the VM was powered off before
protecting it, you cannot power it on.

41498 VM protection When you run the Protect VM Wizard by right-clicking on the VM that you want to protect, when
the wizard is finished, there is no indication that the42 consistency group has been created
successfully.

14 EMC RecoverPoint for Virtual Machines 4.3 Release Notes


Product features

Table 7 Fixed problems in RecoverPoint for VMs 4.3 (page 2 of 2)

Issue Number Product Feature Problem Summary

42546 VM protection When the “Protect VM wizard” is completed, replication automatically starts without giving you
the option to create the consistency group without beginning replication.

42787 Creating Creating a repository volume fails due to a SCSI error.


repository

42575 vRPA When protecting a VM that has an attached CD-ROM or floppy device and the copy VM is on an-
component error other ESXi, or if the VMware Tools installation task is still running, the following error is dis-
message played repeatedly:
“Deploy OVF template <Cluster Name>. A component of the virtual machine is not accessible on
the host.”

43013 vRPA In some cases there may be performance issues. Refer to the RecoverPoint for Virtual Machines
performance Scale and Performance Guide.
42862 vSphere Web When a fatal error occurs in the vSphere plug-in, you will not see the error log.
Client

43672 Protection error In rare cases, when you protect a VM, the VM attempts to auto-provision a journal volume of a
specific size, the system selects a datastore with less available capacity than the specified
journal size. In this case, VM protection fails and an “insufficient space” error is displayed in the
vCenter Server.

43816 Consistency Following a disaster, you may not be able to replicate or to create consistency groups for half an
group error hour.

38728 vRPA When there is a disconnection between vRPAs and the vCenter (either because the vCenter is
connectivity down, or there is a connectivity issue) a vRPA reboot removes the VMDKs from the SAN view.
This may cause connectivity issues between the vRPA and one or more VMDKs.
Workaround: Fix the connectivity issue.

43884 GUI When no consistency groups exist in the system, the Consistency Group Transfer Status widget
of the Dashboard, displays the “Loading vRPA Cluster Settings” progress bar instead of the wid-
get contents.

43196 Adding a VMDK When adding a non-persistent VMDK to an existing consistency group, the VMDK is automati-
cally replicated, which may cause an inconsistenc.
Workaround 1: Replace the non-persistent VMDK with a persistent VMDK of the same size and
on the same port.
Workaround 2: Unprotect the VM, remove the non-persistent VMDK and re-protect the VM.

119193 GUI/FAPI In rare cases, after the Linux management server crashes, the GUI and FAPI become
unresponsive.
Workaround: Kill the problematic process in tomcat or reboot the vRPA.

EMC RecoverPoint for Virtual Machines 4.3 Release Notes 15


Environment and system requirements

Environment and system requirements


RecoverPoint for VMs 4.3 is fully customer-installable.
Table 8 General Environmental Requirements

Description Requirement

EMC RecoverPoint for Virtual Machines Version 4.3

VMware vCenter and ESX servers Release 5.1.1 (5.1 Update 1) or later with at least one
registered vSphere 5.1, 5.5 or 6.0.

Network Infrastructure 4 virtual networks (LAN, WAN, 2 software iSCSI adapter per
ESXi node with VMKernel ports)

End of service dates and extended support


EMC has a standard software support duration policy which specifies that a major version
will reach End of Service Life (EOSL) a minimum of 36 months following the General
Availability (GA). EOSL may be followed by an Extended Support period during which
customers may elect to pay an additional fee to extend their support coverage rather than
migrate to a current software version.
Once a software product reaches EOSL, EMC Technical Support is no longer available
under base support/maintenance agreements. Customers interested in uninterrupted
support must upgrade to a current release or contract for Extended Support.
EMC Online Support site contains a list of documents that provide end-of-service and
extended support information for EMC software and hardware products.
To access these documents on EMC Online Support:
◆ Go to EMC Online Support, at http://support.emc.com.
◆ Go to Support by Product pages and search for RecoverPoint for VMs.
◆ In the product page, scroll down the left and click Release and End of Life Dates.
◆ Find the EMC Software Release and End of Service Life Notifications document in the
results.
◆ Open it and search for your product and version.
This document provides EOSL dates for EMC software products.
This policy is in effect for select releases and will be phased in as new versions are
made available. In cases where a software release is not eligible for Extended
Support, the previous policy, which specifies product support and maintenance under
Continuous Coverage Product Maintenance (CCPM), terms still apply.

16 EMC RecoverPoint for Virtual Machines 4.3 Release Notes


Known problems and limitations

Known problems and limitations


This section lists the limitations and known problems in the current RecoverPoint for
Virtual Machines release.
All information regarding interoperability limitations is available on E-Lab Navigator, at
https://elabnavigator.EMC.com

Limitations
RecoverPoint for VMs has the following limitations:
◆ RecoverPoint for VMs journals and repository VMDKs cannot reside on VMware Virtual
Volumes datastores.
◆ vRPA clusters cannot be deployed if the NTP server is defined as a host name. The NTP
server must be defined as an IP address.
◆ RecoverPoint for VMs does not currently support the IPv6 protocol.
◆ All vRPA clusters in a system must have the same number of vRPAs.
◆ User action on shadow VMs is not supported.
◆ RecoverPoint for Virtual Machines does not support CHAP for splitter to vRPA iSCSI
authentication.
◆ RecoverPoint for VMs is supported in environments that use VLAN tagged frames (IEEE
802.1q). vRPAs do not tag the traffic that they send.
◆ RecoverPoint for VMs is not supported in environments that use Layer 2 Quality of
Service protocol for traffic prioritization (IEEE 802.1p).
◆ RecoverPoint for VMs is not supported in environments that use Differentiated
Services Code Point (DSCP) to provide packet classification for Quality of Service
(QoS) management.
◆ RecoverPoint for VMs does not support Network Address Translation (NAT) between
vRPAs. vRPAs require that all other vRPAs in the system be accessible using the
configured IP addresses.
◆ The number of snapshots that can be taken is unlimited. However, when selecting an
image from the list in the Enable Image Access dialog box, a maximum of 1024
snapshots (images) are presented.
◆ RecoverPoint for VMs does not currently support WAN accelerators, unless the device
is specifically supported in the EMC Support Matrix with RecoverPoint. EMC is aware
of configurations in which performance is degraded when using WAN accelerators in
conjunction with RecoverPoint for VMs, such as when enabling compression on both
RecoverPoint for VMs and the WAN accelerator.
◆ Supported CLI commands
• Only the CLI commands in the procedures of RecoverPoint for VMs 4.3
documentation are supported.
◆ The vSphere scratch location must be a permanently available, persistent storage
device.

EMC RecoverPoint for Virtual Machines 4.3 Release Notes 17


Known problems and limitations

◆ RecoverPoint for VMs requires that each ESXi server has a unique hardware UUID.
◆ When replicating a production VMDK that is defined as thick eager zero, the replica
copy VMDK is configured, by default, as thick provisioning lazy zero. To change the
default, contact EMC Customer Support.

Known Problems
Table 9 on page 18 lists the known problems found in RecoverPoint for VMs 4.3 and later.
Where a problem is only relevant to a specific RecoverPoint release, it is noted in the
problem summary.

Table 9 Known problems found in RecoverPoint for Virtual Machines 4.3 and later (page 1 of 12)

Issue Number Product Feature Problem Summary

126819 boxmgmt After removing a cluster through boxmgmt, the UI displays the following error message in a
loop: Failed to execute step.
Workaround: Restart boxmgmt.

132008 boxmgmt In versions 4.3.x, you are unable to change the web certificate using boxmgmt.
Workaround: Run this signed script:
M2VmNmJmYmYzNjg1MzY2ODQ1MmZjYjViZjlhYjc5YmYKdW5saW1pdGVkCm5vdF9yZXN0cmljd
GVk
ClRoZSBpZCBvZiB0aGUgc2NyaXB0IGlzOjEzMjAwOApBZGQgaG9tZS9rb3Mva2FzaHlhL2FyY2hp
dmUvY2xhc3Nlcy9ycHNlcnZlcnMuamFyIHRvIHRoZSBjbGFzc3BhdGggaW4gdGhlIG9zX3NlcnZp
Y2VzLnNoLCB0aGlzIGlzIG5lZWRlZCB0byBjaGFuZ2UgYSBjZXJ0aWZpY2F0ZSBvZiB0aGUgd2Vi
IHNlcnZlcgpFbGkgUGVyc2luCnNlZCAtaSAtZSAicywvaG9tZS9rb3Mva2FzaHlhL2FyY2hpdmUv
Y2xhc3Nlcy9zcm1fc2VydmVyLmphciwvaG9tZS9rb3Mva2FzaHlhL2FyY2hpdmUvY2xhc3Nlcy9y
cHNlcnZlcnMuamFyOi9ob21lL2tvcy9rYXNoeWEvYXJjaGl2ZS9jbGFzc2VzL3NybV9zZXJ2ZXIu
amFyLGciIC9ob21lL2tvcy9rYm94L3NyYy9pbnN0YWxsYXRpb24vZGlzdHJpYnV0aW9uL29zX3Nl
cnZpY2VzL29zX3NlcnZpY2VzLnNoCg==
#

136561 Changing Unable to modify the cluster management IP. As a result, any future dynamic configuration
cluster changes will not be applied. The following message is shown in the control logs:
management IP "SaveGlobalSystemConfigurationHelper: failed to copy RecoverPoint.xml efx file".
Workaround: The following signed script can be used to create the dir. Run this signed script on
each RPA:
MjUxMzNmMjFkOTQyMTRjYzAzZWUyMTNkMTYxOGZiMTUKdW5saW1pdGVkCm5vdF9yZXN0cmlj
dGVk
ClRoZSBpZCBvZiB0aGUgc2NyaXB0IGlzOjEzNjU2MQpDcmVhdGUgZm9sZGVyIC92YXIvd3d3L2Nv
bmZpZy9zZXJ2aWNlX2RlZgpZYWtpcgpta2RpciAvdmFyL3d3dy9jb25maWcvc2VydmljZV9kZWYK
Y2htb2QgNzU1IC92YXIvd3d3L2NvbmZpZy9zZXJ2aWNlX2RlZgo=
#

43547 Changing web When changing the web server certificate, the private key generated is in PKCS#8 format.
server certificate Importing keys in PKCS#8 format fails.
Workaround: Convert the private key to PKCS#1 format before importing it to RecoverPoint.

130980 Consistency RecoverPoint and RecoverPoint for VM consistency groups might experience a journal resource
group leak and eventual fatal errors, history loss and a full sweep.
Workaround: Disabling Snapshot Consolidation will reduce the probability of encountering this
issue.

43517 Consistency If a target vCenter does not have a vSwitch or a dvSwitch in a default VM network, a consistency
group disabled groups will remain disabled.
Workaround: Build a vSwitch on the remote ESXi hosts.

18 EMC RecoverPoint for Virtual Machines 4.3 Release Notes


Known problems and limitations

Table 9 Known problems found in RecoverPoint for Virtual Machines 4.3 and later (page 2 of 12)

Issue Number Product Feature Problem Summary

118490 Creating When creating a multiple VM consistency group, the consistency group may be in error state.
consistency Workaround: Contact EMC Customer Support.
group

125241 Deployer When using the Deployer to install or configure a cluster on RPA1, if RPA2 is shutdown or
unresponsive, installation or configuration will be paused by system for 30 minutes and then
fail.
Workaround: Re-run the installation from the beginning.

125615 Deployer When running the Cluster Modification wizard in the Deployer, all vRPA connections may restart.

125718 Deployer When deploying a RecoverPoint cluster on existing vRPAs, you may not be able to format or
configure repositories.
Workaround: In the vSphere web client, edit the vRPA setting and remove the RecoverPoint
device disk. This disk is typically called RPDevice.vmdk, is either 1MB or 10MB, and is usually
on SCSI 0:1.

125898 Deployer Every vRPA on one datastore may use an additional 1MB of space. There is no validation that
there is enough space in the datastore. If the datastore does not have enough space for all the
vRPAs, deployment will fail.
Workaround: Ensure that there is enough free space on the datastore that the vRPA is on (1MB
per vRPA on the datastore)

126427 Deployer You may not be able to log into the Deployer on RPA3-8.
Workaround: Login using RPA1 or RPA2 IPs or cluster management IPs.

126814 Deployer The home page of the RecoverPoint for VMs Deployer may occasionally become inaccessible.
Workaround: Wait 5-10 minutes and reload the home page. If problem persists, contact EMC
Customer Support.

127270 Deployer In the Deployer, installation may fail at 64% complete if the selected datastore for repository
provisioning is not accessible by all vRPAs.
Workaround: Click back and select a different datastore for the repository.

127317 Deployer When registering ESXis, you may receive the error “Could not find ip address of the ESXi’s
splitter” in the Deployer's Troubleshoot ESX Cluster dialog even though the configuration is
valid.
Workaround: Start the ESXi registration process from the beginning.

127381 Deployer During either the Installation wizard or the Modification wizard, under connectivity settings, you
will be allowed to enter IP addresses that are out-of-subnet range; you will not receive
validation errors. If you complete the wizard, installation or modification will fail.
Workaround: Ensure that you enter the correct IP addresses. Do not rely on validation.

128321 Deployer While installing RecoverPoint for VMS 4.3.1 using the Deployer, pre-validations fails after 30
minutes.
Workaround: Contact EMC Customer Support.

131293 Deployer Installation appears to be stuck at 50% even though the installation continues normally and
eventually completes successfully. If the installation completes successfully, ignore the error
message.

136301 Deployer In the Deployer GUI, there is no validation during the deployment process stopping a user from
selecting a vCenter on which the vRPA is not registered. As a result, the user will not be able to
complete the deployment process.
Workaround: Select the vCenter on which are the vRPA is registered.

126536 Deploying OVF When deploying an OVF template, if you enter incorrect information, such as the wrong IP
address, you the deployment will fail.
Workaround: Delete the VM and start the deployment again.

EMC RecoverPoint for Virtual Machines 4.3 Release Notes 19


Known problems and limitations

Table 9 Known problems found in RecoverPoint for Virtual Machines 4.3 and later (page 3 of 12)

Issue Number Product Feature Problem Summary

118415 Deployment When using Deployment Manager to perform a non-disruptive upgrade, you may be unable to
Manager attach RPAs to the cluster you will receive the message “Internal error”; or when rebooting RPAs,
you may be unable to reattach them to the cluster.
Workaround: Reboot the RPA. If this does not help, contact EMC Customer Support.

120203 Deployment When using the DM to upgrade multiple vRPAs, the upgrade will fail, and the vRPAs will enter
Manager reboot regulation.
Workaround: Reboot one vRPA, and run the upgrade again.

125855 Deployment If the connect clusters wizard is canceled or fails, the new cluster you are connecting stays in
Manager maintenance mode.
Workaround: Manually exit maintenance mode.

118280 Deployment RecoverPoint for Virtual Machines 4.3 Deployment REST API XML Schema Definition (xsd) does
120467 REST API not correspond exactly to the RecoverPoint for VMs object model. Consequently, REST clients
that automate serialization and deserialization will likely fail. Manually creating JSON bodies
using only the necessary parameters will likely succeed. If not, contact EMC Customer Support
for assistance.

42728 Distributed In rare cases, the Override Port Policies option in the distributed virtual switch cannot be used.
virtual switch

126489 ESX A change in the HW-UUID of one or more ESX hosts attached to a RecoverPoint cluster, or a
situation where more than one ESX host has the same HW-UUID (for example. the HW-UUID is
not unique in the RecoverPoint cluster), will stop the replication.
Workaround: The workaround requires you to remove the problematic ESX, stabilize the
RecoverPoint environment, and then add the ESX again after troubleshooting and fixing the
HW-UUID issue.
Perform the following steps:
1. Identify all bad ESXs reporting duplicate-UIDs (using a query via vCenter) or degenerate-UIDs
(using the Control logs).
2. Move all VMs and vRPAs from that ESX to other ESXs in the ESX-cluster (vMotion).
3. Remove all bad ESXs from their ESX-Cluster, or move them to a non-RP ESX-Cluster
(unregistered ESX-Cluster).
4. In case of Reboot-Regulation, attach the RPAs to the cluster.
5. Verify that the system is stabilizing:
a. Verify that the cluster has no remaining duplicate-UIDs (using a query via vCenter) or
degenerate-UIDs (using the Control logs).
b. Check that the consistency groups are out of error state and are initializing.
c. When the consistency groups are active again, perform an integrity check and validate
consistency. If inconsistency is detected, disable and enable the impacted consistency
groups. Note that this will cause a Full-Sweep.
6. Troubleshoot the bad ESX:
a. Check the SMBIOS dump for the current ESX-UID, if UID is degenerate (this workaround
doesn't support degenerate duplicate-UIDs based on duplicate-HW-UUID).
b. Reboot the ESX to retrieve the original UUID.
c. If it doesn't work after a couple of retries, as a root user on the ESX host, run grep uuid
/etc/vmware/esx.conf. Note the UUID returned, and collaborate with the host team in order
to change the HWUUID on the ESX host from 00000000-0000-0000-0000-000000000000 to
the UUID returned in the command.

Note that this workaround enables you to register this ESX host back to the RecoverPoint cluster,
but it does not prevent future HW-UUID changes on this ESX host.

20 EMC RecoverPoint for Virtual Machines 4.3 Release Notes


Known problems and limitations

Table 9 Known problems found in RecoverPoint for Virtual Machines 4.3 and later (page 4 of 12)

Issue Number Product Feature Problem Summary

127098 ESX In RecoverPoint for VMs 4.3.1 and later, when registering ESX clusters that use vCenter linked
mode, the ESX clusters of the remotely linked vCenter may not appear in the available ESX
clusters list of the Register ESX Cluster dialog box.
Workaround: Close the Register ESX Cluster dialog box and click Add.. again to display the ESX
clusters of the remote vCenter.

128950 ESX In RecoverPoint for VMs 4.3.1 and later, when using the RecoverPoint for VMs plugin in vCenter
web client 6.0 with Google Chrome browser, if the screen resolution is 1440x900 or less, the
Register ESX Cluster dialog box is too small and you may not be able to see every ESX available
for registration.
Workaround: Set your screen resolution higher or close the Recent Tasks in vCenter to gain more
real estate on your screen.

129329 ESX In RecoverPoint for VMs 4.3.1 and later, when deploying a vRPA cluster while NTP is disabled on
an ESX in your RecoverPoint for VMs system, an “Installation failed” message is wrongly
displayed to the user, even though the system has actually completed the deployment.
Workaround: The message is incorrect, and the vRPA cluster should be successfully deployed.
To suppress this message in future deployments, enable NTP on every ESX in your RecoverPoint
for VMs system before deploying your vRPA clusters.

134174 ESX The Troubleshoot ESX Cluster screen shows errors even though the configuration is valid.

129045 ESX registration In RecoverPoint for VMs 4.3, 4.3.0.1, and 4.3.1, when storage adapters do not exist on an ESX
that has been registered at a vRPA cluster in RecoverPoint, the RecoverPoint for VMs plugin and
the RecoverPoint for VMs Actions menu are not displayed in the vCenter Web client hosting the
ESX.
Workaround: Add a software iSCSI adapter to the ESX before registering it at a vRPA cluster or
upgrade to RecoverPoint for VMs version 4.3.1.1.

120762 ESXi After the splitter is paused by system, you may experience an error in the group transfer. This
may cause a full sweep.
Workaround: Manually rescan the HBAs.

42225 ESXi splitter After a full sweep, the VM's console may get stuck with a white blinking underscore in the upper
left corner. This is due to a BIOS corruption.
Workaround 1:
1. Load default BIOS settings.
2. Enter the BIOS and press F9, Enter, F10, Enter.
Workaround 2: Replace the .nvram file of the VM with the .nvram file from the production VM.

26393 Event filters Defining “info” level filtering for syslog notification only shows “info” event logs and does not
display higher level event logs (“errors” and “warnings”).
Workaround: Define filters for “warning” and “error” levels.

121308 FAPI Calling VM affinity (VMwareDiscoverer) related APIs using FAPI, may fail with error 'Illegal
vCenter server parameter'
Workaround: Kill tomcat or reboot the vRPA.

120142 GUI You cannot pause transfer of a group set.


Workaround: Pause transfer on each consistency group in the group set.

130682 GUI In the Deployment GUI, if you first fill the vCenter details on the Prerequisites, Connectivity
Settings and Environmental screens and then import JSON with a different registered vCenter,
the imported vCenter settings override the vCenter settings that you just configured.
Workaround: First import the JSON, and then enter the vCenter settings in the Deployment GUI.

131202 GUI After editing a vCenter server, there is no indication in the GUI if the changes have been applied.
Workaround: Use the CLI command get_storage to show the vCenter registration.

EMC RecoverPoint for Virtual Machines 4.3 Release Notes 21


Known problems and limitations

Table 9 Known problems found in RecoverPoint for Virtual Machines 4.3 and later (page 5 of 12)

Issue Number Product Feature Problem Summary

133442 GUI Changes to the array are not shown in the RecoverPoint GUI.
Workaround: Reboot the RPA.

128434 Image access In RecoverPoint for VMs version 4.3.1, RecoverPoint for VMs is unable to create a shadow VM for
(128921) a copy VM if there is a device configured on IDE0:0 of its corresponding production VM.

133180 Installation If an RPA is rebooted during an installation (using REST or the Deployer GUI) the installation
fails.
Workaround: Redeploy. If using the Deployer GUI, you can press the “Retry” button.

127203 iSCSI You may not be able to modify individual iSCSI IP addresses.
Workaround: Modify both iSCSI IP addresses.

134725 Journal Rarely, if the journal corrupts, replication fails, crashes, and leads to reboot regulation.
Workaround: Disable and enable the consistency group, accept full sweep initialization and
journal loss, and attach the RPAs back to the cluster.

135016 Journal If the journal reaches a level of 100% usage before the first journal consolidation attempt, this
consolidation may cause all journal consolidation attempts to fail with high probability.

135017 Journal If a journal consolidation request is registered but waiting to begin, it may take an indefinite
consolidation amount of time to begin, greatly increasing the chances that it will fail.

41977 Journal When selecting a datastore pool for journal registration, the user may select an ESXi local
registration datastore. Since the datastore is only exposed to one ESXi server, any vRPA that is not on the
selected ESXi will not be exposed to the journals provisioned on that datastore, and the journals
will be unavailable.
Workaround: Ensure that the datastore is accessible to all vRPAs.

125446 KVSS After running KVSS, the command vssadmin List Writers may show writers involved in the
previous KVSS command in Error state.
Workaround: N/A. Ignore the warning.

28413 LDAP When an LDAP user has a boxmgmt role, the LDAP user is not fully functional.

30367 LDAP When creating an LDAP type user, the new user cannot be limited to a specified consistency
group.

41051 LDAP test error Immediately after configuring LDAP authentication, the user runs the CLI command
test_ldap_connection, the test may return “Error: unable to connect to primary LDAP server.”
Workaround: Wait five minutes and run the test again.

119425 Licenses When using vCenter in linked mode, licenses are only displayed in the Administration >
Licensing screen of the RecoverPoint plug-in for vCenter Server when you are connected directly
to the vCenter Server to which the license is enforced.
Workaround: Connect directly to the vCenter Server to which the license is enforced to display
the license details or remove the license.

136884 Localization When the vCenter server has localization set to something other than English, error messages in
the RecoverPoint logs may appear as ??? instead of displaying the correct message.
Workaround: Errors should be properly logged in the vCenter server logs.

126098 Log collection In rare cases, you may not be able to collect logs.
Workaround: Run the regenerate_encryption_keys command in the CLI. (The vRPA cluster
should not be in maintenance mode before running the command.)

131864 Logging in Users in an LDAP group may not be able to log in to the classic RP GUI and RP plugin if the LDAP
server has high latency (greater than 30 seconds).

22 EMC RecoverPoint for Virtual Machines 4.3 Release Notes


Known problems and limitations

Table 9 Known problems found in RecoverPoint for Virtual Machines 4.3 and later (page 6 of 12)

Issue Number Product Feature Problem Summary

43716 Moving an ESXi When you move an existing ESXi with RecoverPoint-protected VMs to a new vCenter Server, and
host delete the ESXi from the old vCenter Server, an error in transfer is displayed for all VMs, and rep-
lication between the production and copy VMs stops.
Workaround: Unprotect and reprotect each VM, and re-configure your protection policies. Once
protected, the error in transfer is resolved, replication is enabled, all copy journals are lost, and
a full sweep commences to synchronize the copies with their production sources.

127174 NDU When upgrading a multi-site environment from RecoverPoint 4.3.0.1 to RecoverPoint 4.3.1,
upgrading only one vRPA cluster may result in a settings conflict. Upon completing the DM
wizard, you will receive the following error message: “Error: conflict in setting - please resolve”.
Workaround: Resolve the settings conflicts manually. You may have to exit maintenance mode.

127349 NDU The first attempt to upgrade from RecoverPoint 4.3 to 4.3.1 may fail.
Workaround: The upgrade will succeed on the second attempt

132419 NDU During the non-disruptive software installation upgrade (NDU) flow we ignore the user input for
modifications in the Deployment GUI. As a result, all signed scripts and tweak overrides will run
and be preserved on the new version (after the NDU).
Workaround: Adapt RPA tweaks, and run undo scripts before or after the NDU flow.

132426 NDU During non-disruptive software installation upgrade (NDU), if the ISO upgrade time exceeds 15
minutes, the retry (clicking Back and Next) might not work, and the NDU flow cannot finish suc-
cessfully.
Workaround: Contact EMC Customer Support.

44667 Protecting VMs When protecting a large number of VMs over several clusters, you may not be able to connect to
the ESXi server.
Workaround 1: Run the kill_tomcat command.
Workaround 2: Detach and re-attach the clusters or perform a virtual reboot.

129182 Protecting VMs In RecoverPoint for VMs 4.3 and later, when protecting VMs with a large number of VMDKs,
replication may not start.
Workaround: Contact EMC Customer Support or upgrade to 4.3.1.1.

131307 Protecting VMs In large scale environments, after you protect (replicate) a VM, or after a failover occurs, a
Consistency Group will be in a state of error, and VCenter will try unsuccessfully to delete the
shadow VM (displayed as a loop of commands).
Workaround: Power off the shadow VM.

131331 Protecting VMs In large scale environments, after you protect (replicate) a VM, or after a failover occurs, the
shadow VM will not contain any disks.
Workaround: Power off and then power on the shadow VM.

118294 Protection In rare cases, when protecting a large number of VMs over 4 vRPA clusters, you may momentarily
become disconnected from the vCenter server.

EMC RecoverPoint for Virtual Machines 4.3 Release Notes 23


Known problems and limitations

Table 9 Known problems found in RecoverPoint for Virtual Machines 4.3 and later (page 7 of 12)

Issue Number Product Feature Problem Summary

43033 PXE screen After installing a new RecoverPoint for VMs splitter and powering-up a VM, a Preboot Extended
Environment (PXE) boot screen may appear instead of the VM operating system. This is a known
VMware bug caused by a corrupted or altered NVRAM file.
Workaround:
1. Check the vCenter Server to verify that all associated disks are still present.
2. If they are present, power off the virtual machine.
3. Delete the NVRAM file.
The NVRAM file is recreated when the virtual desktop is powered on.
4. Reboot. The virtual machine should now boot into the operating system.

If, after performing these steps, the VM does not power-up, search the VMware Knowledge Base
for articles related to troubleshooting VM boot issues. If you cannot find a suitable document, or
if the issue persists, file a support request with VMware Support and note KB article 2001345 in
the problem description. For more information, see “Filing a Support Request in My VMware”
(KB article 2006985).

127276 RecoverPoint for When running the RecoverPoint for VMs plug-in on a version of Internet Explorer lower than IE11,
VMs plug-in the plug-in will not display correctly.
Workaround: Update to Internet Explorer 11 or run the plug-in in Firefox or Chrome
(recommended).

129253 RecoverPoint for Under specific circumstances the RecoverPoint for VMs plugin is not displayed in the vCenter.
VMs plugin As a result, the user is not able to use RecoverPoint using the RecoverPoint for VMs plugin.
Workaround: Contact EMC Customer Support.

137290 RecoverPoint for The RecoverPoint for VMs plugin cannot work if the vCenter has other plugins that use the same
VMs plugin HTTPS connection (for example, VMWare’s Hybridity).

120806 Recovery A group set may appear in the Recovery Activities pane of the RecoverPoint for VMs plug-ins
Activities even though none of consistency groups in the group set are in image access mode.
Workaround: In the classic GUI, in the relevant vRPA, navigate to Manage recovery activities. Run
the Disable image access command for the problematic group set.

42339 Removing VMDK If you accidentally remove a VMDK from a protected VM, or you intentionally remove a VMDK
using the CLI command remove_replication_set, the consistency group enters an error state,
and replication stops. You will receive the following warning:
“The VMDKs of VMs of production group <CG_name> are not identical to their copies <VM_name>.
VMDKs are missing from production. Add VMDKs with the same port type and ID and the same
size as the original (causes volume sweep); or unprotect and reprotect production VMs (causes
journal loss and full sweep).”
Workaround:
1. Unprotect the VMs in the consistency group.
2. Reprotect the VMs. This will re-create the consistency. This will cause a full-sweep and journal
loss.

120990 Replication During replication, when the production and non-production copy volumes are identical, when
transfer is interrupted you may experience an unending full-sweep.
Workaround: Contact EMC Customer Support.

134626 Replication Under rare conditions, replication crashes, and 20 minutes before the crash, the replication pro-
cess is deadlocked, and may be unresponsive to management actions, or unable to replicate.
Workaround: None. The problem resolves itself after the replication process restarts.

137676 Replication The vNIC adapter type is not replicated from the production site to the replica site. Therefore, the
replica VM does not match the production VM’s network configuration if the production configu-
ration changes.
Workaround: Manually set the replica VM’s network configuration.

24 EMC RecoverPoint for Virtual Machines 4.3 Release Notes


Known problems and limitations

Table 9 Known problems found in RecoverPoint for Virtual Machines 4.3 and later (page 8 of 12)

Issue Number Product Feature Problem Summary

120462 Resizing VMDKs You may not be able to resize a VMDK on a non-production copy to larger than 2 TB. You also
may not be able to create a VMDK larger that 2 TB.

118280 REST API While RecoverPoint for VMs supports a maximum number of specific objects in certain
properties (such as the number of RPAs). This information is not exposed in the API XSD, which
is used when generating the automatic client code.

130113 RPA In some cases you may not be able to collect logs from an RPA in a cluster.
Workaround: Reboot that RPA and try again.

126956 SMTP When trying to set the SMTP configurations (sender address), when you test connectivity you
configuration will receive the following error: 'FROM field is not active in SMTP configuration.'

43471 Syslog Syslog notifications are not sent to the specified target hosts.
notification Workaround: Contact EMC Customer Support.

35911 System When all of the following conditions are true, you may receive the following error as a false
positive in the GUI, “System Limitations exceeded”:
• Asynchronous links
• Remote links WAN over FC/IP
• Time-based RPO definitions
• No apparent WAN connectivity issues
• No burst in the application traffic
• No misconfiguration of the load on the RPA
• No highloads for an extended period time
• Measure-lag-to-kbox=true
• Without application-regulation
• System limitation warning remains for a significant amount of time without intermittently
disappearing/reappearing
Workaround: Ignore the warning. You may change the default RPO to data=500MB. You may
also pause and then resume transfer.

43203 System If you click the test a copy icon, and then fail over or recover production, only the test a copy
report is generated; the failover or recover production reports are not generated.
Workaround: Click the failover or recover production icon to first test the copy and then fail over
or recover production.

120747 System If you enter an incorrect IP when configuring an external host, the connectivity check may return:
connectivity OK.
Workaround: Refer to the Osiris process log to see if there is connectivity.

121017 System If, during a long resynchronization, a vRPA restarts, this may cause a full sweep of the
consistency group. After the full sweep, the system should recover without errors.

122425 System SAN view snapshots are not deleted once passing a certain file count and fills the /tmp
directory. Log collection may fail due to snapshot directory being too large.
Workaround: Contact EMC Customer Support.

123854 System If a consistency group is in image access for an extended period of time, the system may enter
permanent highload, and the consistency group will be in error state.
Workaround 1: Disable image access.
Workaround 2: Increase journal capacity.

124844 System If the control process crashes, it may take longer than expected for the vRPAs to reboot.

125981 System You may only be able to access statistics from the last few days of replication. This is particularly
relevant to scaled environments.
Workaround: Contact EMC Customer Support.

EMC RecoverPoint for Virtual Machines 4.3 Release Notes 25


Known problems and limitations

Table 9 Known problems found in RecoverPoint for Virtual Machines 4.3 and later (page 9 of 12)

Issue Number Product Feature Problem Summary

126257 System Replication may be paused by system for 20 minutes, after which, the control process will crash
and recover.

126390 System When protecting multiple VMs at the same time, or when dismissing multiple user prompts, the
system may crash and enter a short initialization.
Workaround: Once the short initialization is complete, the system will proceed without issues.

126465 System Due to network problems, it may take some time to add a new vRPA cluster. If you try adding
another cluster before the first cluster connection is completed, both clusters are not added.
Workaround: Wait for the connection of the first vRPA cluster to complete before adding the
second vRPA cluster. This may take a while if there are connection issues.

126974 System After creating and removing a consistency group, you may not be able to create a new
consistency group.
Workaround: In the CLI, run hijack_cluster, and enter the ID from the deleted cluster.

127063 System After unprotecting a VM, a delete file task will appear as failed.
Workaround: None, there is no impact on the user.

127384 System During high availability, if the shadow VM does not power on, replication will be paused by
system. If the replica VM does not power on, image access may not be enabled.
Workaround 1: Provide the vCenter the required resources to power on the shadow VM in high
availability
Workaround 2: Configure the vCenter to ignore high availability when powering on VMs.

129917 System You are unable to protect a VM with a higher hardware version than what is supported at the 
target vCenter if you use a replica VM that was auto-provisioned.
Workaround: Use a manually provisioned VM as the replica VM with the highest hardware 
version supported by the target vCenter.

131120 System If certification changes, or the credentials used to login to the vCenter changes, the vCenter is
locked and the GUI cannot connect to RecoverPoint clusters.
Workaround: To unlock the vCenter account, perform the following:
1. In the CLI, login as admin.
2. Run the command update_vcenter_server_registration.
3. When asked “Would you like to change the connection parameters and credentials? (y/n)” 
type n. This will allow you to update the vCenter password without validating it.

131629 System When using DNS, you cannot add a new ESX to an ESX cluster if the new ESX does not have DNS
configured on it.
Workaround: Configure DNS on the ESX or use the Management IP of the ESX.

131690 System The default domain value is set during deployment of RecoverPoint for VMs.
Workaround: The domain value may be changed through “Modify Settings” in boxmgmt 
(Setup -> Modify settings).

29504 Transfer paused If you change several consistency groups (CGs) from distributed to non-distributed, and vice
versa, at the same time, distributed CGs-non-distributed CGs transition will not complete, and
transfer will pause.
Workaround 1: Change CGs to be distributed or non-distributed one at a time.
Workaround 2: Kill all replication processes, one at a time.
Workaround 3: Reboot vRPAs one at a time.

120557 Upgrading from If the vRPAs are shutdown or rebooted after the auto upgrade and converting the repository vol-
RecoverPoint for ume from the previous version to the current version, you will not be able to continue the up-
VMs 4.2 to 4.3 grade.
Workaround: Continue the upgrade manually with boxmgmt.

26 EMC RecoverPoint for Virtual Machines 4.3 Release Notes


Known problems and limitations

Table 9 Known problems found in RecoverPoint for Virtual Machines 4.3 and later (page 10 of 12)

Issue Number Product Feature Problem Summary

121154 Upgrading to In rare cases, when upgrading from RecoverPoint for VMs 4.2 to RecoverPoint for VMs 4.3,
RecoverPoint for replication will be paused by system because one of the sites is down.
VMs 4.3 Workaround: Re-format the repository volume.

43098 Upgrading vRPA Upgrading the RecoverPoint for VMs splitter may cause a full sweep.
Workaround: Enter maintenance mode on the splitter:
1. Remove the splitter from the cluster.
2. Install the splitter.
3. Re-add the splitter to cluster.
4. Exit maintenance mode.

133674 Upgrading vRPA During the upgrade process, or after a disaster, creating a proxy to FAPI or communicating with
the command line may fail using the Deployer GUI or WDM.
Workaround: Reboot the entire RPA cluster. Note that the message: “Could not create proxy for
rpa RPA” may appear on a different RPA than the one that needs rebooting.

122468 User prompts If a user prompt is defined on a recovery operation, completing the recovery operation may be
prevented, and you will not be able to close the user prompt.

129063 User Script In RecoverPoint for VMs 4.3 and later, when enabling access to a copy image on VMs with a
Timeout specified startup sequence, user script and timeout, the VM may or may not power up, or the
power up sequence stops and a user prompt is displayed informing the user that the startup
sequence has stopped because the timeout value has been exceeded.
Workaround: None. The issue will resolve itself. In the future, before enabling access to a copy
image containing VMs with a specified startup sequence with a timeout value, either set a larger
timeout value or check your script to ensure it doesn't exceed the allotted timeout period.

43705 Using existing When you protect a VM and select an existing VM to be the copy, and you delete a VM snapshot,
VM as copy the shadow VM might not configure properly. This may also occur immediately after disabling
image access.
Workaround: Unprotect the VM and reprotect it.

127333 vCenter If a user manually copies a VM to a different vCenter Server and tries to power it on, vCenter
(127331) displays a message asking the user whether he copied or moved the copied VM. If the user
selects the move option, the copied VM can be added to a group and replication will start when
the group is created but when the user tries to perform any operations on this group the
message “Error: The same volume has been added at more than one RPA cluster.” is displayed
and all operations on the group are blocked.
Workarounds:
• Delete the group and the copied VM. Create a new group and use the Automatically create
the copy VM option in the Protect VM wizard to define the VM copy.
• Delete the group and the copied VM. Manually copy the VM to a different vCenter. Power the
copied VM on, and when prompted by vCenter select the “I copied it” option, create the
group and manually define the copy VM.

129243 vCenter If a user changes the credentials of a vCenter that has already been registered at a vRPA cluster,
(129383) RecoverPoint for VMs keeps trying to connect to the old vCenter credentials and the vCenter may
lock the user’s account as a result.
Workaround: Before changing the credentials of a vCenter registered at a vRPA cluster,
unregister the vCenter from the relevant vRPA cluster(s) in RecoverPoint for VMs, then, change
the vCenter credentials and re-register the vCenter in RecoverPoint for VMs.

EMC RecoverPoint for Virtual Machines 4.3 Release Notes 27


Known problems and limitations

Table 9 Known problems found in RecoverPoint for Virtual Machines 4.3 and later (page 11 of 12)

Issue Number Product Feature Problem Summary

129860 vCenter After re-installing or upgrading the vCenter, the vCenter UUID may change, causing the vRPAs in
that cluster go into reboot regulation (reboot over and over again until they detach from the
cluster).
Workaround: Perform the following steps:
1. Remove the license(s).
2. Using a web browser, navigate to
https://[vCenterServerIP]/mob/?moid=CustomFieldsManager 
replacing [vCenterServerIP] with the IP of the vCenter server.
3. Clear the "config.RecoverPoint_LICENSES" custom field.
4. Attach RPAs to the cluster.
5. Apply a new license with the new LOCKING_ID that matches the new vCenter UUID.

126879 vCenter After removing a vRPA cluster from the vCenter, and then manually removing its vCenter license,
licensing you may receive the following warning: WARNING: vCenter Sever <vc> is not licensed.
Workaround: Restart the management server.

43679 vCenter Server In rare cases, after a vCenter Server is restarted, vRPA clusters disappear from vSphere.
restart Workaround: Wait for a few minutes to see if the vRPA clusters appear again. If they don't appear
within five minutes, restart the vSphere Web Client service.

126213 vDSwitch If the vDSwitch is on the non-production copy, when you enable of disable image access, the
network adapter disconnects and cannot be reconnected.
Workaround:
1. Modify the vNIC configuration and connect to a different vDSwitch, ensuring the vNIC is
connected.
2. Modify the vNIC configuration again and set it back to the desired vDSwitch.
For more information, refer to VMware KB Article 2099117

118397 VM Start-up After performing image access, there is a 10 second delay before VM start-up prompts are
prompts displayed.

120702 VMDKs During failover or recover production to a point-in-time image with one or more VMDKs missing,
you may receive the following error:
“Error: Cannot add or remove volumes from this copy while the copy is enabled and is reporting
one or more bad volumes.”
Workaround: If you did not manually turn off any VMs between image access and failover or re-
cover production, wait a few minutes and retry the recovery action. If you did turn off the VMs,
turn them on and re-run the recovery action

125742 VMDKs Improve the warning message that appears when the independent/persistent properties of VM-
DKs in production and replica mismatch, when the replica VMDK is of type RDM.

32271 VMware When shutting down the vRPA using Installation Manager (boxmgmt), it does not shut down the
VM of the vRPA.
Workaround: Shut down the vRPA and the VM manually.

129215 VMware NSX In RecoverPoint for VMs version 4.3, if a user defines NSX security group rules on a VM and
(129218) manually selects it as the target VM while protecting a VM, fails over, or recovers production, the
copy VM will be disassociated from the security group.
Workaround: Re-configure the security group rules after VM protection, failover, or recover
production, or upgrade to 4.3.1.1.

43852 VMware When a user promotes a VMware snapshot of a copy VM, there is no full sweep to ensure consis-
snapshot tency between the production and the copy, causing inconsistency.
Workaround: Unprotect the VM and reprotect. Re-configure your protection policies.

128897 vRPA The auth.log file causes the /var directory to fill up, resulting in problems with login and
boxmgmt function.

28 EMC RecoverPoint for Virtual Machines 4.3 Release Notes


Known problems and limitations

Table 9 Known problems found in RecoverPoint for Virtual Machines 4.3 and later (page 12 of 12)

Issue Number Product Feature Problem Summary

41721 vRPA When the connection to a vRPA cluster is down, or the cluster itself is down, the GUI displays an
communication error “Fibre connection between all RPAs is unknown”
Workaround: Contact EMC Customer Support.

39765 vRPA crash When using LDAP (rather than LDAPS) over port 636 to authenticate users or test settings, the
vRPA crashes.
Workaround 1: For secure LDAP access, use LDAPS instead of LDAP (over port 636).
Workaround 2: For unsecure LDAP access, refrain from using the reserved LDAPS port.

42665 vRPA image When the journal is full or in error state, the copy vRPA becomes unresponsive and replication
access stops. After approximately 20 minutes, replication can be restarted. This causes a short init.
Other consistency groups running on the vRPA may be affected. There will also be some ac-
knowledged I/Os that will not be recorded in the journal until after the short init is completed.
Workaround: If the journal is full, add journal volumes. If the journal is in error state, contact
EMC Customer Support.

34636 vRPA reboot In a vRPA environment, when the iSCSI IPs of all vRPAs are changed at the same time, an unex-
plained reboot may occur.
Workaround 1: Detach all vRPAs before changing their iSCSI IPs.
Workaround 2: Change the IPs of each vRPA one at a time. For example, verify that vRPA 1 is ex-
posed to the repository before changing the IP of vRPA 2.

37923 vRPA reboots When a vRPA cluster configured to use LDAP and LDAP services are blocked by the firewall, the
control process may become stuck and lead vRPAs to reboot frequently.
Workaround: Restore LDAP service or contact EMC Customer Support.

120376 vRPAs In rare cases the control process may crash.

129108 VSAN A single journal volume on a VSAN datastore cannot exceed 254 GB in size.

127618 vSAN 6.0 When provisioning journals or repositories on vSAN 6.0, you may receive the following error:
"device not thick".
Workaround: Ignore the error.

118722 vSphere plug-in When adding, deleting or editing group sets the changes will not be reflected in the Recover-
Point for VMs plug-in.
Workaround: Refresh the plug-in.

120341 vSphere Web After upgrading to vCenter 6, in the Recent Tasks pane of the vSphere Web Client, the custom
Client RecoverPoint for VMs tasks do not display correctly. you will see the following error message:
“XXX <task name>.lable not found XXX”
Workaround: Delete the old plug-in files from the previous version's location, and reinstall the
plug-in.

EMC RecoverPoint for Virtual Machines 4.3 Release Notes 29


Documentation

Documentation
The following documents, available on the EMC Online Support, at
http://support.emc.com, provide additional information about RecoverPoint for Virtual
Machines:

Table 10 RecoverPoint for Virtual Machines 4.3 and 4.3.1 Core Documents

RecoverPoint for VMs 4.3 Core Docs RecoverPoint for VMs 4.3.1 Core Docs

RecoverPoint for VMs 4.3 Release Notes

RecoverPoint for VMs 4.3 Installation and RecoverPoint for VMs 4.3 .1 Installation and
Deployment Guide Deployment Guide

RecoverPoint for VMs 4.3 Administrator's Guide

RecoverPoint for VMs 4.3.1CLI Reference Guide

RecoverPoint for VMs 4.3 REST API RecoverPoint for VMs 4.3.1 REST API
Programming Guide Programming Guide

RecoverPoint for VMs 4.3 Deployment REST RecoverPoint for VMs 4.3.1 Deployment REST
API Programming Guide API Programming Guide

RecoverPoint for Virtual Machines 4.3 Security Configuration Guide

RecoverPoint for VMs 4.3 Quick Start RecoverPoint for VMs 4.3.1 Quick Start
Installation Poster Installation Poster

EMC RecoverPoint for Virtual Machines 4.3 Product Guide

RecoverPoint for VMs 4.3 Scale and Performance Guide

Software media, organization, and files


GPL-licensed code is included herewith. If you would like source code for any such
GPL-licensed code, please send a written request to: EMC Legal, 176 South Street,
Hopkinton, MA 01748, ATTN: Open Source Program Office. In your request, please indicate
the EMC Software Package or EMC Product which included an offer for GPL-licensed source
code.

Installation and Upgrade


Note: When installing or upgrading, always use the latest version of the Deployment
Manager

Instructions for installation and upgrade are presented in the EMC RecoverPoint for Virtual
Machines 4.3 Installation and Deployment Guide.
Upgrading from RecoverPoint for VMs 4.3, or later to 4.3.1, or later, is non-disruptive.
Replication is stopped temporarily to complete to complete the upgrade process.
For upgrades from RecoverPoint for VMs 4.2.x to RecoverPoint for VMs 4.3.x:

30 EMC RecoverPoint for Virtual Machines 4.3 Release Notes


Troubleshooting and getting help

◆ Upgrade to RecoverPoint for VMs 4.3.x is non-disruptive with regard to production.


◆ Upgrade to RecoverPoint for VMs 4.3.x will disrupt replication, and will require
subsequent initialization. Journal and system configurations are saved during the
upgrade.
◆ RecoverPoint for VMs 4.2.x licensed customers may open a SR to request that EMC
Customer Support perform the upgrade to RecoverPoint for VMs 4.3.x.

Troubleshooting and getting help


EMC support, product, and licensing information can be obtained as follows:
Product information — For documentation, release notes, software updates, or
information about EMC products, go to EMC Online Support at:
https://support.emc.com
Technical support — Go to EMC Online Support and click Service Center. You will see
several options for contacting EMC Technical Support. Note that to open a service request,
you must have a valid support agreement. Contact your EMC sales representative for
details about obtaining a valid support agreement or with questions about your account

Copyright © 2016 EMC Corporation. All rights reserved. Published in the USA.

Published December 2016

EMC believes the information in this publication is accurate as of its publication date. The information is subject to change without
notice.

The information in this publication is provided as is. EMC Corporation makes no representations or warranties of any kind with
respect to the information in this publication, and specifically disclaims implied warranties of merchantability or fitness for a
particular purpose. Use, copying, and distribution of any EMC software described in this publication requires an applicable software
license.

EMC2, EMC, the EMC logo, and EMC RecoverPoint are registered trademarks or trademarks of EMC Corporation in the United States
and other countries. All other trademarks used herein are the property of their respective owners.

For the most up-to-date regulatory document for your product line, go to EMC Online Support (https://support.emc.com).

EMC RecoverPoint for Virtual Machines 4.3 Release Notes 31


Troubleshooting and getting help

32 EMC RecoverPoint for Virtual Machines 4.3 Release Notes

You might also like