VADP: Possibility to cleanup created VMware snapshots

Affected products/clients by this RFE:
TSM B/A Client
TSM for VE
FlashCopy Manager (for VMware)

Our clients which work with the VADP are able to create and remove VMware-snapshots, but in case of a failed schedule for the allover environment, our clients to not cleanup the created snapshots.

Example 1:
A schedule which was created in the vCenter Plugin covers the backup of 100 VMs. Therefore we will create VMware-snapshots of these 100 VMs. In such an enterprise environment it is very common at a couple VMs cannot create its snapshot. If one VM out of 100 cannot create its VMware-snapshot the whole backup schedule will fail and TSM might not cleanup the created 99 snapshots of the other VMs.

Example 2:
If a backup schedule is ctrl-c'd, then TSM also won't cleanup the created VMware-snapshots.

All affected clients (BA; VE; FCM) who work with the VADP require a functionality to cleanup created VMware snapshots if a backup schedule fails or is being aborted. Of course: the only snapshots which must be removed should be snapshots which are created by TSM.

Background: VMware puts its snapshots into the same vmfs like the productive data. Usually, datastores are not much bigger than 800GB, so if there is a mass of VMware snapshots it is very likely that they fillup the vmfs. Unfortunately, all the VMs in this vmfs won't be able to work any more. The VMware admins loose the power to control the VMware-snapshots. This clearly is a scalability issue of VMware but TSM product should not make this behavior more critical than it already is.