AppSync: Using RDF Metro Migration with "Migration Spoofing" Enabled May Not Create AppSync Copies on the Correct Array

Summary: This article explains an issue where AppSync creates copies on the source array instead of the migrated array during RDF Metro migration with migration spoofing enabled.

This article applies to This article does not apply to This article is not tied to any specific product. Not all product versions are identified in this article.
Check out other resources

Symptoms

RDF/Metro array migration has migrated the data, however the WWN spoofing is still in place.
RDF/Metro Migration is a tool used to migrate data from one array to a new array.

AppSync tries to make a copy on the old VMAX array, using the LUN number from the new VMAX array.

 

Cause

The new VMAX array's serial number is not updated in the AppSync repository when the information about the source LUN is requested from SMI-S.

"inq.windowsamd64_exe -wwn" on the Source host is used to acquire the wwn of the source LUN.

In this example, we see the WWN:

D:\EMC Software>inq.windowsamd64_exe -wwn
Inquiry utility, Version V8.4-2352 (Rev 0.3) built with SYMAPI Version V8.4.0.3 (Edit Level 2352)
Copyright (c) [1997-2017] EMC Corporation. All Rights Reserved.
For help type inq -h.
------------------------------------------------------------------------------
DEVICE              :VEND    :PROD            :WWN
-------------------------------------------------------------------------------
 \\.\PHYSICALDRIVE17 :EMC     :SYMMETRIX       :60000970000196700xxx533030123456
Note: An inq with no parameters still shows the LUN device ID as being on the "migrated from" VMAX array.

SMIS-S is then queried to get the proper array using the WWN above.

To manually query SMI-S, the following can be used:

  1. Run TestSmiProvider on the SMIS-S and select the "ei" option
  2. Enter "CIM_StorageVolume" when prompted for the Class. This is case-sensitive.
  3. Press enter taking all the defaults for the other prompts.

This may run for a few hours. The output is in the TestSmiProvider.log file in the folder or directory where TestSMIProvider was run from. When the output is reviewed, you find one lengthy entry with the WWN acquired from "inq.windowsamd64_exe -wwn."

With a lot of the lengthy entry removed for readability, it lists as:

Instance 5494:
ObjectPath : Symm_StorageVolume.CreationClassName="Symm_StorageVolume",DeviceID="004FE",SystemCreationClassName="Symm_StorageSystem",SystemName="SYMMETRIX-+-000164200abc"

<PROPERTY NAME="SystemName"  CLASSORIGIN="CIM_LogicalDevice" PROPAGATED="true" TYPE="string">
<VALUE>SYMMETRIX-+-000164200abc</VALUE>

<PROPERTY NAME="EMCWWN"  CLASSORIGIN="EMC_StorageVolume" PROPAGATED="true" TYPE="string">
<VALUE>60000970000196700xxx533030123456</VALUE>

The xxx in the WWN may resemble the old VMAX array, however the Serial Number "000164200abc" is the new VMAX array.

The cause is: AppSync is not updating the AppSync database with this serial number, resulting in AppSync attempting to make the copy on the "migrated from" array.

 

Resolution

A hotfix exists for AppSync 3.0.2. Contact Dell Customer Support to request this hotfix. Quote this knowledge base article ID when opening a new service request.

 

Affected Products

AppSync

Products

AppSync
Article Properties
Article Number: 000059203
Article Type: Solution
Last Modified: 02 يوليو 2026
Version:  6
Find answers to your questions from other Dell users
Support Services
Check if your device is covered by Support Services.