Info
Document Version
Release Date
Details
2
22 November 2017
Updated the Resolution section with the software version that contains the fix
1
14 August 2017
Original Document Release
An issue has been identified with HPE Recovery Manager Central Software (RMC) where an HPE 3PAR StoreServ snapshot to parent volume association is reported incorrectly after a volume is migrated to Thinly Deduped Virtual Volume version 3 (TDVV3) format with the
–keepvv
option.
When the
-keepvv
option is used with migration, HPE 3PAR StoreServ will retain the snapshots but associate them with a newly created volume that are of old formats (TDVV2 or 1). HPE RMC will not recognize this change and will continue to show the snapshot as associated with the original volume (now TDVV3). In addition, when a snapshot restore (promote) is performed through HPE RMC:
The snapshots will overwrite the new volumes (TDVV 2 or 1) against a user’s intent that the restore should be done using the original volume (TDVV3).
The HPE RMC GUI will incorrectly report that the restore operation has been performed on the original volume, while the restore has been done on the newly created one.
Scope
This issue affects HPE Recovery Manager Central Software version 4.0.0. Snapshots created after the migration are not impacted. Express Protect backups are not impacted.
This issue is only seen with HPE 3PAR OS version 3.3.1, as TDVV3 is introduced in this OS version.
Resolution
This issue has been addressed in the HPE Recovery Manager Central 4.1.0 software release.
RECEIVE PROACTIVE UPDATES
: Receive support alerts (such as Customer Advisories), as well as updates on drivers, software, firmware, and customer replaceable components, proactively in your e-mail through HPE Subscriber's Choice. Sign up for Subscriber's Choice at the following URL:
Proactive Updates Subscription Form