Recently ran across a misbehaving NetApp where it’s deduplication process would be triggered on a Saturday morning, and still be running come the Monday. It wouldn’t happen on every scheduled run, but when it did, it hurt storage performance significantly. We’re working on the usual tasks, there’s a lot of misaligned data on the volume. But in the meantime, I used the NetApp Data ONTAP PowerShell Module to create a little script that will shoot an email if it detects a running SIS process.
Configure it as a scheduled task on a system that has the DataONTAP powershell module installed. Here’s an example of the command line parameters:
With the release of Tintri OS 184.108.40.206, Tintri introduced their support for SCVMM and Hyper-V integration.
After upgrading to the new release, you’ll be able to add Hyper-V hosts into the Tintri UI settings screen – allowing the Tintri to grab details of running VMs. A SMI-S interface is also available after the upgrade, that you can use with SCVMM to create and manage SMB3 file shares, including setting quotas and applying a storage classification.
As with all new feature releases in the history of everything, there’s some problems. You might find – after configuring your SCVMM install and Hyper-V hosts according to the documentation (available on the support site) – that your hosts don’t have access to the share. You’ll be unable to create new VMs on the new share, or even remove the share through SCVMM.
Here’s how to avoid these problems and get those file shares working.
In the Tintri UI, open ‘Settings’, and open the ‘Management Access’ panel
Remove the entry for your SMI-S Run-As Account group (the one you created while following through the documentation)
Save the settings, and then re-open the ‘Settings’ window
Go back to the ‘Management Access’ panel, and re-add the SMI-S Run-As Account group with Super admin access
On a host that has access to your Tintri’s data IP, while logged in as a domain user that has Super admin privileges on the Tintri, open a command prompt or powershell window
Enter the following command, substituting for your share path and Hyper-V host group name:
Go ahead and try to create a new VM, it should work
Tintri are aware of this and there’s apparently an internal bug ticket for it – hopefully it’s resolved in the next code release.