AppSync: Application mapping fails for VMWare Virtual Disks on VMWare Virtual NVMe Controllers
Summary: AppSync does not Support VMWare NVMe Virtual Controllers.
Symptoms
Application mapping phase failed with java.lang.StringIndexOutOfBoundsException: String index out of range as seen in the AppSync Server log.
The CSV Event will show:
2019-02-17 19:48:29.688,Application mapping, MILE_000005,AppSyncServer,Application mapping phase for APPLICATION completed with errors
AppSync Server Log:
02-17-2019 19:48:27.845 DEBUG >>> Finding physicaldisks associated with HostFileSystemEntity: E:\
02-17-2019 19:48:27.845 ERROR WFLYEJB0034: EJB Invocation failed on component GetSourceStorageCommandBean for method public java.util.List ... throws com.emc.archway.errorMessages.UnsupportedOperationException: javax.ejb.EJBTransactionRolledbackException: String index out of range: -40
Caused by: java.lang.StringIndexOutOfBoundsException: String index out of range: -40
02-17-2019 19:48:28.485 ERROR Exception Occurred: StringIndexOutOfBoundsException, Message: String index out of range: -40
From the agent logs the WWN for the physical drives are coming as 72 characters as the expected value instead of 32 characters which triggers the out of range/bound exception.
AppSync Agent Logs:
2019-02-17 19:48:23.201 INFO [6580] [] [XXXXXXXXX] [f5f10af6-18eb-47f2-aa9c-ab57e7c82e91] -----------------
2019-02-17 19:48:23.201 INFO [6580] [] [XXXXXXXXX] [f5f10af6-18eb-47f2-aa9c-ab57e7c82e91] Device Type : (0x0)
2019-02-17 19:48:23.201 INFO [6580] [] [XXXXXXXXX] [f5f10af6-18eb-47f2-aa9c-ab57e7c82e91] Removable Media : No
2019-02-17 19:48:23.201 INFO [6580] [] [XXXXXXXXX] [f5f10af6-18eb-47f2-aa9c-ab57e7c82e91] Vendor ID : VMware
2019-02-17 19:48:23.201 INFO [6580] [] [XXXXXXXXX] [f5f10af6-18eb-47f2-aa9c-ab57e7c82e91] Product ID : Virtual disk
2019-02-17 19:48:23.201 INFO [6580] [] [XXXXXXXXX] [f5f10af6-18eb-47f2-aa9c-ab57e7c82e91] Product Revision: 2.0
2019-02-17 19:48:23.201 INFO [6580] [] [XXXXXXXXX] [f5f10af6-18eb-47f2-aa9c-ab57e7c82e91] Serial Number : 6000c292XXXXXXXXXXXXXXX
2019-02-17 19:48:23.201 INFO [6580] [] [XXXXXXXXX] [f5f10af6-18eb-47f2-aa9c-ab57e7c82e91] PHYSICALDRIVE :
.*PHYSICALDRIVEXX*
2019-02-17 19:48:23.201 INFO [6580] [] [XXXXXXXXX] [f5f10af6-18eb-47f2-aa9c-ab57e7c82e91] RMInquiry::InquireDrive - Inquire drive successfully completed for : \\.\PHYSICALDRIVEXX
2019-02-17 19:48:23.201 INFO [6580] [] [XXXXXXXXX] [f5f10af6-18eb-47f2-aa9c-ab57e7c82e91] Number of Page 83 idenfitiers: 1
2019-02-17 19:48:23.201 INFO [6580] [] [XXXXXXXXX] [f5f10af6-18eb-47f2-aa9c-ab57e7c82e91] Page 83 identifier index 0, id=8 size=36
2019-02-17 19:48:23.201 INFO [6580] [] [XXXXXXXXX] [f5f10af6-18eb-47f2-aa9c-ab57e7c82e91] Page 83 SCSI name string found
2019-02-17 19:48:23.201 INFO [6580] [] [XXXXXXXXX] [f5f10af6-18eb-47f2-aa9c-ab57e7c82e91] Device WWN: 566972747561XXXXXX69736B00000000303030305F303030305F303030305F3030XXXXXX
Cause
AppSync does not support VMWare NVMe Controllers.
Resolution
Use an AppSync supported VMWare Controller as outlined in the AppSync Support Matrix.
As of March 5 2019, the AppSync Support Matrix states:
Additional Information
This Article depicts this issue for a mapping failure having a SQL Server database being protected that resides on VMWare virtual disk defined to a VMWare NVMe Controller as seen in edit settings for the Source host.
A regular inq as seen in the output in emcreports from the Source host can be used to identify if an NVMe Controller is being used, like so:
(c) 2018 Copyright Dell Inc. All Rights Reserved.
For help type inq -h.
...................
------------------------------------------------------------------------------
DEVICE :VEND :PROD :REV :SER NUM :CAP(kb)
------------------------------------------------------------------------------
\\.\PHYSICALDRIVE0 :NVMe :Virtual disk :1.0 : : 3351248896
\\.\PHYSICALDRIVE1 :NVMe :Virtual disk :1.0 : : 1073741824
\\.\PHYSICALDRIVE2 :NVMe :Virtual disk :1.0 : : 16106127360
\\.\PHYSICALDRIVE3 :NVMe :Virtual disk :1.0 : : 3351248896