Tintri, Hyper-V, Veeam and the Reddit Thread

Update – Here are the links to the youtube videos showing Hyper-V backup using both Commvault and Veeam.

Commvault

Veeam

Original Post

Few weeks back there was a comment posted on Reddit by a Tintri customer regarding Tintri, Hyper-V and Veeam.

https://www.reddit.com/r/sysadmin/comments/41uje6/tintri_veeam_hyperv_scvmm_and_woe/

The comment went something like this –

For all the love they show each other about compatability, Hyper-V is not supported by Veeam on Tintri VM Stores. This is due to Tintri not having a hardware VSS provider. Lots of finger pointing to find the answer.

Also, Tintri’s SMB3 implementation has a few major gaps. Folder inheritence isn’t a thing right now (slated for bugfix in 4.2), which means if you add hosts to a cluster, you have to fix permissions on all existing subfolders.

On top of all that, SCVMM can create shares using SMI-S, but cannot delete them. You have to delete the share on the VM Store and then rescan the storage provider.

Edit: I forgot to mention their powershell modules have no consistency between them. One uses Verb-TTNoun, the other uses Verb-TintriNoun.

There were a lot of comments and sub-comments on the thread. Some were accurate and others were not. We tried to post a response to the thread but because of Reddit’s strict policies, none of the comments ever showed up. As a result, the thread has caused some confusion amongst some of our customers and prospects.

So I wanted to take this opportunity to respond to the thread, clarify a few things and update everyone on the current status.

  • Backing up using a backup application through Remote VSS

The Tintri VMstore’s Microsoft VSS integration did lack some functionality needed for remote VSS based backups for Hyper-V (for using backup apps such as Veeam, Commvault). It will be fully supported in an upcoming release that is in QA and will be available to customers soon.

  • Folder inheritance over SMB

Folder inheritance over SMB has been supported since Tintri OS 3.1.1 in the context of storage for virtual machines. There is a specific case where this wasn’t handled correctly and as the customer pointed out, is rectified in the same upcoming Tintri OS update as above.

  • Removing SMB share using SCVMM

There is an issue removing SMB shares via SCVMM (SMI-S) and that has also been fixed in the update mentioned above. As the customer pointed out, it is still possible to remove the SMB share through the VMstore UI.

  • Inconsistency in the naming of Powershell cmdlets

To clarify, there is no inconsistency here and this is as per design. The Verb-TintriNoun PowerShell cmdlets represent the Tintri Automation Toolkit (free download from our support site) and is used for customer automation around Tintri products.

The Verb-TTNoun cmdlets are a collection of cmdlets for validating certain Microsoft environmental factors, not specific to Tintri, that can impact Hyper-V functionality. The latter is primarily used by Tintri field and support technicians and some automation. The separate ‘TT’ namespace is to avoid confusion or overlap with other modules.

As always, Tintri is committed to its multi-hypervisor story including Hyper-V and we have several large customers who have successfully deployed Tintri with Hyper-V and are enjoying the benefits of Tintri’s VM-Aware functionality in their environments. We apologize for the inconvenience caused to our customers because of this. We have ensured that all of these issues are ironed out as part of the upcoming Tintri OS release.

PS: Although the customer didn’t mention anything about his company, we believe the customer contacted support and received an update directly from the support team

@storarch