VMstore performance

View trends

IOPS

12,736 IOPS

1,269 - 19,073

 

Throughput

321 MBps

57 - 659

 

Latency

1.0 ms

7.5 ms

Flash hit ratio

100 %


Performance Reserves

49% free

auto allocated
free
51% used

Physical Space

9.7 TiB free

other
live data
snapshots
free
300 GB used (3%)
3.6 TIB Logical (12x space savings)

Protection

0 MB replicated a day

Performance reserves changers

SWDev_226.4% 26.4
MySQL VM0.6% -9.4
Test_411.2%  9.3
RHEV_VM0.8%  -5.9
OpenStack VM1 6.1%  -4.5
HyperV VM30.6%   -3.9
HyperV VM40.2% -2.8
XenServer VM11.5% 1.5
Eng Desktop_NewHire6.3% -0.9
Sales Desktop_NewHire0.6%  0.6

Space Changers

MySQL VM0.2 GB 0.2
OpenStack VM10.2 GB  0.2
Test_40.2 GB 0.2
RHEV_VM0.2 GB 0.2
SWDev_2 57.5 GB 5.0
HyperV VM30.2 GB 0.2
XenServer VM10.2 GB 0.2
HyperV VM457.5 GB 5.0
Eng Desktop_NewHire0.2 GB 0.6
Stats at 04:52 am | Refresh
Service Groups
VM Replication State IOPS MBps Latency ms Provisioned GiB Used GiB Change MB/day High frequency snapshots
SWDev_2 Replica up to date
7,807
84.6
1.4
53
24.9
1,555 disabled
MySQL VM Replica up to date
0
0.0
0.0
36
0.0
0 disabled
Test_4 Replica up to date
0
0.0
0.0
26
0 disabled
RHEV_VM not configured
0
0.0
0.0
29
0.3
0 disabled
OpenStack VM1 not configured
0
0.0
0.0
50
0.4
0 disabled
HyperV VM3 not configured
0
0.0
0.0
50
0 disabled
HyperV VM4 not configured
0
0.0
0.0
50
0 disabled
XenServer VM1 not configured
0
0.0
0.0
50
0 disabled
Eng Desktop_NewHire not configured
4
0.1
1.3
108
0 disabled
Sales Desktop_NewHire not configured
0
0.0
0.0
51
0 disabled
1 to 28 | 77 Total    | Show graphs
Virtual Disk content
Snapshots


Here's your trusty Tintri dashboard. Want to see how easy it is to setup replication for an individual VM?

Mission: Set-up hourly snapshots for data protection and then create a replication schedule.

Action: Let's get started. Click on the "Virtual Machines" tab in the top left corner of the screen.

Notice that you can see all the VMs and their replication states in the 1st and 2nd columns on the left. You can also see that the mission critical RHEV_VM does not have replication configured. Time to protect that VM!

Action: Click on RHEV_VM in the left column to setup its replication policy.

Good. Now select "Protect" to setup replication for RHEV_VM

Let's schedule those snapshots. Assuming this is a mission critical VM, we want to configure snapshots to be as frequent as possible.

Action: Select the "Hourly" option in the pop-up dialog box.

Now you can see Tintri allows snapshot intervals as short as 15 minutes.

Action: Select the 15 minute interval from the dropdown menu.

Now that you've selected a snapshot schedule, you also need to create a replication schedule for each of these snapshots to complete our disaster recovery (DR) setup.

Action: Click on "Protect by replicating snapshots" to setup disaster recovery (DR).

Now you need to assign a secondary Tintri VMStore as the destination for replicated snapshots. In the event of a disaster, we can clone a recent snapshot of this VM from the secondary VMStore.

Disaster recovery on Tintri is that easy.

Action: Select the dropdown next to "Replicate to" and select "Tintri_T5060_DR1".

Before we wrap up, notice just below that dropdown an option for high frequency snapshots. We won't need it for this VM, but it's good to know it's there for your most important VMs.

Action: We're all done here. Click on "Protect" in the bottom right corner of the dialog box.

Summary: Done! You’ve just replicated an individual VM – setting up 15 minute snapshot intervals and replication to a secondary Tintri VMstore. Just one more example of the simplicity of VM-aware storage.


Return to Tintri Hub