Loading...
Loading...
Import > Sessions x Import_FNM00104600114_migrate_xxx Error block Hovering over the red X, in the above error, shows more details: "The import session failed due to a non-recoverable error. Go to session properties dialog to check health details and resolution steps in GUI or use UEMCLI command import/session/element show -detail to check session health details and resolution steps." The UEMCLI output of the session details shows similar messaging: spa:~>uemcli /import/session show -detail 1: ID = import_65548 Name = Import_ABCD1234567890_101_20160915160406.767527+000 Session type = block Health state = Critical failure (25) Health details = "The import session failed due to a non-recoverable error. For Block import session non-recoverable error details, check session element's health details and resolution steps." State = Error ---output abridged---- The UEMCLI output of the session element details for the above Import Session ID: Example 1: spa:~>uemcli /import/session/element -importId import_65548 show -detail 1: Source system = RS_65560 Source resource = LUN 101 Target resource = sv_11 Health state = Major failure (20) Health details = "Element import session related Sancopy session ran into error: 0x712A8021: The destination device could not be found. This is probably due to incorrect zoning on the switch or the device is not in the correct storage group. (WWN). This can be due to FC Zoning or iSCSI Connection configuration between VNX and Unity arrays. Please follow documentation to configure connectivity between all SP pairs between VNX and Unity system. Once FC/iSCSI connection configuration is validated, please run 'Verify and Update' operation for Remote System connection to VNX to discover/update all configuration changes. Then issue resume operation on the import session to recover session from error state." Example 2: spb:~> uemcli /import/session/element -importId import_65600 show -detail 2: Source system = RS_65596 Source resource = block_1 Target resource = sv_79 Health state = Critical failure (25) Health details = "The import session failed due to a non-recoverable failure. Cancel the import session and determine the integrity of the data."
A "Non-recoverable error" in a Block Import Session can have various causes and may not always be permanent. Examining the Element details helps identify the root cause of the issue. Potential causes include: iSCSI connectivity issues, which can be resolved and allow the session to restart Issues on the Source VNX array, such as a missing LUN in a Consistency Group, which may require canceling the session Source LUN unavailability due to deletion or lack of updates on the Unity array, which also requires canceling the session Investigating the Element details can help determine the cause and take appropriate action to resolve or cancel the failed session.
As outlined above, there could be different issues that lead to a 'Non-recoverable error' for a Block Import Session. Unisphere (UI) may not provide enough detail to resolve the issue. It is advised to use the output of the UEMCLI session element in order to troubleshoot and resolve the issue. Import Session has failed with 'Non-recoverable error': 1. From UEMCLI, determine the Import Session ID: spb:~> uemcli /import/session/block show -detail 1: ID = import_65600 Name = Import_ABCD1234567890_migrate_20161027142745.428999+000 Session type = block Health state = Critical failure (25) 2. View the details of the Import Session Element for the Import Session ID: spb:~> uemcli /import/session/element -importId import_65600 show -detail 1: Source system = RS_65596 Source resource = block_1 Target resource = sv_79 Health state = Critical failure (25) Health details = "The import session failed due to a non-recoverable failure. Cancel the import session and determine the integrity of the data." 3. Follow the advice provided in the 'Health details' output to troubleshoot and resolve the Import Session issue. Note: To proceed, resume the Session under 'More actions' in the UI.
Click on a version to see all relevant bugs
Dell Integration
Learn more about where this data comes from
Bug Scrub Advisor
Streamline upgrades with automated vendor bug scrubs
BugZero Enterprise
Wish you caught this bug sooner? Get proactive today.