Migration session Failed due to bad block on source device
Hello all,
I'm migrating data from cx4 to vnx using push incremental sancopy, all my sessions are completed successfully except for 2. in the status it shows that the error under the source tab that a bad block was encoutered on the source device
anyone knows how to overcome this or fix it to get going with my migration??
if that failure status is true, that's not a good thing ..support will probably want to run background verify on those LUNs and see what's going on. Have good backups of data on those LUNs ?
Here's is what is shows when i downloaded the SPA_Sancopy_info.txt using Triage...Copy Descriptor Name: 22
Copy Descriptor ID: 77 Owner: SPB Source LUN WWN: 60:06:01:60:2D:C0:24:00:56:6E:C2:94:BE:8A:DF:11 Number of Blocks to Copy: 4294967296 Number Of Destinations: 1 Destination LUN WWN: 60:06:01:60:18:A0:31:00:3C:1B:E6:5F:F2:36:E2:11 Session Status: The Session failed because either the source or all destinations have failed. Check the device that failed. For a device on a remote storage array, verify the FC zoning and/or iSCSI connection set and ensure that it is in the correct storage group. Initial Throttle: 6 Current Throttle: 8 Transfer Count: 867328 Percent Complete: 0 Completion Time: 12/11/12 23:10:29 Failure Status: A bad block was encountered on the source device. (0x712ac015)
Thanks Dynamox for your quick response, in fact i don't know where to find this message u just replied by.. on the other hand the message i have is in the Unisphere Gui, under migration, when i choose the failed session and click status, under the copy tab, this appears to be the status details: The Session failed because either the source or all destinations have failed. Check the device that failed and the path to it. For a device on a remote storage array, verify the zoning and ensure that it is in the correct storage group
then under the source tab, it says: a bad block was encountered on the source device.
Yeah i guess that's the case, i did some reading and as u said it appears that a background verify needs to be done.thanks for ur support dynamox. most appreciated.
Adding to what dynamox already mentioned, if you intend to use replicated data for restore/recovery. Please, also ensure the data integrity by means of host-based application-level data integrity mechanisms.
dynamox
11 Legend
•
20419 Posts
•
87439 Points
890
0
Posted December 13th, 2012 06:00
if that failure status is true, that's not a good thing ..support will probably want to run background verify on those LUNs and see what's going on. Have good backups of data on those LUNs ?