Dell MD3200i Hardware VSS

[mickej67]

Anyone using Dell MD3200i with hardware provider SmVssProvider with succes on Hyper-V Windows 2008R2 cluster?

[foggy]

Michael, do you see any specific issues with your setup?

[mickej67]

With the latest version we are getting errors like this:

Code: Select all

Log Name:      Application
Source:        Application Error
Date:          2015-05-06 13:55:53
Event ID:      1000
Task Category: (100)
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      xxxxxxxxx.DATACENTER.local
Description:
Faulting application name: SMPROV~1.EXE, version: 11.20.206.4, time stamp: 0x547cb806
Faulting module name: SMPROV~1.EXE, version: 11.20.206.4, time stamp: 0x547cb806
Exception code: 0xc0000005
Fault offset: 0x00000000000387be
Faulting process id: 0xd1c
Faulting application start time: 0x01d087f30d673619
Faulting application path: C:\PROGRA~2\Dell\SMPROV~1\provider\SMPROV~1.EXE
Faulting module path: C:\PROGRA~2\Dell\SMPROV~1\provider\SMPROV~1.EXE
Report Id: d87f0cc3-f3e6-11e4-81d6-001b21988140
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="Application Error" />
    <EventID Qualifiers="0">1000</EventID>
    <Level>2</Level>
    <Task>100</Task>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2015-05-06T11:55:53.000000000Z" />
    <EventRecordID>260454</EventRecordID>
    <Channel>Application</Channel>
    <Computer>xxxxxxxxx.DATACENTER.local</Computer>
    <Security />
  </System>
  <EventData>
    <Data>SMPROV~1.EXE</Data>
    <Data>11.20.206.4</Data>
    <Data>547cb806</Data>
    <Data>SMPROV~1.EXE</Data>
    <Data>11.20.206.4</Data>
    <Data>547cb806</Data>
    <Data>c0000005</Data>
    <Data>00000000000387be</Data>
    <Data>d1c</Data>
    <Data>01d087f30d673619</Data>
    <Data>C:\PROGRA~2\Dell\SMPROV~1\provider\SMPROV~1.EXE</Data>
    <Data>C:\PROGRA~2\Dell\SMPROV~1\provider\SMPROV~1.EXE</Data>
    <Data>d87f0cc3-f3e6-11e4-81d6-001b21988140</Data>
  </EventData>
</Event>

Andra felet:

Log Name:      Application
Source:        VSS
Date:          2015-05-06 13:55:53
Event ID:      12293
Task Category: None
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      xxxxxxxxx.DATACENTER.local
Description:
Volume Shadow Copy Service error: Error calling a routine on a Shadow Copy Provider {24e4e8a3-69cb-4370-8b7b-c5276cd49765}. Routine details LocateLuns returned 0x80010105 [hr = 0x80010105, The server threw an exception.
]. 

Operation:
   Exposing Disks
   Locating shadow-copy LUNs
   PostSnapshot Event
   Executing Asynchronous Operation

Context:
   Execution Context: Provider
   Provider Name: SmVssProvider
   Provider Version: 11.20.0004
   Provider ID: {24e4e8a3-69cb-4370-8b7b-c5276cd49765}
   Current State: DoSnapshotSet
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="VSS" />
    <EventID Qualifiers="0">12293</EventID>
    <Level>2</Level>
    <Task>0</Task>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2015-05-06T11:55:53.000000000Z" />
    <EventRecordID>260455</EventRecordID>
    <Channel>Application</Channel>
    <Computer>xxxxxxxxx.DATACENTER.local</Computer>
    <Security />
  </System>
  <EventData>
    <Data>{24e4e8a3-69cb-4370-8b7b-c5276cd49765}</Data>
    <Data>LocateLuns returned 0x80010105</Data>
    <Data>0x80010105, The server threw an exception.
</Data>
    <Data>

Operation:
   Exposing Disks
   Locating shadow-copy LUNs
   PostSnapshot Event
   Executing Asynchronous Operation

Context:
   Execution Context: Provider
   Provider Name: SmVssProvider
   Provider Version: 11.20.0004
   Provider ID: {24e4e8a3-69cb-4370-8b7b-c5276cd49765}
   Current State: DoSnapshotSet</Data>
    <Binary>2D20436F64653A20434F5248494D504330303030303335342D2043616C6C3A20434F5248494D504330303030303332312D205049443A202030303030323435362D205449443A202030303030343138302D20434D443A2020433A5C57696E646F77735C73797374656D33325C76737376632E6578652020202D20557365723A204E616D653A204E5420415554484F524954595C53595354454D2C205349443A532D312D352D313820</Binary>
  </EventData>
</Event>

[foggy]

I'd first contact Dell with this, since their application produces the error.

[mickej67]

Done that and got answer after a lot of tests that the provider will not be developed anymore!!??

[foggy]

Did they confirm any issues with their software?

[mickej67]

This is the final reply from Dell:

It is important to know that hardware and controller firmware versions (and licensing) dictate how many snapshots can be created on a given volume, on a PitGroup, and on an array. Attempting to exceed these limits will cause an error.

Resetting Diskshadow between commands is a good idea.

Resetting the service in between snapshot create/delete’s causes VSS to run more successfully. In addition we put a pause in between stopping and starting the service, and between the start and the command to create a snapshot.

The following Powershell command will stop the VSS provider:
Stop-Service ‘SMprovider’ –f

The following Powershell command will start the VSS provider:
Start-Service ‘SMprovider’

And the following Powershell command will pause a script for 5 seconds:
Start-Sleep –s 5

Powershell commands can be executed from within a Diskshadow script by using the exec command:
exec c:\windows\system32\windowspowershell\v1.0\powershell.exe Start-Sleep -s 5

Diskshadow scripts can be run from a file like this:
diskshadow -s .\create_16_on_M.txt

The content of our test scripts (such as create_16_on_M.txt above) look very similar to this:
#Create snapshot: 1
exec c:\windows\system32\windowspowershell\v1.0\powershell.exe Stop-Service 'SMprovider' -f
exec c:\windows\system32\windowspowershell\v1.0\powershell.exe Start-Sleep -s 5
exec c:\windows\system32\windowspowershell\v1.0\powershell.exe Start-Service 'SMprovider'
exec c:\windows\system32\windowspowershell\v1.0\powershell.exe Start-Sleep -s 5
Reset
Set Option differential
Set Context persistent
add volume M: provider {24e4e8a3-69cb-4370-8b7b-c5276cd49765}
create
list shadows all
#
#Create snapshot: 2
exec c:\windows\system32\windowspowershell\v1.0\powershell.exe Stop-Service 'SMprovider' -f
exec c:\windows\system32\windowspowershell\v1.0\powershell.exe Start-Sleep -s 5
exec c:\windows\system32\windowspowershell\v1.0\powershell.exe Start-Service 'SMprovider'
exec c:\windows\system32\windowspowershell\v1.0\powershell.exe Start-Sleep -s 5
Reset
Set Option differential
Set Context persistent
add volume M: provider {24e4e8a3-69cb-4370-8b7b-c5276cd49765}
create
list shadows all

In most cases, VSS will run successfully many times without fail. Typically, the failures occur during the first attempt at creating a snapshot on a volume for the first time since a reboot. Often, once a successful snapshot has been created, a script to create many snapshots will continue through the entire script.

When a failure occurs, it is important to delete all relevant PitViews, Pits, and PitGroups on the given volume. Use SANtricity to verify there are no PitGroups, Pits, or PitViews on the volume, and then resume the creation process.

As a last resort, If failures continue, reboot the array.

MD Development has informed that E-Series VSS hardware provider’s final release was with 08.20 firmware and no more releases will be provided. Also request for bug fixes on the MDSM 11.20 release will no longer be accepted.

[foggy]

So looks like they've suggested the workaround. Do you find it applicable to your setup?

[mickej67]

Cant se how that could help when using Veeam to backup the VM:s? Reseting the service SMprovider before a backup job does not help at all.

[foggy]

Then I'm afraid you're left with on-host backups, unless upgrading the Hyper-V is an option (chances are the issue will not show up on a newer OS). You can also contact Veeam technical support, probably they could give some advise after reviewing your setup more closely.

[mickej67]

The strange thing is that it has worked with previous versions (Some buggy though!) One would think that there should be better functionality in newer versions. Is there really no one in this forum who uses the Dell MD32xxi storage?

[foggy]

Quick forum search shows a few threads where users reported different issues with this storage. If it has worked before, consider downgrading to the previous version, if acceptable.

[mickej67]

OK uninstalled SmVssProvider 11.20.206.4 installed SmVssProvider 11.10.206.1 and now hardware vss snapshots is working again??