Home > Tintri VMstore™ > Knowledge Base > What is a Tintri Snapshot of type VAAI

What is a Tintri Snapshot of type VAAI

Applies To

 

Product(s)

Version(s)

All VMstore

All

Description


Virtual Machines are cloned on a Tintri VMstore by leveraging Snapshots. When cloning VMs through vSphere on ESXi hosts, with the VAAI plugin installed, the cloning process takes seconds and a VAAI snapshot gets created on the Tintri VMstore. This is by design.

 

Q & A

What is a snapshot of type VAAI?

The Tintri VMstore Admin guide defines VAAI as:

"VAAI. Created when the Tintri VAAI plug-in is used for cloning. These snapshots are automatically deleted when the clone is deleted. These snapshots cannot be used for cloning from the VMs in the VMstore GUI. "

How can VAAI Snapshots be deleted?

The same rules as other Tintri snapshots apply.

See the section on shared snapshot deletion in the Admin guide (copied below):

What is a shared snapshot?

A shared snapshot, also known as a base snapshot, is a snapshot from which Tintri space efficient clones are created. The number of clones created from a shared snapshot are tracked and reported as a clone ref count.

 

Can shared snapshots be deleted?

Yes, shared snapshots can be deleted if the following conditions are met:
• The shared snapshot backs only one clone (clone ref count = 1).
• The shared snapshot has no VM of its own (e.g. the VM is deleted and reclaimed) except for a synthetic VM.
• The shared snapshot has no younger or older snapshots.
• When there is a hierarchy of shared snapshots, the shared snapshot to be deleted is currently not being used for shared snapshot deletion.
• When there is a hierarchy of shared snapshots, the shared snapshot to be deleted is not using another shared snapshot which is not being used for shared snapshot deletion.
• If the shared snapshot was created from a Thin provisioned file, then it’s clone should also be Thin provisioned.
• If the shared snapshot is on the replication destination, then the replication relationship should be broken.


How do I make a shared snapshot deletable?

If the shared snapshot does not meet the previously mentioned criteria, consider the following:
• If the shared snapshot has more than one clone dependency, then delete the excess clones so that only one clone at most is dependent.
• If the VM corresponding to the shared snapshot is still present, then power down and delete the VM.
• If the shared snapshot has younger or older snapshots, then delete the sibling snapshots. 
• If there is a hierarchy of shared snapshots, wait for the underlying shared snapshot to complete deletion, if it is already marked for deletion.
• If there is a hierarchy of shared snapshots, wait for the clone snapshot that is dependent on this shared snapshot to complete deletion, if that is a shared snapshot and is already marked for deletion.
• If the shared snapshot was created from a Thin provisioned VM and its clone was marked Thick provisioned, then convert the clone to a Thin provisioned VM.
• If the shared snapshot belongs to a VM that is a replication destination, then break the replication relationship.

There are two key indicators in the Tintri UI to help manage this.

In the Virtual Machines window, click on the VM column and scroll down to select "Cloned From"

 

 

This will show the Snapshots VMs are cloned from.

Using the same method in the Snapshots window, you can add a field called "Clone Count"

 

Viewing 4 of 4 comments: view all
Article technically reviewed and approved after minor formatting changes
Posted 07:51, 22 Feb 2017
Approved - RD 27/02/2017
Posted 05:21, 27 Feb 2017
Nomenclature change
Posted 14:42, 9 May 2017
A link to the entire Admin guide as referenced above needs to be added.
Posted 14:44, 9 May 2017
Viewing 4 of 4 comments: view all
You must to post a comment.
Last modified
14:42, 9 May 2017

Tags

Classifications

This page has no classifications.