12,690 - 52,875
57 - 659
|SQL VM_2||0.2 GB||0.2|
|SQL VM_1||0.2 GB||0.2|
|QA Server||0.2 GB||0.2|
|VM||IOPS||MBps||Latency ms||Provisioned GiB||Used GiB||Change MB/day||Replication State|
|SQL VM||982||64.4||118||0||not configured|
|1 to 28 | 77 Total | hide graph|
Explore Tintri Storage by completing a few
simple challenges. Compare your performance on these
challenges to peers and be entered to win.
You've got to provision 2TB for 100VMs. Do you
have enough capacity and performance? Click on
your capacity reserves, and then click on your
Which VM is your troublemaker?
Click the one that is really sopping up your performance reserves.
Pssst. Check the top right corner - that's your performance movers and shakers.
OK, so one click and you're working with individual VMs. On the top are ALL the individual VMs on your Tintri VMstore.
On the bottom, a visualization of the IOPS used by your selected VM. And woah, it's gone rogue. Time to tone it down.
To complete challenge #2, you just need to reduce the MAX IOPS from 42,000 to 22,000.
Yep, that's it All you have to do is drag the MAX throttle .
Challenge completed. This is my impressed face. You just set exact Quality of Service for an individual VM in .
It's simple and visual, and right over my shoulder you can see the immediate impact of your change.
So, you're pretty good at this VM-aware storage thing. But are you ready for...
You just noticed 'SQL VM' (second row in the table above) is struggling with high latency. But what’s the root cause?
Time to call your vendor? Nope. Just scroll over the Latency bar graph.
And you’ve done it. You just solved a latency issue in with zero calls to your storage provider’s support line.
You’re flying through this, so how about one more to get a real feel for Tintri?
Let's replicate a VM. First, hit "Hide Graphs" straight above my head (at the bottom of the table).
Good. Here are all of your VMs.
Now find the one named OracleDB and click it. Let’s see if you can replicate it in five clicks or less.
Right click on "OracleDB". I'm counting...
Select your schedule. Click "Daily". Now hit the radio button to replicate to your "Remote VMstore."
And... you just replicated a VM in five clicks. So, let’s review. In the you’ve been here you have (a) assessed headroom, (b) set QoS for a single VM, (c) exposed the root cause of a latency issue, and (d) replicated a VM.
All with no storage PhD.
While you’re at it, click here to issue the Tintri challenge to your followers via Twitter.