Renaming an LDEV fails due to unresolved variables

Ops Center Protector User Guide

Version
7.7.x
Audience
anonymous
Part Number
MK-99PRT002-08
ft:lastEdition
2023-10-26

Problem:

When trying to name or rename an LDEV using a variable (e.g. %ORIGIN_SERIAL%), the following error message is logged:

Unable to generate custom secondary logical device name because one or more variables could not be resolved.

If the referenced LDEV has no name then %XXXX_LDEV_NAME% variables will evaluate to an empty string and an error will be logged.

If upgrading from a version earlier than v6.6, the information required to resolve substitution variables may not be present in the metadata for exising LDEVs created prior to upgrade. For example the %ORIGIN_SERIAL% (serial number of the origin storage array for the LDEV) is not included in previous Protector versions.
  • For replications, this metadata is added when the replication is next evaluated, following an upgrade to Protector v6.6.
  • For snapshot, this metadata is never added since snapshots are not re-evaluated, and will eventually be retired.

Solution:

Review the naming string in the Secondary Logical Device Name field of the Replication/Snapshot Operation Properties or Rename Secondary LDEVs dialog, and for:
  • %XXXX_LDEV_NAME% variables - Ensure the existing LDEV has a name, then retry the naming operation.
  • All other variables - For replications, ensure they have been re-evaluated, then retry the naming operation. For snapshots, remove the offending substitution variable(s).