Unsolved
This post is more than 5 years old
10 Posts
0
1465
How to troubleshoot - > HIT/ME Alert: Create Smart Copy - Failed on host XXX
I frequently get this error:
The recent EqualLogic Snapshot operation scheduled to take place on SERVER02 at 11/7/2017 11:09:37 PM has failed. The following errors occurred during the operation:
[23:09:37] Component '8B0E1DEC-60D7-4E99-A21A-09C075AAD643 66841cd4-6ded-4f4b-8f17-fd23f8ddc3de:1458777c-5e20-421b-9976-6817a335bcfb:SERVER01 ' reported an error: '' (-2147212302). Check the application component to verify it is in a valid state for the operation.
How do I go about troubleshooting this? What do those long strings (eg, 8B0E1...) mean?
Anonymous
5 Practitioner
5 Practitioner
•
274.2K Posts
0
November 8th, 2017 15:00
Hello,
That's the error returned by Volume Shadow Service (VSS). That long string is the ID of the volume assigned by MS I believe.
Best suggestion I have is open a support case with Dell, so they can look at the logs. Are you running the latest EQL firmware and HIT kit software?
Regards,
Don
Anonymous
5 Practitioner
5 Practitioner
•
274.2K Posts
0
November 9th, 2017 07:00
Hello,
Well VSS is at the heart of this. ASM is requesting that VSS quiet the filesystem, allowing EQL to create a more consistent snapshot/replica. So array is rather passive in this process.
Both array and VSS operate on the volume level primarily. So I don't know of a way to drill down deeper to see what VM or VMs are causing the problem. Possibly Microsoft can?
The Requester (in this case ASM), asks VSS to flush cache, pause I/O, and create a snapshot. If you create a driver for VSS, known as a "Hardware Provider", it will create a hardware based snapshot instead of a hidden snapshot at the filesstem level. So VSS, via the H/W provider talks directly to the array and says "select volume XXX create snapshot/replica now." ASM doesn't send that command, VSS does. It returns the volume info back to the server in XML format.
Regards,
Don
SeeingEyeIT
10 Posts
0
November 9th, 2017 07:00
Thanks, Don.
Of course, the next logical question is how do I go from the ID of the volume to VM?
I have opened several support cases and each time was a one-off. There doesn't seem to be one answer except it's always a VSS problem.